Is Sweep safe?
Sweep scores 41.6/100 (Grade D), ranked #599 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 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 →
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-08-25 07:32 UTC·Repo last pushed 341 days ago — may be stale
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 341 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.
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.
