How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-07 22:30 UTC·Repo last pushed yesterday
Activity & Reach
Stars
5.6k
Forks
780
Last Push
2026-07-06
yesterday
Commits (4 wk)
29
Downloads (7d)
4,166,099
pypi
HN mentions (30d)
—
Open Issues
13
Rank Change
NEW
Analysis
HVTrust Dimensions
43.4 / 100 · 67.0% confidence
Safety / IntegrityOSSF, provenance, signatures
5.0 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
17.8 / 20
AdoptionStars and downloads
17.8 / 20
Activity Inputs
79.3 / 100
StarsRepository reach
22.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
18.4 / 25
CommunityFork signal
13.5 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
100%
of last 100 commits verified
Is mini-SWE-agent safe?
Public trust evidence for mini-SWE-agent is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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?
No OpenSSF Scorecard data is currently published for mini-SWE-agent. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is mini-SWE-agent actively maintained?
Actively maintained. The repository was pushed to within the last 1 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
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 →
MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Amazon Bedrock
OpenAI
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?
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.
