Is Strands Agents safe to use?

Strands Agents has an HVTrust score of 90.5/100 (Grade A), ranked #19 of 1371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Strands Agents?

Strands Agents scores 90.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 8.8k GitHub stars and is categorized under Agent Frameworks.

Strands Agents

Repository Website

Build an agent harness and control it end-to-end. Open-source SDK for production AI agents in Python & TypeScript - any model, any cloud.

Agent Frameworks Python Listed Apache-2.0

Is Strands Agents safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.4 / 10

Provenance Attested

Signed commits 100%

Last push today

Advisories None known

Compare Strands Agents

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Strands Agents scores 90.5/100 (Grade A), ranked #19 of 1371 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.4/10; 100% of recent commits are signed; no published advisory affects its latest release (@strands-agents/sdk, strands-agents); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Strands Agents could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 5.4 to 9.0lowest checks: CII-Best-Practices 0, Dangerous-Workflow 0, Fuzzing 0 +5.3 → 95.8 A · #3 of 129

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Strands Agents and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/strands-agents/harness-sdk, Apache-2.0, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.4/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection5
- Signed Releasesn/a
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies2
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 1

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages Linked and attested
- npm @strands-agents/sdk Source link points back to this repo Build provenance attested
- PyPI strands-agents Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest releases checked: @strands-agents/sdk 1.20.0, strands-agents 1.59.0. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Strands Agents.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Strands Agents’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Strands Agents compares in Agent Frameworks

Bars show each HVTrust score; the tick marks Strands Agents’s 90.5.

Where the 90.5 comes from

HVTrust dimensions vs the Agent Frameworks average

90.5 / 100 · 100.0% confidence

Strands Agents Agent Frameworks average (129 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

19.2 / 25

9.6 above avg 9.6

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.4 above avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

13.1 / 17

0.8 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.7 above avg 14.3

AdoptionLog-scaled stars · package downloads

18.7 / 20

7.5 above avg 11.2

Quick Trust Read

What Would Improve It

Improve safety / integrity to lift the weakest part of the trust profile.

Recent Changes

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-09-21

Rank Moved

Rank rose 19 spots (#32 → #13)

2026-09-20

Rank Moved

Rank dropped 16 spots (#16 → #32)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.4/10. Tighten the weakest checks to improve public safety evidence.

Compare with Haystack Get email alerts for Strands Agents View Agent Frameworks Report missing data

88.3

Activity sub-score · out of 100

In Agent Frameworks

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 →

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars

8.8k

Forks

1.3k

Last Push

2026-10-09

today

Commits (4 wk)

269

Downloads (7d)

9,215,765

npm+pypi

HN mentions (30d)

—

Open Issues

578

Rank Change

▼1

was #18

Analysis

Activity Inputs

88.3 / 100

StarsRepository reach

23.7 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

14.6 / 20

Common questions about Strands Agents

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.4/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.

Compare Strands Agents head-to-head

Strands Agents vs Haystack → Strands Agents vs Vercel AI SDK → Strands Agents vs OpenAI Agents SDK (JS) →

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

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

high confidence

4 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared 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

How this surface has changed

Detected changes to Strands Agents'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-09-23

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-09-03

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Google Gemini, OpenAI

Maintain Strands Agents?

For maintainers

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-09-21

Rank Moved

Rank rose 19 spots (#32 → #13)

2026-09-20

Rank Moved

Rank dropped 16 spots (#16 → #32)

2026-09-10

Rank Moved

Rank rose 15 spots (#25 → #10)

2026-09-09

Rank Moved

Rank dropped 14 spots (#11 → #25)

2026-09-03

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Google Gemini, OpenAI

GitHub → Website → PyPI: strands-agents npm: @strands-agents/sdk

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/strands-agents.svg)](https://hvtracker.net/agents/strands-agents)
            
HTML:
            <a href="https://hvtracker.net/agents/strands-agents"><img src="https://hvtracker.net/badge/strands-agents.svg" alt="HVTrust"></a>

Other agents in Agent Frameworks

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Strands Agents

How Strands Agents could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Strands Agents compares in Agent Frameworks

Where the 90.5 comes from

HVTrust dimensions vs the Agent Frameworks average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Strands Agents

Compare Strands Agents head-to-head

AI agent surface

Maintain Strands Agents?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Frameworks