Is Langfuse safe to use?

Langfuse has an HVTrust score of 79.8/100 (Grade B), ranked #162 of 1371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Langfuse?

Langfuse scores 79.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 35.6k GitHub stars and is categorized under Observability & Evaluation.

Langfuse

Repository

Website

🪢 Open source agent evals & observability: Trace, evaluate, and improve LLM applications with one open platform.

Observability & Evaluation TypeScript Listed NOASSERTION

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

OSSF Scorecard 7.4 / 10

Provenance None

Signed commits 94%

Last push today

Advisories None known

Compare Langfuse

How does it stack up against its Observability & Evaluation neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Langfuse scores 79.8/100 (Grade B), ranked #162 of 1371 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.4/10; 94% of recent commits are signed; no published advisory affects its latest release (langfuse, langfuse); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Langfuse 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 packagesnpm publish --provenance from CI +13.2 → 93.0 A · #1 of 26
Raise the OSSF Scorecard from 7.4 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 1, Branch-Protection 3 +3.0 → 82.8 A · #6 of 26

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Langfuse 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/langfuse/langfuse, NOASSERTION, last pushed 2026-10-09. 94% 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.4/10 (scanned Oct 4, 2026). The checks that decide who can get a change released:
- Code Review1
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions5
- Pinned Dependencies7
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 10

License 9

Maintained 10

Packaging 10

Pinned-Dependencies 7

SAST 10

Security-Policy 9

Signed-Releases -1

Token-Permissions 5

Vulnerabilities 3
Published packages Not linked
- npm langfuse Source link points to langfuse/langfuse-js, same owner No build attestation
- PyPI langfuse Source link points to langfuse/langfuse-python, same owner 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 releases checked: langfuse 3.39.2, langfuse 4.17.0. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

2026-08-07 Provenance drift warning cleared (now: unknown)

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 Langfuse’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 Langfuse compares in Observability & Evaluation

Bars show each HVTrust score; the tick marks Langfuse’s 79.8.

Where the 79.8 comes from

HVTrust dimensions vs the Observability & Evaluation average

79.8 / 100 · 100.0% confidence

Langfuse Observability & Evaluation average (26 agents)

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

14.0 / 25

2.8 above avg 11.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

14.8 / 17

2.8 above avg 12.0

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

4.7 above avg 15.3

AdoptionLog-scaled stars · package downloads

20.0 / 20

6.6 above avg 13.4

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-10-04

Rank Moved

Rank rose 15 spots (#169 → #154)

2026-09-23

Rank Moved

Rank dropped 82 spots (#76 → #158)

2026-09-21

Rank Moved

Rank rose 83 spots (#158 → #75)

Maintainer Checklist

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with Promptfoo Get email alerts for Langfuse View Observability & Evaluation Report missing data

94.0

Activity sub-score · out of 100

In Observability & Evaluation

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-09

Activity & Reach

Stars

35.6k

Forks

4.0k

Last Push

2026-10-09

today

Commits (4 wk)

795

Downloads (7d)

6,386,592

pypi

HN mentions (30d)

Open Issues

320

Rank Change

▲1

was #163

Analysis

Activity Inputs

94.0 / 100

StarsRepository reach

27.3 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

16.7 / 20

Common questions about Langfuse

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

94% 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

Langfuse vs Promptfoo → Langfuse vs MLflow → Langfuse vs OpenLLMetry →

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

2 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-09-02

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-08-07

Drift Warning Cleared

Provenance drift warning cleared (now: unknown)

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-10-04

Rank Moved

Rank rose 15 spots (#169 → #154)

2026-09-23

Rank Moved

Rank dropped 82 spots (#76 → #158)

2026-09-21

Rank Moved

Rank rose 83 spots (#158 → #75)

2026-09-09

Rank Moved

Rank dropped 11 spots (#160 → #171)

2026-09-07

Rank Moved

Rank dropped 14 spots (#151 → #165)

2026-09-05

Rank Moved

Rank dropped 26 spots (#119 → #145)

2026-09-02

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-08-31

Rank Moved

Rank dropped 14 spots (#94 → #108)

2026-08-26

Rank Moved

Rank dropped 10 spots (#78 → #88)

2026-08-07

Drift Warning Cleared

Provenance drift warning cleared (now: unknown)

2026-07-13

Rank Moved

Rank dropped 11 spots (#80 → #91)

GitHub → Website → PyPI: langfuse npm: langfuse

Embed Badge Badge guide for maintainers →

For maintainers

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

Langfuse

How Langfuse 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 Langfuse compares in Observability & Evaluation

Where the 79.8 comes from

HVTrust dimensions vs the Observability & Evaluation average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Langfuse

Compare Langfuse head-to-head

AI agent surface

Maintain Langfuse?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Observability & Evaluation