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.
7 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 -- tanstack-start-learn
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
2 findings · 0.6s
v2.0.11
19 findings · 6.9s
v0.3.74
2 findings · 2.3s
v0.1.0
7 findings · 3.1s
v0.1.0
0 findings · 3.2s
v0.71.0
82 findings · 0.3s
v2.3.8
106 findings · 6.8s
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.8s
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 | Flagged40 | — | 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 218 findings across every scanner that examined this package. None of the 7 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.
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: permissions-no-block, hooks-no-pretooluse · Files: .vscode/settings.json · reported by agentshield
1 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: DATA_EXFIL_JS_FS_ACCESS · Files: /repo/src/routes/demo/sentry.testing.tsx · reported by cisco-skill-scanner
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.
10 DATA_EXFIL_JS_NETWORK
Files: /repo/src/routes/api/users.ts, /repo/src/routes/courses/fetch-loader-data-params.$userId.tsx, /repo/src/routes/courses/fetch-loader-data.tsx and 6 more · reported by cisco-skill-scanner
7 opt.nerlo-rules.nerlo-hardcoded-external-egress
Files: /repo/src/routes/api/users.ts, /repo/src/routes/courses/fetch-loader-data.tsx, /repo/src/routes/courses/fetch-tanstack-query.tsx and 3 more · reported by nerlo-behavioral
3 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-5p4m-2wfm-xmqj
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
3 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 CVE-2025-65944
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-33671
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-33672
Files: pnpm-lock.yaml · reported by trivy
2 GHSA-33hq-fvwr-56pm
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6465-jgvq-jhgp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-73rr-hh4g-fpgx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-8qm3-746x-r74r
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-9m65-766c-r333
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f886-m6hf-6m8v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-h67p-54hq-rp68
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mh29-5h37-fv8m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r292-9mhp-454m
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-AGENT-002
Files: .cursorrules · reported by agent-audit-kit
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 CVE-2025-62522
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-64118
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-64718
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-12151
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13149
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13697
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-14257
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-14643
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-15157
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-1525
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-1526
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-1527
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-1528
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16728
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16729
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-22036
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-2229
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-22774
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-22775
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23736
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23737
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23745
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23950
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23956
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23957
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-24001
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-24006
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-24842
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-26960
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-26996
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27606
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-28794
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-29786
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-30226
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-31802
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-32887
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33331
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33732
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33750
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-35209
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-41305
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45623
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45736
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-48779
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-49356
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53550
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-53655
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54285
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59869
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59871
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59873
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59874
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59875
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59940
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-6733
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69152
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-9678
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-9679
Files: pnpm-lock.yaml · reported by trivy
1 FILE_MAGIC_MISMATCH
Files: /repo/eslint.config.js · reported by cisco-skill-scanner
1 GHSA-23hp-3jrh-7fpw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-25h7-pfq9-p65f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-26f5-8h2x-34xh
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-29xp-372q-xqph
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-2mjp-6q6p-2qxm
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-35p6-xmwp-9g52
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-38f7-945m-qr2g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3j22-8qj3-26mx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3rxj-6cgf-8cfw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3vj8-jmxq-cgj5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4992-7rv2-5pvq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4cwx-7wf7-3272
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4hxc-9384-m385
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-58qx-3vcg-4xpx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5xrq-8626-4rwp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-66fc-rw6m-c2q6
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-737v-mqg7-c878
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7f6v-3gx7-27q8
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-83g3-92jg-28cx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8988-4f7v-96qf
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-8xcm-r25x-g524
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-96hv-2xvq-fx4p
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-cfw5-2vxh-hr84
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f269-vfmq-vjvj
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-g2pg-6438-jwpf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g8m3-5g58-fq7m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g9mf-h72j-4rw9
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-hj76-42vx-jwp4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hx9m-jf43-8ffr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jr45-8vmc-qm54
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-m272-9rp6-32mc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-m8rv-5g2x-5cg5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mv8w-475r-vwqw
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-mwv9-gp5h-frr4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p36q-q72m-gchr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p88m-4jfj-68fv
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-pr7r-676h-xcf6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q5pr-72pq-83v3
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-r6q2-hw4h-h46w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rf6f-7fwh-wjgh
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-v3r7-h72x-cjcm
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-v9p9-hfj2-hcw8
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-vrm6-8vpv-qv8q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vw5p-8cq8-m7mv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vxpw-j846-p89q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w8wr-v893-vjvp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 HIDDEN_DATA_FILE
Files: /repo/.cta.json · 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
The model could have called any of these a false positive and did not.
3 DATA_EXFIL_JS_NETWORK
Files: /repo/src/routes/demo/start.api-request.tsx, /repo/src/routes/demo/tanstack-query.tsx · reported by cisco-skill-scanner
1 CVE-2026-11525
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-mwv9-gp5h-frr4
Files: pnpm-lock.yaml · reported by trivy
Critical vulnerabilities found in dependencies
The artifact contains multiple critical vulnerabilities in its dependencies, as identified in `pnpm-lock.yaml`. These include CVE-2026-28794, CVE-2026-59940, CVE-2026-59873, and several GHSA vulnerabilities. Additionally, numerous high severity vulnerabilities are present in the dependency tree. Further investigation into the specific impact of these vulnerabilities is recommended.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 106; 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.