Loading the registry…
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI; scanned with the same pipeline.
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.
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI. Review the scanned source before copying them into your own project.
nerlo install -- chuckle123/voice-agent-playground
4 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
12 findings · 12.9s
v0.3.74
2 findings · 3.8s
v0.1.0
2 findings · 5.5s
v0.1.0
0 findings · 5.5s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.7s
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.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 19, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-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 16 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 12 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.
2 LOW_ANALYZABILITY
Files: /repo/frontend, /repo · reported by cisco-skill-scanner
1 AAK-LEGAL-002
Files: frontend/package.json · reported by agent-audit-kit
1 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/frontend/src/app/App.tsx · reported by nerlo-behavioral
12 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: DATA_EXFIL_JS_NETWORK, AAK-HEALTHCARE-AI-004, SOCIAL_ENG_VAGUE_DESCRIPTION and 2 more · Files: /repo/frontend/src/app/App.tsx, /repo/frontend/src/app/agentConfigs/customerServiceRetail/returns.ts, /repo/frontend/src/app/lib/realtimeConnection.ts and 3 more · reported by cisco-skill-scanner, agent-audit-kit, nerlo-behavioral
Critical finding and secret exposure to network egress.
The artifact includes a critical finding in `/repo/backend/src/server.ts` and high severity findings in `/repo/backend/src/services/IncomingCall/index.ts`. A high severity finding also indicates a secret is used with network egress in `/repo/frontend/src/app/App.tsx`. Furthermore, high severity findings point to low analyzability in the `/repo` and `/repo/frontend` directories.
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.