Trust and health report
LazyLLM - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated today · GitHub synced today
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Very active96% signal
last push 1d ago · last release 1w · 3 releases (90d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 810121174
- Not a fork
- Verified publisher: organization account
- Computed today
Security scan
Dependency advisory security scan when a lockfile is present. Not a full code audit.
- Status
- 31 low
- Last scan
- today
- Scanner
- osv@v1
Findings
GHSA-9hjg-9r4m-mvj7
requests@2.32.2 · requirements.txt
GHSA-gc5v-m9x4-r6x2
requests@2.32.2 · requirements.txt
PYSEC-2026-1872
requests@2.32.2 · requirements.txt
GHSA-39mp-8hj3-5c49
gradio@5.49.1 · requirements.txt
GHSA-7hp7-4p35-3cx2
gradio@5.49.1 · requirements.txt
GHSA-h3h8-3v2v-rg7m
gradio@5.49.1 · requirements.txt
GHSA-jmh7-g254-2cq9
gradio@5.49.1 · requirements.txt
GHSA-pfjf-5gxr-995x
gradio@5.49.1 · requirements.txt
PYSEC-2026-211
gradio@5.49.1 · requirements.txt
PYSEC-2026-63
gradio@5.49.1 · requirements.txt
PYSEC-2026-64
gradio@5.49.1 · requirements.txt
PYSEC-2026-65
gradio@5.49.1 · requirements.txt
PYSEC-2026-66
gradio@5.49.1 · requirements.txt
GHSA-7gcm-g887-7qv7
protobuf@3.20.1 · requirements.txt
GHSA-8gq9-2x98-w8hf
protobuf@3.20.1 · requirements.txt
GHSA-8qvm-5x2c-j2w7
protobuf@3.20.1 · requirements.txt
PYSEC-2026-1805
protobuf@3.20.1 · requirements.txt
PYSEC-2026-1806
protobuf@3.20.1 · requirements.txt
PYSEC-2026-899
protobuf@3.20.1 · requirements.txt
GHSA-752w-5fwx-jx9f
pyjwt@2.8.0 · requirements.txt
GHSA-993g-76c3-p5m4
pyjwt@2.8.0 · requirements.txt
GHSA-fhv5-28vv-h8m8
pyjwt@2.8.0 · requirements.txt
GHSA-w7vc-732c-9m39
pyjwt@2.8.0 · requirements.txt
GHSA-xgmm-8j9v-c9wx
pyjwt@2.8.0 · requirements.txt
PYSEC-2025-183
pyjwt@2.8.0 · requirements.txt
PYSEC-2026-120
pyjwt@2.8.0 · requirements.txt
PYSEC-2026-175
pyjwt@2.8.0 · requirements.txt
PYSEC-2026-177
pyjwt@2.8.0 · requirements.txt
PYSEC-2026-178
pyjwt@2.8.0 · requirements.txt
PYSEC-2026-179
pyjwt@2.8.0 · requirements.txt
GHSA-54jj-px8x-5w5q
deepdiff@8.6.1 · requirements.txt
Method and caveats:these are sourced, dated heuristics from public GitHub data and optional dependency scans. A status like "no criticals found on 2026-07-11" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/lazyagi-lazyllm/trust.
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.
- 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 for full scope and limits.