DSPy has an HVTrust score of 75.8/100 (Grade B), ranked #238 of 1378 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 75.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 38.7k GitHub stars and is categorized under Agent Frameworks.

DSPy

Repository Website

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

Agent Frameworks Python Listed MIT

Is DSPy safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.1 / 10

Provenance None

Signed commits 100%

Last push yesterday

Advisories None known

Compare DSPy

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Suggest a correction

In detail: DSPy scores 75.8/100 (Grade B), ranked #238 of 1378 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 7.1/10; 100% of recent commits are signed; no published advisory affects its latest release (dspy); last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How DSPy could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.7 → 90.5 A · #7 of 130
Raise the OSSF Scorecard from 7.1 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Fuzzing 0 +3.9 → 79.7 B · #17 of 130

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships DSPy and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/stanfordnlp/dspy, MIT, last pushed 2026-10-16. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Strong

OpenSSF Scorecard rates the repository's practices 7.1/10 (scanned Oct 14, 2026). The checks that decide who can get a change released:
- Code Review5
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies6
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 5

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
Published packages Not linked
- PyPI dspy Source link isn't a GitHub repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: dspy 3.4.1. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of DSPy.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions

Verify this score yourself

Every build re-issues DSPy’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How DSPy compares in Agent Frameworks

Bars show each HVTrust score; the tick marks DSPy’s 75.8.

Where the 75.8 comes from

HVTrust dimensions vs the Agent Frameworks average

75.8 / 100 · 100.0% confidence

DSPy Agent Frameworks average (130 agents)

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

13.9 / 25

4.0 above avg 9.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

14.5 / 17

2.1 above avg 12.4

Maintenance60% last-push freshness · 40% commit activity

19.2 / 20

4.8 above avg 14.4

AdoptionLog-scaled stars · package downloads

19.2 / 20

7.9 above avg 11.3

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-23

Rank Moved

Rank dropped 129 spots (#86 → #215)

2026-09-21

Rank Moved

Rank rose 125 spots (#209 → #84)

Maintainer Checklist

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

91.6

Activity sub-score · out of 100

#20

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-09-29 2026-10-17

Activity & Reach

Stars

38.7k

Forks

3.4k

Last Push

2026-10-16

yesterday

Commits (4 wk)

Downloads (7d)

1,290,644

pypi

HN mentions (30d)

Open Issues

365

Rank Change

was #238

Analysis

Activity Inputs

91.6 / 100

StarsRepository reach

27.5 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

22.7 / 25

CommunityFork signal

16.4 / 20

Common questions about DSPy

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 7.1/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?

100% 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-09-23

Rank Moved

Rank dropped 129 spots (#86 → #215)

2026-09-21

Rank Moved

Rank rose 125 spots (#209 → #84)

2026-09-07

Rank Moved

Rank dropped 17 spots (#183 → #200)

2026-09-05

Rank Moved

Rank dropped 40 spots (#148 → #188)

2026-08-31

Rank Moved

Rank dropped 18 spots (#113 → #131)

2026-08-26

Rank Moved

Rank dropped 10 spots (#94 → #104)

GitHub → Website → 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.4 · Raw JSON

DSPy

How DSPy could raise its score

Chain of custody

Source Signed

Review and release Strong

Published packages Not linked

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How DSPy compares in Agent Frameworks

Where the 75.8 comes from

HVTrust dimensions vs the Agent Frameworks average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about DSPy

AI agent surface

Maintain DSPy?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Frameworks