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 -- hand-royal
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.5s
v0.3.74
6 findings · 6.8s
v0.1.0
0 findings · 5.1s
v0.1.0
0 findings · 5.1s
v0.71.0
43 findings · 0.3s
v2.0.11
No skill bundle was found in this artifact. What each scanner covers
0 findings · 6.4s
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.7s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
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 22, 2026 | Flagged47 | — | agentshield: completecisco-skill-scanner ·n/a: not applicableagent-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 49 findings across every scanner that examined this package.
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 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/docker.yml · reported by agent-audit-kit
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
2 CVE-2025-27789
Files: package-lock.json · reported by trivy
2 CVE-2026-34077
Files: package-lock.json · reported by trivy
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SECRET-004
Files: src/lib/supabase.ts · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2025-30208
Files: package-lock.json · reported by trivy
1 CVE-2025-31125
Files: package-lock.json · reported by trivy
1 CVE-2025-31486
Files: package-lock.json · reported by trivy
1 CVE-2025-32395
Files: package-lock.json · reported by trivy
1 CVE-2025-43864
Files: package-lock.json · reported by trivy
1 CVE-2025-43865
Files: package-lock.json · reported by trivy
1 CVE-2025-46565
Files: package-lock.json · reported by trivy
1 CVE-2025-48370
Files: package-lock.json · reported by trivy
1 CVE-2025-58751
Files: package-lock.json · reported by trivy
1 CVE-2025-58752
Files: package-lock.json · reported by trivy
1 CVE-2025-59057
Files: package-lock.json · reported by trivy
1 CVE-2025-62522
Files: package-lock.json · reported by trivy
1 CVE-2025-68470
Files: package-lock.json · reported by trivy
1 CVE-2026-21884
Files: package-lock.json · reported by trivy
1 CVE-2026-22029
Files: package-lock.json · reported by trivy
1 CVE-2026-22030
Files: package-lock.json · reported by trivy
1 CVE-2026-27606
Files: package-lock.json · reported by trivy
1 CVE-2026-33532
Files: package-lock.json · reported by trivy
1 CVE-2026-39363
Files: package-lock.json · reported by trivy
1 CVE-2026-39365
Files: package-lock.json · reported by trivy
1 CVE-2026-40181
Files: package-lock.json · reported by trivy
1 CVE-2026-41305
Files: package-lock.json · reported by trivy
1 CVE-2026-41907
Files: package-lock.json · reported by trivy
1 CVE-2026-42211
Files: package-lock.json · reported by trivy
1 CVE-2026-42342
Files: package-lock.json · reported by trivy
1 CVE-2026-45623
Files: package-lock.json · reported by trivy
1 CVE-2026-45736
Files: package-lock.json · reported by trivy
1 CVE-2026-48779
Files: package-lock.json · reported by trivy
1 CVE-2026-49356
Files: package-lock.json · reported by trivy
1 CVE-2026-53571
Files: package-lock.json · reported by trivy
1 CVE-2026-53632
Files: package-lock.json · reported by trivy
1 CVE-2026-53666
Files: package-lock.json · reported by trivy
1 CVE-2026-53669
Files: package-lock.json · reported by trivy
1 CVE-2026-55685
Files: package-lock.json · reported by trivy
1 CVE-2026-67213
Files: package-lock.json · reported by trivy
1 CVE-2026-67214
Files: package-lock.json · reported by trivy
1 CVE-2026-69153
Files: package-lock.json · reported by trivy
1 CVE-2026-73646
Files: package-lock.json · reported by trivy
1 GHSA-67mh-4wv8-2f99
Files: package-lock.json · reported by trivy
Exposed secret and critical vulnerabilities detected
The artifact contains an exposed secret in `src/lib/supabase.ts`, which could lead to unauthorized credential access. Additionally, multiple high-severity vulnerabilities (CVEs) are present in the artifact's dependencies, as indicated in `package-lock.json`. These vulnerabilities could enable various risks, including remote code execution, denial of service, or further system compromise.
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.