Loading the registry…
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.
1 critical finding reported by 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 -- nerlo-ingest-jr7fbyiq
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
7 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.
v1.4.0
0 findings · 0.6s
v2.0.11
6 findings · 6.9s
v0.3.74
3 findings · 3.7s
v0.2.0
0 findings · 3.6s
v0.2.0
0 findings · 3.6s
v0.71.0
59 findings · 0.2s
v2.3.8
61 findings · 7.6s
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 · 1.1s
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
7 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 11, 2026 | Flagged48 | — | agentshield: completecisco-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 |
| Jul 30, 2026 | Flagged47 | — | cisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicable | completed |
| Jul 21, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completetrivy: completeosv-scanner: complete | rejected |
| Jul 20, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completetrivy: completeosv-scanner: complete | rejected |
| Jul 20, 2026 | Scan Halted | Clean → Flagged | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completetrivy: completeosv-scanner: complete | rejected |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·n/a: not applicable | completed |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·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 129 findings across every scanner that examined this package. None of the 1 finding rated critical by their scanner were dismissed.
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.
1 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: OVERSIZED_FILE · Files: /repo/docs/demo/minimal.mp4 · reported by cisco-skill-scanner
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
2 AAK-LEGAL-002
Files: package.json, ts_functions/package.json · reported by agent-audit-kit
2 GHSA-jm82-fx9c-mx94
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 CVE-2025-13466
Files: package-lock.json · reported by trivy
1 CVE-2025-15284
Files: package-lock.json · reported by trivy
1 CVE-2025-59343
Files: package-lock.json · reported by trivy
1 CVE-2025-62707
Files: uv.lock · reported by trivy
1 CVE-2025-62708
The model could have called any of these a false positive and did not.
1 CVE-2026-27024
Files: uv.lock · reported by trivy
1 CVE-2026-27025
Files: uv.lock · reported by trivy
Critical vulnerability and numerous high-severity issues detected.
A critical vulnerability (PYSEC-2026-2120) is present in a dependency listed in `/repo/uv.lock`. Additionally, 24 high-severity vulnerabilities are identified across dependencies in `package-lock.json` and `uv.lock`. The artifact also exhibits undeclared network egress capabilities.
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.
Files: uv.lock · reported by trivy
1 CVE-2025-64756
Files: package-lock.json · reported by trivy
1 CVE-2025-66019
Files: uv.lock · reported by trivy
1 CVE-2025-66414
Files: package-lock.json · reported by trivy
1 CVE-2025-71176
Files: uv.lock · reported by trivy
1 CVE-2026-0621
Files: package-lock.json · reported by trivy
1 CVE-2026-12590
Files: package-lock.json · reported by trivy
1 CVE-2026-22690
Files: uv.lock · reported by trivy
1 CVE-2026-22691
Files: uv.lock · reported by trivy
1 CVE-2026-2391
Files: package-lock.json · reported by trivy
1 CVE-2026-24688
Files: uv.lock · reported by trivy
1 CVE-2026-25547
Files: package-lock.json · reported by trivy
1 CVE-2026-26996
Files: package-lock.json · reported by trivy
1 CVE-2026-27026
Files: uv.lock · reported by trivy
1 CVE-2026-27628
Files: uv.lock · reported by trivy
1 CVE-2026-27888
Files: uv.lock · reported by trivy
1 CVE-2026-27903
Files: package-lock.json · reported by trivy
1 CVE-2026-27904
Files: package-lock.json · reported by trivy
1 CVE-2026-28351
Files: uv.lock · reported by trivy
1 CVE-2026-28804
Files: uv.lock · reported by trivy
1 CVE-2026-31826
Files: uv.lock · reported by trivy
1 CVE-2026-32274
Files: uv.lock · reported by trivy
1 CVE-2026-33123
Files: uv.lock · reported by trivy
1 CVE-2026-33699
Files: uv.lock · reported by trivy
1 CVE-2026-40260
Files: uv.lock · reported by trivy
1 CVE-2026-41168
Files: uv.lock · reported by trivy
1 CVE-2026-41312
Files: uv.lock · reported by trivy
1 CVE-2026-41313
Files: uv.lock · reported by trivy
1 CVE-2026-41314
Files: uv.lock · reported by trivy
1 CVE-2026-4539
Files: uv.lock · reported by trivy
1 CVE-2026-48155
Files: uv.lock · reported by trivy
1 CVE-2026-48156
Files: uv.lock · reported by trivy
1 CVE-2026-48735
Files: uv.lock · reported by trivy
1 CVE-2026-4923
Files: package-lock.json · reported by trivy
1 CVE-2026-4926
Files: package-lock.json · reported by trivy
1 CVE-2026-49460
Files: uv.lock · reported by trivy
1 CVE-2026-49461
Files: uv.lock · reported by trivy
1 CVE-2026-54530
Files: uv.lock · reported by trivy
1 CVE-2026-54531
Files: uv.lock · reported by trivy
1 CVE-2026-54651
Files: uv.lock · reported by trivy
1 CVE-2026-59935
Files: uv.lock · reported by trivy
1 CVE-2026-59936
Files: uv.lock · reported by trivy
1 CVE-2026-59937
Files: uv.lock · reported by trivy
1 CVE-2026-59938
Files: uv.lock · reported by trivy
1 CVE-2026-71852
Files: uv.lock · reported by trivy
1 CVE-2026-71870
Files: uv.lock · reported by trivy
1 CVE-2026-82398
Files: uv.lock · reported by trivy
1 CVE-2026-82417
Files: package-lock.json · reported by trivy
1 CVE-2026-84309
Files: uv.lock · reported by trivy
1 CVE-2026-84310
Files: uv.lock · reported by trivy
1 CVE-2026-84311
Files: uv.lock · reported by trivy
1 CVE-2026-8723
Files: package-lock.json · reported by trivy
1 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/latex_mcp_server/functions/latex_ops.py · reported by cisco-skill-scanner
1 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-23w6-3w8w-8484
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-27v5-c462-wpq7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4mjr-xmp4-gh2g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5j98-mcp5-4vw2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6rw7-vpxm-498p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-763m-79hh-57f2
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-7h2j-956f-4vf2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8r9q-7v3j-jr4g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fc8x-2rww-xw9m
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-j3q9-mxjg-w52f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jp53-mhqp-8xcg
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vj76-c3g6-qr5v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w48q-cv73-mx4w
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w7fw-mjwx-w883
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wqch-xfxh-vrr4
Files: /repo/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 PYSEC-2026-1827
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1828
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1829
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1831
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1832
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1833
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1845
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2120
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2121
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2987
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3004
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3005
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3006
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3007
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3009
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3010
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3011
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3012
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3013
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3014
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3015
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3016
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3017
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3018
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3019
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3020
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3021
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3022
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3023
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3024
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3025
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3026
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3027
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3610
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3611
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3612
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3613
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3655
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3656
Files: /repo/uv.lock · reported by osv-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 TOOL_ABUSE_UNDECLARED_NETWORK
Files: /repo/repo/README.md · reported by cisco-skill-scanner
Showing 25 of 26; the rest are in the per-scanner reports above.