Is FastAgency safe?
FastAgency scores 48.6/100 (Grade D), ranked #243 of 328 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types).
The public evidence: no package-provenance attestation found;
OSSF Scorecard rates its supply-chain practices 5.8/10;
100% of recent commits are signed;
last pushed 2026-02-23. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
48.6/100 · Grade D
Strongest Signal
Transparency
13.4/17
Weakest Signal
Maintenance
2.8/20
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-04
Provider Removed
Runtime surface shrank — no longer detected: Postgres
2026-06-27
Grade Changed
Trust grade C → D
2026-06-24
Rank Moved
Rank dropped 30 spots (#200 → #230)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 5.8/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
Refresh maintenance signalsThe repo was last pushed 138 days ago. Fresh activity helps separate stable projects from stale ones.
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed 138 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
544
Forks
63
Last Push
2026-02-23
138 days ago
Commits (4 wk)
0
Downloads (7d)
155
npm+pypi
HN mentions (30d)
0
Open Issues
72
Rank Change
=
was #243
Analysis
HVTrust Dimensions
48.6 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.2 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.4 / 17
MaintenanceFreshness and commits
2.8 / 20
AdoptionStars and downloads
9.5 / 20
Activity Inputs
30.6 / 100
StarsRepository reach
16.4 / 30
FreshnessLast push recency
5.8 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
8.4 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.8 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection8
CI-Tests2
CII-Best-Practices0
Code-Review7
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained0
Packaging10
Pinned-Dependencies0
SAST7
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 5.8/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 138 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.
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
browser
Detailed evidence is not shown in the public view.
Package Provenance Drift
medium confidence
Partial
Some package metadata matches; some source metadata is missing
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
How this surface has changed
Detected changes to FastAgency's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
2026-07-04
Provider Removed
Runtime surface shrank — no longer detected: Postgres
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.
