Loading the registry…
Analizzatore di documentazione JSON Rust con integrazione Knowledge Graph
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
10 critical findings reported by trivy, osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- mcp-py-json-doc
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
7 findings · 12.7s
v0.3.74
5 findings · 6.0s
v0.1.0
0 findings · 4.0s
v0.1.0
0 findings · 4.0s
v0.71.0
100 findings · 1.9s
v2.3.8
105 findings · 1.6s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 2.4s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged47 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 217 findings across every scanner that examined this package. None of the 10 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 159 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
3 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: AAK-MCP-STDIO-LAUNCHER-INJECT-001, AAK-IPI-WILD-CORPUS-001, AAK-MCP-ATTEST-001 · Files: examples/mcp.json, doc/tokio.json · reported by agent-audit-kit
The model could have called any of these a false positive and did not.
1 AAK-MCP-SDK-CVE-2026-52869-001
Files: uv.lock · reported by agent-audit-kit
1 CVE-2025-53000
Files: uv.lock · reported by trivy
1 CVE-2025-59420
Files: uv.lock · reported by trivy
1 CVE-2025-64340
Files: uv.lock · reported by trivy
1 CVE-2025-66416
Files: uv.lock · reported by trivy
1 CVE-2025-66471
Files: uv.lock · reported by trivy
1 CVE-2025-67221
Files: uv.lock · reported by trivy
101 The model's answer could not be read.
Rules: PYSEC-2026-36, CVE-2026-44727, PYSEC-2026-2537 and 95 more · Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
57 The review budget for this scan was already spent before these findings were reached.
Rules: GHSA-pw6j-qg29-8w7f, CVE-2026-48817, PYSEC-2026-2208 and 48 more · Files: /repo/uv.lock, uv.lock, SECURITY.md and 3 more · reported by osv-scanner, trivy, agent-audit-kit and 1 more
1 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: TOOL_ABUSE_UNDECLARED_NETWORK · Files: /repo/repo/README.md · reported by cisco-skill-scanner
Critical vulnerabilities and sensitive data exposure risks identified.
The artifact contains multiple critical vulnerabilities in its dependencies, as identified by `osv-scanner` and `trivy` in `uv.lock`. High severity findings from `bearer` indicate potential for sensitive data exposure or risky operations within the artifact's own code, specifically in `analyze_rust_code.py`, `explore_kg.py`, `src/main.py`, and `src/native_kg.py`. These findings suggest capabilities that could lead to credential access or data leakage. Reviewing these specific locations is crucial before deployment.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
1 CVE-2025-67726
Files: uv.lock · reported by trivy
1 CVE-2025-71176
Files: uv.lock · reported by trivy
1 CVE-2026-25645
Files: uv.lock · reported by trivy
1 CVE-2026-26007
Files: uv.lock · reported by trivy
1 CVE-2026-28490
Files: uv.lock · reported by trivy
1 CVE-2026-39377
Files: uv.lock · reported by trivy
1 CVE-2026-41425
Files: uv.lock · reported by trivy
1 CVE-2026-42266
Files: uv.lock · reported by trivy
1 CVE-2026-44897
Files: uv.lock · reported by trivy
1 CVE-2026-49476
Files: uv.lock · reported by trivy
1 CVE-2026-49853
Files: uv.lock · reported by trivy
1 CVE-2026-49855
Files: uv.lock · reported by trivy
1 CVE-2026-59922
Files: uv.lock · reported by trivy
1 CVE-2026-59930
Files: uv.lock · reported by trivy
1 CVE-2026-59950
Files: uv.lock · reported by trivy
1 CVE-2026-73417
Files: uv.lock · reported by trivy
1 GHSA-537c-gmf6-5ccf
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-78cv-mqj4-43f7
Files: uv.lock · reported by trivy
1 GHSA-c2jp-c369-7pvx
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-gj48-438w-jh9v
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-pppj-hq3g-57pj
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-rcfx-77hg-w2wv
Files: uv.lock · reported by trivy
1 PYSEC-2025-267
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1200
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1201
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1364
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1617
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-188
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1998
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2187
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2209
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2210
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2212
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2213
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2229
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2230
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2287
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2475
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2476
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2532
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2682
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3552
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3553
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3554
Files: /repo/uv.lock · reported by osv-scanner
Showing 12 of 12; the rest are in the per-scanner reports above.