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.
11 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 -- interview-question
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.5s
v2.0.11
6 findings · 7.4s
v0.3.74
2 findings · 2.9s
v0.1.0
0 findings · 3.3s
v0.1.0
0 findings · 3.3s
v0.71.0
114 findings · 0.4s
v2.3.8
171 findings · 7.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 · 1.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 20, 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 295 findings across every scanner that examined this package. None of the 11 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 101 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
4 CVE-2026-42349
Files: pnpm-lock.yaml · reported by trivy
4 GHSA-5p4m-2wfm-xmqj
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
4 GHSA-w24r-5266-9c3c
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
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-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 CVE-2025-53548
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2025-64718
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-41248
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-41907
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-53550
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-59869
Files: pnpm-lock.yaml · reported by 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-6g55-p6wh-862q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-8h8q-6873-q5fj
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-9mp4-77wg-rwx9
Files: /repo/pnpm-lock.yaml · reported by 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-f88m-g3jw-g9cj
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-h25m-26qc-wcjf
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
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-mwv6-3258-q52c
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-q4gf-8mx6-v5v3
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-qx2v-qp2m-jg93
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-vqx2-fgx2-5wq9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w5hq-g745-h8pq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-SUPPLY-003
Files: package.json · reported by agent-audit-kit
1 CVE-2025-54880
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-54881
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-55173
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-55182
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-57752
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-57822
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-59471
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-66400
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-71329
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-71330
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-0540
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13311
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-25896
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-26278
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-32763
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33036
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33468
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-39356
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-40299
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41148
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41149
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41150
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41240
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41305
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44573
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44575
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44578
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44579
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44580
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44581
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44635
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45109
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45623
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-46625
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4800
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64641
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64645
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64646
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64648
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64649
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-65898
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-65902
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-65903
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-65914
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-71437
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71439
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-73646
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-9277
Files: pnpm-lock.yaml · reported by trivy
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-267c-6grr-h53f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-26hh-7cqf-hhc6
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-2v37-7h3g-55p8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2v8p-3f2j-5mp7
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-36qx-fr4f-26g5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-395f-4hp3-45gv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-39q2-94rc-95cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3rrr-jr9j-h3q3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3x4c-7xq6-9pq8
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-4992-7rv2-5pvq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4c35-wcg5-mm9h
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-4cwx-7wf7-3272
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5p2g-fcmc-qvqq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-68g3-v927-f742
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6m6c-36f7-fhxh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7rqq-prvp-x9jh
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-89xv-2m56-2m9x
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8cpq-38p9-67gx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8gc5-j5rx-235r
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-9g9p-9gw9-jx7f
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-9qr9-h5gf-34mp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-c4j6-fc7j-m34r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-cjmm-f4jc-qw8r
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-ffhc-5mcf-pf4q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g5qg-72qw-gw5v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-ggv3-7p47-pfv8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-gpj5-g38j-94v9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-h7mw-gpvr-xq4m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-h8r8-wccr-v5f2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jmr7-xgp7-cmfj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-m7jm-9gc2-mpf2
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-m99w-x7hq-7vfj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mg66-mrh9-m8jx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p9j2-gv94-2wf4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-pv5w-4p9q-p3v2
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-qjx8-664m-686j
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-r5fr-rjxr-66jc
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-rhh3-jpg6-66xh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rp9w-3fw7-7cwq
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-v8jm-5vwx-cfxm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v9jr-rg53-9pgp
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-vrm6-8vpv-qv8q
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-w3rx-r6r6-pgpr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w7jw-789q-3m8p
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-wmrf-hv6w-mr66
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xv57-4mr9-wg8v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
101 The review budget for this scan was already spent before these findings were reached.
Rules: CVE-2026-65913, CVE-2026-64643, FILE_MAGIC_MISMATCH and 93 more · Files: pnpm-lock.yaml, /repo/src/i18n/navigation.ts, /repo/pnpm-lock.yaml and 5 more · reported by trivy, cisco-skill-scanner, osv-scanner and 2 more
Multiple critical vulnerabilities found in artifact dependencies.
The artifact contains multiple critical and high severity vulnerabilities, primarily within its dependencies, as indicated by findings in `pnpm-lock.yaml`. These vulnerabilities could enable capabilities such as remote code execution, denial of service, or unauthorized information access. High severity findings are also present in `src/components/analytics/clarity.tsx` and `src/components/blocks/mermaid/index.tsx`, warranting attention for potential risks in those components.
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 23 of 23; the rest are in the per-scanner reports above.