Keyphrases MCP server - Model Context Protocol server to extract keyphrases from a text using a BERT model
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.
pypi: keyphrases-mcp @ 0.0.4, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- keyphrases-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
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.
v2.0.11
10 findings · 7.3s
v0.3.74
8 findings · 1.3s
v0.1.0
0 findings · 2.9s
v0.1.0
0 findings · 2.9s
v0.1.0
0 findings · 7.7s
v0.71.0
113 findings · 0.3s
v2.3.8
136 findings · 1.6s
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.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 | Flagged41 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: 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 267 findings across every scanner that examined this package. None of the 13 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 1 finding stand exactly as their scanners reported them, at full severity, as they would have without this review.
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.
4 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md, /repo/tests/fixtures/SKILL.md · reported by cisco-skill-scanner
3 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: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/pypi-publish.yml, .github/workflows/pulsemcp-publish.yml · reported by agent-audit-kit
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 GHSA-537c-gmf6-5ccf
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-c2jp-c369-7pvx
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-rcfx-77hg-w2wv
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-rf74-v2fm-23pw
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
1 AAK-MCP-SDK-CVE-2026-52869-001
Files: uv.lock · reported by agent-audit-kit
1 AAK-MCP-STATELESS-001
Files: src/server.py · reported by agent-audit-kit
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
1 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: HIDDEN_DATA_FILE · Files: /repo/.env-example · reported by cisco-skill-scanner
Critical vulnerabilities in dependencies and potential sensitive data exposure.
Critical vulnerabilities are present in several dependencies, as indicated by multiple PYSEC and CVE findings in `uv.lock`. The artifact may expose sensitive data, with a high severity finding related to `AAK-SECRET-004` in `src/config.py`. Potential resource abuse, specifically an infinite loop, was identified in `/repo/openai_agents_sdk/keyphrases_assistant.py`. Further high severity findings indicate potential issues with stateless components and SDK vulnerabilities.
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.
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SECRET-004
Files: src/config.py · reported by agent-audit-kit
1 AAK-TAINT-003
Files: src/server.py · reported by agent-audit-kit
1 CVE-2025-1194
Files: uv.lock · reported by trivy
1 CVE-2025-14009
Files: uv.lock · reported by trivy
1 CVE-2025-2099
Files: uv.lock · reported by trivy
1 CVE-2025-2148
Files: uv.lock · reported by trivy
1 CVE-2025-2149
Files: uv.lock · reported by trivy
1 CVE-2025-2953
Files: uv.lock · reported by trivy
1 CVE-2025-2998
Files: uv.lock · reported by trivy
1 CVE-2025-2999
Files: uv.lock · reported by trivy
1 CVE-2025-3000
Files: uv.lock · reported by trivy
1 CVE-2025-3001
Files: uv.lock · reported by trivy
1 CVE-2025-32434
Files: uv.lock · reported by trivy
1 CVE-2025-3262
Files: uv.lock · reported by trivy
1 CVE-2025-3263
Files: uv.lock · reported by trivy
1 CVE-2025-3264
Files: uv.lock · reported by trivy
1 CVE-2025-3730
Files: uv.lock · reported by trivy
1 CVE-2025-3777
Files: uv.lock · reported by trivy
1 CVE-2025-3933
Files: uv.lock · reported by trivy
1 CVE-2025-5197
Files: uv.lock · reported by trivy
1 CVE-2025-6051
Files: uv.lock · reported by trivy
1 CVE-2025-62727
Files: uv.lock · reported by trivy
1 CVE-2025-62800
Files: uv.lock · reported by trivy
1 CVE-2025-62801
Files: uv.lock · reported by trivy
1 CVE-2025-64340
Files: uv.lock · reported by trivy
1 CVE-2025-66221
Files: uv.lock · reported by trivy
1 CVE-2025-6638
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-68146
Files: uv.lock · reported by trivy
1 CVE-2025-68158
Files: uv.lock · reported by trivy
1 CVE-2025-69196
Files: uv.lock · reported by trivy
1 CVE-2025-6921
Files: uv.lock · reported by trivy
1 CVE-2025-71408
Files: uv.lock · reported by trivy
1 CVE-2025-8869
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-1703
Files: uv.lock · reported by trivy
1 CVE-2026-1839
Files: uv.lock · reported by trivy
1 CVE-2026-21441
Files: uv.lock · reported by trivy
1 CVE-2026-21860
Files: uv.lock · reported by trivy
1 CVE-2026-22701
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-27124
Files: uv.lock · reported by trivy
1 CVE-2026-27199
Files: uv.lock · reported by trivy
1 CVE-2026-27962
Files: uv.lock · reported by trivy
1 CVE-2026-28490
Files: uv.lock · reported by trivy
1 CVE-2026-28498
Files: uv.lock · reported by trivy
1 CVE-2026-28684
Files: uv.lock · reported by trivy
1 CVE-2026-28802
Files: uv.lock · reported by trivy
1 CVE-2026-3219
Files: uv.lock · reported by trivy
1 CVE-2026-32871
Files: uv.lock · 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-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-41425
Files: uv.lock · reported by trivy
1 CVE-2026-41479
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-4372
Files: uv.lock · reported by trivy
1 CVE-2026-44431
Files: uv.lock · reported by trivy
1 CVE-2026-44681
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-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-5241
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-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-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-59890
Files: uv.lock · reported by trivy
1 CVE-2026-59950
Files: uv.lock · reported by trivy
1 CVE-2026-6357
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-8643
Files: uv.lock · reported by trivy
1 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/scripts/pulsemcp_validate_server_json.py · reported by cisco-skill-scanner
1 GHSA-c678-jfcj-6jmf
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-f4hp-rmr7-r7v8
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-qfhq-4f3w-5fph
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-qq3j-4f4f-9583
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-rrmf-rvhw-rf47
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-vgrw-7cvw-pwgx
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-x3gm-94wq-g975
Files: /repo/uv.lock · reported by osv-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 PYSEC-2024-259
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-191
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-198
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-203
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-204
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-205
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-206
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-207
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-208
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-209
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-211
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-212
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-213
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-214
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-216
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-217
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-218
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-41
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1201
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1364
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1365
Files: /repo/uv.lock · 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-139
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-1795
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1796
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-188
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1942
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-196
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1970
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1977
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1979
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1980
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1981
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1983
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1984
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1985
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1986
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1987
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1988
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-2044
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2046
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-2116
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2117
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2118
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2119
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-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-2286
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2288
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2289
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2290
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2320
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2474
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2475
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2476
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-25
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-287
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2874
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2875
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2876
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-338
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3447
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-35
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-3657
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-597
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 RESOURCE_ABUSE_INFINITE_LOOP
Files: /repo/openai_agents_sdk/keyphrases_assistant.py · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 TOOL_ABUSE_UNDECLARED_NETWORK
Files: /repo/repo/README-pypi.md · reported by cisco-skill-scanner
Showing 25 of 135; the rest are in the per-scanner reports above.