Is LangWatch safe?
LangWatch scores 72.7/100 (Grade B), ranked #67 of 328 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-07-11. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Promising trust profile, but some evidence still deserves review.
72.7/100 · Grade B
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
11.9/25
What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
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)
Maintainer Checklist
Add Scorecard coverageExpose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 refreshed2026-07-11 05:00 UTC·Repo last pushed today
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
3.4k
Forks
328
Last Push
2026-07-11
today
Commits (4 wk)
433
Downloads (7d)
88,342
npm+pypi
HN mentions (30d)
1
Open Issues
527
Rank Change
=
was #67
Analysis
HVTrust Dimensions
72.7 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
11.9 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
15.1 / 20
Activity Inputs
82.9 / 100
StarsRepository reach
21.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
11.7 / 20
Supply Chain Trust
Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
89%
of last 100 commits verified
Is LangWatch safe?
LangWatch has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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.
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.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
browser
code
database
shell
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.
Detected MCP server support changed: none → implemented
2026-06-05
Provenance Added
Package provenance attestation detected
Maintain LangWatch?
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.
