Is Strands Agents safe?
Strands Agents scores 91.7/100 (Grade A), ranked #4 of 328 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types).
The public evidence: its packages ship with cryptographic provenance;
OSSF Scorecard rates its supply-chain practices 5.6/10;
100% of recent commits are signed;
last pushed 2026-07-10. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Strong public trust posture, backed by multiple independent signals.
91.7/100 · Grade A
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
19.5/25
What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Recent Changes
2026-07-08
Scorecard Added
OSSF Scorecard: 5.4/10
2026-07-08
Rank Moved
Rank rose 30 spots (#34 → #4)
2026-07-08
HVTrust Changed
HVTrust up 8.7pts (82.7 → 91.4)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.
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. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed yesterday
Rank Trend
2026-07-072026-07-11
Activity & Reach
Stars
6.5k
Forks
938
Last Push
2026-07-10
yesterday
Commits (4 wk)
300
Downloads (7d)
7,805,889
npm+pypi
HN mentions (30d)
—
Open Issues
389
Rank Change
=
was #4
Analysis
HVTrust Dimensions
91.7 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
19.5 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
13.3 / 17
MaintenanceFreshness and commits
19.9 / 20
AdoptionStars and downloads
18.3 / 20
Activity Inputs
86.7 / 100
StarsRepository reach
22.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.8 / 20
Supply Chain Trust
Package Provenance
Verified
npm, pypi attestation
OSSF Scorecard
5.6 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
100%
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-Dependencies2
SAST1
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities2
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.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 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?
100% 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.
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
high confidence
Implemented
Strands Agents appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Extensions
Extension based plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
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.
