Trust and health report
LLM4Decompile - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated 4d · GitHub synced 4d
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Slowing36% signal
last push 186d ago
+205 stars (30d) · 0 open issues (30d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 764418725
- Not a fork
- Personal account
- Computed 4d
Security intelligence
Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.
OSV dependency advisories
Published findings- Last query
- 1mo
- Scanner
- osv@v1
- Stored findings
- 41
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
GHSA-3mwp-wvh9-7528
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-3ww4-5jv9-j5gm
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-4qjh-9fv9-r85r
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-5vqr-wprc-cpp7
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-6pr9-rp53-2pmc
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-7h4p-rffg-7823
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-8fr4-5q9j-m8gm
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-94f4-hr76-p5j6
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-98f3-hwg4-4rf7
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-cj47-qj6g-x7r4
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-ggpf-24jw-3fcw
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-hgg8-fqqc-vfmw
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-mgrm-fgjv-mhv8
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-pgr7-mhp5-fgjp
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-q8gq-377p-jq3r
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-qh4c-xf7m-gxfc
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-rh4j-5rhw-hr54
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-rm76-4mrf-v9r8
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-rxc4-3w6r-4v47
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-w2r7-9579-27hf
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-wc36-9694-f9rf
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-wr9h-g72x-mwhm
vllm@0.4.0 · osv@v1
requirements.txt
GHSA-x368-4g9h-fvv4
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2025-222
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2025-223
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2025-42
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2025-43
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2025-50
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2025-53
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2025-58
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2025-62
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2026-2015
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2026-2020
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2026-2021
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2026-2024
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2026-2025
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2026-2026
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2026-226
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2026-227
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2026-566
vllm@0.4.0 · osv@v1
requirements.txt
PYSEC-2026-568
vllm@0.4.0 · osv@v1
requirements.txt
Method and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/albertan017-llm4decompile/trust.
Common questions
- Is LLM4Decompile maintained?
- GraphCanon rates LLM4Decompile "Slowing" (36% maintenance signal from public GitHub metadata, computed 4d). Last push was 186 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is LLM4Decompile safe to use?
- Last scanned 1mo (deps profile). Status: 41 low - 41 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 LLM4Decompile as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is LLM4Decompile a fork?
- No. LLM4Decompile is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does LLM4Decompile have known security vulnerabilities?
- Last scanned 1mo (deps profile). Status: 41 low - 41 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 LLM4Decompile trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 4d (methodology github_public_v1).
- What does GraphCanon never claim about LLM4Decompile?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for LLM4Decompile. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for LLM4Decompile?
- 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.