updated 2026-08-22 00:32 UTC

mini-SWE-agent

SWE-agent/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

Coding Agents Python Grade B Listed MIT
72.2/100
Rank #121 of 1308
Compare mini-SWE-agent

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-17 · 5d ago
Recent change
Rank

Is mini-SWE-agent safe? mini-SWE-agent scores 72.2/100 (Grade B), ranked #121 of 1308 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; 100% of recent commits are signed; last pushed 2026-08-17. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#11 OpenHands — 72.6 (B) → #12 GPTMe — 72.5 (B) → #14 CodeWhale — 70.1 (B) → #15 Open SWE — 69.0 (B) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-17
Rank Moved
Rank rose 13 spots (#116 → #103)
2026-08-13
Rank Moved
Rank dropped 12 spots (#100 → #112)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.1/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for mini-SWE-agent View Coding Agents Report missing data
68.6
Activity sub-score · out of 100
#13
In Coding Agents

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 →

Signals refreshed 2026-08-22 00:32 UTC · Repo last pushed 5 days ago

Rank Trend

2026-08-11 2026-08-22

Activity & Reach

Stars
6.7k
Forks
923
Last Push
2026-08-17
5 days ago
Commits (4 wk)
3
Downloads (7d)
4,166,099
pypi
HN mentions (30d)
—
Open Issues
20
Rank Change
▲2
was #123

Analysis

HVTrust Dimensions vs Coding Agents

72.2 / 100 · 100.0% confidence

mini-SWE-agent Coding Agents average (70 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.6 / 25
5.0 above avg 7.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
13.7 / 17
2.6 above avg 11.1
Maintenance60% last-push freshness · 40% commit activity
14.1 / 20
0.9 below avg 15.0
AdoptionLog-scaled stars · package downloads
18.0 / 20
5.7 above avg 12.3

Activity Inputs

68.6 / 100
StarsRepository reach
22.9 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
7.5 / 25
CommunityFork signal
13.8 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.1 / 10
OpenSSF Scorecard · scanned Aug 21, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 3
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 10

Is mini-SWE-agent safe?

mini-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 mini-SWE-agent publish package provenance?
No published build provenance is currently detected for mini-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 mini-SWE-agent have an OpenSSF Scorecard?
mini-SWE-agent has an OpenSSF Scorecard score of 6.1/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 mini-SWE-agent actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does mini-SWE-agent use?
mini-SWE-agent ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are mini-SWE-agent's commits signed?
100% of the last 100 commits to mini-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.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 3Listed 1HVTrust 1Grade 1Scorecard 1
2026-08-17
Rank Moved
Rank rose 13 spots (#116 → #103)
2026-08-13
Rank Moved
Rank dropped 12 spots (#100 → #112)
2026-07-08
Scorecard Added
OSSF Scorecard: 6.1/10
2026-07-08
Grade Changed
Trust grade D → B
2026-07-08
Rank Moved
Rank rose 208 spots (#264 → #56)
2026-07-08
HVTrust Changed
HVTrust up 32.7pts (43.4 → 76.1)
2026-07-07
Newly Listed
First tracked at rank #264
GitHub → PyPI: mini-swe-agent

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 72.2 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/mini-swe-agent.svg)](https://hvtracker.net/agents/mini-swe-agent)
HTML:
<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

Data sources
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.3 · Raw JSON