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.
13 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 -- gayashan4lk/crewai-demo
6 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.
v2.0.11
6 findings · 6.5s
v0.3.74
2 findings · 0.9s
v0.1.0
0 findings · 2.7s
v0.1.0
0 findings · 2.7s
v0.71.0
223 findings · 0.3s
v2.3.8
231 findings · 8.3s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.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.9s
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 | Flagged47 | — | agentshield ·n/a: not applicablecisco-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 462 findings across every scanner that examined this package. None of the 13 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.
2 CVE-2026-45134
Files: ai_crew/uv.lock · reported by trivy
2 CVE-2026-55443
Files: ai_crew/uv.lock · reported by trivy
2 GHSA-4gg8-gxpx-9rph
Files: ai_crew/uv.lock, /repo/ai_crew/uv.lock · reported by trivy, osv-scanner
2 GHSA-537c-gmf6-5ccf
Files: ai_crew/uv.lock, /repo/ai_crew/uv.lock · reported by trivy, osv-scanner
2 GHSA-69x8-hrgq-fjj8
Files: ai_crew/uv.lock, /repo/ai_crew/uv.lock · reported by trivy, osv-scanner
2 GHSA-6g55-p6wh-862q
Files: /repo/ui/package-lock.json · reported by osv-scanner
2 GHSA-8h8q-6873-q5fj
Files: ui/package-lock.json, /repo/ui/package-lock.json · reported by trivy, osv-scanner
2 GHSA-f4xh-w4cj-qxq8
Files: ai_crew/uv.lock, /repo/ai_crew/uv.lock · reported by trivy, osv-scanner
2 GHSA-f88m-g3jw-g9cj
Files: /repo/ui/package-lock.json, ui/package-lock.json · reported by osv-scanner, trivy
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/ui/package-lock.json · reported by osv-scanner
2 GHSA-h25m-26qc-wcjf
Files: /repo/ui/package-lock.json, ui/package-lock.json · reported by osv-scanner, trivy
2 GHSA-jm82-fx9c-mx94
Files: /repo/ai_crew/uv.lock, ai_crew/uv.lock · reported by osv-scanner, trivy
2 GHSA-mwv6-3258-q52c
Files: ui/package-lock.json, /repo/ui/package-lock.json · reported by trivy, osv-scanner
2 GHSA-pjjw-68hj-v9mw
Files: /repo/ai_crew/uv.lock, ai_crew/uv.lock · reported by osv-scanner, trivy
2 GHSA-q4gf-8mx6-v5v3
Files: ui/package-lock.json, /repo/ui/package-lock.json · reported by trivy, osv-scanner
2 GHSA-qx2v-qp2m-jg93
Files: /repo/ui/package-lock.json · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/ui/package-lock.json · reported by osv-scanner
2 GHSA-w37m-7fhw-fmv9
Files: ui/package-lock.json, /repo/ui/package-lock.json · reported by trivy, osv-scanner
2 GHSA-w476-p2h3-79g9
Files: ai_crew/uv.lock, /repo/ai_crew/uv.lock · reported by trivy, osv-scanner
2 GHSA-xf7x-x43h-rpqh
Files: ai_crew/uv.lock, /repo/ai_crew/uv.lock · reported by trivy, osv-scanner
2 MANIFEST_MISSING_LICENSE
Files: /repo/ai_crew/SKILL.md, /repo/ui/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/ai_crew/SKILL.md, /repo/ui/SKILL.md · reported by cisco-skill-scanner
1 AAK-HEALTHCARE-AI-004
Files: ai_crew/report-3.md · reported by agent-audit-kit
1 AAK-LEGAL-002
Files: ui/package.json · reported by agent-audit-kit
1 CVE-2024-47081
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-0628
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-29927
Files: ui/package-lock.json · reported by trivy
1 CVE-2025-43859
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-4565
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-47273
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-48068
Files: ui/package-lock.json · reported by trivy
1 CVE-2025-50181
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-50182
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-53643
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-54121
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-54368
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-55173
Files: ui/package-lock.json · reported by trivy
1 CVE-2025-55182
Files: ui/package-lock.json · reported by trivy
1 CVE-2025-55197
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-57752
Files: ui/package-lock.json · reported by trivy
1 CVE-2025-57804
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-57822
Files: ui/package-lock.json · reported by trivy
1 CVE-2025-59471
Files: ui/package-lock.json · reported by trivy
1 CVE-2025-62707
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-62708
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-62727
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-65106
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-66019
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-66418
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-66471
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-67221
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-68146
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-68480
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-68664
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-69223
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-69224
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-69225
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-69226
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-69227
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-69228
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-69229
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-69230
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-6984
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2025-6985
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-0994
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-10812
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-21441
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-22690
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-22691
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-22701
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-22815
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-23490
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-24486
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-24688
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-2473
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-25087
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-25645
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-25990
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-26007
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-26013
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-27026
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-27628
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-27888
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-27980
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-28351
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-28684
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-28804
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-29057
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-30922
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-31240
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-31241
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-31245
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-31826
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-32597
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-33123
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-33699
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-34070
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-34073
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-34513
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-34514
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-34515
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-34516
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-34517
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-34518
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-34519
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-34520
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-34525
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-34993
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-35029
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-35030
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-40087
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-40192
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-40260
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-40347
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-41168
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-41182
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-41205
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-41305
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-41312
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-41313
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-41314
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-41481
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-41488
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-42308
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-42310
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-42311
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-42561
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-44307
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-44431
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-44572
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-44573
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-44575
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-44576
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-44577
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-44578
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-44579
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-44580
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-44581
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-44582
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-44843
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-45109
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-4539
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-45409
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-45623
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-47101
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-47102
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-47265
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-48155
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-48156
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-48522
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-48523
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-48524
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-48525
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-48526
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-48710
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-48735
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-48817
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-48818
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-49460
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-49461
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-49468
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-49476
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-49477
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-50269
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-53537
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-53538
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-53539
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-53540
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54058
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54059
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54060
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54273
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54274
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54275
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54276
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54277
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54278
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54279
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54280
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54283
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54530
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54531
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54651
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-55379
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-55380
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-55798
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59197
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59198
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59199
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59200
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59204
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59205
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59819
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59820
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59821
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59822
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59881
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59884
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59885
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59886
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59890
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59935
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59936
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59937
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-59938
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-64641
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-64643
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-64645
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-64646
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-64647
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-64648
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-64649
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-67213
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-67214
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-69153
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-69243
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-69244
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-69247
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-69249
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-71554
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-71852
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-71870
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-73646
Files: ui/package-lock.json · reported by trivy
1 CVE-2026-7597
Files: ai_crew/uv.lock · reported by trivy
1 GHSA-267c-6grr-h53f
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-26hh-7cqf-hhc6
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-36qx-fr4f-26g5
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-3g8h-86w9-wvmq
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-3h52-269p-cp9r
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-3x4c-7xq6-9pq8
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-4342-x723-ch2f
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-4633-3j49-mh5q
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-4c39-4ccg-62r3
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-68g3-v927-f742
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-89xv-2m56-2m9x
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-955p-x3mx-jcvp
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-9g9p-9gw9-jx7f
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-9qr9-h5gf-34mp
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-c4j6-fc7j-m34r
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-f82v-jwr5-mffw
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-ffhc-5mcf-pf4q
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-g5qg-72qw-gw5v
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-ggv3-7p47-pfv8
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-gx5p-jg67-6x7h
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-h64f-5h5j-jqjh
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-m99w-x7hq-7vfj
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-mg66-mrh9-m8jx
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-p9j2-gv94-2wf4
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-pqhf-p39g-3x64
Files: ai_crew/uv.lock · reported by trivy
1 GHSA-vfv6-92ff-j949
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-wfc6-r584-vfw7
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 GHSA-xv57-4mr9-wg8v
Files: /repo/ui/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo/ui · reported by cisco-skill-scanner
1 MANIFEST_INVALID_NAME
Files: /repo/ai_crew/SKILL.md · reported by cisco-skill-scanner
1 PYSEC-2025-183
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2025-49
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-107
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1097
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1099
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1100
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1101
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1104
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1105
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1106
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1107
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1109
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-113
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-120
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1374
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1375
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1435
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1515
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1518
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1520
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1546
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1605
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-165
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-175
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-176
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1761
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1762
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-177
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-178
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-179
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1805
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1806
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1810
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1827
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1828
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1829
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1830
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1831
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1832
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1833
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1852
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1872
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1941
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1942
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1994
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1996
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1997
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1998
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-1999
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2001
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2094
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2095
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2096
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2097
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2098
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2099
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2100
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2101
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2102
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2103
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2104
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2105
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2106
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2107
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2108
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2109
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2110
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2111
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2112
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2113
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2141
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2192
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2193
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2249
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2250
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2252
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2253
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2254
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2255
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2256
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2257
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2263
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2280
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2295
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-237
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2500
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2555
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2556
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2562
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2563
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2564
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2582
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2583
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2597
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2598
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2600
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2617
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2633
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2634
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2635
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2636
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2874
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-2987
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3004
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3005
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3006
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3007
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3009
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3010
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3011
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3012
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3013
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3014
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3015
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3016
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3017
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3018
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3019
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3020
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3021
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3022
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3023
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3024
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3025
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3026
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3027
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3036
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3037
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3038
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3039
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3040
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3041
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3071
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3072
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3447
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3451
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3453
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3454
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3455
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3456
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3457
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3468
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3476
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3477
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3478
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3479
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-348
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3493
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3494
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3495
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3496
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-35
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3545
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3546
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3547
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3552
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3553
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3554
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3610
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3611
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3612
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3613
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3628
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3655
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-3656
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-373
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-388
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-390
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-76
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-77
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
1 PYSEC-2026-88
Files: /repo/ai_crew/uv.lock · reported by osv-scanner
The model could have called any of these a false positive and did not.
1 CVE-2026-27024
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-27025
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-54282
Files: ai_crew/uv.lock · reported by trivy
1 CVE-2026-69248
Files: ai_crew/uv.lock · reported by trivy
Artifact contains critical vulnerabilities in dependencies.
This artifact includes dependencies with multiple critical vulnerabilities, such as PYSEC-2026-2102 and CVE-2025-43859 in `ai_crew/uv.lock`, and GHSA-9qr9-h5gf-34mp and CVE-2025-29927 in `ui/package-lock.json`. These issues could lead to remote code execution, denial of service, or information disclosure. Several high severity vulnerabilities are also present across these dependency files.
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 194; the rest are in the per-scanner reports above.