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.
2 critical findings reported by cisco-skill-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
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 -- spike-idempotent-requests
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.6s
v2.0.11
38 findings · 7.9s
v0.3.74
3 findings · 2.5s
v0.1.0
1 finding · 3.5s
v0.1.0
0 findings · 3.5s
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 42 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 36 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 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md, /repo/docs/tasks/SKILL.md, /repo/docs/diagrams/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/src/frontend/SKILL.md · reported by cisco-skill-scanner
1 HIDDEN_DATA_FILE
Files: /repo/src/frontend/.env · reported by cisco-skill-scanner
36 The review call did not complete.
Rules: COMMAND_INJECTION_JS_CHILD_PROCESS, DATA_EXFIL_JS_FS_ACCESS, LOW_ANALYZABILITY and 7 more · Files: /repo/scripts/setup.js, /repo/src/backend/plugin.cjs, /repo/src/frontend and 18 more · reported by cisco-skill-scanner, nerlo-behavioral, agent-audit-kit
Critical command injection and data exfiltration risks.
The artifact contains critical findings for command injection and potential credential access within `scripts/setup.js`. High severity findings also indicate dynamic execution in `scripts/setup.js` and data exfiltration via file system access in `src/backend/plugin.cjs`. These capabilities could lead to unauthorized shell execution, access to sensitive data, and network egress.
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.