Loading the registry…
LightNow Local Proxy for centrally managed MCP client configuration
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.
2 critical findings reported by agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.
This artifact ships from 3 sources and their verdicts differ. The worst is github (Flagged). Installing from a cleaner source does not mean the others are safe — check the source you actually install from.
github: https://github.com/lightnow-ai/lightnow-proxy, 26 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- lightnow-proxy
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
7 findings · 8.3s
v0.3.26
15 findings · 2.8s
v0.1.0
0 findings · 28.0s
v0.1.0
0 findings · 28.0s
v0.1.0
0 findings · 23.7s
v1.4.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 0.2s
No report in this scan: capslock, 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 3, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: complete | 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 22 findings across every scanner that examined this package. None of the 2 findings 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.
5 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/release-please.yml, .github/workflows/ci.yml, .github/workflows/release.yml · reported by agent-audit-kit
5 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: AAK-ANTHROPIC-SDK-001, AAK-MCP-STATELESS-001, AAK-OAUTH-005 and 1 more · Files: tests/test_mcp_app.py, tests/test_registry.py, tests/test_config_auth_router.py · reported by agent-audit-kit
2 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md · 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-ANTHROPIC-SDK-001
Files: src/lightnow_proxy/main.py, src/lightnow_proxy/upstream.py · reported by agent-audit-kit
1 AAK-MCP-STDIO-CMD-INJ-001
Files: src/lightnow_proxy/upstream.py · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-STDIO-001
Files: src/lightnow_proxy/main.py · reported by agent-audit-kit
1 HIDDEN_DATA_FILE
Files: /repo/.release-please-manifest.json · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
Critical command injection and network egress risks identified.
The artifact contains critical command injection vulnerabilities in `src/lightnow_proxy/upstream.py` and `src/lightnow_proxy/main.py`, allowing shell execution. It also exhibits high-severity network egress capabilities in `src/lightnow_proxy/main.py` and `src/lightnow_proxy/upstream.py` through an Anthropic SDK, and undeclared network activity. Additionally, a high-severity infinite loop is present in `src/lightnow_proxy/router.py` which could lead to resource abuse.
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.
1 RESOURCE_ABUSE_INFINITE_LOOP
Files: /repo/src/lightnow_proxy/router.py · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 TOOL_ABUSE_UNDECLARED_NETWORK
Files: /repo/repo/CHANGELOG.md · reported by cisco-skill-scanner