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.
3 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 -- preact-ssr-fastify-vite
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
4 findings · 8.0s
v0.3.74
2 findings · 1.4s
v0.1.0
0 findings · 3.8s
v0.1.0
0 findings · 3.8s
v0.71.0
27 findings · 0.2s
v2.3.8
59 findings · 8.1s
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 · 0.9s
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 | Flagged46 | — | 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 92 findings across every scanner that examined this package. None of the 3 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 GHSA-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-003
Files: package.json · reported by agent-audit-kit
1 CVE-2025-64756
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-69873
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13676
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-15074
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16221
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-18446
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-22028
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-22031
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-25223
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-25224
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-25547
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-26996
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27903
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27904
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33804
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33806
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-3635
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-47219
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4923
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4926
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-6270
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-6321
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-6322
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-6410
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-6414
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-7120
Files: pnpm-lock.yaml · reported by trivy
1 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/server/prod-server.ts · reported by cisco-skill-scanner
1 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-23hp-3jrh-7fpw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-247c-9743-5963
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-27v5-c462-wpq7
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-2g4f-4pwh-qvx6
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-34x7-hfp2-rc4v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-36hm-qxxp-pg3m
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-444r-cwp2-x5xf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4c8g-83qw-93j6
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-6g55-p6wh-862q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-72c6-fx6q-fr5w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7h2j-956f-4vf2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7p8r-x3mc-p8w7
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-83g3-92jg-28cx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-83w8-p2f5-377r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8p85-9qpw-fwgw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8pvw-jcv7-9cmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8qq5-rm4j-mr97
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8x88-c5mf-7j5w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-93m4-6634-74q7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9ppj-qmqm-q256
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-c96f-x56v-gq3h
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-cxrg-g7r8-w69p
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-g4jq-h2w9-997c
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-gvwx-54wh-qm9j
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j3q9-mxjg-w52f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jqfw-vq24-v9c3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jx2c-rxcm-jvmq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mrq3-vjjr-p77c
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-pr96-94w5-mx2h
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q3j6-qgpj-74h6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qffp-2rhf-9h96
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-r292-9mhp-454m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r6q2-hw4h-h46w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2hh-gcrm-f6hx
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-v39h-62p7-jpjc
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-v9ww-2j6r-98q6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vmf3-w455-68vh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w8wr-v893-vjvp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-x428-ghpx-8j92
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
The model could have called any of these a false positive and did not.
1 CVE-2026-2880
Files: pnpm-lock.yaml · reported by trivy
Critical vulnerabilities and file system access detected
The artifact contains critical vulnerabilities in its dependencies, which could lead to various security compromises. A high-severity finding indicates potential file system access within `/repo/server/prod-server.ts`. These issues warrant immediate attention due to their severity and potential impact.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 60; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.