updated 2026-09-08 14:33 UTC

LangChain4j

langchain4j/langchain4j

LangChain4j is an idiomatic, open-source Java library for building LLM-powered applications on the JVM. It offers a unif

Agent Frameworks Java Grade D Listed Apache-2.0
26.6/100
Rank #1293 of 1328
Compare LangChain4j

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-09-08 · 0d ago
Recent change
New

Is LangChain4j safe? LangChain4j scores 26.6/100 (Grade D), ranked #1293 of 1328 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 79% of recent commits are signed; last pushed 2026-09-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#114 BabyAGI — 29.4 (D) → #115 Yunjue-Agent — 29.2 (D) → #117 JARVIS / HuggingGPT — 26.5 (D) → #118 DocsGPT — 23.4 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-08
Newly Listed
First tracked at rank #1293
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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.5
Activity sub-score · out of 100
#116
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-08 14:33 UTC · Repo last pushed today

Activity & Reach

Stars
13.0k
Forks
2.5k
Last Push
2026-09-08
today
Commits (4 wk)
192
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
613
Rank Change
NEW

Analysis

HVTrust Dimensions vs Agent Frameworks

26.6 / 100 · 50.0% confidence

LangChain4j Agent Frameworks average (122 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.0 / 25
5.5 below 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
8.5 / 17
3.8 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.0 above avg 14.0
AdoptionLog-scaled stars · package downloads
9.9 / 20
1.3 below avg 11.2

Activity Inputs

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

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
79%
of last 100 commits verified

Is LangChain4j safe?

Public trust evidence for LangChain4j is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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?
No OpenSSF Scorecard data is currently published for LangChain4j. 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 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?
79% 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

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
Listed 1
2026-09-08
Newly Listed
First tracked at rank #1293
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 26.6 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON