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 -- vite_react_shadcn_ts
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.5s
v2.0.11
6 findings · 7.6s
v0.3.74
2 findings · 3.7s
v0.2.0
0 findings · 4.6s
v0.2.0
0 findings · 4.6s
v0.71.0
21 findings · 0.4s
v2.3.8
122 findings · 7.9s
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 · 2.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
2 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 11, 2026 | Flagged47 | — | 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 |
| Aug 1, 2026 | Flagged47 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: complete | 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 151 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.
6 GHSA-3jxr-9vmj-r5cp
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
6 GHSA-mh99-v99m-4gvg
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
6 GHSA-rgw5-rvv9-x895
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
4 CVE-2026-40181
Files: bun.lock, package-lock.json · reported by trivy
4 GHSA-2j2x-hqr9-3h42
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
4 GHSA-82fw-gwwq-j7x9
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 CVE-2026-53666
Files: bun.lock, package-lock.json · reported by trivy
2 CVE-2026-53668
Files: bun.lock, package-lock.json · reported by trivy
2 CVE-2026-53669
Files: bun.lock, package-lock.json · reported by trivy
2 GHSA-2883-xcg3-v3hh
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-28wg-ghj8-5hjv
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-2v37-7h3g-55p8
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-337j-9hxr-rhxg
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-35p6-xmwp-9g52
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-4c8g-83qw-93j6
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-4cwx-7wf7-3272
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-4x5r-pxfx-6jf8
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-5c6j-r48x-rmvq
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-5xrq-8626-4rwp
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-6g55-p6wh-862q
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-73wf-gq98-2v4g
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-7p8r-x3mc-p8w7
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-8xcm-r25x-g524
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-c83g-rgw3-j3cx
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-f65p-4m7j-42xc
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-f88m-g3jw-g9cj
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-fv7c-fp4j-7gwp
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-fx2h-pf6j-xcff
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-g8m3-5g58-fq7m
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-h67p-54hq-rp68
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-hm92-r4w5-c3mj
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-jjmj-jmhj-qwj2
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-jqff-g426-hqxp
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-jr45-8vmc-qm54
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-jxxr-4gwj-5jf2
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-m8rv-5g2x-5cg5
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-p498-v437-472g
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-p88m-4jfj-68fv
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-pr7r-676h-xcf6
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-q3j6-qgpj-74h6
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-qj8w-gfj5-8c6v
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-qx2v-qp2m-jg93
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-rgj7-g3m4-5g8c
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-v2hh-gcrm-f6hx
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-v39h-62p7-jpjc
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-v3r7-h72x-cjcm
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-v6wh-96g9-6wx3
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-vmh5-mc38-953g
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-vxpw-j846-p89q
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-w5vr-8v7q-w6rv
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-w9m9-85wc-3x92
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-wrjc-x8rr-h8h6
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-xwg4-73v4-xw9w
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 BINARY_FILE_DETECTED
Files: /repo/bun.lockb · reported by cisco-skill-scanner
1 CVE-2026-13149
Files: package-lock.json · reported by trivy
1 CVE-2026-14257
Files: package-lock.json · reported by trivy
1 CVE-2026-41305
Files: package-lock.json · reported by trivy
1 CVE-2026-45623
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-69152
Files: package-lock.json · reported by trivy
1 CVE-2026-69153
Files: package-lock.json · reported by trivy
1 CVE-2026-73086
Files: package-lock.json · reported by trivy
1 CVE-2026-73646
Files: package-lock.json · reported by trivy
1 CVE-2026-9358
Files: package-lock.json · reported by trivy
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-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
1 UNANALYZABLE_BINARY
Files: /repo/bun.lockb · reported by cisco-skill-scanner
Critical and high-severity vulnerabilities found
The artifact contains critical and numerous high-severity vulnerabilities in its installed code, primarily identified in dependency lock files. One critical vulnerability (GHSA-5xrq-8626-4rwp) and many high-severity vulnerabilities (e.g., GHSA-mh99-v99m-4gvg, GHSA-rgw5-rvv9-x895, CVE-2026-14257) warrant immediate attention. Additionally, a low analyzability finding suggests that the full security posture of the artifact could not be determined.
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 81; the rest are in the per-scanner reports above.