Is Open SWE safe to use?

Open SWE has an HVTrust score of 69.1/100 (Grade B), ranked #157 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Open SWE?

Open SWE scores 69.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 10.6k GitHub stars and is categorized under Coding Agents.

Open SWE

langchain-ai/open-swe

An Open-Source Asynchronous Coding Agent

Coding Agents Python Grade B Listed MIT

69.1/100

Rank #157 of 1308

Compare Open SWE

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-25 · 0d ago

Recent change

Rank +2

Is Open SWE safe? Open SWE scores 69.1/100 (Grade B), ranked #157 of 1308 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.7/10; 100% of recent commits are signed; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#13 CodeWhale — 71.4 (B) → #14 mini-SWE-agent — 71.2 (B) → #16 Goose — 68.4 (B) → #17 Kilo Code — 67.5 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-24

Rank Moved

Rank dropped 10 spots (#147 → #157)

2026-08-22

Rank Moved

Rank rose 14 spots (#160 → #146)

2026-08-18

Rank Moved

Rank rose 13 spots (#156 → #143)

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for Open SWE View Coding Agents Report missing data

88.6

Activity sub-score · out of 100

#15

In Coding Agents

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars

10.6k

Forks

1.2k

Last Push

2026-08-25

today

Commits (4 wk)

349

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #157

Analysis

HVTrust Dimensions vs Coding Agents

69.1 / 100 · 100.0% confidence

Open SWE Coding Agents average (70 agents)

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

13.4 / 25

5.8 above avg 7.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

14.2 / 17

3.1 above avg 11.1

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.1 above avg 14.9

AdoptionLog-scaled stars · package downloads

9.7 / 20

2.6 below avg 12.3

Activity Inputs

88.6 / 100

StarsRepository reach

24.2 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

14.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.7 / 10

OpenSSF Scorecard · scanned Aug 24, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 8

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 3

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 4

SAST 9

Security-Policy 9

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Is Open SWE safe?

Open SWE has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Open SWE publish package provenance?

No published build provenance is currently detected for Open SWE. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Open SWE have an OpenSSF Scorecard?

Open SWE has an OpenSSF Scorecard score of 6.7/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 Open SWE actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Open SWE use?

Open SWE ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Open SWE's commits signed?

100% of the last 100 commits to Open SWE 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.

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

medium confidence

Implemented

Open SWE appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Fireworks AI

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

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 signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Open SWE'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-06-16

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-06-15

Mcp Status Changed

Detected MCP server support changed: implemented → none

2026-06-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-06-11

Mcp Status Changed

Detected MCP server support changed: implemented → none

2026-06-10

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Open SWE?

For maintainers

HVTrust scores Open SWE 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-08-24

Rank Moved

Rank dropped 10 spots (#147 → #157)

2026-08-22

Rank Moved

Rank rose 14 spots (#160 → #146)

2026-08-18

Rank Moved

Rank rose 13 spots (#156 → #143)

2026-08-16

Rank Moved

Rank dropped 17 spots (#147 → #164)

2026-08-13

Rank Moved

Rank dropped 10 spots (#139 → #149)

2026-08-12

Rank Moved

Rank rose 31 spots (#170 → #139)

2026-08-10

Rank Moved

Rank dropped 12 spots (#167 → #179)

2026-08-08

Rank Moved

Rank dropped 28 spots (#137 → #165)

2026-08-04

Rank Moved

Rank dropped 12 spots (#125 → #137)

2026-07-13

Rank Moved

Rank dropped 14 spots (#103 → #117)

2026-06-16

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-06-15

Mcp Status Changed

Detected MCP server support changed: implemented → none

2026-06-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-06-11

Mcp Status Changed

Detected MCP server support changed: implemented → none

2026-06-10

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-05-29

HVTrust Changed

HVTrust up 10.0pts (58.8 → 68.8)

2026-05-28

Activity Score Changed

Activity score up 25pts (63 → 88)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON