updated 2026-10-21 20:07 UTC

LangChain4j

Repository Website

LangChain4j is an idiomatic, open-source Java library for building LLM-powered applications on the JVM. It offers a unified API over popular LLM providers and vector stores, and makes implementing tool calling (including MCP support), agents and RAG easy. It integrates seamlessly with enterprise…

Agent Frameworks Java Listed Apache-2.0

Is LangChain4j safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.3 / 10
Provenance None
Signed commits 81%
Last push today
Compare LangChain4j

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →
Suggest a correction

In detail: LangChain4j scores 66.5/100 (Grade B), ranked #468 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.3/10; 81% of recent commits are signed; last pushed 2026-10-21. Every point is earned from checkable signals — never paid placement. How scoring works →

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

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships LangChain4j and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/langchain4j/langchain4j, Apache-2.0, last pushed 2026-10-21. 81% 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.3/10 (scanned Oct 14, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection8
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies10
    All 18 Scorecard checks
    Binary-Artifacts 9
    Branch-Protection 8
    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 10
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. LangChain4j is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-09-10 OSSF Scorecard: 6.6/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues LangChain4j’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 LangChain4j compares in Agent Frameworks

  1. #37 Astrid 67.1 +0.6
  2. #38 PraisonAI 67.0 +0.5
  3. #39 LangChain4j 66.5 this agent
  4. #40 VoltAgent 66.3 −0.2
  5. #41 Semantic Kernel 66.2 −0.3

Bars show each HVTrust score; the tick marks LangChain4j’s 66.5.

Where the 66.5 comes from

HVTrust dimensions vs the Agent Frameworks average

66.5 / 100 · 100.0% confidence

LangChain4j Agent Frameworks average (130 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.9 / 25
1.9 above avg 10.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
13.9 / 17
1.4 above avg 12.5
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.3 above avg 14.7
AdoptionLog-scaled stars · package downloads
9.9 / 20
1.3 below avg 11.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-14
Rank Moved
Rank dropped 25 spots (#439 → #464)
2026-10-12
Rank Moved
Rank dropped 12 spots (#427 → #439)
2026-10-09
Rank Moved
Rank dropped 18 spots (#405 → #423)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.3/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 LangChain4j View Agent Frameworks Report missing data
90.6
Activity sub-score · out of 100
#39
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 B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-21 20:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-21

Activity & Reach

Stars
13.3k
Forks
2.6k
Last Push
2026-10-21
today
Commits (4 wk)
128
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
653
Rank Change
▼2
was #466

Analysis

Activity Inputs

90.6 / 100
StarsRepository reach
24.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.9 / 20

Common questions about LangChain4j

LangChain4j 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 LangChain4j publish package provenance?
No published build provenance is currently detected for LangChain4j. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does LangChain4j have an OpenSSF Scorecard?
LangChain4j has an OpenSSF Scorecard score of 6.3/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 LangChain4j actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does LangChain4j use?
LangChain4j ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are LangChain4j's commits signed?
81% of the last 100 commits to LangChain4j 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
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
N/A
No package source configured
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 LangChain4j'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-23
Mcp Status Changed
Detected MCP server support changed: none → declared

Maintain LangChain4j?

For maintainers

HVTrust scores LangChain4j 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
Rank 5Listed 2HVTrust 2Grade 2Scorecard 1Delisted 1MCP 1
2026-10-14
Rank Moved
Rank dropped 25 spots (#439 → #464)
2026-10-12
Rank Moved
Rank dropped 12 spots (#427 → #439)
2026-10-09
Rank Moved
Rank dropped 18 spots (#405 → #423)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Grade Changed
Trust grade C → B
2026-09-23
Rank Moved
Rank dropped 93 spots (#297 → #390)
2026-09-23
HVTrust Changed
HVTrust up 12.7pts (54.5 → 67.2)
2026-09-22
Newly Listed
First tracked at rank #297
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-10
Scorecard Added
OSSF Scorecard: 6.6/10
2026-09-10
Grade Changed
Trust grade D → B
2026-09-10
Rank Moved
Rank rose 913 spots (#1299 → #386)
2026-09-10
HVTrust Changed
HVTrust up 40.3pts (26.6 → 66.9)
2026-09-08
Newly Listed
First tracked at rank #1294
GitHub → Website →

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON