Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 16:04 UTC

BaizeAI / kcover

🧯 Kubernetes coverage for fault awareness and recovery, works for any LLMOps, MLOps, AI workloads.

GoApache-2.0★ 35 stars⑂ 4 forkssince Jul 2024View on GitHub ↗
KindNetwork serviceLibraryhow this is determined

BaizeAI/kcover holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (75/100) and lowest on Community & Adoption (39/100). It was last updated 10 days ago. 2 contributors account for most of its recent work.

63
overall / 100
Moderate

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

63
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 59 is calibrated to 63 on the published index scale (record calibration 2026-08-02).

Ownership

Baize AIOrganization
18 followers12 public repossince Mar 2024

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/baizeai/kcoverv0.12.0-1258 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

75Good · 21% of overall
How it's scored
28.8/36Push recency — last push 10 days ago
5.5/36Commit cadence — 8/52 weeks with commits
14.1/18Commit volume — 36 commits in the last year
10/10OpenSSF Scorecard: Maintained — 24 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year36
human_commit_share0.707
days_since_last_push10
active_weeks_last_year8

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 5 releases published
36/36Release recency — latest release 58 days ago
27/27Release cadence — a release every ~12.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count5
latest_release_tagv0.12.0
releases_from_tagsno
days_since_latest_release58
mean_days_between_releases12.3
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

39Weak · 17% of overall
How it's scored
24.8/60Stars — 35 stars
4/25Forks — 4 forks
0/15Watchers — 1 watchers
Inputs used
forks4
stars35
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

57Moderate · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.5/22.5Commit distribution — top contributor authored 49% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 19 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled3
top_contributor_share0.488
How it's scored
7/42Issue resolution — 17% of issues closed
23.2/30PR acceptance — 41/53 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/14 approved changesets -- score normalized to 0
Inputs used
merged_prs41
open_issues5
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.167
closed_unmerged_prs12
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
9.2/25Owner reach — 18 followers of BaizeAI
13.1/25Track record — 12 public repos, account ~2 yr old
Inputs used
followers18
owner_typeOrganization
is_verifiedno
owner_loginBaizeAI
public_repos12
account_age_days912

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 58 days ago
20/20Version history — 12 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/baizeai/kcover
ecosystemsgo
any_deprecatedno
min_days_since_publish58

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests — 3 out of 30 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://baizeai.github.io/talks/2024-08-21-kubecon-hk/#/1
10/10Repository description
10/10Topics — 10 topics
0/10Wiki
Inputs used
topicskubeflow, kubernetes, kubernetes-controller, llm, llmops, mlops, nvidia-gpu, pytorchjob, tfjob, xid-error
has_wikino
homepagehttps://baizeai.github.io/talks/2024-08-21-kubecon-hk/#/1
docs_sitehttps://baizeai.github.io/talks/2024-08-21-kubecon-hk/#/1
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

62Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0.2/2.5CI-Tests — 3 out of 30 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/14 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 19 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 24 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.2
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories2
affected_packages2
assessed_packages42
unassessed_packages0
affected_by_severityunknown 2
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 42 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

64Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 32 of 41 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.78
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 58
8/8Automated maintenance — 17 of the last 58 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsgo.mod
dependency_bot_commit_share0.293
How it's scored
45/45Type-checkable code — Go (statically typed)
55/55Manageable file sizes — 0/54 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes57,268
source_files_sampled54
oversized_source_files0

Key facts

35GitHub stars
3contributors
36commits, last 12 months
10days since last push
5releases
2bus factor
5open issues
Gopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-02-03: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 35 stars today.

More detail

Star and fork history 35 ★ / 4 ⇿
35Stars
4Forks
5Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

Star history is shown as collected on 2026-02-03. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

013253835472024-082025-082026-08
Major 0Minor 3Patch 2

Each point covers 2 days.

OpenSSF Scorecard 5.2 / 10
5.2aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-12 16:04 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
1CI-Tests3 out of 30 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/14 approved changesets -- score normalized to 0
10Contributorsproject has 19 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained24 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
Gogithub.com/jellydator/ttlcache/v3v3.4.1go.mod
Gogopkg.in/yaml.v3v3.0.1go.mod
Gok8s.io/apiv0.36.2go.mod
Gok8s.io/apimachineryv0.36.2go.mod
Gok8s.io/client-gov0.36.2go.mod
Gok8s.io/klog/v2v2.140.0go.mod
All dependencies 42

Full resolved dependency set from the GitHub dependency graph: 6 direct and 36 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Gogithub.com/jellydator/ttlcache/v3v3.4.1direct
Gogopkg.in/yaml.v3v3.0.1direct
Gok8s.io/apiv0.36.2direct
Gok8s.io/apimachineryv0.36.2direct
Gok8s.io/client-gov0.36.2direct
Gok8s.io/klog/v2v2.140.0direct
Gogithub.com/davecgh/go-spewv1.1.2-0.20180830191138-d8f796af33ccindirect
Gogithub.com/emicklei/go-restful/v3v3.13.0indirect
Gogithub.com/fxamacker/cbor/v2v2.9.0indirect
Gogithub.com/go-logr/logrv1.4.3indirect
Gogithub.com/go-openapi/jsonpointerv0.21.0indirect
Gogithub.com/go-openapi/jsonreferencev0.21.0indirect
Gogithub.com/go-openapi/swagv0.23.0indirect
Gogithub.com/google/gnostic-modelsv0.7.0indirect
Gogithub.com/google/uuidv1.6.0indirect
Gogithub.com/josharian/internv1.0.0indirect
Gogithub.com/json-iterator/gov1.1.12indirect
Gogithub.com/mailru/easyjsonv0.9.0indirect
Gogithub.com/modern-go/concurrentv0.0.0-20180306012644-bacd9c7ef1ddindirect
Gogithub.com/modern-go/reflect2v1.0.3-0.20250322232337-35a7c28c31eeindirect
Gogithub.com/munnerz/goautonegv0.0.0-20191010083416-a7dc8b61c822indirect
Gogithub.com/pmezard/go-difflibv1.0.1-0.20181226105442-5d4384ee4fb2indirect
Gogithub.com/spf13/pflagv1.0.9indirect
Gogithub.com/x448/float16v0.8.4indirect
Gogo.yaml.in/yaml/v2v2.4.3indirect
Gogo.yaml.in/yaml/v3v3.0.4indirect
Gogolang.org/x/netv0.55.0indirect
Gogolang.org/x/oauth2v0.34.0indirect
Gogolang.org/x/syncv0.20.0indirect
Gogolang.org/x/sysv0.45.0indirect
Gogolang.org/x/termv0.43.0indirect
Gogolang.org/x/textv0.37.0indirect
Gogolang.org/x/timev0.14.0indirect
Gogoogle.golang.org/protobufv1.36.12-0.20260120151049-f2248ac996afindirect
Gogopkg.in/evanphx/json-patch.v4v4.13.0indirect
Gogopkg.in/inf.v0v0.9.1indirect
Gok8s.io/kube-openapiv0.0.0-20260317180543-43fb72c5454aindirect
Gok8s.io/utilsv0.0.0-20260210185600-b8788abfbbc2indirect
Gosigs.k8s.io/jsonv0.0.0-20250730193827-2d320260d730indirect
Gosigs.k8s.io/randfillv1.0.0indirect
Gosigs.k8s.io/structured-merge-diff/v6v6.3.2indirect
Gosigs.k8s.io/yamlv1.6.0indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 42 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/netv0.55.0indirectunknown11.27.0-rc.3
golang.org/x/textv0.37.0indirectunknown10.39.0

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — Go.