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.
2 critical findings reported by trivy, osv-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 -- jnaranja/clawdplayspokemon
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.
v2.0.11
4 findings · 7.6s
v0.3.74
1 finding · 1.7s
v0.1.0
0 findings · 3.5s
v0.1.0
0 findings · 3.5s
v0.71.0
31 findings · 0.2s
v2.3.8
31 findings · 1.4s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
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.0s
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 21, 2026 | Flagged46 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_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 67 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
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 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/frames/SKILL.md · reported by cisco-skill-scanner
1 AAK-SECRET-004
Files: claude_player/interface/claude_interface.py · reported by agent-audit-kit
1 CVE-2024-28219
Files: Pipfile.lock · reported by trivy
1 CVE-2024-34062
Files: Pipfile.lock · reported by trivy
1 CVE-2024-35195
Files: Pipfile.lock · reported by trivy
1 CVE-2024-37891
Files: Pipfile.lock · reported by trivy
1 CVE-2024-47081
Files: Pipfile.lock · reported by trivy
1 CVE-2025-43859
Files: Pipfile.lock · reported by trivy
1 CVE-2025-50181
Files: Pipfile.lock · reported by trivy
1 CVE-2025-50182
Files: Pipfile.lock · reported by trivy
1 CVE-2025-66418
Files: Pipfile.lock · reported by trivy
1 CVE-2025-66471
Files: Pipfile.lock · reported by trivy
1 CVE-2025-68146
Files: Pipfile.lock · reported by trivy
1 CVE-2026-21441
Files: Pipfile.lock · reported by trivy
1 CVE-2026-22701
Files: Pipfile.lock · reported by trivy
1 CVE-2026-25645
Files: Pipfile.lock · reported by trivy
1 CVE-2026-28684
Files: Pipfile.lock · reported by trivy
1 CVE-2026-42308
Files: Pipfile.lock · reported by trivy
1 CVE-2026-42310
Files: Pipfile.lock · reported by trivy
1 CVE-2026-44431
Files: Pipfile.lock · reported by trivy
1 CVE-2026-45409
Files: Pipfile.lock · reported by trivy
1 CVE-2026-54058
Files: Pipfile.lock · reported by trivy
1 CVE-2026-54059
Files: Pipfile.lock · reported by trivy
1 CVE-2026-54060
Files: Pipfile.lock · reported by trivy
1 CVE-2026-55379
Files: Pipfile.lock · reported by trivy
1 CVE-2026-55380
Files: Pipfile.lock · reported by trivy
1 CVE-2026-55798
Files: Pipfile.lock · reported by trivy
1 CVE-2026-59197
Files: Pipfile.lock · reported by trivy
1 CVE-2026-59198
Files: Pipfile.lock · reported by trivy
1 CVE-2026-59199
Files: Pipfile.lock · reported by trivy
1 CVE-2026-59200
Files: Pipfile.lock · reported by trivy
1 CVE-2026-59204
Files: Pipfile.lock · reported by trivy
1 CVE-2026-59205
Files: Pipfile.lock · reported by trivy
1 PYSEC-2026-1374
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-1375
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-165
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-1793
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-1872
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-1873
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-1976
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-1994
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-1995
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-1996
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-1997
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-1998
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-1999
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-2253
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-2254
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-2255
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-2256
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-2257
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-2874
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-3451
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-3453
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-3454
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-348
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-3493
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-3494
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-3495
Files: /repo/Pipfile.lock · reported by osv-scanner
1 PYSEC-2026-3496
Files: /repo/Pipfile.lock · reported by osv-scanner
1 RESOURCE_ABUSE_INFINITE_LOOP
Files: /repo/claude_player/interface/claude_interface.py · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/frames/SKILL.md · reported by cisco-skill-scanner
Critical vulnerabilities, hardcoded secret, and potential infinite loop detected.
This artifact contains critical vulnerabilities in its dependencies, as indicated by findings in `Pipfile.lock`, which could enable system compromises. A hardcoded secret in `claude_player/interface/claude_interface.py` presents a credential access risk. An infinite loop vulnerability in the same file could lead to resource exhaustion, and numerous high-severity dependency vulnerabilities are also present.
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 25 of 34; the rest are in the per-scanner reports above.