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. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed today
Rank Trend
2026-05-242026-06-04
Activity & Reach
Stars
9.9k
Forks
1.1k
Last Push
2026-06-04
today
Commits (4 wk)
130
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
13
Rank Change
▼11
was #77
Analysis
HVTrust Dimensions
66.5 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.6 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
9.6 / 20
Activity Inputs
88.2 / 100
StarsRepository reach
24.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.2 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.0 / 10
via deps.dev · OpenSSF
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection3
CI-Tests10
CII-Best-Practices0
Code-Review0
Contributors6
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging-1
Pinned-Dependencies5
SAST10
Security-Policy9
Signed-Releases-1
Token-Permissions0
Vulnerabilities3
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.0/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.
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 Open SWE?
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) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
