Home/console/Trust report

Trust and health report

console - 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

75views this month

Maintenance

Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.

Very active96% signal

last push 0d ago · last release Sep 18, 2026 · 30 releases (90d)

+12 stars (30d) · -16 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 1135473716
  • Not a fork
  • Verified publisher: organization account
  • Computed Sep 18, 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
Sep 18, 2026
Scanner
osv@v1
Stored findings
5
View source evidence

deps.dev advisories

Partial coverage as of 2026-09-13
Last query
Sep 13, 2026
Scanner
deps.dev@v1
View source evidence

OpenSSF Scorecard

Published findings
Last query
Aug 23, 2026
Scanner
openssf-scorecard@v1
Stored findings
5

Weekly public scans omit some checks at scale.

View source evidence

Dependency advisories (deduplicated)

GHSA-8wmf-6v46-5gfg
go.opentelemetry.io/otel/exporters/otlp/otlptrace@v1.44.0 · osv@v1
go.sum
GO-2026-6179
golang.org/x/mod@v0.38.0 · osv@v1
go.sum
GO-2026-6180
golang.org/x/mod@v0.38.0 · osv@v1
go.sum
GHSA-2v4p-qf9q-27wj
google.golang.org/grpc@v1.83.1 · osv@v1
go.sum
GO-2026-6443
google.golang.org/grpc@v1.83.1 · osv@v1
go.sum

OpenSSF Scorecard checks

Branch-Protection (3/10): branch protection is not maximal on development and all release branches
https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#branch-protection
Code-Review (0/10): Found 1/30 approved changesets -- score normalized to 0
https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#code-review
Contributors (6/10): project has 2 contributing companies or organizations -- score normalized to 6
https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#contributors
Pinned-Dependencies (4/10): dependency not pinned by hash detected -- score normalized to 4
https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#pinned-dependencies
Signed-Releases (4/10): 3 out of the last 5 releases have a total of 3 signed artifacts.
https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#signed-releases

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/kubestellar-console/trust.

Common questions

Is console maintained?
GraphCanon rates console "Very active" (96% maintenance signal from public GitHub metadata, computed Sep 18, 2026). Last push was 0 days ago. 30 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
Is console safe to use?
Last scanned Sep 18, 2026 (deps profile). Status: 5 low - 5 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 console as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is console a fork?
No. console is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does console have known security vulnerabilities?
Last scanned Sep 18, 2026 (deps profile). Status: 5 low - 5 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 console trust report updated?
Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed Sep 18, 2026 (methodology github_public_v1).
What does GraphCanon never claim about console?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for console. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for console?
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.

Was this helpful?

Anonymous feedback helps us improve pages and translations.