--- title: "LazyLLM trust report" type: "trust-report" slug: "lazyagi-lazyllm" canonical_url: "https://www.graphcanon.com/tools/lazyagi-lazyllm/trust" computed_at: "2026-07-11T10:41:31.161Z" maintenance_label: "Very active" security_status: "findings" --- # LazyLLM 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: Very active (96% recency signal) - Days since last push: 1 - Last release: 2026-07-03T10:00:39Z - Releases (90d): 3 - Methodology: github_public_v1 ## Provenance - GitHub repo id: 810121174 - Not a fork - Owner type: Organization - Computed at: 2026-07-11T10:41:31.161Z - Methodology: github_public_v1 ## Security scan - Status: Findings present (0 critical, 0 high, 0 medium, 31 low) · last scan 2026-07-11T10:41:32.027Z ### Findings - **low**: GHSA-9hjg-9r4m-mvj7 (requests@2.32.2 · requirements.txt) - **low**: GHSA-gc5v-m9x4-r6x2 (requests@2.32.2 · requirements.txt) - **low**: PYSEC-2026-1872 (requests@2.32.2 · requirements.txt) - **low**: GHSA-39mp-8hj3-5c49 (gradio@5.49.1 · requirements.txt) - **low**: GHSA-7hp7-4p35-3cx2 (gradio@5.49.1 · requirements.txt) - **low**: GHSA-h3h8-3v2v-rg7m (gradio@5.49.1 · requirements.txt) - **low**: GHSA-jmh7-g254-2cq9 (gradio@5.49.1 · requirements.txt) - **low**: GHSA-pfjf-5gxr-995x (gradio@5.49.1 · requirements.txt) - **low**: PYSEC-2026-211 (gradio@5.49.1 · requirements.txt) - **low**: PYSEC-2026-63 (gradio@5.49.1 · requirements.txt) - **low**: PYSEC-2026-64 (gradio@5.49.1 · requirements.txt) - **low**: PYSEC-2026-65 (gradio@5.49.1 · requirements.txt) - **low**: PYSEC-2026-66 (gradio@5.49.1 · requirements.txt) - **low**: GHSA-7gcm-g887-7qv7 (protobuf@3.20.1 · requirements.txt) - **low**: GHSA-8gq9-2x98-w8hf (protobuf@3.20.1 · requirements.txt) - **low**: GHSA-8qvm-5x2c-j2w7 (protobuf@3.20.1 · requirements.txt) - **low**: PYSEC-2026-1805 (protobuf@3.20.1 · requirements.txt) - **low**: PYSEC-2026-1806 (protobuf@3.20.1 · requirements.txt) - **low**: PYSEC-2026-899 (protobuf@3.20.1 · requirements.txt) - **low**: GHSA-752w-5fwx-jx9f (pyjwt@2.8.0 · requirements.txt) - **low**: GHSA-993g-76c3-p5m4 (pyjwt@2.8.0 · requirements.txt) - **low**: GHSA-fhv5-28vv-h8m8 (pyjwt@2.8.0 · requirements.txt) - **low**: GHSA-w7vc-732c-9m39 (pyjwt@2.8.0 · requirements.txt) - **low**: GHSA-xgmm-8j9v-c9wx (pyjwt@2.8.0 · requirements.txt) - **low**: PYSEC-2025-183 (pyjwt@2.8.0 · requirements.txt) - **low**: PYSEC-2026-120 (pyjwt@2.8.0 · requirements.txt) - **low**: PYSEC-2026-175 (pyjwt@2.8.0 · requirements.txt) - **low**: PYSEC-2026-177 (pyjwt@2.8.0 · requirements.txt) - **low**: PYSEC-2026-178 (pyjwt@2.8.0 · requirements.txt) - **low**: PYSEC-2026-179 (pyjwt@2.8.0 · requirements.txt) - **low**: GHSA-54jj-px8x-5w5q (deepdiff@8.6.1 · 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 LazyLLM maintained? GraphCanon rates LazyLLM "Very active" (96% maintenance signal from public GitHub metadata, computed today). Last push was 1 days ago. 3 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained. ### Is LazyLLM safe to use? Last scanned today (deps profile). Status: 31 low - 31 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 LazyLLM as safe - review maintenance, provenance, and scan findings on this page before adopting. ### Is LazyLLM a fork? No. LazyLLM is not flagged as a fork in GitHub metadata at the time of the last refresh. ### Does LazyLLM have known security vulnerabilities? Last scanned today (deps profile). Status: 31 low - 31 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 LazyLLM 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 LazyLLM? We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for LazyLLM. Signals are sourced heuristics with explicit limits - see [trust methodology](/trust-methodology). ### How does GraphCanon assess trust for LazyLLM? 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/lazyagi-lazyllm/trust`](/api/graphcanon/tools/lazyagi-lazyllm/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/_