Problem or use case
A security tool asking users to trust it must be verifiable. agentsec depends on broad version ranges (detect-secrets>=1.4,<2, pyyaml>=6.0,<7). A compromised dependency could exfiltrate the secrets agentsec scans. No pinned lockfile, no SLSA provenance, no Sigstore signatures on PyPI releases.
Proposed solution
- Ship a pinned lockfile with hashes for all dependencies
- Add SLSA Level 2+ provenance to PyPI releases via GitHub Actions
- Add Sigstore signatures on release artifacts
- Support
pip install --require-hashes compatible install path
- Add dependency hash verification in CI
Area
Build / supply chain
Problem or use case
A security tool asking users to trust it must be verifiable. agentsec depends on broad version ranges (detect-secrets>=1.4,<2, pyyaml>=6.0,<7). A compromised dependency could exfiltrate the secrets agentsec scans. No pinned lockfile, no SLSA provenance, no Sigstore signatures on PyPI releases.
Proposed solution
pip install --require-hashescompatible install pathArea
Build / supply chain