mini-SWE-agent
The 100 line AI agent that solves GitHub issues or helps you in your command line. Radically simple, no huge configs, no giant monorepo—but scores >74% on SWE-bench verified!
Is mini-SWE-agent safe? Promising trust profile, but some evidence still deserves review.
Compare mini-SWE-agent
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: mini-SWE-agent scores 69.6/100 (Grade B), ranked #342 of 1346 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.1/10; 98% of recent commits are signed; no published advisory affects its latest release (mini-swe-agent); last pushed 2026-09-28. Every point is earned from checkable signals — never paid placement. How scoring works →
How mini-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.4 → 84.0 A · #8 of 75
- Raise the OSSF Scorecard from 6.1 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Fuzzing 0 +6.1 → 75.7 B · #11 of 75
Chain of custody
Scanners check what the code says. This traces who ships mini-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/mini-swe-agent, MIT, last pushed 2026-09-28. 98% 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 6.1/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:
- Code Review3
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests 10CII-Best-Practices 0Code-Review 3Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 0SAST 0Security-Policy 10Signed-Releases -1Token-Permissions 0Vulnerabilities 10 -
Published packages Linked, not attested
- PyPI mini-swe-agent Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: mini-swe-agent 2.4.6. No published advisory affects it (OSV, checked 2026-10-05).
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of mini-SWE-agent.
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues mini-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 mini-SWE-agent compares in Coding Agents
- #17 Claude Code 70.6 +1.0
- #18 Open Interpreter 70.3 +0.7
- #19 mini-SWE-agent 69.6 this agent
- #20 Goose 69.1 −0.5
- #21 prime-agent 69.0 −0.6
Bars show each HVTrust score; the tick marks mini-SWE-agent’s 69.6.
Where the 69.6 comes from
HVTrust dimensions vs the Coding Agents average
69.6 / 100 · 100.0% confidencemini-SWE-agent Coding Agents average (75 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 B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
61.7 / 100Common questions about mini-SWE-agent
Does mini-SWE-agent publish package provenance?
Does mini-SWE-agent have an OpenSSF Scorecard?
Is mini-SWE-agent actively maintained?
What license does mini-SWE-agent use?
Are mini-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 →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain mini-SWE-agent?
For maintainers
HVTrust scores mini-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/mini-swe-agent)
<a href="https://hvtracker.net/agents/mini-swe-agent"><img src="https://hvtracker.net/badge/mini-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
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON