Is JavaLens safe to use?

JavaLens has an HVTrust score of 69.5/100 (Grade B), ranked #386 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for JavaLens?

JavaLens scores 69.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 47 GitHub stars and is categorized under MCP Servers.

JavaLens

Repository by pzalutski-pixel

MCP server providing semantic Java code analysis for AI agents. Built on Eclipse JDT with tools for navigation, refactoring, search, and metrics.

MCP Servers Java Listed MIT

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

OSSF Scorecard 3.2 / 10

Provenance Attested

Signed commits 0%

Last push 23d ago

Advisories None known

Compare JavaLens

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: JavaLens scores 69.5/100 (Grade B), ranked #386 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.2/10; recent commits are unsigned; no published advisory affects its latest release (javalens-mcp); last pushed 2026-10-18. Every point is earned from checkable signals — never paid placement. How scoring works →

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

Raise the OSSF Scorecard from 3.2 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +12.2 → 81.7 A · #71 of 778
Sign every commit0% signed today +5.0 → 74.5 B · #162 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

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

Source Unsigned

github.com/pzalutski-pixel/javalens-mcp, MIT, last pushed 2026-10-18. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 3.2/10 (scanned Nov 8, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0
Published packages Linked and attested
- npm javalens-mcp Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: javalens-mcp 1.5.3. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

2026-10-19 Package provenance attestation detected
2026-08-30 OSSF Scorecard: 3.8/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues JavaLens’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 JavaLens compares in MCP Servers

Bars show each HVTrust score; the tick marks JavaLens’s 69.5.

Where the 69.5 comes from

HVTrust dimensions vs the MCP Servers average

69.5 / 100 · 100.0% confidence

JavaLens MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

11.5 / 25

0.7 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

11.2 / 17

1.1 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

15.4 / 20

3.2 above avg 12.2

AdoptionLog-scaled stars · package downloads

7.4 / 20

in line with avg 7.6

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-11-10

Rank Moved

Rank dropped 13 spots (#373 → #386)

2026-11-09

Rank Moved

Rank dropped 16 spots (#357 → #373)

2026-11-06

Rank Moved

Rank dropped 17 spots (#338 → #355)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.2/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent View MCP Servers Report missing data

52.6

Activity sub-score · out of 100

#227

In MCP Servers

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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-10-18

23 days ago

Commits (4 wk)

Downloads (7d)

362

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼13

was #373

Analysis

Activity Inputs

52.6 / 100

StarsRepository reach

10.1 / 30

FreshnessLast push recency

21.8 / 25

ActivityRecent commits

15.3 / 25

CommunityFork signal

5.3 / 20

Common questions about JavaLens

JavaLens 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 JavaLens publish package provenance?

Yes. JavaLens's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does JavaLens have an OpenSSF Scorecard?

JavaLens has an OpenSSF Scorecard score of 3.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 JavaLens actively maintained?

Maintained. Last push was 23 days ago.

What license does JavaLens use?

JavaLens ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are JavaLens's commits signed?

0% of the last 100 commits to JavaLens 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

Implemented

JavaLens 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 JavaLens'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-10-19

Provenance Added

Package provenance attestation detected

2026-10-11

Activity Resumed

Activity resumed

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-14

Activity Went Stale

No commits for 90 days

Maintain JavaLens?

For maintainers

HVTrust scores JavaLens 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

2026-11-10

Rank Moved

Rank dropped 13 spots (#373 → #386)

2026-11-09

Rank Moved

Rank dropped 16 spots (#357 → #373)

2026-11-06

Rank Moved

Rank dropped 17 spots (#338 → #355)

2026-11-05

Rank Moved

Rank dropped 11 spots (#327 → #338)

2026-10-25

Rank Moved

Rank rose 15 spots (#308 → #293)

2026-10-19

Provenance Added

Package provenance attestation detected

2026-10-19

Grade Changed

Trust grade C → B

2026-10-19

Rank Moved

Rank rose 434 spots (#741 → #307)

2026-10-19

HVTrust Changed

HVTrust up 14.6pts (58.0 → 72.6)

2026-10-18

Rank Moved

Rank rose 240 spots (#981 → #741)

2026-10-18

HVTrust Changed

HVTrust up 7.0pts (51.0 → 58.0)

2026-10-18

Activity Score Changed

Activity score up 19pts (43 → 62)

2026-10-16

Rank Moved

Rank dropped 10 spots (#962 → #972)

2026-10-11

Activity Resumed

Activity resumed

2026-10-11

Grade Changed

Trust grade D → C

2026-10-11

Rank Moved

Rank rose 186 spots (#1136 → #950)

2026-10-11

HVTrust Changed

HVTrust up 8.2pts (43.0 → 51.2)

2026-10-11

Activity Score Changed

Activity score up 20pts (24 → 44)

2026-10-09

Rank Moved

Rank dropped 12 spots (#1122 → #1134)

2026-10-02

Rank Moved

Rank dropped 12 spots (#1104 → #1116)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 138 spots (#1216 → #1078)

2026-09-23

HVTrust Changed

HVTrust up 26.4pts (17.9 → 44.3)

2026-09-22

Newly Listed

First tracked at rank #1216

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-15

Rank Moved

Rank dropped 37 spots (#1030 → #1067)

2026-09-14

Activity Went Stale

No commits for 90 days

2026-09-12

Rank Moved

Rank dropped 13 spots (#1011 → #1024)

2026-09-11

Rank Moved

Rank dropped 11 spots (#1000 → #1011)

2026-09-09

Rank Moved

Rank dropped 17 spots (#986 → #1003)

2026-09-07

Rank Moved

Rank dropped 43 spots (#934 → #977)

2026-09-06

Rank Moved

Rank dropped 16 spots (#918 → #934)

2026-09-05

Rank Moved

Rank rose 287 spots (#1205 → #918)

2026-09-05

HVTrust Changed

HVTrust up 15.7pts (31.2 → 46.9)

2026-09-04

Rank Moved

Rank dropped 16 spots (#1189 → #1205)

2026-09-03

Rank Moved

Rank dropped 44 spots (#1145 → #1189)

2026-09-02

Rank Moved

Rank dropped 39 spots (#1106 → #1145)

2026-09-01

Rank Moved

Rank dropped 40 spots (#1066 → #1106)

2026-08-31

Rank Moved

Rank dropped 31 spots (#1035 → #1066)

2026-08-30

Scorecard Added

OSSF Scorecard: 3.8/10

2026-08-30

Rank Moved

Rank rose 213 spots (#1248 → #1035)

2026-08-30

HVTrust Changed

HVTrust up 13.3pts (18.1 → 31.4)

2026-08-29

Rank Moved

Rank dropped 18 spots (#1230 → #1248)

2026-08-28

Rank Moved

Rank dropped 12 spots (#1218 → #1230)

2026-08-27

Rank Moved

Rank dropped 11 spots (#1207 → #1218)

2026-08-26

Rank Moved

Rank dropped 39 spots (#1168 → #1207)

2026-08-16

Rank Moved

Rank dropped 24 spots (#1141 → #1165)

GitHub → npm: javalens-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/javalens.svg)](https://hvtracker.net/agents/javalens)
            
HTML:
            <a href="https://hvtracker.net/agents/javalens"><img src="https://hvtracker.net/badge/javalens.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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

JavaLens

How JavaLens could raise its score

Chain of custody

Source Unsigned

Review and release Weak

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How JavaLens compares in MCP Servers

Where the 69.5 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about JavaLens

AI agent surface

Maintain JavaLens?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers