Trust and health report
code-review-graph - 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.
last push 26d ago
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 1167788341
- Not a fork
- Personal account
- Computed today
Security scan
Manifest-only review of declared MCP transports and auth fields. Not a full code audit.
- Status
- No MCP manifest
- Last scan
- today
- Scanner
- none
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/tirth8205-code-review-graph/trust.
Common questions
- Is code-review-graph maintained?
- GraphCanon rates code-review-graph "Active" (82% maintenance signal from public GitHub metadata, computed today). Last push was 26 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is code-review-graph safe to use?
- Last scanned today (mcp_manifest profile). Status: No MCP manifest. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits. GraphCanon does not certify code-review-graph as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is code-review-graph a fork?
- No. code-review-graph is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does code-review-graph have known security vulnerabilities?
- Last scanned today (mcp_manifest profile). Status: No MCP manifest. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits.
- How often is the code-review-graph 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 code-review-graph?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for code-review-graph. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for code-review-graph?
- 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.