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 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 -- react-router-shadcn-playground
7 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.7s
v2.0.11
11 findings · 9.0s
v0.3.74
3 findings · 3.0s
v0.1.0
0 findings · 4.2s
v0.1.0
0 findings · 4.2s
v0.71.0
38 findings · 0.3s
v2.3.8
55 findings · 7.3s
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 22, 2026 | Flagged48 | — | agentshield: completecisco-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 107 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
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.
7 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE, MANIFEST_INVALID_NAME · Files: /repo/.github/SKILL.md, /repo/.github/prompts/SKILL.md, /repo/.github/instructions/SKILL.md · reported by cisco-skill-scanner
2 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/pr-publish.yml, .github/workflows/repo-sync.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.
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 CVE-2025-13465
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-15284
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-7339
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-12590
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-21884
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-22029
Critical vulnerabilities identified in artifact dependencies
This artifact contains critical vulnerabilities in its dependencies, as indicated by GHSA-fmh4-wr37-44fp and GHSA-j76j-5p5g-9wfr found in pnpm-lock.yaml. These issues could potentially lead to severe impacts, including remote code execution or data compromise, depending on the specific vulnerability. Additionally, numerous high-severity vulnerabilities are present across various dependencies, further increasing the overall risk profile.
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.
1 CVE-2026-22030
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-2391
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27606
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-2950
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33244
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33245
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33532
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33671
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33672
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-34077
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-39363
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-39364
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-39365
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-40181
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41305
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42211
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42342
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45623
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4800
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4867
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-5078
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53571
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53632
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53666
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53668
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53669
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-55685
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-67213
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-67214
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69153
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-73646
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-8723
Files: pnpm-lock.yaml · reported by trivy
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2j2x-hqr9-3h42
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2w69-qvjg-hvjx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-337j-9hxr-rhxg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-37ch-88jc-xwx2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-48c2-rrv3-qjmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-49rj-9fvp-4h2h
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4vj7-5mj6-jm8m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4w7w-66w2-5vf9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4x5r-pxfx-6jf8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5j98-mcp5-4vw2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5qjj-4xww-7phc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6g55-p6wh-862q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6rw7-vpxm-498p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-76c9-3jph-rj3q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8646-j5j9-6r62
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8v8x-cx79-35w7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8x6r-g9mw-2r78
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-c2c7-rcm5-vvqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-c6m7-q6pr-c64r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-chx6-hx7r-mcp5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-cpqf-f22c-r95x
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f22v-gfqf-p8f3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f23m-r3pf-42rh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f886-m6hf-6m8v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fmh4-wr37-44fp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g239-q96q-x4qm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-h5cw-625j-3rxh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j76j-5p5g-9wfr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jjmj-jmhj-qwj2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mw96-cpmx-2vgc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p9ff-h696-f583
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r5fr-rjxr-66jc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rxv8-25v2-qmq8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2wj-q39q-566r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v457-wxvj-p9w9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v6h2-p8h4-qcjw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v6wh-96g9-6wx3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w7fw-mjwx-w883
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w94c-4vhp-22gx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wrjc-x8rr-h8h6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
Showing 25 of 50; the rest are in the per-scanner reports above.