Loading the registry…
SecureGuard Pro - Multi-Cam Correlation Backend
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.
3 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 -- secureguard-pro-backend
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.7s
v2.0.11
43 findings · 14.0s
v0.3.74
5 findings · 8.0s
v0.1.0
2 findings · 9.4s
v0.1.0
1 finding · 9.4s
vv0.3.2
No Go packages 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 · 2.2s
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 51 findings across every scanner that examined this package. None of the 3 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 26 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.
8 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/app/update_proctoring.cjs, /repo/update_live_proctoring.js, /repo/update_seed.js · reported by cisco-skill-scanner
4 DATA_EXFIL_JS_NETWORK
Files: /repo/app/src/lib/api.ts, /repo/src/scripts/e2eSmoke.ts · reported by cisco-skill-scanner
2 AAK-LEGAL-002
Files: package.json, app/package.json · reported by agent-audit-kit
2 AAK-SECRET-004
Files: src/controllers/examController.ts · reported by agent-audit-kit
2 COMMAND_INJECTION_JS_FUNCTION_CONSTRUCTOR
Files: /repo/app/src/components/CodingQuestion.tsx · reported by cisco-skill-scanner
2 EXCESSIVE_FILE_COUNT
Files: /repo/., /repo/app/. · reported by cisco-skill-scanner
2 LOW_ANALYZABILITY
Files: /repo, /repo/app · reported by cisco-skill-scanner
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 SECRET_GOOGLE_API
Files: /repo/src/services/aiReportGenerator.ts · reported by cisco-skill-scanner
1 UNANALYZABLE_BINARY
Files: /repo/Convert-Light.ps1 · reported by cisco-skill-scanner
26 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: opt.nerlo-rules.nerlo-js-secret-to-network-egress, opt.nerlo-rules.nerlo-install-pipe-to-shell, UNANALYZABLE_BINARY and 6 more · Files: /repo/src/scripts/e2eSmoke.ts, /repo/README.md, /repo/app/build_err2.log and 9 more · reported by nerlo-behavioral, nerlo-install-instruction, cisco-skill-scanner
Critical: command injection, secrets, network egress.
The artifact contains critical findings, including potential command injection in `/repo/app/src/components/CodingQuestion.tsx` that could lead to shell execution. Multiple secrets, such as a Google API key, are exposed in `/repo/src/services/aiReportGenerator.ts` and `src/controllers/examController.ts`, risking credential access. Network egress with exposed secrets is also identified in `/repo/src/scripts/e2eSmoke.ts`, and installation instructions in `/repo/README.md` suggest piping content directly to a shell.
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.