updated 2026-08-25 05:32 UTC

LangChain

langchain-ai/langchain

The agent engineering platform.

Agent Frameworks Python Grade A Listed MIT
82.1/100
Rank #63 of 1308
Compare LangChain

How does it stack up against its Agent Frameworks 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 LangChain safe? LangChain scores 82.1/100 (Grade A), ranked #63 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.6/10; 100% 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 Agent Frameworks

#9 DawnAI — 84.8 (A) → #10 OpenAI Agents SDK — 84.8 (A) → #12 CrewAI — 81.8 (A) → #13 Threadplane — 81.6 (A) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.6/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.
Compare with another agent Get email alerts for LangChain View Agent Frameworks Report missing data
100.0
Activity sub-score · out of 100
#11
In Agent Frameworks

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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-25 05:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars
144.9k
Forks
24.2k
Last Push
2026-08-25
today
Commits (4 wk)
192
Downloads (7d)
78,314,260
pypi
HN mentions (30d)
9
Open Issues
336
Rank Change
=
was #63

Analysis

HVTrust Dimensions vs Agent Frameworks

82.1 / 100 · 100.0% confidence

LangChain Agent Frameworks average (119 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.2 / 25
5.1 above avg 8.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
14.1 / 17
2.6 above avg 11.5
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.9 above avg 14.1
AdoptionLog-scaled stars · package downloads
20.0 / 20
8.7 above avg 11.3

Activity Inputs

100.0 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
20 / 20

Supply Chain Trust

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

Is LangChain safe?

Public supply-chain signals for LangChain are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but LangChain carries less obvious unverified-evidence risk than projects with thin signals.
Does LangChain publish package provenance?
No published build provenance is currently detected for LangChain. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does LangChain have an OpenSSF Scorecard?
LangChain has an OpenSSF Scorecard score of 6.6/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 LangChain actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does LangChain use?
LangChain ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are LangChain's commits signed?
100% of the last 100 commits to LangChain 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.

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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain LangChain?

For maintainers

HVTrust scores LangChain 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
HVTrust 1
2026-05-29
HVTrust Changed
HVTrust up 10.0pts (65.0 → 75.0)
GitHub → PyPI: langchain

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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