Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-06 02:58 UTC

kilork / keycloak

Keycloak REST API Client

RustUnlicense★ 82 stars⑂ 41 forkssince Mar 2020View on GitHub ↗
KindLibraryNetwork servicehow this is determined

kilork/keycloak holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (77/100) and lowest on Security (44/100). It was last updated 4 days ago. A single contributor accounts 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

Alexander KorolevPersonal account
45 followers63 public repossince Jan 2010

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
crates.iokeycloak26.7.30037,739684 days agoapiasynckeycloakrestapi-bindingsasynchronous

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
4.2/36Commit cadence6/52 weeks with commits
12.1/18Commit volume21 commits in the last year
10/10OpenSSF Scorecard: Maintained9 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year21
human_commit_share1
days_since_last_push4
active_weeks_last_year6

Release discipline

100Exceptional
How it's scored
27/27Ships releases42 releases published
36/36Release recencylatest release 4 days ago
27/27Release cadencea release every ~43.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count42
latest_release_tagv26.7.300
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases43.5
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?

54Moderate · 17% of overall
How it's scored
31/60Stars82 stars
13.4/25Forks41 forks
0/15Watchers2 watchers
Inputs used
forks41
stars82
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Unlicense)
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
How it's scored
61/80Monthly downloads37,739 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageskeycloak
dependents
ecosystemscrates
total_downloads695,550
monthly_downloads37,739
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.3/22.5Commit distributiontop contributor authored 90% of commits
13.5/13.5Contributor breadth12 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled12
top_contributor_share0.898
How it's scored
38.9/42Issue resolution93% of issues closed
26/30PR acceptance85/98 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 3/30 approved changesets -- score normalized to 1
Inputs used
merged_prs85
open_issues7
closed_issues89
prs_merged_7d2
prs_decided_7d3
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio0.927
closed_unmerged_prs13
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
12/25Owner reach45 followers of kilork
25/25Track record63 public repos, account ~16 yr old
Inputs used
followers45
owner_typeUser
is_verified
owner_loginkilork
public_repos63
account_age_days6,064
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 crates
35/35Publish recencylatest publish 4 days ago
20/20Version history68 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageskeycloak
ecosystemscrates
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

54Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests18 out of 22 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/keycloak
10/10Repository description
10/10Topics7 topics
10/10Wiki
Inputs used
topicsauth, keycloak, api, api-client, rest, rest-api, admin
has_wikiyes
homepage
docs_sitehttps://docs.rs/keycloak
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

44Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2/2.5CI-Tests18 out of 22 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 3/30 approved changesets -- score normalized to 1
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained9 commit(s) and 3 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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

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.

63Moderate · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
30.9/40Legible commit history58 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.58
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes6,838
How it's scored
12.6/18One-command bootstrapCargo.toml (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
49.6/55Manageable file sizes6/61 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes106,081
source_files_sampled61
oversized_source_files6
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)api/openapi.json
0/20MCP server
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesapi/openapi.json
interfaces_expected_ofnetwork-service

Key facts

82GitHub stars
12contributors
21commits, last 12 months
4days since last push
42releases
1bus factor
7open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 41 ⇿
0Stars
41Forks
39Releases

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.

0102030404022021-022023-102026-05
Major 5Minor 4Patch 30

Each point covers 5 days.

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-06 02:57 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
8CI-Tests18 out of 22 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/30 approved changesets -- score normalized to 1
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained9 commit(s) and 3 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
crates.ioreqwest120.12Cargo.toml
crates.ioreqwest130.13Cargo.toml
crates.ioserde_json1Cargo.toml
crates.ioserde1Cargo.toml
crates.ioserde_with3Cargo.toml
crates.ioasync-trait0.1Cargo.toml
crates.ioschemars1.2.1Cargo.toml
crates.iopercent-encoding2.3.2Cargo.toml
All dependencies 12

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

RegistryPackageVersionRelation
crates.ioasync-traitdirect
crates.iopercent-encodingdirect
crates.ioschemarsdirect
crates.ioserdedirect
crates.ioserde_jsondirect
crates.ioserde_withdirect
crates.ioclapindirect
crates.ioheckindirect
crates.ioindexmapindirect
crates.ioreqwestindirect
crates.iotokioindirect
crates.iotomlindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 statisticscrates.io.