How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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 3 days ago
Rank Trend
2026-05-232026-06-04
Activity & Reach
Stars
19.4k
Forks
2.1k
Last Push
2026-06-01
3 days ago
Commits (4 wk)
1?
Downloads (7d)
92
pypi
HN mentions (30d)
2
Open Issues
37
Rank Change
▼14
was #105
Analysis
HVTrust Dimensions
61.1 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
11.6 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.4 / 17
MaintenanceFreshness and commits
12.4 / 20
AdoptionStars and downloads
12.9 / 20
Activity Inputs
69.7 / 100
StarsRepository reach
25.7 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
15.5 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.8 / 10
via deps.dev · OpenSSF
Signed Commits
87%
of last 100 commits verified
Binary-Artifacts6
Branch-Protection3
CI-Tests8
CII-Best-Practices0
Code-Review5
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained8
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities10
Is SWE-agent safe?
SWE-agent 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 SWE-agent publish package provenance?
No published build provenance is currently detected for SWE-agent. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does SWE-agent have an OpenSSF Scorecard?
SWE-agent has an OpenSSF Scorecard score of 5.8/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 SWE-agent actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does SWE-agent use?
SWE-agent ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are SWE-agent's commits signed?
87% of the last 100 commits to SWE-agent 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 SWE-agent?
HVTrust scores SWE-agent 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.
