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.
11 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 -- erulabs.com
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
2 findings · 0.6s
v2.0.11
22 findings · 10.6s
v0.3.74
2 findings · 1.8s
v0.1.0
0 findings · 3.7s
v0.1.0
0 findings · 3.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 · 2.1s
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 26 findings across every scanner that examined this package. None of the 11 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 9 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.
5 COMMAND_INJECTION_EVAL
Files: /repo/.yarn/releases/yarn-4.12.0.cjs · reported by cisco-skill-scanner
3 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/.yarn/releases/yarn-4.12.0.cjs, /repo/lib/posts.js · reported by cisco-skill-scanner
2 COMMAND_INJECTION_JS_FUNCTION_CONSTRUCTOR
Files: /repo/.yarn/releases/yarn-4.12.0.cjs · reported by cisco-skill-scanner
2 DATA_EXFIL_JS_NETWORK
Files: /repo/.yarn/releases/yarn-4.12.0.cjs · reported by cisco-skill-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 COMMAND_INJECTION_JS_CHILD_PROCESS
Files: /repo/.yarn/releases/yarn-4.12.0.cjs · reported by cisco-skill-scanner
1 FILE_MAGIC_MISMATCH
Files: /repo/pages/_document.js · reported by cisco-skill-scanner
1 HIDDEN_DATA_FILE
Files: /repo/.yarn/releases/yarn-4.12.0.cjs · reported by cisco-skill-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
9 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: SECRET_AWS_KEY, TOOL_ABUSE_SYSTEM_MODIFICATION, YARA_credential_harvesting_generic and 6 more · Files: /repo/.yarn/releases/yarn-4.12.0.cjs, /repo/deploy.sh, /repo/k8s/dev/secrets/tls.key and 4 more · reported by cisco-skill-scanner, agent-audit-kit, agentshield
Critical command execution and credential exposure risks.
The artifact contains multiple critical command injection vulnerabilities in JavaScript files, allowing for arbitrary shell execution. It also includes a script capable of system modification and exposes an AWS key and other credentials. Further findings indicate potential for file system access 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.