Loading the registry…
MCP-based Audit & Compliance Platform with Financial Data and Policy Engine Tools
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.
5 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-audit-compliance-platform
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
4 findings · 7.9s
v0.3.74
10 findings · 2.1s
v0.1.0
0 findings · 3.5s
v0.1.0
0 findings · 3.5s
v0.71.0
134 findings · 0.4s
v2.3.8
135 findings · 2.0s
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.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 21, 2026 | Flagged37 | — | 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 283 findings across every scanner that examined this package. None of the 5 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 AAK-OAUTH-3P-001
Files: pyproject.toml · reported by agent-audit-kit
2 AAK-SSRF-TOCTOU-001
Files: pyproject.toml, uv.lock · reported by agent-audit-kit
2 CVE-2026-45134
Files: uv.lock · reported by trivy
2 GHSA-2f96-g7mh-g2hx
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-3f7w-8rr8-f37f
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-3rp5-jjmw-4wv2
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-4gmw-gg2m-w46p
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-539m-9xh6-q6rr
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-6p8h-3wgx-97gf
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-94p4-4cq8-9g67
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-956x-8gvw-wg5v
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-9rj7-rf2p-w77r
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-f4xh-w4cj-qxq8
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-fjr4-x663-mwxc
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-hh9p-6wh2-4mfc
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-hmq2-w58f-27jc
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-jm78-9fvv-mhgr
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-mv93-w799-cj2w
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-p538-c434-8v24
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-pw6j-qg29-8w7f
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-r9mr-m37c-5fr3
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-rwj8-pgh3-r573
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-wvpp-8hx9-p66j
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
1 AAK-DNS-REBIND-002
Files: pyproject.toml · reported by agent-audit-kit
1 AAK-LANGCHAIN-SSRF-REDIR-001
Files: uv.lock · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SECRET-004
Files: src/tracing.py · reported by agent-audit-kit
1 CVE-2025-62727
Files: uv.lock · reported by trivy
1 CVE-2025-65106
Files: uv.lock · 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-67221
Files: uv.lock · reported by trivy
1 CVE-2025-67724
Files: uv.lock · reported by trivy
1 CVE-2025-67725
Files: uv.lock · reported by trivy
1 CVE-2025-67726
Files: uv.lock · reported by trivy
1 CVE-2025-68480
Files: uv.lock · reported by trivy
1 CVE-2025-68664
Files: uv.lock · 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-71176
Files: uv.lock · reported by trivy
1 CVE-2026-0994
Files: uv.lock · reported by trivy
1 CVE-2026-10804
Files: uv.lock · reported by trivy
1 CVE-2026-21441
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-25087
Files: uv.lock · reported by trivy
1 CVE-2026-25528
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-26013
Files: uv.lock · reported by trivy
1 CVE-2026-27794
Files: uv.lock · reported by trivy
1 CVE-2026-28277
Files: uv.lock · reported by trivy
1 CVE-2026-28684
Files: uv.lock · reported by trivy
1 CVE-2026-31958
Files: uv.lock · reported by trivy
1 CVE-2026-32274
Files: uv.lock · reported by trivy
1 CVE-2026-33682
Files: uv.lock · reported by trivy
1 CVE-2026-34070
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-35536
Files: uv.lock · reported by trivy
1 CVE-2026-40087
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-41182
Files: uv.lock · reported by trivy
1 CVE-2026-41205
Files: uv.lock · reported by trivy
1 CVE-2026-41481
Files: uv.lock · reported by trivy
1 CVE-2026-41488
Files: uv.lock · reported by trivy
1 CVE-2026-42215
Files: uv.lock · reported by trivy
1 CVE-2026-42284
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-44243
Files: uv.lock · reported by trivy
1 CVE-2026-44244
Files: uv.lock · reported by trivy
1 CVE-2026-44307
Files: uv.lock · reported by trivy
1 CVE-2026-44431
Files: uv.lock · reported by trivy
1 CVE-2026-44843
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-47265
Files: uv.lock · reported by trivy
1 CVE-2026-48710
Files: uv.lock · reported by trivy
1 CVE-2026-48775
Files: uv.lock · reported by trivy
1 CVE-2026-48776
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-49853
Files: uv.lock · reported by trivy
1 CVE-2026-49854
Files: uv.lock · reported by trivy
1 CVE-2026-49855
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-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-55379
Files: uv.lock · reported by trivy
1 CVE-2026-55380
Files: uv.lock · reported by trivy
1 CVE-2026-55443
Files: uv.lock · reported by trivy
1 CVE-2026-55798
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-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 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/streamlit_app.py · reported by cisco-skill-scanner
1 GHSA-78cv-mqj4-43f7
Files: uv.lock · reported by trivy
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 PYSEC-2025-265
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-266
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-267
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-107
Files: /repo/uv.lock · reported by osv-scanner
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-113
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-140
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1518
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1605
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-1805
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1845
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-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-212
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2120
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2121
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2160
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2162
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2163
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2192
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2193
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-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-2285
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2287
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-237
Files: /repo/uv.lock · 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-2560
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2562
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2563
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2564
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2573
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2574
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2575
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2582
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2583
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2584
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2617
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-3387
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3388
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3389
Files: /repo/uv.lock · 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-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-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-373
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-76
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-77
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-83
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-88
Files: /repo/uv.lock · reported by osv-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · 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.
1 CVE-2026-54282
Files: uv.lock · reported by trivy
Critical vulnerabilities and high-risk issues detected
The artifact contains multiple critical vulnerabilities in its dependencies, as indicated by several PYSEC and CVE findings in `uv.lock`. High-severity issues include a potential secret exposure in `src/tracing.py`, which could lead to credential access. Additionally, the artifact exhibits a Server-Side Request Forgery (SSRF) vulnerability with redirection, potentially enabling network egress and access to internal resources.
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 154; the rest are in the per-scanner reports above.