Loading the registry…
Windows Bridge for Claude Communication
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.
38 critical findings reported by cisco-skill-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 -- claude-bridge-windows
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.
v1.4.0
0 findings · 0.5s
v2.0.11
356 findings · 18.0s
v0.3.74
9 findings · 2.1s
v0.1.0
0 findings · 3.1s
v0.1.0
11 findings · 3.1s
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.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: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-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 376 findings across every scanner that examined this package. None of the 38 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 240 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 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_INVALID_NAME, MANIFEST_MISSING_LICENSE · Files: /repo/node_modules/function-bind/.github/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
56 LOW_ANALYZABILITY
Files: /repo/node_modules/range-parser, /repo/node_modules/accepts, /repo/node_modules/type-is and 53 more · reported by cisco-skill-scanner
21 DATA_EXFIL_JS_NETWORK
Files: /repo/node_modules/node-fetch/lib/index.es.js, /repo/node_modules/node-fetch/lib/index.js, /repo/node_modules/node-fetch/lib/index.mjs and 5 more · reported by cisco-skill-scanner
19 TOOL_ABUSE_SYSTEM_MODIFICATION
Files: /repo/scripts/install.sh, /repo/scripts/setup-services.sh · reported by cisco-skill-scanner
12 COMMAND_INJECTION_JS_FUNCTION_CONSTRUCTOR
Files: /repo/node_modules/function-bind/implementation.js, /repo/node_modules/get-intrinsic/index.js, /repo/node_modules/node-fetch/browser.js and 2 more · reported by cisco-skill-scanner
6 COMMAND_INJECTION_EVAL
Files: /repo/node_modules/proxy-addr/index.js, /repo/node_modules/get-intrinsic/index.js · reported by cisco-skill-scanner
6 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/node_modules/mime/src/build.js, /repo/node_modules/send/index.js, /repo/node_modules/mime/mime.js · reported by cisco-skill-scanner
4 AAK-SECRET-007
Files: claude_config/claude_desktop_config.json, claude_config/claude_desktop_config_template.json · reported by agent-audit-kit
4 TOOL_ABUSE_SYSTEM_PACKAGE_INSTALL
Files: /repo/scripts/install.sh · reported by cisco-skill-scanner
2 AAK-SECRET-005
Files: key.pem, cert.pem · reported by agent-audit-kit
1 AAK-IPI-WILD-CORPUS-001
Files: README.md · reported by agent-audit-kit
1 AAK-SKILL-UNTRUSTED-EXEC-PATH
Files: scripts/install.sh · reported by agent-audit-kit
1 YARA_credential_harvesting_generic
Files: /repo/key.pem · reported by cisco-skill-scanner
177 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: opt.nerlo-rules.nerlo-install-pipe-to-shell, opt.nerlo-rules.nerlo-install-fetch-raw-then-run, PIPELINE_TAINT_FLOW and 6 more · Files: /repo/INSTALL.md, /repo/README.md, /repo/claude_config/setup_claude_config.sh and 83 more · reported by nerlo-install-instruction, cisco-skill-scanner
62 The review call did not complete.
Rules: AAK-LEGAL-002, HIDDEN_DATA_FILE, EXCESSIVE_FILE_COUNT and 4 more · Files: package.json, /repo/node_modules/side-channel-map/.nycrc, /repo/node_modules/has-symbols/.nycrc and 45 more · reported by agent-audit-kit, cisco-skill-scanner, nerlo-install-instruction
1 The model did not answer for these findings.
Rules: PIPELINE_TAINT_FLOW · Files: /repo/INSTALL.md · reported by cisco-skill-scanner
Critical risks: system modification, command injection, credential access.
The artifact contains critical findings related to system modification, command injection, and credential access. Code in `scripts/install.sh` performs system modifications, and several `node_modules` files show potential for command injection. A credential harvesting finding was identified in `key.pem`, indicating sensitive data exposure.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 24 of 24; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.