Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 07:52 UTC

flux159 / mcp-server-kubernetes

MCP Server for kubernetes management commands

TypeScriptMIT★ 1,459 stars⑂ 259 forkssince Dec 2024View on GitHub ↗
KindMCP serverLibraryNetwork servicehow this is determined

flux159/mcp-server-kubernetes holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (90/100) and lowest on Security (55/100). It was last updated today. 2 contributors account for most of its recent work.

89
overall / 100
Excellent

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.

89
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 75 is calibrated to 89 on the published index scale (record calibration 2026-08-02).

Ownership

Suyog SonwalkarPersonal account
97 followers53 public repossince Jul 2011Chronotale, Inc.

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmmcp-server-kubernetes4.0.460,747851 day agomcpkubernetesclaudeanthropickubectl

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
26.3/36Commit cadence38/52 weeks with commits
18/18Commit volume264 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year264
human_commit_share
days_since_last_push0
active_weeks_last_year38
How it's scored
27/27Ships releases83 releases published
36/36Release recencylatest release 1 days ago
27/27Release cadencea release every ~5.9 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count83
latest_release_tagv4.0.4
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases5.9

Community & Adoption

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

75Good · 17% of overall
How it's scored
51.3/60Stars1,459 stars
20.1/25Forks259 forks
5.6/15Watchers11 watchers
Inputs used
forks259
stars1,459
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
63.8/80Monthly downloads60,747 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmcp-server-kubernetes
dependents
ecosystemsnpm
total_downloads
monthly_downloads60,747
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

73Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14.2/22.5Commit distributiontop contributor authored 37% of commits
13.5/13.5Contributor breadth44 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor2
contributors_sampled44
top_contributor_share0.369
How it's scored
38.1/42Issue resolution91% of issues closed
25.9/30PR acceptance198/229 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 2/26 approved changesets -- score normalized to 0
Inputs used
merged_prs198
open_issues10
closed_issues99
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.908
closed_unmerged_prs31
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
14.3/25Owner reach97 followers of Flux159
24.6/25Track record53 public repos, account ~15 yr old
Inputs used
followers97
owner_typeUser
is_verified
owner_loginFlux159
public_repos53
account_age_days5,487
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 1 days ago
20/20Version history85 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmcp-server-kubernetes
ecosystemsnpm
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://www.npmjs.com/package/mcp-server-kubernetes
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsinfrastructure, kubernetes, mcp, server
has_wikino
homepagehttps://www.npmjs.com/package/mcp-server-kubernetes
docs_sitehttps://www.npmjs.com/package/mcp-server-kubernetes
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

55Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 2/26 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate5.5

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.

67Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes6,707
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesbun.lockb
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/82 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes33,788
source_files_sampled82
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

1,459GitHub stars
44contributors
264commits, last 12 months
0days since last push
83releases
2bus factor
10open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 5.5 / 10
5.5aggregate

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-07-17 07:51 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/26 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 6 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
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
npm@kubernetes/client-node1.3.0package.json
npm@modelcontextprotocol/sdk1.26.0package.json
npm@opentelemetry/api1.9.1package.json
npm@opentelemetry/auto-instrumentations-node0.77.0package.json
npm@opentelemetry/exporter-trace-otlp-grpc0.219.0package.json
npm@opentelemetry/resources2.7.1package.json
npm@opentelemetry/sdk-node0.219.0package.json
npm@opentelemetry/semantic-conventions1.40.0package.json
npmexpress4.21.2package.json
npmjs-yaml4.1.1package.json
npmyaml2.8.3package.json
npmzod3.25.76package.json
All dependencies 19

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

RegistryPackageVersionRelation
npm@kubernetes/client-node1.3.0direct
npm@modelcontextprotocol/sdk1.26.0direct
npm@opentelemetry/api1.9.1direct
npm@opentelemetry/auto-instrumentations-node0.77.0direct
npm@opentelemetry/exporter-trace-otlp-grpc0.219.0direct
npm@opentelemetry/resources2.7.1direct
npm@opentelemetry/sdk-node0.219.0direct
npm@opentelemetry/semantic-conventions1.40.0direct
npmexpress4.21.2direct
npmjs-yaml4.1.1direct
npmyaml2.8.3direct
npmzod3.25.76direct
npm@anthropic-ai/mcpb1.1.0indirect
npm@types/express5.0.1indirect
npm@types/js-yaml4.0.9indirect
npm@types/node22.9.3indirect
npmshx0.3.4indirect
npmtypescript5.6.2indirect
npmvitest3.2.6indirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.