LangChain

The agent engineering platform.

Agent Frameworks Python Listed MIT

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

OSSF Scorecard 6.2 / 10
Provenance None
Signed commits 100%
Last push yesterday
Advisories None known
Compare LangChain

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →
Suggest a correction

In detail: LangChain scores 83.3/100 (Grade A), ranked #110 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 6.2/10; 100% of recent commits are signed; no published advisory affects its latest release (langchain); last pushed 2026-10-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How LangChain 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.

Chain of custody

Scanners check what the code says. This traces who ships LangChain 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.

  1. Source Signed

    github.com/langchain-ai/langchain, MIT, last pushed 2026-10-08. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.2/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies8
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 2
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 8
    SAST 9
    Security-Policy 9
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 4
  3. Published packages Linked, not attested

    • PyPI langchain Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: langchain 1.4.3. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of LangChain.

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 LangChain’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.

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 LangChain compares in Agent Frameworks

  1. #9 Agno 87.4 +4.1
  2. #10 Threadplane 84.0 +0.7
  3. #11 LangChain 83.3 this agent
  4. #12 Reef 83.0 −0.3
  5. #13 DawnAI 82.3 −1.0

Bars show each HVTrust score; the tick marks LangChain’s 83.3.

Where the 83.3 comes from

HVTrust dimensions vs the Agent Frameworks average

83.3 / 100 · 100.0% confidence

LangChain Agent Frameworks average (129 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.8 / 25
3.3 above avg 9.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
13.8 / 17
1.8 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
6.3 above avg 13.6
AdoptionLog-scaled stars · package downloads
20.0 / 20
9.2 above avg 10.8

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-06
Rank Moved
Rank dropped 12 spots (#101 → #113)
2026-10-01
Rank Moved
Rank rose 11 spots (#110 → #99)
2026-09-23
Rank Moved
Rank dropped 45 spots (#62 → #107)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.2/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.
100.0
Activity sub-score · out of 100
#11

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-10-09 08:15 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
147.4k
Forks
24.7k
Last Push
2026-10-08
yesterday
Commits (4 wk)
224
Downloads (7d)
37,870,116
pypi
HN mentions (30d)
13
Open Issues
521
Rank Change
=
was #110

Analysis

Activity Inputs

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

Common questions about LangChain

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.2/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
high confidence
Implemented
LangChain appears to expose MCP server capabilities.
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
How this surface has changed

Detected changes to LangChain'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-04
Mcp Status Changed
Detected MCP server support changed: none → implemented

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.

Reputation Timeline

Signal history
Rank 7MCP 1
2026-10-06
Rank Moved
Rank dropped 12 spots (#101 → #113)
2026-10-01
Rank Moved
Rank rose 11 spots (#110 → #99)
2026-09-23
Rank Moved
Rank dropped 45 spots (#62 → #107)
2026-09-21
Rank Moved
Rank rose 44 spots (#106 → #62)
2026-09-05
Rank Moved
Rank dropped 22 spots (#68 → #90)
2026-09-04
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-04
Rank Moved
Rank rose 12 spots (#80 → #68)
2026-08-31
Rank Moved
Rank dropped 15 spots (#74 → #89)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 83.3 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.4 · Raw JSON