Langfuse

🪢 Open source AI engineering platform: LLM evals, observability, metrics, prompt management, playground, datasets. Integ

Observability & Evaluation TypeScript Grade B Listed NOASSERTION
78.2/100
Rank #77 of 1308
Compare Langfuse

Strong public trust posture, backed by multiple independent signals.

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

Is Langfuse safe? Langfuse scores 78.2/100 (Grade B), ranked #77 of 1308 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.5/10; 91% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Observability & Evaluation

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-07
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.5/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.
93.6
Activity sub-score · out of 100
#5

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 →

Signals refreshed 2026-08-19 06:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
33.4k
Forks
3.6k
Last Push
2026-08-19
today
Commits (4 wk)
611
Downloads (7d)
6,935,809
npm+pypi
HN mentions (30d)
6
Open Issues
300
Rank Change
▼5
was #72

Analysis

HVTrust Dimensions vs Observability & Evaluation

78.2 / 100 · 100.0% confidence

Langfuse Observability & Evaluation average (23 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.7 / 25
1.7 above avg 11.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.2 below avg 13.0
Transparency50% declared license · 50% OSSF Scorecard
14.0 / 17
2.1 above avg 11.9
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
4.9 above avg 15.1
AdoptionLog-scaled stars · package downloads
20.0 / 20
6.1 above avg 13.9

Activity Inputs

93.6 / 100
StarsRepository reach
27.1 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
16.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.5 / 10
OpenSSF Scorecard · scanned Aug 18, 2026
Signed Commits
91%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 9
Maintained 10
Packaging 10
Pinned-Dependencies 7
SAST 10
Security-Policy 9
Signed-Releases -1
Token-Permissions 5
Vulnerabilities 0

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?
91% 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.

Compare Langfuse 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
high confidence
Implemented
Langfuse appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
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
How this surface has changed

Detected changes to Langfuse'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-08-07
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)
2026-06-05
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo

Maintain Langfuse?

For maintainers

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.

Reputation Timeline

Signal history
HVTrust 2Listed 1Grade 1Scorecard 1Score 1Drift 1Rank 1Drift 1
2026-08-07
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)
2026-07-13
Rank Moved
Rank dropped 11 spots (#80 → #91)
2026-06-05
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
2026-05-29
HVTrust Changed
HVTrust up 10.0pts (64.7 → 74.7)
2026-05-28
Activity Score Changed
Activity score up 25pts (68 → 93)
2026-05-27
Scorecard Added
OSSF Scorecard: 6.8/10
2026-05-27
Grade Changed
Trust grade C → B
2026-05-27
HVTrust Changed
HVTrust up 33.0pts (37.7 → 70.7)
2026-05-25
Newly Listed
First tracked at rank #51

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 78.2 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/langfuse.svg)](https://hvtracker.net/agents/langfuse)
HTML:
<a href="https://hvtracker.net/agents/langfuse"><img src="https://hvtracker.net/badge/langfuse.svg" alt="HVTrust"></a>

Other agents in Observability & Evaluation

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · 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