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.
14 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 -- travel-website
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
216 findings · 13.4s
v0.3.74
2 findings · 13.6s
v0.1.0
0 findings · 5.3s
v0.1.0
0 findings · 5.3s
v0.71.0
208 findings · 1.4s
v2.3.8
278 findings · 10.9s
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.7s
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 | Flagged39 | — | 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 706 findings across every scanner that examined this package. None of the 14 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.
95 UNANALYZABLE_BINARY
Files: /repo/downloaded_images/67227f933a8ae770ec510ad0_13.avif, /repo/downloaded_images/67228273df376d574be84297_13.avif, /repo/downloaded_images/67227f325e6e18aea341dda0_4.avif and 92 more · reported by cisco-skill-scanner
94 BINARY_FILE_DETECTED
Files: /repo/downloaded_images/6723f43bea3b303b3c2a5dca_5.avif, /repo/public/images/rock_cliff_background.avif, /repo/downloaded_images/6723f44dfc99a7d020338780_7.avif and 91 more · reported by cisco-skill-scanner
8 DATA_EXFIL_JS_NETWORK
Files: /repo/app/(admin)/leafway/solutions/admin/invoices/new/page.tsx, /repo/components/destination-matrix/GlobeOrthographicLoader.tsx, /repo/components/destination-matrix/globe-orthographic.tsx and 4 more · reported by cisco-skill-scanner
8 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
8 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
8 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
8 GHSA-f88m-g3jw-g9cj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml, package-lock.json and 1 more · reported by osv-scanner, trivy
7 YARA_prompt_injection_unicode_steganography
Files: /repo/downloaded_images/67227bb9eddb8eec160eef18_4.avif, /repo/downloaded_images/67228273df376d574be84297_13.avif, /repo/public/animations/images/out_0037.webp and 4 more · reported by cisco-skill-scanner
6 GHSA-6475-r3vj-m8vf
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml, package-lock.json and 1 more · reported by osv-scanner, trivy
4 CVE-2025-15284
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
4 CVE-2026-2391
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
4 CVE-2026-25896
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
4 CVE-2026-26278
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
4 CVE-2026-26996
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
4 CVE-2026-27903
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
4 CVE-2026-27904
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
4 CVE-2026-27942
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
4 CVE-2026-33036
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
4 CVE-2026-33349
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
4 CVE-2026-41650
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
4 CVE-2026-8723
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
4 GHSA-3jxr-9vmj-r5cp
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-6rw7-vpxm-498p
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-8gc5-j5rx-235r
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-fj3w-jwp8-x2g3
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-fxqj-rqcc-2cmp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-gh4j-gqv2-49f6
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-h25m-26qc-wcjf
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml, package-lock.json and 1 more · reported by osv-scanner, trivy
4 GHSA-jmr7-xgp7-cmfj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-jp2q-39xq-3w4g
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-m7jm-9gc2-mpf2
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-mwv6-3258-q52c
Files: package-lock.json, pnpm-lock.yaml, /repo/package-lock.json and 1 more · reported by trivy, 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-q8mj-m7cp-5q26
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by 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
4 GHSA-w37m-7fhw-fmv9
Files: package-lock.json, pnpm-lock.yaml, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 GHSA-w7fw-mjwx-w883
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 CVE-2025-13465
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2025-13466
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2025-55182
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2025-59471
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2025-64756
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-0933
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-12143
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-12151
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-12590
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-13149
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-13697
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-14257
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-14643
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-15157
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-1525
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-1526
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-1527
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-1528
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-16728
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-16729
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-22036
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-2229
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-25128
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-25547
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
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-2950
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-3125
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-33532
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-33671
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-33672
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-33750
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-35209
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-39356
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-41907
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-4800
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-4923
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-4926
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-6733
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-69152
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 CVE-2026-9678
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-9679
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-27v5-c462-wpq7
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-2mjp-6q6p-2qxm
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-34x7-hfp2-rc4v
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-35p6-xmwp-9g52
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-36p8-mvp6-cv38
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-37qj-frw5-hhjh
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-48c2-rrv3-qjmp
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-4992-7rv2-5pvq
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-4cwx-7wf7-3272
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-5j98-mcp5-4vw2
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-67mh-4wv8-2f99
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-737v-mqg7-c878
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-7h2j-956f-4vf2
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-8qq5-rm4j-mr97
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-8xcm-r25x-g524
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-9g9p-9gw9-jx7f
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-9qr9-h5gf-34mp
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-c7mq-gh6q-6q7c
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f23m-r3pf-42rh
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f269-vfmq-vjvj
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-g8m3-5g58-fq7m
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-g9mf-h72j-4rw9
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-gpj5-g38j-94v9
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-hmw2-7cc7-3qxx
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-j3q9-mxjg-w52f
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-jr45-8vmc-qm54
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-m8rv-5g2x-5cg5
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-mh29-5h37-fv8m
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-p88m-4jfj-68fv
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-pr7r-676h-xcf6
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-r5fr-rjxr-66jc
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r6q2-hw4h-h46w
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-v3r7-h72x-cjcm
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v9p9-hfj2-hcw8
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-vrm6-8vpv-qv8q
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-vxpw-j846-p89q
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w5hq-g745-h8pq
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
2 GHSA-wqch-xfxh-vrr4
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/readme/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/readme/SKILL.md · reported by cisco-skill-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 ARCHIVE_FILE_DETECTED
Files: /repo/scripts/data/ne_110m_admin_0_countries.zip · reported by cisco-skill-scanner
1 CVE-2026-39244
Files: package-lock.json · reported by trivy
1 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/download_image.py · reported by cisco-skill-scanner
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 FILE_MAGIC_MISMATCH
Files: /repo/downloaded_images/view.php · reported by cisco-skill-scanner
1 GHSA-xcpc-8h2w-3j85
Files: /repo/package-lock.json · reported by osv-scanner
1 HIDDEN_DATA_FILE
Files: /repo/.dev.vars · reported by cisco-skill-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 OVERSIZED_FILE
Files: /repo/public/destinations/activities/dubai/aquaventure-waterpark.jpg · reported by cisco-skill-scanner
1 TOOL_ABUSE_UNDECLARED_NETWORK
Files: /repo/repo/README.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
2 CVE-2026-11525
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
Critical vulnerabilities detected in artifact dependencies
The artifact contains multiple critical vulnerabilities identified in its dependencies, specifically within `package-lock.json` and `pnpm-lock.yaml`. These findings, including GHSA-m7jm-9gc2-mpf2 and CVE-2026-25896, indicate severe risks that could lead to remote code execution or other significant system compromise. Further high-severity vulnerabilities are also present across various dependency files.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 261; 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.