Home/katib/Trust report

Trust and health report

katib - 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.

Very active96% signal

last push 1d ago · last release 8mo

Provenance

Repository identity and fork provenance (github_public_v1).

Security scan

Dependency advisory security scan when a lockfile is present. Not a full code audit.

Status
51 low
Last scan
today
Scanner
osv@v1

Findings

GHSA-p436-gjf2-799p
github.com/docker/cli@v28.2.2+incompatible · go.sum
GO-2026-4610
github.com/docker/cli@v28.2.2+incompatible · go.sum
GHSA-mh2q-q3fh-2475
go.opentelemetry.io/otel@v1.36.0 · go.sum
GHSA-9h8m-3fm2-qjrq
go.opentelemetry.io/otel/sdk@v1.34.0 · go.sum
GHSA-hfvc-g4fc-pqhx
go.opentelemetry.io/otel/sdk@v1.34.0 · go.sum
GO-2026-4394
go.opentelemetry.io/otel/sdk@v1.34.0 · go.sum
GHSA-45gg-vh54-h5m9
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-5cgq-3rg8-m6cv
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-78mq-xcr3-xm33
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-89gr-r52h-f8rx
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-9m57-25v3-79x9
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-f5wc-c3c7-36mc
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-f6x5-jh6r-wrfv
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-j5w8-q4qc-rx2x
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-jppx-rxg9-jmrx
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-q4h4-gmj2-qvw2
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-qpw4-5x99-6vjp
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-rm3j-f69w-wqmq
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-vgwf-h737-ff37
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-w879-237q-wc7r
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-x527-x647-q7gg
golang.org/x/crypto@v0.39.0 · go.sum
GO-2025-4116
golang.org/x/crypto@v0.39.0 · go.sum
GO-2025-4134
golang.org/x/crypto@v0.39.0 · go.sum
GO-2025-4135
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5005
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5006
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5013
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5014
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5015
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5016
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5017
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5018
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5019
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5020
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5021
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5023
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5033
golang.org/x/crypto@v0.39.0 · go.sum
GO-2026-5932
golang.org/x/crypto@v0.39.0 · go.sum
GHSA-5cv4-jp36-h3mw
golang.org/x/net@v0.41.0 · go.sum
GO-2026-4440
golang.org/x/net@v0.41.0 · go.sum
GO-2026-4441
golang.org/x/net@v0.41.0 · go.sum
GO-2026-4918
golang.org/x/net@v0.41.0 · go.sum
GO-2026-5025
golang.org/x/net@v0.41.0 · go.sum
GO-2026-5026
golang.org/x/net@v0.41.0 · go.sum
GO-2026-5027
golang.org/x/net@v0.41.0 · go.sum
GO-2026-5028
golang.org/x/net@v0.41.0 · go.sum
GO-2026-5029
golang.org/x/net@v0.41.0 · go.sum
GO-2026-5030
golang.org/x/net@v0.41.0 · go.sum
GO-2026-5024
golang.org/x/sys@v0.33.0 · go.sum
GHSA-p77j-4mvh-x3m3
google.golang.org/grpc@v1.72.1 · go.sum
GO-2026-4762
google.golang.org/grpc@v1.72.1 · go.sum

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/kubeflow-katib/trust.

Common questions

Is katib maintained?
GraphCanon rates katib "Very active" (96% maintenance signal from public GitHub metadata, computed today). Last push was 1 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
Is katib safe to use?
Last scanned today (deps profile). Status: 51 low - 51 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 katib as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is katib a fork?
No. katib is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does katib have known security vulnerabilities?
Last scanned today (deps profile). Status: 51 low - 51 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 katib 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 katib?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for katib. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for katib?
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.