Pysa is a security-focused static analysis tool for Python that tracks data flows to find security and privacy issues — for example, user-controlled input reaching a dangerous sink such as remote code execution or SQL injection. Pysa can analyze codebases with millions of lines of code. Refer to our documentation to get started.
Pysa relies on type information from Pyrefly, Meta's performant Python type checker.
Pysa is also available on the GitHub Marketplace as a GitHub Action.
Installation
Pysa requires Python 3.9 or later. Install it with pip:
$ pip install pyre-check
Pysa is currently distributed as part of the pyre-check package, since it was historically bundled with Pyre, Meta's (deprecated) type checker. In the future, Pysa will ship as its own PyPI package.
Running Pysa
Pysa relies on type information from Pyrefly. Before running Pysa, make sure Pyrefly can successfully check your code:
$ pyrefly check
Once Pyrefly runs cleanly, run Pysa from your project directory to find security and privacy issues:
$ pyre analyze
Pysa uses models to identify sources of taint (where untrusted data enters) and sinks (dangerous operations). For details on configuring Pysa, writing models, and interpreting results, see the Pysa documentation.
Join the Pysa community
See CONTRIBUTING.md for how to help out.
License
Pysa is licensed under the MIT license.
16 maintainers
Metadata
16 maintainers
Release files for pyre-check 0.10.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyre_check-0.10.0-py3-none-manylinux1_x86_64.whl | Python 3 | none | Linux glibc 2.5+ x86-64 | Details for pyre_check-0.10.0-py3-none-manylinux1_x86_64.whl |
| pyre_check-0.10.0-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for pyre_check-0.10.0-py3-none-macosx_11_0_arm64.whl |
Total release size: 70.7 MB
Release files / pyre_check-0.10.0-py3-none-manylinux1_x86_64.whl
| Download URL | pyre_check-0.10.0-py3-none-manylinux1_x86_64.whl |
|---|---|
| Size | 46.6 MB |
| Tags | Linux glibc 2.5+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
715d1c4ec3ab5823bb6c9168a4954cb419d995d637e3e9617d9af1ff49be18b6
|
|
BLAKE2b-256 checksum How to use checksums |
243bbea383248304b63dac47759378e729ba51a4a1f7d5ed216503753bbf034c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.12.0 requests/2.32.3+fb3 setuptools/70.0.0 requests-toolbelt/0.9.1 tqdm/4.67.3 CPython/3.12.13+meta
|
Release files / pyre_check-0.10.0-py3-none-macosx_11_0_arm64.whl
| Download URL | pyre_check-0.10.0-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 24.1 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
e458fa2926f462971016a421a22d0ab7658222cfc5c455d39df9ddfd85f242e1
|
|
BLAKE2b-256 checksum How to use checksums |
a75b7921b13e19ff33efee2853536d4dfdbb6d95ecb806e27edc7d28e5bb7570
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.12.0 requests/2.32.3+fb3 setuptools/70.0.0 requests-toolbelt/0.9.1 tqdm/4.67.3 CPython/3.12.13+meta
|
Security for pyre-check 0.10.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
