How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed today
Rank Trend
2026-05-292026-06-04
Activity & Reach
Stars
185
Forks
30
Last Push
2026-06-04
today
Commits (4 wk)
235
Downloads (7d)
229
pypi
HN mentions (30d)
—
Open Issues
6
Rank Change
▼2
was #31
Analysis
HVTrust Dimensions
78.1 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
17.4 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
14.1 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
8.6 / 20
Activity Inputs
70.5 / 100
StarsRepository reach
13.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
6.9 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
6.6 / 10
via deps.dev · OpenSSF
Signed Commits
34%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection3
CI-Tests10
CII-Best-Practices0
Code-Review0
Contributors0
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies3
SAST10
Security-Policy10
Signed-Releases0
Token-Permissions10
Vulnerabilities8
Is AIPass safe?
Public supply-chain signals for AIPass are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but AIPass carries less obvious unverified-evidence risk than projects with thin signals.
Does AIPass publish package provenance?
Yes. AIPass's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does AIPass have an OpenSSF Scorecard?
AIPass has an OpenSSF Scorecard score of 6.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is AIPass actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does AIPass use?
AIPass ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are AIPass's commits signed?
34% of the last 100 commits to AIPass are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain AIPass?
HVTrust scores AIPass from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
