SWE-agent
SWE-agent takes a GitHub issue and tries to automatically fix it, using your LM of choice. It can also be employed for offensive cybersecurity or competitive coding challenges. [NeurIPS 2024]
Is SWE-agent safe? Promising trust profile, but some evidence still deserves review.
Compare SWE-agent
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: SWE-agent scores 60.3/100 (Grade C), ranked #642 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.9/10; 94% of recent commits are signed; last pushed 2026-10-06. Every point is earned from checkable signals — never paid placement. How scoring works →
How SWE-agent 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.
- Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.7 → 75.0 B · #11 of 77
- Raise the OSSF Scorecard from 5.9 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Pinned-Dependencies 0 +6.5 → 66.8 B · #24 of 77
Chain of custody
Scanners check what the code says. This traces who ships SWE-agent 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/SWE-agent/SWE-agent, MIT, last pushed 2026-10-06. 94% 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.9/10 (scanned Sep 28, 2026). The checks that decide who can get a change released:
- Code Review8
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 6Branch-Protection 3CI-Tests 9CII-Best-Practices 0Code-Review 8Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 6Packaging -1Pinned-Dependencies 0SAST 0Security-Policy 10Signed-Releases -1Token-Permissions 0Vulnerabilities 10 -
Published packages Not linked
- PyPI sweagent Source link isn't a GitHub repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of SWE-agent.
Evidence behind this score
Coverage A: 4 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues SWE-agent’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.
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 SWE-agent compares in Coding Agents
- #32 Kiro Crew 62.4 +2.1
- #33 oh-my-openagent 62.4 +2.1
- #34 SWE-agent 60.3 this agent
- #35 loushang 60.2 −0.1
- #36 zerostack 60.0 −0.3
Bars show each HVTrust score; the tick marks SWE-agent’s 60.3.
Where the 60.3 comes from
HVTrust dimensions vs the Coding Agents average
60.3 / 100 · 100.0% confidenceSWE-agent Coding Agents average (77 agents)
Quick Trust Read
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. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
66.1 / 100Common questions about SWE-agent
Does SWE-agent publish package provenance?
Does SWE-agent have an OpenSSF Scorecard?
Is SWE-agent actively maintained?
What license does SWE-agent use?
Are SWE-agent's commits signed?
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
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 →
- code
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain SWE-agent?
For maintainers
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/swe-agent)
<a href="https://hvtracker.net/agents/swe-agent"><img src="https://hvtracker.net/badge/swe-agent.svg" alt="HVTrust"></a>
Other agents in Coding Agents
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON