Loading the registry…
Website development with specialized chatbot
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 -- website-development
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
Timed out
0 findings · 300.0s
v0.3.74
Incomplete run
0 findings · 20.5s
v0.1.0
29 findings · 36.7s
v0.1.0
0 findings · 36.7s
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 · 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 ·!: timeoutagent-audit-kit ·!: incompletenerlo-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 29 findings across every scanner that examined this package.
The model could have called any of these a false positive and did not.
27 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/cyber-risk-dashboard/backend/controllers/riskController.js, /repo/cyber-risk-dashboard/backend/test-login.js, /repo/cyber-risk-dashboard/src/contexts/AuthContext.tsx and 3 more · reported by nerlo-behavioral
2 opt.nerlo-rules.nerlo-py-dynamic-exec
Files: /repo/New models for the risk quant/script.py, /repo/risk mitigation strat/risk mitigation strategy.py · reported by nerlo-behavioral
Critical findings expose credentials and enable dynamic execution.
The artifact contains critical findings related to credential exposure or sensitive data handling in `createMockData.js`, `server.js`, `test-login.js`, and `mongo-init.js`. It performs dynamic code execution in `script.py`. Additionally, secrets are transmitted over the network from `riskController.js`, `test-login.js`, and `AuthContext.tsx`. These capabilities present significant security risks.
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.