--- title: "optimum-tpu trust report" type: "trust-report" slug: "huggingface-optimum-tpu" canonical_url: "https://www.graphcanon.com/tools/huggingface-optimum-tpu/trust" computed_at: "2026-07-11T23:37:57.293Z" maintenance_label: "Archived" security_status: "findings" --- # optimum-tpu 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: Archived (8% recency signal) - Days since last push: 169 - Last release: 2024-12-19T10:43:41Z - Methodology: github_public_v1 ## Provenance - GitHub repo id: 756234502 - Not a fork - Owner type: Organization - Computed at: 2026-07-11T23:37:57.293Z - Methodology: github_public_v1 ## Security scan - Status: Findings present (1 critical, 0 high, 3 medium, 17 low) · last scan 2026-07-11T23:37:57.841Z ### Findings - **low**: PyTorch susceptible to local Denial of Service (torch@2.5.1 · CVE-2025-2953 · requirements.txt) - **critical**: PyTorch: `torch.load` with `weights_only=True` leads to remote code execution (torch@2.5.1 · CVE-2025-32434 · requirements.txt) - **medium**: PyTorch Improper Resource Shutdown or Release vulnerability (torch@2.5.1 · CVE-2025-3730 · requirements.txt) - **low**: PyTorch Tuple Handler is Vulnerable to Memory Corruption through Manipulation of None Argument (torch@2.5.1 · CVE-2025-2148 · requirements.txt) - **medium**: PyTorch is Vulnerable to Memory Consumption through pad_packed_sequence Function (torch@2.5.1 · CVE-2025-2998 · requirements.txt) - **low**: PyTorch is vulnerable to memory corruption through its torch.lstm_cell function (torch@2.5.1 · CVE-2025-3001 · requirements.txt) - **low**: PyTorch is vulnerable to memory corruption through its torch.jit.script function (torch@2.5.1 · CVE-2025-3000 · requirements.txt) - **medium**: PyTorch is vulnerable to memory corruption through its unpack_sequence function (torch@2.5.1 · CVE-2025-2999 · requirements.txt) - **low**: PyTorch: Manipulation of the argument scale/zero_point leads to improper initialization via Quantized Sigmoid Module (torch@2.5.1 · CVE-2025-2149 · requirements.txt) - **low**: PYSEC-2025-191 (torch@2.5.1 · CVE-2025-2953 · requirements.txt) - **low**: PYSEC-2025-198 (torch@2.5.1 · CVE-2025-46148 · requirements.txt) - **low**: PYSEC-2025-203 (torch@2.5.1 · CVE-2025-55551 · requirements.txt) - **low**: PYSEC-2025-204 (torch@2.5.1 · CVE-2025-55552 · requirements.txt) - **low**: PYSEC-2025-205 (torch@2.5.1 · CVE-2025-55553 · requirements.txt) - **low**: PYSEC-2025-206 (torch@2.5.1 · CVE-2025-55554 · requirements.txt) - **low**: PYSEC-2025-207 (torch@2.5.1 · CVE-2025-55557 · requirements.txt) - **low**: PYSEC-2025-208 (torch@2.5.1 · CVE-2025-55558 · requirements.txt) - **low**: PYSEC-2025-209 (torch@2.5.1 · CVE-2025-55560 · requirements.txt) - **low**: PYSEC-2025-41 (torch@2.5.1 · CVE-2025-32434 · requirements.txt) - **low**: PYSEC-2026-139 (torch@2.5.1 · CVE-2026-4538 · requirements.txt) - **low**: PyTorch Improper Resource Shutdown or Release vulnerability (torch@2.5.1 · CVE-2025-3730 · 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 optimum-tpu maintained? optimum-tpu is archived on GitHub. GraphCanon treats archived repositories as dormant regardless of past activity. ### Is optimum-tpu safe to use? Last scanned today (deps profile). Status: 1 critical, 3 medium, 17 low - 1 critical, 3 medium, 17 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 optimum-tpu as safe - review maintenance, provenance, and scan findings on this page before adopting. ### Is optimum-tpu a fork? No. optimum-tpu is not flagged as a fork in GitHub metadata at the time of the last refresh. ### Does optimum-tpu have known security vulnerabilities? Last scanned today (deps profile). Status: 1 critical, 3 medium, 17 low - 1 critical, 3 medium, 17 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 optimum-tpu 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 optimum-tpu? We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for optimum-tpu. Signals are sourced heuristics with explicit limits - see [trust methodology](/trust-methodology). ### How does GraphCanon assess trust for optimum-tpu? 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/huggingface-optimum-tpu/trust`](/api/graphcanon/tools/huggingface-optimum-tpu/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/_