updated 2026-10-09 16:07 UTC

Sweep

Repository

Sweep: AI coding assistant for JetBrains

Coding Agents Jupyter Notebook Needs review NOASSERTION Source-available

Is Sweep safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.2 / 10
Provenance None
Signed commits 24%
Last push 386d ago
Advisories None known
Compare Sweep

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Sweep scores 32.5/100 (Grade D), ranked #1294 of 1371 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 4.2/10; 24% of recent commits are signed; no published advisory affects its latest release (sweepai); last pushed 2025-09-18. Every point is earned from checkable signals — never paid placement. How scoring works →

How Sweep 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.

Already done? Suggest a correctionAdd the trust badge
Active listing, but review is needed
  • [4.2.1] no meaningful activity in 12 months (last push 2025-09-18)

Chain of custody

Scanners check what the code says. This traces who ships Sweep 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.

  1. Source Partly signed

    github.com/sweepai/sweep, NOASSERTION, last pushed 2025-09-18. 24% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.2/10 (scanned Oct 4, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection6
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 9
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • PyPI sweepai Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: sweepai 3.2.5. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Sweep.

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 Sweep’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.

Signed credential (JSON) How to verify

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 Sweep compares in Coding Agents

  1. #67 GPT Pilot 39.4 +6.9
  2. #68 Continue 33.2 +0.7
  3. #69 Sweep 32.5 this agent
  4. #70 10x 30.3 −2.2
  5. #71 PearAI 28.8 −3.7

Bars show each HVTrust score; the tick marks Sweep’s 32.5.

Where the 32.5 comes from

HVTrust dimensions vs the Coding Agents average

32.5 / 100 · 100.0% confidence

Sweep Coding Agents average (77 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.5 / 25
2.5 below avg 9.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
12.1 / 17
in line with avg 11.8
Maintenance60% last-push freshness · 40% commit activity
0 / 20
15.0 below avg 15.0
AdoptionLog-scaled stars · package downloads
12.0 / 20
in line with avg 12.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 614 spots (#660 → #1274)
2026-09-22
Rank Moved
Rank dropped 246 spots (#414 → #660)
2026-09-21
Rank Moved
Rank rose 858 spots (#1272 → #414)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 386 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[4.2.1] no meaningful activity in 12 months (last push 2025-09-18)
Compare with another agent Get email alerts for Sweep View Coding Agents Report missing data
35.7
Activity sub-score · out of 100
#69
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 D 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-10-09 16:07 UTC · Repo last pushed 386 days ago — may be stale

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
7.7k
Forks
467
Last Push
2025-09-18
386 days ago
Commits (4 wk)
0
Downloads (7d)
99
pypi
HN mentions (30d)
—
Open Issues
244
Rank Change
▼9
was #1285

Analysis

Activity Inputs

35.7 / 100
StarsRepository reach
23.3 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.4 / 20

Common questions about Sweep

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Sweep may have internal security practices not visible through public signals.
Public trust evidence for Sweep 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 Sweep publish package provenance?
No published build provenance is currently detected for Sweep. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Sweep have an OpenSSF Scorecard?
Sweep has an OpenSSF Scorecard score of 4.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 Sweep actively maintained?
Stale. The repository has not been pushed to in 386 days. Consider whether the project is still being maintained.
What license does Sweep use?
Sweep ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Sweep's commits signed?
24% of the last 100 commits to Sweep 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
5 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
3 tags
Broad capability areas detected.
  • code
  • database
  • shell
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 Sweep?

For maintainers

HVTrust scores Sweep 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 25Warning Issued 1HVTrust 1
2026-09-23
Rank Moved
Rank dropped 614 spots (#660 → #1274)
2026-09-22
Rank Moved
Rank dropped 246 spots (#414 → #660)
2026-09-21
Rank Moved
Rank rose 858 spots (#1272 → #414)
2026-09-19
Rank Moved
Rank dropped 143 spots (#1133 → #1276)
2026-09-19
HVTrust Changed
HVTrust down 10.0pts (41.3 → 31.3)
2026-09-18
Warning Issued
Warning: eligibility issues detected
2026-09-12
Rank Moved
Rank dropped 13 spots (#1120 → #1133)
2026-09-09
Rank Moved
Rank dropped 15 spots (#1101 → #1116)
2026-09-07
Rank Moved
Rank dropped 24 spots (#1071 → #1095)
2026-09-06
Rank Moved
Rank dropped 13 spots (#1058 → #1071)
2026-09-05
Rank Moved
Rank dropped 43 spots (#1015 → #1058)
2026-09-04
Rank Moved
Rank dropped 22 spots (#993 → #1015)
2026-09-03
Rank Moved
Rank dropped 52 spots (#941 → #993)
2026-09-02
Rank Moved
Rank dropped 51 spots (#890 → #941)
2026-09-01
Rank Moved
Rank dropped 33 spots (#857 → #890)
2026-08-31
Rank Moved
Rank dropped 29 spots (#828 → #857)
2026-08-30
Rank Moved
Rank dropped 32 spots (#796 → #828)
2026-08-29
Rank Moved
Rank dropped 47 spots (#749 → #796)
2026-08-28
Rank Moved
Rank dropped 28 spots (#721 → #749)
2026-08-27
Rank Moved
Rank dropped 23 spots (#698 → #721)
2026-08-26
Rank Moved
Rank dropped 94 spots (#604 → #698)
2026-08-16
Rank Moved
Rank dropped 11 spots (#591 → #602)
2026-08-10
Rank Moved
Rank dropped 21 spots (#569 → #590)
2026-08-08
Rank Moved
Rank dropped 186 spots (#383 → #569)
2026-07-15
Rank Moved
Rank dropped 25 spots (#332 → #357)
2026-07-14
Rank Moved
Rank dropped 18 spots (#314 → #332)
2026-07-13
Rank Moved
Rank dropped 36 spots (#278 → #314)
GitHub → PyPI: sweepai

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 32.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/sweep.svg)](https://hvtracker.net/agents/sweep)
HTML:
<a href="https://hvtracker.net/agents/sweep"><img src="https://hvtracker.net/badge/sweep.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.4 · Raw JSON