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 -- vesper
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
5 findings · 8.4s
v0.3.74
4 findings · 3.6s
v0.1.0
0 findings · 3.6s
v0.1.0
0 findings · 3.6s
v0.71.0
75 findings · 0.3s
v2.3.8
125 findings · 7.2s
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 | Flagged44 | — | 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 211 findings across every scanner that examined this package. None of the 11 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
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.
3 AAK-LEGAL-002
Files: package.json, apps/server/package.json, apps/web/package.json · reported by agent-audit-kit
3 GHSA-2vg6-77g8-24mp
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
3 GHSA-569q-mpph-wgww
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
3 GHSA-86j7-9j95-vpqj
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
3 GHSA-9h47-pqcx-hjr4
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
3 GHSA-qq9h-g4jm-xgf3
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
3 GHSA-wxw3-q3m9-c3jr
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
3 GHSA-x732-6j76-qmhm
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
3 GHSA-xg6x-h9c9-2m83
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 CVE-2026-67213
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-67214
Files: pnpm-lock.yaml · reported by trivy
2 GHSA-28wg-ghj8-5hjv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2v37-7h3g-55p8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-33hq-fvwr-56pm
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-6g55-p6wh-862q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-7w99-5wm4-3g79
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-8qm3-746x-r74r
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-99h5-pjcv-gr6v
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-fmh4-wcc4-5jm3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-g38m-r43w-p2q7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-p6v2-xcpg-h6xw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-pw9m-5jxm-xr6h
Files: /repo/pnpm-lock.yaml · reported by 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
1 AAK-MCP-BETTERAUTH-CVE-2026-53512-001
Files: pnpm-lock.yaml · reported by agent-audit-kit
1 CVE-2025-13465
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-13466
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-15284
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-48985
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-55182
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-59471
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-61928
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-68130
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-12590
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-2391
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27980
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-29057
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-2950
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-30226
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-32763
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33468
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-35209
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-39356
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41305
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44572
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44573
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44574
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44575
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44576
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44577
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-44582
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-45364
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-4800
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-48779
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-53512
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53514
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53516
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53518
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64641
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64643
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64644
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-64647
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-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 CVE-2026-8769
Files: pnpm-lock.yaml · reported by trivy
1 DATA_EXFIL_JS_NETWORK
Files: /repo/apps/web/src/utils/trpc.ts · reported by cisco-skill-scanner
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-23hp-3jrh-7fpw
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-27v5-c462-wpq7
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-3g8h-86w9-wvmq
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-3qcw-2rhx-2726
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-3x4c-7xq6-9pq8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-43p4-m455-4f4j
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4633-3j49-mh5q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-492v-c6pp-mqqv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4c39-4ccg-62r3
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-58qx-3vcg-4xpx
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-5xrq-8626-4rwp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-67mh-4wv8-2f99
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-6rw7-vpxm-498p
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-73rr-hh4g-fpgx
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-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-866g-f22w-33x8
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-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-955p-x3mx-jcvp
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-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-c2c7-rcm5-vvqj
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-cfw5-2vxh-hr84
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-ffhc-5mcf-pf4q
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-g2pg-6438-jwpf
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-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-gvwx-54wh-qm9j
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-gx5p-jg67-6x7h
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-h64f-5h5j-jqjh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hcf7-66rw-9f5r
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-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-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-p9ff-h696-f583
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-q8mj-m7cp-5q26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q8wf-6r8g-63ch
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-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-rwvc-j5jr-mgvh
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-v6wh-96g9-6wx3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vfv6-92ff-j949
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-vw5p-8cq8-m7mv
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-w8wr-v893-vjvp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wfc6-r584-vfw7
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-wqch-xfxh-vrr4
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 GHSA-mwv9-gp5h-frr4
Files: pnpm-lock.yaml · reported by trivy
Critical vulnerabilities found in dependencies
Multiple critical vulnerabilities are present in the artifact's dependencies, as indicated by findings in `pnpm-lock.yaml`. These issues could lead to severe impacts such as remote code execution, data compromise, or denial of service. Several high-severity vulnerabilities are also noted, further increasing the risk profile. Attention is warranted for all critical and high-severity findings.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 117; 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.