Is Open SWE safe?
Open SWE scores 67.2/100 (Grade B), ranked #104 of 328 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.5/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
Promising trust profile, but some evidence still deserves review.
67.2/100 · Grade B
Strongest Signal
Maintenance
19.9/20
Weakest Signal
Adoption
9.6/20
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 6.5/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
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 →
Signals refreshed2026-07-11 08:30 UTC·Repo last pushed yesterday
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
10.2k
Forks
1.2k
Last Push
2026-07-10
yesterday
Commits (4 wk)
209
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
6
Rank Change
▼1
was #103
Analysis
HVTrust Dimensions
67.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
13.1 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
14.0 / 17
MaintenanceFreshness and commits
19.9 / 20
AdoptionStars and downloads
9.6 / 20
Activity Inputs
88.4 / 100
StarsRepository reach
24.1 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.3 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.5 / 10
OpenSSF Scorecard · scanned Jul 8, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection4
CI-Tests9
CII-Best-Practices0
Code-Review4
Contributors6
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging-1
Pinned-Dependencies5
SAST9
Security-Policy9
Signed-Releases-1
Token-Permissions0
Vulnerabilities5
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.5/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.
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.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
code
database
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
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.
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.2 · Raw JSON
