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. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed 259 days ago — may be stale
Rank Trend
2026-05-232026-06-04
Activity & Reach
Stars
7.7k
Forks
462
Last Push
2025-09-18
259 days ago
Commits (4 wk)
0
Downloads (7d)
65
pypi
HN mentions (30d)
—
Open Issues
750
Rank Change
▼7
was #168
Analysis
HVTrust Dimensions
41.2 / 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.8 / 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
via deps.dev · OpenSSF
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 259 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Sweep?
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.
