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.
2 critical findings reported by 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 -- try-on
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.5s
v2.0.11
3 findings · 7.3s
v0.3.74
2 findings · 3.4s
v0.1.0
0 findings · 3.5s
v0.1.0
0 findings · 3.5s
v0.71.0
71 findings · 0.3s
v2.3.8
145 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 · 1.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 22, 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 221 findings across every scanner that examined this package. None of the 2 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.
4 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-8h8q-6873-q5fj
Files: package-lock.json, pnpm-lock.yaml, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 GHSA-c2c7-rcm5-vvqj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-f886-m6hf-6m8v
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-f88m-g3jw-g9cj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml, package-lock.json and 1 more · reported by osv-scanner, trivy
4 GHSA-fxqj-rqcc-2cmp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-q4gf-8mx6-v5v3
Files: package-lock.json, pnpm-lock.yaml, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 GHSA-qx2v-qp2m-jg93
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 CVE-2026-27980
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-29057
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-41305
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44572
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44573
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44574
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44575
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44576
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44577
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44578
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44579
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44580
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44581
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44582
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-45109
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-45623
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-45736
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-48779
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64641
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64643
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64644
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64645
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64646
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64647
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64648
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64649
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-67213
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-67214
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-69153
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-73646
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 GHSA-23hp-3jrh-7fpw
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-25h7-pfq9-p65f
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-267c-6grr-h53f
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-26hh-7cqf-hhc6
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-28wg-ghj8-5hjv
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2g4f-4pwh-qvx6
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2v37-7h3g-55p8
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-36qx-fr4f-26g5
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3g8h-86w9-wvmq
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3x4c-7xq6-9pq8
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4633-3j49-mh5q
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-492v-c6pp-mqqv
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4c39-4ccg-62r3
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-58qx-3vcg-4xpx
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-68g3-v927-f742
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-83g3-92jg-28cx
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-89xv-2m56-2m9x
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-8x88-c5mf-7j5w
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-955p-x3mx-jcvp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-96hv-2xvq-fx4p
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-9ppj-qmqm-q256
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-c4j6-fc7j-m34r
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-ffhc-5mcf-pf4q
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-ggv3-7p47-pfv8
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-gvwx-54wh-qm9j
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-gx5p-jg67-6x7h
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-h64f-5h5j-jqjh
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-h67p-54hq-rp68
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-m99w-x7hq-7vfj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mg66-mrh9-m8jx
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-p9j2-gv94-2wf4
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-q8wf-6r8g-63ch
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-qffp-2rhf-9h96
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r292-9mhp-454m
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rf6f-7fwh-wjgh
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-vfv6-92ff-j949
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-vmf3-w455-68vh
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w8wr-v893-vjvp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-wfc6-r584-vfw7
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2026-27977
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27978
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27979
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-49356
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64642
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-4x5r-pxfx-6jf8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6gpp-xcg3-4w24
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-h27x-g6w4-24gq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jcc7-9wpm-mj36
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mq59-m269-xvcx
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
Critical vulnerability found in installed code dependencies.
This artifact includes a critical vulnerability (GHSA-23hp-3jrh-7fpw) within its dependencies, as identified in package-lock.json and pnpm-lock.yaml. Additionally, numerous high-severity vulnerabilities are present in the installed code, primarily within dependencies listed in package-lock.json. A high-severity finding also indicates low analyzability of the repository, which may hinder further security assessment.
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 121; the rest are in the per-scanner reports above.