Trust and health report
LiveCodeBench - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated Oct 8, 2026 · GitHub synced Oct 8, 2026
36views this month
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
last push 449d ago
+22 stars (30d) · +6 open issues (30d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 771234452
- Not a fork
- Verified publisher: organization account
- Computed Oct 8, 2026
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
No lockfile (source not queried)- Last query
- Jul 11, 2026
- Scanner
- osv@v1
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceMethod 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/livecodebench-livecodebench/trust.
Common questions
- Is LiveCodeBench maintained?
- GraphCanon rates LiveCodeBench "Dormant" (18% maintenance signal from public GitHub metadata, computed Oct 8, 2026). Last push was 449 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is LiveCodeBench safe to use?
- Last scanned Jul 11, 2026 (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits. GraphCanon does not certify LiveCodeBench as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is LiveCodeBench a fork?
- No. LiveCodeBench is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does LiveCodeBench have known security vulnerabilities?
- Last scanned Jul 11, 2026 (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits.
- How often is the LiveCodeBench trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed Oct 8, 2026 (methodology github_public_v1).
- What does GraphCanon never claim about LiveCodeBench?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for LiveCodeBench. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for LiveCodeBench?
- 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.