How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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 yesterday
Rank Trend
2026-05-242026-06-04
Activity & Reach
Stars
6.0k
Forks
862
Last Push
2026-06-03
yesterday
Commits (4 wk)
183
Downloads (7d)
5,629,696
pypi
HN mentions (30d)
—
Open Issues
706
Rank Change
▲1
was #17
Analysis
HVTrust Dimensions
88.7 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
19.3 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
13.4 / 17
MaintenanceFreshness and commits
19.9 / 20
AdoptionStars and downloads
18.1 / 20
Activity Inputs
86.4 / 100
StarsRepository reach
22.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.7 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
5.8 / 10
via deps.dev · OpenSSF
Signed Commits
91%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests10
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow0
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies1
SAST0
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities6
Is Strands Agents safe?
Public supply-chain signals for Strands Agents are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Strands Agents carries less obvious unverified-evidence risk than projects with thin signals.
Does Strands Agents publish package provenance?
Yes. Strands Agents's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Strands Agents have an OpenSSF Scorecard?
Strands Agents 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 Strands Agents actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Strands Agents use?
Strands Agents ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Strands Agents's commits signed?
91% of the last 100 commits to Strands Agents 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 Strands Agents?
HVTrust scores Strands Agents 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.
