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. Full methodology →
Signals refreshed2026-06-06 16:20 UTC·Repo last pushed 24 days ago
Activity & Reach
Stars
11.8k
Forks
1.4k
Last Push
2026-05-13
24 days ago
Commits (4 wk)
2
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
32
Rank Change
NEW
Analysis
HVTrust Dimensions
22.0 / 100 · 50.0% confidence
Safety / IntegrityOSSF, provenance, signatures
2.7 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
12.3 / 20
AdoptionStars and downloads
9.8 / 20
Activity Inputs
66.7 / 100
StarsRepository reach
24.4 / 30
FreshnessLast push recency
21.7 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
14.6 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
54%
of last 100 commits verified
Is Agent-S safe?
Public trust evidence for Agent-S 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 Agent-S publish package provenance?
No published build provenance is currently detected for Agent-S. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Agent-S have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Agent-S. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Agent-S actively maintained?
Maintained. Last push was 24 days ago.
What license does Agent-S use?
Agent-S ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Agent-S's commits signed?
54% of the last 100 commits to Agent-S 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
HVTrust currently does not score runtime-trust fields yet. This public view shows a compact runtime snapshot from repo docs and manifests. An experimental ranking preview is available in Score Lab →, and progress is tracked on the roadmap →
MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Anthropic
Azure OpenAI
Google Gemini
OpenAI
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
2 tags
Broad capability areas detected.
browser
code
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
MCP support live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain Agent-S?
HVTrust scores Agent-S 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.
Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.2 · Raw JSON
