Pathros Local
Read-only access-path scanning for GitHub Actions, CI/CD, and cloud IAM risk.
uvx --from pathros-local pathros scan .
Pathros maps hidden access paths and shows the evidence.
Default behavior:
- no writes
- no cloud API calls
- no telemetry
- no upload
- secret-like values redacted
Run Pathros locally. No cloud account required. No network calls by default. No writes. Evidence-rich output in one command.
Quick demo
uvx --from pathros-local pathros scan examples/phase-3/vulnerable/v01-pr-target-checkout-aws-role
Persistent install
pipx install pathros-local
pathros doctor
pathros scan .
Verify your install
pathros doctor
pathros version
pathros --version
pathros doctor reports the installed version, distribution name, install mode, Python version, safety defaults, reporter availability, and the next command to run.
Output formats
pathros scan . --format console
pathros scan . --format json
pathros scan . --format markdown
pathros scan . --format sarif
Markdown is the human report. JSON and SARIF are machine-readable reports for CI and review workflows. Pathros Local generates SARIF; it does not upload SARIF or scan results by default.
What Pathros Local currently detects
- GitHub Actions workflows that expose cloud deployment paths
pull_request_targetrisk patterns- AWS role assumption from CI/CD
- broad AWS trust-policy and permission patterns
- long-lived cloud credential references
Findings include evidence hops back to local files, rules, and source locations. A finding without evidence is not emitted.
What Pathros Local does not do yet
- no live AWS scan by default
- no Okta / Entra connector in the local package
- no Snowflake connector in the local package
- no automatic remediation
- no hosted upload unless explicitly added later
Local development
git clone https://github.com/pathros/pathros-python.git
cd pathros-python
uv sync --all-extras --dev
uv run pathros doctor
uv run pathros scan examples/phase-3/vulnerable/v01-pr-target-checkout-aws-role
Configuration
Create local defaults explicitly:
uv run pathros init
pathros init writes pathros.toml and .pathrosignore. pathros scan does not create config files.
Use pathros.toml for report defaults, scan scope, safety posture, enabled rules, and CI fail behavior. CLI flags override config values.
Ignore rules
Pathros automatically applies built-in ignore rules for generated, dependency, cache, and local secret files. It reads .pathrosignore from the scan root when present. .env is ignored by default; .env.example is allowed.
Safety posture
Pathros Local reads local GitHub Actions workflows, Terraform IAM configuration, and supported policy/config files. It does not read .env values by default. It writes nothing during scan unless --output names an explicit report file. It does not call GitHub, AWS, Okta, Entra, Snowflake, Terraform, or any hosted Pathros service by default.
CI fail thresholds
pathros scan . --fail-on high
Exit codes are stable: 0 means the scan completed and no finding met the threshold, 1 means at least one finding met the threshold, 2 means invalid user input, and 3 means an internal error.
Release verification
Release artifacts include a wheel, source distribution, checksums.txt, and GitHub build provenance attestations. See docs/release-verification.md.
More docs
Metadata
Release files for pathros-local 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pathros_local-0.4.0.tar.gz | 66.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pathros_local-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 133.3 kB
Release files / pathros_local-0.4.0.tar.gz
| Download URL | pathros_local-0.4.0.tar.gz |
|---|---|
| Size | 66.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e321f61029c96f01086fe61f2b5a87bb932fa424c642c27659d5fdfdc61524ba
|
|
BLAKE2b-256 checksum How to use checksums |
e55ddbf11d7248186f4a048f72ff1c3a23c0d968eba09044e4f7fe72ebb9a89f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 3, 2026.
Transparency logRelease files / pathros_local-0.4.0-py3-none-any.whl
| Download URL | pathros_local-0.4.0-py3-none-any.whl |
|---|---|
| Size | 66.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6fe2411af29df78943fd85837ac7d17d69d497b76cfb150cb6fd7a334b26d645
|
|
BLAKE2b-256 checksum How to use checksums |
66e77327640a9c2d265b562bcb8453f3e65f977e24faa0bf177cb8137f0ac718
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 3, 2026.
Transparency logSecurity for pathros-local 0.4.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pathros_local-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 3, 2026.
Transparency logA 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.