Is SWE-agent safe to use?

SWE-agent has an HVTrust score of 61.4/100 (Grade C), ranked #312 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for SWE-agent?

SWE-agent scores 61.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 20.1k GitHub stars and is categorized under Coding Agents.

SWE-agent

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

Coding Agents Python Grade C Listed MIT

61.4/100

Rank #312 of 1308

Compare 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 A · 4/5 signals

Last push

2026-08-17 · 2d ago

Recent change

Rank +6

Is SWE-agent safe? SWE-agent scores 61.4/100 (Grade C), ranked #312 of 1308 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 6.2/10; 91% 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

#23 DeepSeek-Reasonix — 62.0 (C) → #24 Archon — 62.0 (C) → #26 GitHub Copilot CLI — 60.9 (C) → #27 Junie — 60.0 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-19

Rank Moved

Rank dropped 15 spots (#297 → #312)

2026-08-17

Rank Moved

Rank rose 21 spots (#319 → #298)

2026-08-16

Rank Moved

Rank dropped 26 spots (#293 → #319)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.2/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 SWE-agent View Coding Agents Report missing data

66.2

Activity sub-score · out of 100

#25

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 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

2026-08-11 2026-08-19

Activity & Reach

Stars

20.1k

Forks

2.2k

Last Push

2026-08-17

2 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

Open Issues

Rank Change

▼15

was #297

Analysis

HVTrust Dimensions vs Coding Agents

61.4 / 100 · 100.0% confidence

SWE-agent Coding Agents average (70 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

12.3 / 25

4.8 above avg 7.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

13.8 / 17

2.7 above avg 11.1

Maintenance60% last-push freshness · 40% commit activity

11.9 / 20

3.4 below avg 15.3

AdoptionLog-scaled stars · package downloads

12.9 / 20

0.6 above avg 12.3

Activity Inputs

66.2 / 100

StarsRepository reach

25.8 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

15.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.2 / 10

OpenSSF Scorecard · scanned Aug 18, 2026

Signed Commits

91%

of last 100 commits verified

Binary-Artifacts 6

Branch-Protection 3

CI-Tests 9

CII-Best-Practices 0

Code-Review 8

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

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 6.2/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 2 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?

91% 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.

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

medium confidence

1 detected

Public provider/service dependencies detected.

Multi-provider (LiteLLM)

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

1 tags

Broad capability areas detected.

code

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-19

Rank Moved

Rank dropped 15 spots (#297 → #312)

2026-08-17

Rank Moved

Rank rose 21 spots (#319 → #298)

2026-08-16

Rank Moved

Rank dropped 26 spots (#293 → #319)

2026-08-15

Rank Moved

Rank dropped 40 spots (#253 → #293)

2026-08-15

Activity Score Changed

Activity score down 6pts (72 → 66)

2026-08-13

Rank Moved

Rank dropped 18 spots (#232 → #250)

2026-08-12

Rank Moved

Rank rose 14 spots (#246 → #232)

2026-08-08

Rank Moved

Rank dropped 47 spots (#187 → #234)

2026-08-06

Grade Changed

Trust grade B → C

2026-08-06

Rank Moved

Rank dropped 16 spots (#155 → #171)

2026-07-29

Rank Moved

Rank dropped 12 spots (#133 → #145)

2026-07-13

Rank Moved

Rank dropped 11 spots (#110 → #121)

2026-06-29

Rank Moved

Rank rose 11 spots (#120 → #109)

2026-06-18

Scorecard Added

OSSF Scorecard: 6.0/10

2026-06-18

Grade Changed

Trust grade D → B

2026-06-18

Rank Moved

Rank rose 80 spots (#183 → #103)

2026-06-18

HVTrust Changed

HVTrust up 25.9pts (40.4 → 66.3)

2026-06-10

Scorecard Removed

OSSF Scorecard no longer detected

2026-06-10

Grade Changed

Trust grade C → D

2026-06-10

Rank Moved

Rank dropped 71 spots (#119 → #190)

2026-06-10

HVTrust Changed

HVTrust down 22.7pts (60.9 → 38.2)

2026-06-10

Activity Score Changed

Activity score up 8pts (70 → 78)

2026-06-09

Newly Listed

First tracked at rank #119

GitHub → PyPI: sweagent

Embed Badge Badge guide for maintainers →

For maintainers

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

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