--- title: "llm-attacks trust report" type: "trust-report" slug: "llm-attacks-llm-attacks" canonical_url: "https://www.graphcanon.com/tools/llm-attacks-llm-attacks/trust" computed_at: "2026-07-11T23:39:45.768Z" maintenance_label: "Dormant" security_status: "findings" --- # llm-attacks trust report _Sourced [trust signals](/glossary/trust-and-signals/trust-signal) from public GitHub metadata and optional dependency [security scans](/glossary/trust-and-signals/security-scan). Not a security guarantee._ ## Maintenance - Label: Dormant (18% recency signal) - Days since last push: 708 - Methodology: github_public_v1 ## Provenance - GitHub repo id: 671271357 - Not a fork - Owner type: Organization - Computed at: 2026-07-11T23:39:45.768Z - Methodology: github_public_v1 ## Security scan - Status: Findings present (0 critical, 0 high, 0 medium, 58 low) · last scan 2026-07-11T23:39:46.270Z ### Findings - **low**: GHSA-282v-666c-3fvg (transformers@4.28.1 · requirements.txt) - **low**: GHSA-29pf-2h5f-8g72 (transformers@4.28.1 · requirements.txt) - **low**: GHSA-37mw-44qp-f5jm (transformers@4.28.1 · requirements.txt) - **low**: GHSA-37q5-v5qm-c9v8 (transformers@4.28.1 · requirements.txt) - **low**: GHSA-3863-2447-669p (transformers@4.28.1 · requirements.txt) - **low**: GHSA-4w7r-h757-3r74 (transformers@4.28.1 · requirements.txt) - **low**: GHSA-59p9-h35m-wg4g (transformers@4.28.1 · requirements.txt) - **low**: GHSA-69w3-r845-3855 (transformers@4.28.1 · requirements.txt) - **low**: GHSA-6rvg-6v2m-4j46 (transformers@4.28.1 · requirements.txt) - **low**: GHSA-9356-575x-2w9m (transformers@4.28.1 · requirements.txt) - **low**: GHSA-fpwr-67px-3qhx (transformers@4.28.1 · requirements.txt) - **low**: GHSA-hxxf-235m-72v3 (transformers@4.28.1 · requirements.txt) - **low**: GHSA-jjph-296x-mrcr (transformers@4.28.1 · requirements.txt) - **low**: GHSA-phhr-52qp-3mj4 (transformers@4.28.1 · requirements.txt) - **low**: GHSA-q2wp-rjmx-x6x9 (transformers@4.28.1 · requirements.txt) - **low**: GHSA-qq3j-4f4f-9583 (transformers@4.28.1 · requirements.txt) - **low**: GHSA-qxrp-vhvm-j765 (transformers@4.28.1 · requirements.txt) - **low**: GHSA-rcv9-qm8p-9p6j (transformers@4.28.1 · requirements.txt) - **low**: GHSA-v68g-wm8c-6x7j (transformers@4.28.1 · requirements.txt) - **low**: GHSA-wrfc-pvp9-mr9g (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2023-299 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2023-300 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2023-301 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2024-227 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2024-228 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2024-229 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2025-211 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2025-212 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2025-213 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2025-214 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2025-215 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2025-216 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2025-217 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2025-218 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2025-40 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2026-1977 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2026-1978 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2026-1980 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2026-1981 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2026-1982 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2026-1983 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2026-1984 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2026-1985 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2026-1986 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2026-1987 (transformers@4.28.1 · requirements.txt) - **low**: PYSEC-2026-1988 (transformers@4.28.1 · requirements.txt) - **low**: GHSA-5h65-jx66-j7p5 (fschat@0.2.20 · requirements.txt) - **low**: GHSA-77cj-rv5x-v6r2 (fschat@0.2.20 · requirements.txt) - **low**: GHSA-79rp-v9rm-gxm8 (fschat@0.2.20 · requirements.txt) - **low**: GHSA-f3q6-69f3-vwch (fschat@0.2.20 · requirements.txt) - **low**: GHSA-g44m-hpf4-vmrp (fschat@0.2.20 · requirements.txt) - **low**: GHSA-h254-g997-685c (fschat@0.2.20 · requirements.txt) - **low**: GHSA-qg86-f892-m4hj (fschat@0.2.20 · requirements.txt) - **low**: PYSEC-2026-1394 (fschat@0.2.20 · requirements.txt) - **low**: PYSEC-2026-1395 (fschat@0.2.20 · requirements.txt) - **low**: PYSEC-2026-1396 (fschat@0.2.20 · requirements.txt) - **low**: PYSEC-2026-1397 (fschat@0.2.20 · requirements.txt) - **low**: PYSEC-2026-1398 (fschat@0.2.20 · requirements.txt) ## Method and caveats These are heuristics from public GitHub data and optional dependency scans, sourced and dated. "No criticals found on 2026-07-11" is not a guarantee of safety. See the full methodology: [/trust-methodology](/trust-methodology.md). ## Common questions ### Is llm-attacks maintained? GraphCanon rates llm-attacks "Dormant" (18% maintenance signal from public GitHub metadata, computed today). Last push was 708 days ago. This is a recency heuristic, not a guarantee the project will stay maintained. ### Is llm-attacks safe to use? Last scanned today (deps profile). Status: 58 low - 58 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify llm-attacks as safe - review maintenance, provenance, and scan findings on this page before adopting. ### Is llm-attacks a fork? No. llm-attacks is not flagged as a fork in GitHub metadata at the time of the last refresh. ### Does llm-attacks have known security vulnerabilities? Last scanned today (deps profile). Status: 58 low - 58 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. ### How often is the llm-attacks trust report updated? Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed today (methodology github_public_v1). ### What does GraphCanon never claim about llm-attacks? We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for llm-attacks. Signals are sourced heuristics with explicit limits - see [trust methodology](/trust-methodology). ### How does GraphCanon assess trust for llm-attacks? Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read [trust methodology](/trust-methodology) for full scope and limits. --- **Machine-readable endpoints** - JSON: [`/api/graphcanon/tools/llm-attacks-llm-attacks/trust`](/api/graphcanon/tools/llm-attacks-llm-attacks/trust) - LLM index: [/llms.txt](/llms.txt) - Full corpus: [/llms-full.txt](/llms-full.txt) _GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_