Is LangWatch safe to use?

LangWatch has an HVTrust score of 75.7/100 (Grade B), ranked #92 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for LangWatch?

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

LangWatch

langwatch/langwatch

The platform for LLM evaluations and AI agent testing

Observability & Evaluation TypeScript Grade B Listed Apache-2.0

75.7/100

Rank #92 of 1308

Compare LangWatch

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

Pick any agent to compare →

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-25 · 0d ago

Recent change

No recent signal change

Is LangWatch safe? LangWatch scores 75.7/100 (Grade B), ranked #92 of 1308 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 89% of recent commits are signed; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Observability & Evaluation

#5 Langfuse — 78.4 (B) → #6 Evidently — 75.8 (B) → #8 Arize Phoenix — 74.6 (B) → #9 Agenta — 70.8 (B) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

Compare with MLflow Get email alerts for LangWatch View Observability & Evaluation Report missing data

83.1

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-08-11 2026-08-25

Activity & Reach

Stars

3.5k

Forks

352

Last Push

2026-08-25

today

Commits (4 wk)

693

Downloads (7d)

88,342

npm+pypi

HN mentions (30d)

Open Issues

652

Rank Change

was #92

Analysis

HVTrust Dimensions vs Observability & Evaluation

75.7 / 100 · 100.0% confidence

LangWatch Observability & Evaluation average (23 agents)

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

11.9 / 25

1.0 above avg 10.9

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.0 above avg 13.0

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.4 below avg 11.9

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.1 above avg 14.9

AdoptionLog-scaled stars · package downloads

15.1 / 20

1.1 above avg 14.0

Activity Inputs

83.1 / 100

StarsRepository reach

21.3 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

11.8 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

—

Not available

Signed Commits

89%

of last 100 commits verified

Is LangWatch safe?

Public supply-chain signals for LangWatch are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but LangWatch carries less obvious unverified-evidence risk than projects with thin signals.

Does LangWatch publish package provenance?

Yes. LangWatch's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does LangWatch have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for LangWatch. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is LangWatch actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does LangWatch use?

LangWatch ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are LangWatch's commits signed?

89% of the last 100 commits to LangWatch 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 LangWatch head-to-head

LangWatch vs MLflow → LangWatch vs Promptfoo → LangWatch vs Weights & Biases Weave →

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

LangWatch 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

medium confidence

Partial

Some package metadata matches; some source metadata is missing

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 LangWatch'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-06-05

Provenance Added

Package provenance attestation detected

Maintain LangWatch?

For maintainers

HVTrust scores LangWatch 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-07-13

Rank Moved

Rank dropped 10 spots (#67 → #77)

2026-06-16

Scorecard Removed

OSSF Scorecard no longer detected

2026-06-16

Grade Changed

Trust grade A → B

2026-06-16

Rank Moved

Rank dropped 30 spots (#33 → #63)

2026-06-16

HVTrust Changed

HVTrust down 9.8pts (83.1 → 73.3)

2026-06-15

Scorecard Added

OSSF Scorecard: 4.8/10

2026-06-15

Grade Changed

Trust grade B → A

2026-06-15

Rank Moved

Rank rose 28 spots (#61 → #33)

2026-06-15

HVTrust Changed

HVTrust up 10.0pts (73.1 → 83.1)

2026-06-13

Scorecard Removed

OSSF Scorecard no longer detected

2026-06-13

Grade Changed

Trust grade A → B

2026-06-13

Rank Moved

Rank dropped 32 spots (#33 → #65)

2026-06-13

HVTrust Changed

HVTrust down 10.3pts (83.3 → 73.0)

2026-06-11

Scorecard Added

OSSF Scorecard: 4.8/10

2026-06-11

Grade Changed

Trust grade B → A

2026-06-11

Rank Moved

Rank rose 30 spots (#63 → #33)

2026-06-11

HVTrust Changed

HVTrust up 10.3pts (73.1 → 83.4)

2026-06-10

Scorecard Removed

OSSF Scorecard no longer detected

2026-06-10

Grade Changed

Trust grade A → B

2026-06-10

Rank Moved

Rank dropped 34 spots (#29 → #63)

2026-06-10

HVTrust Changed

HVTrust down 10.4pts (83.5 → 73.1)

2026-06-05

Provenance Added

Package provenance attestation detected

2026-05-29

HVTrust Changed

HVTrust up 9.9pts (57.9 → 67.8)

2026-05-28

Activity Score Changed

Activity score up 25pts (58 → 83)

GitHub → PyPI: langwatch npm: @langwatch/server

Embed Badge Badge guide for maintainers →

For maintainers

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