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.
3 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 -- dalin
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
9 findings · 0.8s
v2.0.11
45 findings · 25.8s
v0.3.74
141 findings · 19.8s
v0.1.0
0 findings · 180.7s
v0.1.0
0 findings · 180.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 · 0.9s
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 195 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 195 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
195 The review call did not complete.
Rules: COMMAND_INJECTION_JS_FUNCTION_CONSTRUCTOR, YARA_coercive_injection_generic, COMMAND_INJECTION_EVAL and 25 more · Files: /repo/public/js/filament/forms/components/markdown-editor.js, /repo/public/js/filament/forms/components/rich-editor.js, .env.testing and 50 more · reported by cisco-skill-scanner, agent-audit-kit, agentshield
Critical command injection and credential exposure risks.
The artifact presents critical risks due to command injection vulnerabilities found in JavaScript components like `markdown-editor.js` and `rich-editor.js`, potentially enabling shell execution. High-severity findings indicate possible credential exposure in `.env.testing` and various `public/js` files, alongside OAuth-related issues. Further critical findings are present in several PHP application and configuration files, requiring careful review.
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.
Showing 16 of 16; the rest are in the per-scanner reports above.