Loading the registry…
Add your description here
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.
32 critical findings reported by trivy, osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- mcp-server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
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
2 findings · 6.4s
v0.3.74
6 findings · 1.5s
v0.1.0
0 findings · 2.8s
v0.1.0
1 finding · 2.8s
v0.71.0
134 findings · 0.3s
v2.3.8
148 findings · 1.7s
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 · 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 21, 2026 | Flagged40 | — | 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 291 findings across every scanner that examined this package. None of the 32 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 AAK-MCP-SDK-CVE-2026-52869-001
Files: pyproject.toml, uv.lock · reported by agent-audit-kit
2 GHSA-537c-gmf6-5ccf
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-69x8-hrgq-fjj8
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-c2jp-c369-7pvx
Files: requirements.txt, /repo/requirements.txt · reported by trivy, osv-scanner
2 GHSA-rcfx-77hg-w2wv
Files: requirements.txt, /repo/requirements.txt · reported by trivy, osv-scanner
2 GHSA-rf74-v2fm-23pw
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 PYSEC-2026-2138
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2139
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2140
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-228
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-229
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-319
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-33
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-34
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3448
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-587
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-588
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
1 AAK-MCP-LITELLM-CVE-2026-59822-001
Files: uv.lock · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SSRF-002
Files: main.py · reported by agent-audit-kit
1 AAK-SSRF-005
Files: main.py · reported by agent-audit-kit
1 CVE-2025-14009
Files: uv.lock · reported by trivy
1 CVE-2025-6176
Files: uv.lock · reported by trivy
1 CVE-2025-62727
Files: uv.lock · reported by trivy
1 CVE-2025-62800
Files: requirements.txt · reported by trivy
1 CVE-2025-62801
Files: requirements.txt · reported by trivy
1 CVE-2025-64340
Files: requirements.txt · reported by trivy
1 CVE-2025-66416
Files: uv.lock · reported by trivy
1 CVE-2025-66418
Files: uv.lock · reported by trivy
1 CVE-2025-66471
Files: uv.lock · reported by trivy
1 CVE-2025-68146
Files: uv.lock · reported by trivy
1 CVE-2025-69196
Files: requirements.txt · reported by trivy
1 CVE-2025-69223
Files: uv.lock · reported by trivy
1 CVE-2025-69224
Files: uv.lock · reported by trivy
1 CVE-2025-69225
Files: uv.lock · reported by trivy
1 CVE-2025-69226
Files: uv.lock · reported by trivy
1 CVE-2025-69227
Files: uv.lock · reported by trivy
1 CVE-2025-69228
Files: uv.lock · reported by trivy
1 CVE-2025-69229
Files: uv.lock · reported by trivy
1 CVE-2025-69230
Files: uv.lock · reported by trivy
1 CVE-2025-71408
Files: uv.lock · reported by trivy
1 CVE-2026-0846
Files: uv.lock · reported by trivy
1 CVE-2026-0847
Files: uv.lock · reported by trivy
1 CVE-2026-12061
Files: uv.lock · reported by trivy
1 CVE-2026-12072
Files: uv.lock · reported by trivy
1 CVE-2026-12074
Files: uv.lock · reported by trivy
1 CVE-2026-12075
Files: uv.lock · reported by trivy
1 CVE-2026-12243
Files: uv.lock · reported by trivy
1 CVE-2026-21441
Files: uv.lock · reported by trivy
1 CVE-2026-22701
Files: uv.lock · reported by trivy
1 CVE-2026-22815
Files: uv.lock · reported by trivy
1 CVE-2026-24486
Files: uv.lock · reported by trivy
1 CVE-2026-25645
Files: uv.lock · reported by trivy
1 CVE-2026-25990
Files: uv.lock · reported by trivy
1 CVE-2026-26007
Files: uv.lock · reported by trivy
1 CVE-2026-26216
Files: uv.lock · reported by trivy
1 CVE-2026-26217
Files: uv.lock · reported by trivy
1 CVE-2026-27124
Files: requirements.txt · reported by trivy
1 CVE-2026-27448
Files: uv.lock · reported by trivy
1 CVE-2026-27459
Files: uv.lock · reported by trivy
1 CVE-2026-28684
Files: uv.lock · reported by trivy
1 CVE-2026-32871
Files: requirements.txt · reported by trivy
1 CVE-2026-33230
Files: uv.lock · reported by trivy
1 CVE-2026-33231
Files: uv.lock · reported by trivy
1 CVE-2026-33236
Files: uv.lock · reported by trivy
1 CVE-2026-34073
Files: uv.lock · reported by trivy
1 CVE-2026-34513
Files: uv.lock · reported by trivy
1 CVE-2026-34514
Files: uv.lock · reported by trivy
1 CVE-2026-34515
Files: uv.lock · reported by trivy
1 CVE-2026-34516
Files: uv.lock · reported by trivy
1 CVE-2026-34517
Files: uv.lock · reported by trivy
1 CVE-2026-34518
Files: uv.lock · reported by trivy
1 CVE-2026-34519
Files: uv.lock · reported by trivy
1 CVE-2026-34520
Files: uv.lock · reported by trivy
1 CVE-2026-34525
Files: uv.lock · reported by trivy
1 CVE-2026-34993
Files: uv.lock · reported by trivy
1 CVE-2026-35029
Files: uv.lock · reported by trivy
1 CVE-2026-35030
Files: uv.lock · reported by trivy
1 CVE-2026-39892
Files: uv.lock · reported by trivy
1 CVE-2026-40192
Files: uv.lock · reported by trivy
1 CVE-2026-40347
Files: uv.lock · reported by trivy
1 CVE-2026-41066
Files: uv.lock · reported by trivy
1 CVE-2026-42271
Files: uv.lock · reported by trivy
1 CVE-2026-42308
Files: uv.lock · reported by trivy
1 CVE-2026-42309
Files: uv.lock · reported by trivy
1 CVE-2026-42310
Files: uv.lock · reported by trivy
1 CVE-2026-42311
Files: uv.lock · reported by trivy
1 CVE-2026-42561
Files: uv.lock · reported by trivy
1 CVE-2026-44431
Files: uv.lock · reported by trivy
1 CVE-2026-4539
Files: uv.lock · reported by trivy
1 CVE-2026-45409
Files: uv.lock · reported by trivy
1 CVE-2026-47101
Files: uv.lock · reported by trivy
1 CVE-2026-47102
Files: uv.lock · reported by trivy
1 CVE-2026-47265
Files: uv.lock · reported by trivy
1 CVE-2026-48710
Files: uv.lock · reported by trivy
1 CVE-2026-48817
Files: uv.lock · reported by trivy
1 CVE-2026-48818
Files: uv.lock · reported by trivy
1 CVE-2026-49468
Files: uv.lock · reported by trivy
1 CVE-2026-49476
Files: uv.lock · reported by trivy
1 CVE-2026-49477
Files: uv.lock · reported by trivy
1 CVE-2026-50269
Files: uv.lock · reported by trivy
1 CVE-2026-52869
Files: uv.lock · reported by trivy
1 CVE-2026-53537
Files: uv.lock · reported by trivy
1 CVE-2026-53538
Files: uv.lock · reported by trivy
1 CVE-2026-53539
Files: uv.lock · reported by trivy
1 CVE-2026-53540
Files: uv.lock · reported by trivy
1 CVE-2026-53753
Files: uv.lock · reported by trivy
1 CVE-2026-53754
Files: uv.lock · reported by trivy
1 CVE-2026-53755
Files: uv.lock · reported by trivy
1 CVE-2026-54058
Files: uv.lock · reported by trivy
1 CVE-2026-54059
Files: uv.lock · reported by trivy
1 CVE-2026-54060
Files: uv.lock · reported by trivy
1 CVE-2026-54273
Files: uv.lock · reported by trivy
1 CVE-2026-54274
Files: uv.lock · reported by trivy
1 CVE-2026-54275
Files: uv.lock · reported by trivy
1 CVE-2026-54276
Files: uv.lock · reported by trivy
1 CVE-2026-54277
Files: uv.lock · reported by trivy
1 CVE-2026-54278
Files: uv.lock · reported by trivy
1 CVE-2026-54279
Files: uv.lock · reported by trivy
1 CVE-2026-54280
Files: uv.lock · reported by trivy
1 CVE-2026-54283
Files: uv.lock · reported by trivy
1 CVE-2026-54293
Files: uv.lock · reported by trivy
1 CVE-2026-55379
Files: uv.lock · reported by trivy
1 CVE-2026-55380
Files: uv.lock · reported by trivy
1 CVE-2026-55798
Files: uv.lock · reported by trivy
1 CVE-2026-56266
Files: uv.lock · reported by trivy
1 CVE-2026-59197
Files: uv.lock · reported by trivy
1 CVE-2026-59198
Files: uv.lock · reported by trivy
1 CVE-2026-59199
Files: uv.lock · reported by trivy
1 CVE-2026-59200
Files: uv.lock · reported by trivy
1 CVE-2026-59204
Files: uv.lock · reported by trivy
1 CVE-2026-59205
Files: uv.lock · reported by trivy
1 CVE-2026-59819
Files: uv.lock · reported by trivy
1 CVE-2026-59820
Files: uv.lock · reported by trivy
1 CVE-2026-59821
Files: uv.lock · reported by trivy
1 CVE-2026-59822
Files: uv.lock · reported by trivy
1 CVE-2026-59881
Files: uv.lock · reported by trivy
1 CVE-2026-59950
Files: uv.lock · reported by trivy
1 CVE-2026-69243
Files: uv.lock · reported by trivy
1 CVE-2026-69244
Files: uv.lock · reported by trivy
1 CVE-2026-69247
Files: uv.lock · reported by trivy
1 CVE-2026-69249
Files: uv.lock · reported by trivy
1 CVE-2026-71554
Files: uv.lock · reported by trivy
1 GHSA-2jq4-q6vv-4cp3
Files: uv.lock · reported by trivy
1 GHSA-7cx2-g3h9-382p
Files: uv.lock · reported by trivy
1 GHSA-f989-c77f-r2cq
Files: uv.lock · reported by trivy
1 GHSA-r253-r9jw-qg44
Files: uv.lock · reported by trivy
1 GHSA-wm69-2pc3-rmmf
Files: uv.lock · reported by trivy
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 opt.nerlo-rules.nerlo-install-run-bundled-artifact
Files: /repo/README.md · reported by nerlo-install-instruction
1 PYSEC-2026-1097
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1099
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1100
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1101
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1105
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1106
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1107
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1109
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1364
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1365
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1374
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1375
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1617
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-165
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1852
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1942
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1994
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1996
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1998
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2078
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2085
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2094
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2095
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2096
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2097
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2098
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2099
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2100
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2101
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2102
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2103
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2104
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2105
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2106
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2107
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2108
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2109
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2110
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2111
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2112
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2113
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2235
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2236
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2237
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2250
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2251
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2252
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2253
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2254
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2255
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2256
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2257
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2268
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2269
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2280
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-237
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2401
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2474
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2475
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2476
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2597
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2598
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2599
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2600
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2874
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2987
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3036
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3037
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3038
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3039
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3040
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3041
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3071
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3072
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-338
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3451
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3453
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3454
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3476
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3477
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3478
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3479
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3493
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3494
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3495
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3496
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-35
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3545
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3546
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3547
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3552
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3553
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3554
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3581
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3582
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3583
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3584
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-36
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3628
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3657
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-388
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-390
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-597
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-87
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-96
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-97
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-98
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-99
Files: /repo/uv.lock · reported by osv-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
1 CVE-2026-54282
Files: uv.lock · reported by trivy
1 CVE-2026-69248
Files: uv.lock · reported by trivy
Critical vulnerabilities detected in artifact dependencies
The artifact includes dependencies with multiple critical vulnerabilities, primarily identified in `requirements.txt` and `uv.lock`. These vulnerabilities could potentially lead to remote code execution, denial of service, or information disclosure. Reviewing the specific critical findings, such as PYSEC-2026-2138 and CVE-2026-32871, is essential before deployment.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 179; 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.