DSPy has an HVTrust score of 74.7/100 (Grade B), ranked #88 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for DSPy?

DSPy scores 74.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 37.2k GitHub stars and is categorized under Agent Frameworks.

DSPy

stanfordnlp/dspy

DSPy: The framework for programming—not prompting—language models

Agent Frameworks Python Grade B Listed MIT

74.7/100

Rank #88 of 1283

Compare DSPy

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2026-08-15 · 0d ago

Recent change

No recent signal change

Is DSPy safe? DSPy scores 74.7/100 (Grade B), ranked #88 of 1283 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.9/10; 98% of recent commits are signed; last pushed 2026-08-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#13 Deep Agents — 78.4 (B) → #14 Agent Governance Toolkit — 76.6 (B) → #16 AutoGen — 74.0 (B) → #17 Microsoft Agent Framework — 73.8 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.9/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.

Compare with another agent Get email alerts for DSPy View Agent Frameworks Report missing data

89.6

Activity sub-score · out of 100

#15

In Agent Frameworks

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. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-15

Activity & Reach

Stars

37.2k

Forks

3.2k

Last Push

2026-08-15

today

Commits (4 wk)

Downloads (7d)

1,315,847

pypi

HN mentions (30d)

Open Issues

311

Rank Change

▲9

was #97

Analysis

HVTrust Dimensions vs Agent Frameworks

74.7 / 100 · 100.0% confidence

DSPy Agent Frameworks average (118 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

13.5 / 25

5.3 above avg 8.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

14.4 / 17

2.8 above avg 11.6

Maintenance60% last-push freshness · 40% commit activity

18.7 / 20

4.5 above avg 14.2

AdoptionLog-scaled stars · package downloads

19.1 / 20

7.7 above avg 11.4

Activity Inputs

89.6 / 100

StarsRepository reach

27.4 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

20.9 / 25

CommunityFork signal

16.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.9 / 10

OpenSSF Scorecard · scanned Aug 15, 2026

Signed Commits

98%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 2

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 6

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0

Is DSPy safe?

DSPy has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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.

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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

4 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium confidence

1 tags

Broad capability areas detected.

database

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain DSPy?

For maintainers

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-07-11

Rank Moved

Rank dropped 10 spots (#68 → #78)

2026-06-03

Scorecard Added

OSSF Scorecard: 6.9/10

2026-06-03

Grade Changed

Trust grade D → B

2026-06-03

Rank Moved

Rank rose 111 spots (#147 → #36)

2026-06-03

HVTrust Changed

HVTrust up 30.1pts (46.7 → 76.8)

2026-06-02

Newly Listed

First tracked at rank #147

GitHub → PyPI: dspy

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/dspy.svg)](https://hvtracker.net/agents/dspy)
            
HTML:
            <a href="https://hvtracker.net/agents/dspy"><img src="https://hvtracker.net/badge/dspy.svg" alt="HVTrust"></a>

Other agents in Agent Frameworks

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON