actions-marketplace-validations/Pysa Action
Analyze data flows and detect security and privacy issues in Python code
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| repo-directory | Path to the python source code you want to analyze. If you want to analyze the root of your repo, use './' | yes | — |
| requirements-path | Path to requirements file, relative to `repo-directory`, to look for dependencies. Default will look for requirements.txt in the root of repo-directory | no | requirements.txt |
| use-nightly | Use nightly (unstable) version of Pysa | no | false |
| pysa-version | Version of pyre-check package to be used | no | latest |
| infer-types | Runs pyre infer in-place to add type annotations. Note that this will change your source code during analysis | no | false |
| sapp-version | Version of fb-sapp package to be used | no | latest |
| sapp-filters-directory | Path to your custom SAPP filters | no | — |
| include-default-sapp-filters | Use SAPP filters packaged with Pysa | no | true |
| use-poetry | Use poetry to install dependencies | no | false |
Outputs
no outputs