Loading the registry…
MCP server for image optimization with URL support
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.
npm: mcp-image-optimizer @ 1.0.3, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- mcp-image-optimizer
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
8 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.5s
v2.0.11
14 findings · 7.4s
v0.3.74
4 findings · 1.4s
v0.1.0
0 findings · 3.1s
v0.1.0
0 findings · 3.1s
v0.1.0
0 findings · 7.3s
v0.71.0
85 findings · 0.3s
v2.3.8
42 findings · 7.6s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.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
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged46 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: 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 145 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 144 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
1 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/src/utils/image.ts · reported by cisco-skill-scanner
144 The model's answer could not be read.
Rules: CVE-2026-42033, CVE-2026-42035, CVE-2026-44494 and 85 more · Files: bun.lock, package-lock.json, /repo/package-lock.json and 11 more · reported by trivy, osv-scanner, agent-audit-kit and 1 more
Artifact has high-severity vulnerabilities and potential for network egress.
The artifact contains high-severity vulnerabilities, including a DNS rebinding risk identified in `package.json`. It also uses the Anthropic SDK in `src/server.ts`, which may facilitate network egress. Additionally, multiple high-severity findings from the 'bearer' scanner are present in `/repo/src/handlers/batch.ts` and `/repo/src/handlers/favicon.ts`, indicating further potential for network communication or other sensitive operations. Several high-severity supply chain vulnerabilities are also present in `package-lock.json`.
Concern level assessed by the review: High. 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.
Showing 18 of 18; the rest are in the per-scanner reports above.