Trust and health report
HCP-Coder - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated 2w · GitHub synced 2w
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Dormant18% signal
last push 625d ago
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 820329713
- Not a fork
- Personal account
- Computed 2w
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
- 49
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
GHSA-mf9w-mj56-hr94
python-dotenv@1.0.1 · osv@v1
requirements.txt
GHSA-3f6c-7fw2-ppm4
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-3mwp-wvh9-7528
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-3ww4-5jv9-j5gm
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-4qjh-9fv9-r85r
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-5jv2-g5wq-cmr4
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-69j4-grxj-j64p
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-6fvq-23cw-5628
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-6pr9-rp53-2pmc
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-7h4p-rffg-7823
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-8fr4-5q9j-m8gm
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-94f4-hr76-p5j6
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-98f3-hwg4-4rf7
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-9f8f-2vmf-885j
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-9pcc-gvx5-r5wm
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-ggpf-24jw-3fcw
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-hgg8-fqqc-vfmw
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-hpv8-x276-m59f
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-j828-28rj-hfhp
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-mgrm-fgjv-mhv8
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-pgr7-mhp5-fgjp
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-pmqf-x6x8-p7qw
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-q8gq-377p-jq3r
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-qh4c-xf7m-gxfc
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-rh4j-5rhw-hr54
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-rm76-4mrf-v9r8
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-rxc4-3w6r-4v47
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-wr9h-g72x-mwhm
vllm@0.6.3.post1 · osv@v1
requirements.txt
GHSA-x368-4g9h-fvv4
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2025-223
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2025-42
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2025-43
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2025-50
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2025-53
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2025-58
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2025-62
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2026-2011
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2026-2012
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2026-2013
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2026-2015
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2026-2016
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2026-2017
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2026-2019
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2026-2020
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2026-2021
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2026-2026
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2026-226
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2026-227
vllm@0.6.3.post1 · osv@v1
requirements.txt
PYSEC-2026-568
vllm@0.6.3.post1 · 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/hambaobao-hcp-coder/trust.
Common questions
- Is HCP-Coder maintained?
- GraphCanon rates HCP-Coder "Dormant" (18% maintenance signal from public GitHub metadata, computed 2w). Last push was 625 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is HCP-Coder safe to use?
- Last scanned 1mo (deps profile). Status: 49 low - 49 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 HCP-Coder as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is HCP-Coder a fork?
- No. HCP-Coder is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does HCP-Coder have known security vulnerabilities?
- Last scanned 1mo (deps profile). Status: 49 low - 49 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 HCP-Coder trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 2w (methodology github_public_v1).
- What does GraphCanon never claim about HCP-Coder?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for HCP-Coder. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for HCP-Coder?
- 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.