Is Sweep safe?
Sweep scores 41.3/100 (Grade D), ranked #278 of 328 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;
last pushed 2025-09-18. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
41.3/100 · Grade D
Strongest Signal
Transparency
12.1/17
Weakest Signal
Maintenance
0/20
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-06-24
Rank Moved
Rank dropped 33 spots (#251 → #284)
2026-06-23
Rank Moved
Rank dropped 21 spots (#230 → #251)
2026-06-22
Rank Moved
Rank dropped 10 spots (#220 → #230)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 4.2/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signalsThe repo was last pushed 296 days ago. Fresh activity helps separate stable projects from stale ones.
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 refreshed2026-07-11 04:00 UTC·Repo last pushed 296 days ago — may be stale
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
7.7k
Forks
463
Last Push
2025-09-18
296 days ago
Commits (4 wk)
0
Downloads (7d)
22
pypi
HN mentions (30d)
—
Open Issues
243
Rank Change
=
was #278
Analysis
HVTrust Dimensions
41.3 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
6.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.1 / 17
MaintenanceFreshness and commits
0.0 / 20
AdoptionStars and downloads
11.1 / 20
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
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.2 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
24%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection6
CI-Tests0
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License9
Maintained0
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy0
Signed-Releases0
Token-Permissions0
Vulnerabilities0
Is Sweep safe?
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 296 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.
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.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface 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
How this surface has changed
Detected changes to Sweep's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
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.
