Haystack

Open-source AI orchestration framework for building context-engineered, production-ready LLM applications. Design modula

Agent Frameworks Python Grade A Listed Apache-2.0
96.9/100
Rank #1 of 1283
Compare Haystack

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-11 · 0d ago
Recent change
No recent signal change

Is Haystack safe? Haystack scores 96.9/100 (Grade A), ranked #1 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 9.4/10; 100% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Maintainer Checklist
Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.
92.7
Activity sub-score · out of 100
#1

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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 refreshed 2026-08-11 21:02 UTC · Repo last pushed today

Activity & Reach

Stars
26.2k
Forks
3.0k
Last Push
2026-08-11
today
Commits (4 wk)
262
Downloads (7d)
244,109
pypi
HN mentions (30d)
Open Issues
66
Rank Change
=
was #1

Analysis

HVTrust Dimensions vs Agent Frameworks

96.9 / 100 · 100.0% confidence

Haystack Agent Frameworks average (118 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
24.2 / 25
16.1 above avg 8.1
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.4 above avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
16.5 / 17
4.9 above avg 11.6
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.6 above avg 14.4
AdoptionLog-scaled stars · package downloads
17.8 / 20
6.4 above avg 11.4

Activity Inputs

92.7 / 100
StarsRepository reach
26.5 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
16.2 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
9.4 / 10
OpenSSF Scorecard · scanned Aug 11, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 8
CI-Tests 10
CII-Best-Practices 5
Code-Review 10
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 10
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 5
SAST 8
Security-Policy 10
Signed-Releases -1
Token-Permissions 10
Vulnerabilities 10

Is Haystack safe?

Public supply-chain signals for Haystack are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Haystack carries less obvious unverified-evidence risk than projects with thin signals.
Does Haystack publish package provenance?
Yes. Haystack's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Haystack have an OpenSSF Scorecard?
Haystack has an OpenSSF Scorecard score of 9.4/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 Haystack actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Haystack use?
Haystack ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Haystack's commits signed?
100% of the last 100 commits to Haystack 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.

Compare Haystack head-to-head

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
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
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
How this surface has changed

Detected changes to Haystack's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-05-24
Provenance Added
Package provenance attestation detected

Maintain Haystack?

For maintainers

HVTrust scores Haystack 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.

Reputation Timeline

Signal history
Scorecard 1Provenance 1Rank 1Score 1HVTrust 1
2026-05-29
HVTrust Changed
HVTrust up 10.0pts (80.1 → 90.1)
2026-05-28
Activity Score Changed
Activity score up 25pts (67 → 92)
2026-05-25
Rank Moved
Rank dropped 21 spots (#32 → #53)
2026-05-24
Provenance Added
Package provenance attestation detected
2026-05-24
Scorecard Added
OSSF Scorecard: 5.3/10

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 96.9 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/haystack.svg)](https://hvtracker.net/agents/haystack)
HTML:
<a href="https://hvtracker.net/agents/haystack"><img src="https://hvtracker.net/badge/haystack.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
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON