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 today
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
28.5k
Forks
2.9k
Last Push
2026-06-04
today
Commits (4 wk)
284
Downloads (7d)
5,177,025
pypi
HN mentions (30d)
2
Open Issues
663
Rank Change
▼4
was #30
Analysis
HVTrust Dimensions
77.4 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
13.0 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
14.0 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
19.6 / 20
Activity Inputs
92.8 / 100
StarsRepository reach
26.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
16.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.5 / 10
via deps.dev · OpenSSF
Signed Commits
98%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection4
CI-Tests10
CII-Best-Practices0
Code-Review2
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License9
Maintained10
Packaging-1
Pinned-Dependencies6
SAST10
Security-Policy9
Signed-Releases-1
Token-Permissions5
Vulnerabilities0
Is Langfuse safe?
Public supply-chain signals for Langfuse are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Langfuse carries less obvious unverified-evidence risk than projects with thin signals.
Does Langfuse publish package provenance?
No published build provenance is currently detected for Langfuse. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Langfuse have an OpenSSF Scorecard?
Langfuse has an OpenSSF Scorecard score of 6.5/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 Langfuse actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Langfuse use?
Langfuse ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Langfuse's commits signed?
98% of the last 100 commits to Langfuse 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.
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 Langfuse?
HVTrust scores Langfuse 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.
