Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 23:35 UTC

sdd / kiddo

Kiddo

RustApache-2.0★ 172 stars⑂ 25 forkssince Sep 2022View on GitHub ↗

sdd/kiddo holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (91/100) and lowest on Security (51/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

sdd-orgOrganization
0 followers2 public repossince Jul 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iokiddo5.3.2513,443540 days agokdkd-treekdtreeknnnearest-neighbor

Metrics by category

Vitality

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

91Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
27/36Commit cadence39/52 weeks with commits
18/18Commit volume220 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year220
human_commit_share
days_since_last_push0
active_weeks_last_year39
How it's scored
27/27Ships releases25 releases published
36/36Release recencylatest release 0 days ago
19.8/27Release cadencea release every ~65.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count25
latest_release_tagv6.0.0-alpha.2
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases65.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?

62Moderate · 17% of overall
How it's scored
36.2/60Stars172 stars
11.5/25Forks25 forks
3.3/15Watchers5 watchers
Inputs used
forks25
stars172
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
76.1/80Monthly downloads513,443 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageskiddo
dependents
ecosystemscrates
total_downloads7,140,779
monthly_downloads513,443
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.7/22.5Commit distributiontop contributor authored 84% of commits
13.5/13.5Contributor breadth17 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled17
top_contributor_share0.837
How it's scored
39.2/42Issue resolution93% of issues closed
18.6/30PR acceptance225/363 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/15 approved changesets -- score normalized to 0
Inputs used
merged_prs225
open_issues4
closed_issues56
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.933
closed_unmerged_prs138
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
0/25Owner reach0 followers of sdd-org
3.5/25Track record2 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verified
owner_loginsdd-org
public_repos2
account_age_days4
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 0 days ago
20/20Version history54 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageskiddo
ecosystemscrates
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/kiddo
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_sitehttps://docs.rs/kiddo
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

51Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
6/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests19 out of 19 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 1/15 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflowdangerous 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 12 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
5/5SASTSAST tool is run on all commits
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): 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.

60Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapjustfile
22/22Automated tests
11/11Lint / format config
11/11Static type checkingRust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_filesjustfile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeRust (statically typed)
53.4/55Manageable file sizes5/176 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes172,991
source_files_sampled176
oversized_source_files5
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

172GitHub stars
17contributors
220commits, last 12 months
0days since last push
25releases
1bus factor
4open issues
crates.iopackage ecosystems

More detail

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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 23:35 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests19 out of 19 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 1/15 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 12 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
10SASTSAST tool is run on all commits
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 23
RegistryPackageVersion constraintManifest
crates.ioaligned-vec0.6.1Cargo.toml
crates.ioarray-init2.1.0Cargo.toml
crates.ioaz1Cargo.toml
crates.iocmov0.5Cargo.toml
crates.iononmax0.5.5Cargo.toml
crates.ionum-traits0.2Cargo.toml
crates.iosorted-vec0.8Cargo.toml
crates.iotest-log0.2.19Cargo.toml
crates.iobytecheck0.8Cargo.toml
crates.iocsv1Cargo.toml
crates.iofixed1,<1.31.0Cargo.toml
crates.iohalf2.5.0Cargo.toml
crates.iolas0.9Cargo.toml
crates.iolibc0.2Cargo.toml
crates.iolog0.4Cargo.toml
crates.ioptr_meta0.3Cargo.toml
crates.iorand0.10Cargo.toml
crates.iorand_chacha0.10Cargo.toml
crates.iorayon1Cargo.toml
crates.iorkyv_080.8.9Cargo.toml
crates.ioserde1Cargo.toml
crates.iosmallvec1Cargo.toml
crates.iotracing0.1Cargo.toml
All dependencies 43

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

RegistryPackageVersionRelation
crates.ioaligned-vecdirect
crates.ioarray-initdirect
crates.ioazdirect
crates.iobytecheckdirect
crates.iocmovdirect
crates.iocsvdirect
crates.iohalfdirect
crates.iolasdirect
crates.iolibcdirect
crates.iologdirect
crates.iononmaxdirect
crates.ionum-traitsdirect
crates.ioptr_metadirect
crates.ioranddirect
crates.iorand_chachadirect
crates.iorayondirect
crates.ioserdedirect
crates.iosmallvecdirect
crates.iosorted-vecdirect
crates.iotest-logdirect
crates.iotracingdirect
crates.ioassert_float_eqindirect
crates.iocodspeed-criterion-compatindirect
crates.iocriterionindirect
crates.ioelapsedindirect
crates.ioflate2indirect
crates.iogeneratorindirect
crates.ioitertoolsindirect
crates.iomemmapindirect
crates.iopostcardindirect
crates.ioproc-macro2indirect
crates.ioradiansindirect
crates.iorand_distrindirect
crates.ioreqwestindirect
crates.iorkyvindirect
crates.iorstestindirect
crates.ioserde_jsonindirect
crates.iotracing-subscriberindirect
crates.iotrybuildindirect
crates.ioubyteindirect
crates.ioyep-cache-line-sizeindirect
crates.iozipindirect
crates.iozzzindirect
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.12.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticscrates.io.