How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed 101 days ago
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
540
Forks
64
Last Push
2026-02-23
101 days ago
Commits (4 wk)
0
Downloads (7d)
136
pypi
HN mentions (30d)
0
Open Issues
80
Rank Change
▼10
was #134
Analysis
HVTrust Dimensions
51.6 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.6 / 17
MaintenanceFreshness and commits
5.3 / 20
AdoptionStars and downloads
9.4 / 20
Activity Inputs
35.8 / 100
StarsRepository reach
16.4 / 30
FreshnessLast push recency
11.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
8.4 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.0 / 10
via deps.dev · OpenSSF
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection8
CI-Tests5
CII-Best-Practices0
Code-Review7
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained0
Packaging10
Pinned-Dependencies0
SAST8
Security-Policy0
Signed-Releases-1
Token-Permissions0
Vulnerabilities9
Is FastAgency safe?
Public trust evidence for FastAgency is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does FastAgency publish package provenance?
No published build provenance is currently detected for FastAgency. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does FastAgency have an OpenSSF Scorecard?
FastAgency has an OpenSSF Scorecard score of 6.0/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 FastAgency actively maintained?
Slowing down. Last push was 101 days ago — keep an eye on whether activity resumes.
What license does FastAgency use?
FastAgency ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are FastAgency's commits signed?
100% of the last 100 commits to FastAgency 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 FastAgency?
HVTrust scores FastAgency 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.
