Loading the registry…
The publisher performed an authenticated act of publication — proving control of a namespace in the official MCP registry, or appearing in a first-party catalogue an operator curates. That establishes WHO published it. It is not a security finding, and attested artifacts carry Flagged verdicts too.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- workspace
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
18 findings · 8.7s
v0.3.26
15 findings · 2.2s
v0.1.0
0 findings · 28.0s
v0.1.0
0 findings · 28.0s
v0.71.0
3 findings · 0.5s
v2.3.8
9 findings · 7.4s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 11.9s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
No report in this scan: capslock, govulncheck.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 4, 2026 | Flagged51 | — | agentshield: completecisco-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 |
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 45 findings across every scanner that examined this package.
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.
8 AAK-LEGAL-002
Files: scripts/package.json, artifacts/backend-status/package.json, artifacts/api-server/package.json and 5 more · reported by agent-audit-kit
8 HIDDEN_DATA_FILE
Files: /repo/.agents/memory/MEMORY.md, /repo/.replit, /repo/artifacts/api-server/.replit-artifact/artifact.toml and 5 more · reported by cisco-skill-scanner
4 AAK-TASKS-003
Files: artifacts/api-server/src/routes/tasks.ts, lib/db/src/schema/taskAcceptances.ts, lib/db/src/schema/taskHandoffs.ts and 1 more · reported by agent-audit-kit
2 GHSA-frvp-7c67-39w9
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/.agents/memory/SKILL.md · reported by cisco-skill-scanner
2 SECRET_CONNECTION_STRING
Files: /repo/SKILL.md, /repo/artifacts/api-server/vitest.config.ts · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/.agents/memory/SKILL.md · reported by cisco-skill-scanner
1 AAK-MCP-018
Files: artifacts/api-server/src/mcp/tools.ts · reported by agent-audit-kit
1 AAK-SPLUNK-TOKLOG-001
Files: artifacts/api-server/src/middlewares/bearerAuth.ts · reported by agent-audit-kit
1 AAK-SUPPLY-003
Files: package.json · reported by agent-audit-kit
1 CVE-2026-13676
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16221
Files: pnpm-lock.yaml · reported by trivy
1 DATA_EXFIL_JS_NETWORK
Files: /repo/lib/api-client-react/src/custom-fetch.ts · reported by cisco-skill-scanner
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4c8g-83qw-93j6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g7r4-m6w7-qqqr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v245-v573-v5vm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2hh-gcrm-f6hx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 HIDDEN_EXECUTABLE_SCRIPT
Files: /repo/artifacts/mockup-sandbox/src/.generated/mockup-components.ts · reported by cisco-skill-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
Exposed connection strings, hidden executable script, and critical vulnerabilities.
The artifact contains exposed connection strings in `/repo/SKILL.md` and `/repo/artifacts/api-server/vitest.config.ts`, which could lead to credential access. A hidden executable script is present in `/repo/artifacts/mockup-sandbox/src/.generated/mockup-components.ts`, posing a shell execution risk. Additionally, the artifact logs Splunk tokens in `artifacts/api-server/src/middlewares/bearerAuth.ts` and includes multiple high-severity vulnerabilities in its dependencies, as indicated by OSV and Trivy scanners.
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.