Public record
Software health reportschema 0.16.0 · metrics 2.10.0 · 2026-07-20 21:04 UTC

MinBZK / storybook

Design System voor de Nederlandse Digitale Dienst

TypeScriptNo license detected★ 4 stars⑂ 1 forksince Jan 2026View on GitHub ↗

MinBZK/storybook holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (92/100) and lowest on Community & Adoption (39/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

317 followers146 public repossince Nov 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@nldd/design-system0.8.692,911334 days agodesign-systemweb-componentsrijksoverheidnldd

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
19.4/36Commit cadence28/52 weeks with commits
18/18Commit volume304 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year304
human_commit_share
days_since_last_push0
active_weeks_last_year28
How it's scored
16.2/27Ships releases77 version tags (no GitHub releases)
36/36Release recencylatest release 4 days ago
27/27Release cadencea release every ~3.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count77
latest_release_tagv0.8.69
releases_from_tagsyes
days_since_latest_release4
mean_days_between_releases3.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
7.7/60Stars4 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars4
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
46.2/80Monthly downloads2,911 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@nldd/design-system
dependents
ecosystemsnpm
total_downloads
monthly_downloads2,911
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?

75Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
16.4/22.5Commit distributiontop contributor authored 27% of commits
5.4/13.5Contributor breadth4 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled4
top_contributor_share0.273
How it's scored
24/42Issue resolution57% of issues closed
27.5/30PR acceptance121/132 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 4/30 approved changesets -- score normalized to 1
Inputs used
merged_prs121
open_issues9
closed_issues12
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.571
closed_unmerged_prs11
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
18/25Owner reach317 followers of MinBZK
25/25Track record146 public repos, account ~8 yr old
Inputs used
followers317
owner_typeOrganization
is_verified
owner_loginMinBZK
public_repos146
account_age_days3,164
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 4 days ago
20/20Version history33 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@nldd/design-system
ecosystemsnpm
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

92Excellent · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests17 out of 17 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://minbzk.github.io/storybook/
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://minbzk.github.io/storybook/
docs_sitehttps://minbzk.github.io/storybook/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

48Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests17 out of 17 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.8/7.5Code-ReviewFound 4/30 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 5 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
2.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
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
0/7.5Vulnerabilities53 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.8
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

81Excellent · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.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_filesCLAUDE.md
agent_instruction_max_bytes6,916
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
11/11Lint / format configeslint.config.js
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
5/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
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)
54.7/55Manageable file sizes3/597 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes94,045
source_files_sampled597
oversized_source_files3
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

4GitHub stars
4contributors
304commits, last 12 months
0days since last push
77releases
2bus factor
9open issues
npmpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index npm:@nldd/design-system@0.8.69; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 4.8 / 10
4.8aggregate

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-20 21:04 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
10CI-Tests17 out of 17 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 4/30 approved changesets -- score normalized to 1
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
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
0Vulnerabilities53 existing vulnerabilities detected
Direct dependencies 20
RegistryPackageVersion constraintManifest
npm@codemirror/autocomplete^6.20.3package.json
npm@codemirror/commands^6.10.4package.json
npm@codemirror/lang-css^6.3.1package.json
npm@codemirror/lang-html^6.4.11package.json
npm@codemirror/lang-javascript^6.2.5package.json
npm@codemirror/lang-json^6.0.2package.json
npm@codemirror/lang-markdown^6.5.0package.json
npm@codemirror/lang-python^6.2.1package.json
npm@codemirror/lang-rust^6.0.2package.json
npm@codemirror/lang-sql^6.10.0package.json
npm@codemirror/lang-xml^6.1.0package.json
npm@codemirror/lang-yaml^6.1.3package.json
npm@codemirror/language^6.12.4package.json
npm@codemirror/legacy-modes^6.5.3package.json
npm@codemirror/state^6.7.0package.json
npm@codemirror/view^6.43.4package.json
npm@floating-ui/dom^1.7.6package.json
npm@lezer/highlight^1.2.3package.json
npm@rijkshuisstijl-community/font^1.1.2package.json
npmlit^3.3.1package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.16.0 — full methodology · metrics wiki.

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