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 -- website
6 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.9s
v2.0.11
Incomplete run
0 findings · 120.5s
v0.3.74
5 findings · 75.3s
v0.1.0
2 findings · 5.5s
v0.1.0
0 findings · 5.5s
v0.71.0
0 findings · 2.9s
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.9s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.1s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged88 | — | agentshield: completecisco-skill-scanner ·!: incompleteagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner ·n/a: not applicabletrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
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 7 findings across every scanner that examined this package.
The model could have called any of these a false positive and did not.
3 AAK-SECRET-004
Files: lib/supabase.ts, lib/generated/node-sources.ts · reported by agent-audit-kit
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: package.json · reported by agent-audit-kit
1 opt.nerlo-rules.nerlo-dynamic-exec
Files: /repo/lib/transpilation/executeApp/executeApp.ts · reported by nerlo-behavioral
1 opt.nerlo-rules.nerlo-hardcoded-external-egress
Files: /repo/components/Header.tsx · reported by nerlo-behavioral
Artifact exposes secrets and performs dynamic code execution.
This artifact performs dynamic code execution in `lib/transpilation/executeApp/executeApp.ts`, which could allow arbitrary code execution. It also contains hardcoded secrets in `lib/generated/node-sources.ts` and `lib/supabase.ts`, potentially exposing credentials. Further high severity findings are present in `components/BlogPreview.tsx` and `pages/api/subscribe.ts`.
Concern level assessed by the review: High. 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.