TODO
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 osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
npm: bundled-mcps @ 0.0.0, 1 finding
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 -- bundled-mcps
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
3 findings · 7.8s
v0.3.74
3 findings · 1.2s
v0.1.0
0 findings · 3.0s
v0.1.0
0 findings · 3.0s
v0.1.0
1 finding · 8.1s
v2.3.8
95 findings · 8.8s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.3s
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 | Flagged46 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy ·n/a: not applicableosv-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 102 findings across every scanner that examined this package. None of the 7 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.
3 GHSA-w48q-cv73-mx4w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-378v-28hj-76wf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3ppc-4f35-3m26
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-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-MCP-SDK-CVE-2026-52869-001
Files: pnpm-lock.yaml · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SUPPLY-003
Files: package.json · reported by agent-audit-kit
1 GHSA-27v5-c462-wpq7
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-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-345p-7cg4-v4c7
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-37j7-fg3j-429f
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-3p6v-hrg8-8qj7
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-4w7w-66w2-5vf9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
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-5p2g-fcmc-qvqq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5p4m-2wfm-xmqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5rq4-664w-9x2c
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-5xx3-j724-wmx5
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-6q6h-j7hj-3r64
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-6v7q-wjvx-w8wg
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-848j-6mx2-7j84
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8r9q-7v3j-jr4g
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-95m3-7q98-8xr5
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-f23m-r3pf-42rh
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-f886-m6hf-6m8v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fjxv-7rqg-78g4
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-g4jq-h2w9-997c
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-h67p-54hq-rp68
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-h7cp-r72f-jxh6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hc55-p739-j48w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hmw2-7cc7-3qxx
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-jmr9-qjv8-65gv
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-m8rv-5g2x-5cg5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mh29-5h37-fv8m
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-mwp4-54f8-5fhr
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-q66q-fx2p-7w4m
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-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-r87g-78mx-3wg4
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-rp42-5vxx-qpwr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rpmf-866q-6p89
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2v4-37r5-5v8g
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-v422-hmwv-36x6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v62p-rq8g-8h59
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-v9p9-hfj2-hcw8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vj76-c3g6-qr5v
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-w4gp-fjgq-3q4g
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-w87r-vg9q-crqm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wqch-xfxh-vrr4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-x9g3-xrwr-cwfg
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 nerlo-malware-obfuscated_blob
Files: npm@0.0.0:dist/umi.mjs · reported by nerlo-malware
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
Critical vulnerabilities found in dependencies.
This artifact contains multiple critical and high severity vulnerabilities in its dependencies, as identified by `osv-scanner` in `pnpm-lock.yaml`. These vulnerabilities could potentially lead to remote code execution, denial of service, or other security compromises within the installed code. Additionally, a specific high-severity CVE in an SDK is noted, and the `cisco-skill-scanner` indicates low analyzability for the `/repo` directory, which may obscure further risks.
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 56; the rest are in the per-scanner reports above.