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.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- conduit
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 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
83 findings · 8.0s
v0.3.74
1 finding · 4.4s
v0.1.0
2 findings · 4.3s
v0.1.0
4 findings · 4.3s
vv0.3.2
Incomplete run
0 findings · 2.2s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 0.8s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·!: incompletenerlo-multi-source ·n/a: not applicable | rejected |
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 90 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 11 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.
76 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: opt.nerlo-rules.nerlo-install-pipe-to-shell, opt.nerlo-rules.nerlo-go-secret-to-network-egress, AAK-HEALTHCARE-AI-004 and 4 more · Files: /repo/examples/agent_swarm_llm/README.md, /repo/examples/langchain_mcp_integration/README.md, /repo/examples/rag_chat_terminal/README.md and 23 more · reported by nerlo-install-instruction, nerlo-behavioral, agent-audit-kit and 1 more
The model could have called any of these a false positive and did not.
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 OVERSIZED_FILE
Files: /repo/bin/langchain_ollama · reported by cisco-skill-scanner
1 YARA_prompt_injection_unicode_steganography
Files: /repo/ConduitBanner.png · reported by cisco-skill-scanner
8 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: PIPELINE_TAINT_FLOW, opt.nerlo-rules.nerlo-install-pipe-to-shell, MANIFEST_MISSING_LICENSE and 1 more · Files: /repo/agents/LLM_INTEGRATION.md, /repo/agents/SKILL.md, /repo/SKILL.md and 2 more · reported by cisco-skill-scanner, nerlo-install-instruction, nerlo-behavioral
3 The model did not answer for these findings.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION · Files: /repo/SKILL.md, /repo/swarm/SKILL.md, /repo/agents/SKILL.md · reported by cisco-skill-scanner
Critical findings in database code and shell execution risk.
The artifact includes critical findings in `pgvector.go` that may expose credentials or sensitive data during database interactions. High severity findings also indicate potential shell execution capabilities through installation instructions in `LLM_INTEGRATION.md`. Additional high severity issues suggest insecure data handling or processing in `processors.go`, `utility.go`, and `unified.go`.
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.