Trust and health report
late-cli - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated Sep 20, 2026 · GitHub synced Sep 20, 2026
33views this month
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
last push 2d ago · last release Sep 13, 2026 · 7 releases (90d)
+29 stars (30d) · +1 open issues (30d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 1163756223
- Not a fork
- Personal account
- Computed Sep 20, 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
Published findings- Last query
- Aug 9, 2026
- Scanner
- osv@v1
- Stored findings
- 21
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
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/mlhher-late-cli/trust.
Common questions
- Is late-cli maintained?
- GraphCanon rates late-cli "Very active" (96% maintenance signal from public GitHub metadata, computed Sep 20, 2026). Last push was 2 days ago. 7 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is late-cli safe to use?
- Last scanned Aug 9, 2026 (deps profile). Status: 21 low - 21 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 late-cli as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is late-cli a fork?
- No. late-cli is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does late-cli have known security vulnerabilities?
- Last scanned Aug 9, 2026 (deps profile). Status: 21 low - 21 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 late-cli trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed Sep 20, 2026 (methodology github_public_v1).
- What does GraphCanon never claim about late-cli?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for late-cli. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for late-cli?
- 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.