How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed yesterday
Rank Trend
2026-06-022026-06-04
Activity & Reach
Stars
34.8k
Forks
3.0k
Last Push
2026-06-03
yesterday
Commits (4 wk)
55
Downloads (7d)
1,537,586
pypi
HN mentions (30d)
69
Open Issues
528
Rank Change
▲113
was #149
Analysis
HVTrust Dimensions
76.8 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
13.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
14.4 / 17
MaintenanceFreshness and commits
18.9 / 20
AdoptionStars and downloads
19.2 / 20
Activity Inputs
90.2 / 100
StarsRepository reach
27.3 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
21.8 / 25
CommunityFork signal
16.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.9 / 10
via deps.dev · OpenSSF
Signed Commits
98%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection0
CI-Tests9
CII-Best-Practices0
Code-Review4
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies6
SAST9
Security-Policy10
Signed-Releases-1
Token-Permissions10
Vulnerabilities0
Is DSPy safe?
Public supply-chain signals for DSPy are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but DSPy carries less obvious unverified-evidence risk than projects with thin signals.
Does DSPy publish package provenance?
No published build provenance is currently detected for DSPy. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does DSPy have an OpenSSF Scorecard?
DSPy has an OpenSSF Scorecard score of 6.9/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 DSPy actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does DSPy use?
DSPy ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are DSPy's commits signed?
98% of the last 100 commits to DSPy 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 DSPy?
HVTrust scores DSPy 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.
