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.
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 -- word-soup
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.6s
v2.0.11
4 findings · 7.7s
v0.3.74
1 finding · 1.6s
v0.1.0
0 findings · 3.5s
v0.1.0
0 findings · 3.5s
v0.71.0
87 findings · 0.3s
v2.3.8
86 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 · 2.6s
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 21, 2026 | Flagged48 | — | 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 178 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 1 finding stand exactly as their scanners reported them, at full severity, as they would have without this review.
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.
4 GHSA-5p4m-2wfm-xmqj
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 CVE-2025-27789
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2025-64718
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-33532
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-33hq-fvwr-56pm
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-48c2-rrv3-qjmp
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-67mh-4wv8-2f99
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-968p-4wvh-cqc8
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-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
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 CVE-2024-21538
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2024-47764
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2024-47885
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2024-52011
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2024-53382
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2024-55565
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2024-56140
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2024-56159
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-13465
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-24010
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-30208
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-31125
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-31486
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-32395
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-46565
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-55303
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-57820
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-58751
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-58752
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-5889
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-61925
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-62522
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-64525
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-64756
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-64757
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-64764
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-64765
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-65019
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-66202
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-66400
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-69873
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13149
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13676
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-14257
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-22775
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-24001
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-2950
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-30226
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-33750
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33769
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-39365
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41067
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41305
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45028
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45623
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4800
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-49356
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-50146
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-54298
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54299
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59727
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59729
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-67213
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-67214
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-73422
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-73646
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-23c5-xmqv-rm74
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-2pvr-wf23-7pc7
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-356w-63v5-8wf4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3jxr-9vmj-r5cp
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-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3xgq-45jj-v275
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-49w6-73cw-chjr
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-4fh9-h7wg-q85m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4g3v-8h47-v7g6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4r4m-qw57-chr8
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-5ff5-9fcw-vg88
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-73rr-hh4g-fpgx
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-7pw4-f3q4-r2p2
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-859w-5945-r5v3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8hv8-536x-4wqp
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-c27g-q93r-2cwf
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-c4pw-33h3-35xw
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-f48w-9m4c-m7f5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f886-m6hf-6m8v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fvmw-cj7j-j39q
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-g4jq-h2w9-997c
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g735-7g2w-hh3f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-ggxq-hp9w-j794
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hr2q-hp5q-x767
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j687-52p2-xcff
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-jrpj-wcv7-9fh9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-m85w-3h95-hcf9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mh99-v99m-4gvg
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-mwcw-c2x4-8c55
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-pxg6-pf52-xh8x
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-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-r5fr-rjxr-66jc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rgw5-rvv9-x895
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-v39h-62p7-jpjc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v6h2-p8h4-qcjw
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-vg6x-rcgg-rjx6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vj54-72f3-p5jv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-whqg-ppgf-wp8c
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wrwg-2hg8-v723
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-x3h8-62x9-952g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-x574-m823-4x7w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-x7hr-w5r2-h6wg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xcj6-pq6g-qj4x
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xf8x-j4p2-f749
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xr5h-phrj-8vxv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 HIDDEN_DATA_FILE
Files: /repo/.prettierrc.mjs · 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 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: GHSA-mwv9-gp5h-frr4 · Files: pnpm-lock.yaml · reported by trivy
Numerous critical vulnerabilities detected in installed code.
This artifact contains a significant number of critical vulnerabilities in its installed code, identified by multiple scanners. These vulnerabilities could enable various impacts, including potential for remote code execution, privilege escalation, or data compromise. The high volume of critical findings across different components warrants immediate attention.
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 67; the rest are in the per-scanner reports above.