Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-20 01:34 UTC

ory / k8s

Kubernetes Helm Charts for the ORY ecosystem.

Mustache · Shell · MakefileApache-2.0★ 378 stars⑂ 287 forkssince Aug 2018View on GitHub ↗
KindNetwork servicehow this is determined

ory/k8s holds a health index of 93 out of 100, placing it in the Exceptional band. It scores highest on Vitality (90/100) and lowest on AI Readiness (49/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

93
overall / 100
Exceptional

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.

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

Ownership

OryOrganization
2,122 followers191 public repossince Jan 2017

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

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 1 days ago
18.7/36Commit cadence27/52 weeks with commits
17.9/18Commit volume98 commits in the last year
10/10OpenSSF Scorecard: Maintained18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year98
human_commit_share0.53
days_since_last_push1
active_weeks_last_year27

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 16 days ago
27/27Release cadencea release every ~34.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv0.64.0
releases_from_tagsno
days_since_latest_release16
mean_days_between_releases34.2
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?

79Good · 17% of overall
How it's scored
41.8/60Stars378 stars
20.5/25Forks287 forks
5.6/15Watchers11 watchers
Inputs used
forks287
stars378
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com
has_pull_request_templateyes

Sustainability & Governance

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

74Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
15.1/22.5Commit distributiontop contributor authored 33% of commits
13.5/13.5Contributor breadth98 contributors
10/10OpenSSF Scorecard: Contributorsproject has 24 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled98
top_contributor_share0.331
How it's scored
38.4/42Issue resolution92% of issues closed
25.8/30PR acceptance555/646 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 10/22 approved changesets -- score normalized to 4
Inputs used
merged_prs555
open_issues20
closed_issues216
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.915
closed_unmerged_prs91
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 backingorganization-owned
0/20Verified domain
23.9/25Owner reach2,122 followers of ory
25/25Track record191 public repos, account ~9 yr old
Inputs used
followers2,122
owner_typeOrganization
is_verifiedno
owner_loginory
public_repos191
account_age_days3,525

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
16/16Linter configpackage.json ("prettier")
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests20 out of 20 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://k8s.ory.com/helm
10/10Repository description
10/10Topics12 topics
0/10Wiki
Inputs used
topicsk8s, kubernetes, helm, ory-oathkeeper, ory-hydra, ory-keto, ory-hive, cloud, charts, helm-chart, helm-charts, ory
has_wikino
homepagehttps://k8s.ory.com/helm
docs_sitehttps://k8s.ory.com/helm
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
4.5/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests20 out of 20 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
3/7.5Code-ReviewFound 10/22 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 24 contributing companies or organizations
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.5Maintained18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
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-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
4.5/7.5Vulnerabilities4 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.2
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories4
affected_packages1
assessed_packages60
unassessed_packages0
affected_by_severityhigh 1
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 60 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.

49Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
37.2/40Legible commit history37 of 53 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.698
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format configpackage.json ("prettier")
0/11Static type checking
10/10Reproducible environmentlockfile
8/10Demonstrated agent practice4 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance47 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.04
toolchain_manifests
dependency_bot_commit_share0.47
How it's scored
0/45Type-checkable codeMustache without a type-check config
0/55Manageable file sizesno source files detected
Inputs used
primary_languageMustache
largest_source_bytes
source_files_sampled0
oversized_source_files0
Excluded from scoring (no data or not applicable): Manageable file sizes. Remaining weights renormalized.

Key facts

378GitHub stars
98contributors
98commits, last 12 months
1days since last push
100releases
2bus factor
20open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 287 ⇿
0Stars
287Forks
100Releases

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.

05010015020025030028452019-042022-122026-09
Major 0Minor 43Patch 57

Each point covers 7 days.

OpenSSF Scorecard 6.2 / 10
6.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-20 01:34 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests20 out of 20 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 10/22 approved changesets -- score normalized to 4
10Contributorsproject has 24 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6Vulnerabilities4 existing vulnerabilities detected
All dependencies 60

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

RegistryPackageVersionRelation
npmabbrev1.1.1indirect
npmansi-styles3.2.1indirect
npmarray-find-index1.0.2indirect
npmasap2.0.6indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.12indirect
npmchalk2.4.2indirect
npmcolor-convert1.9.3indirect
npmcolor-name1.1.3indirect
npmconcat-map0.0.1indirect
npmdebug3.2.7indirect
npmdebuglog1.0.1indirect
npmdezalgo1.0.4indirect
npmescape-string-regexp1.0.5indirect
npmfs.realpath1.0.0indirect
npmfunction-bind1.1.1indirect
npmglob7.2.3indirect
npmgraceful-fs4.2.10indirect
npmhas1.0.3indirect
npmhas-flag3.0.0indirect
npmhosted-git-info2.8.9indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-core-module2.11.0indirect
npmjson-parse-even-better-errors2.3.1indirect
npmlicense-checker25.0.1indirect
npmminimatch3.1.5indirect
npmminimist1.2.7indirect
npmmkdirp0.5.6indirect
npmms2.1.3indirect
npmnopt4.0.3indirect
npmnormalize-package-data2.5.0indirect
npmnpm-normalize-package-bin1.0.1indirect
npmonce1.4.0indirect
npmory-prettier-styles1.3.0indirect
npmos-homedir1.0.2indirect
npmos-tmpdir1.0.2indirect
npmosenv0.1.5indirect
npmpath-is-absolute1.0.1indirect
npmpath-parse1.0.7indirect
npmprettier3.9.6indirect
npmread-installed4.0.3indirect
npmread-package-json2.1.2indirect
npmreaddir-scoped-modules1.1.0indirect
npmresolve1.22.1indirect
npmsemver5.7.2indirect
npmslide1.1.6indirect
npmspdx-compare1.0.0indirect
npmspdx-correct3.1.1indirect
npmspdx-exceptions2.3.0indirect
npmspdx-expression-parse3.0.1indirect
npmspdx-license-ids3.0.12indirect
npmspdx-ranges2.1.1indirect
npmspdx-satisfies4.0.1indirect
npmsupports-color5.5.0indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmtreeify1.1.0indirect
npmutil-extend1.0.3indirect
npmvalidate-npm-package-license3.0.4indirect
npmwrappy1.0.2indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion1.1.12indirecthigh45.0.9

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.