Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-18 07:13 UTC

jerrythomas / rokkit

A set of composable, data-driven and themeable UI components.

JavaScript · TypeScript · SvelteMIT★ 32 stars⑂ 3 forkssince Jul 2022View on GitHub ↗

jerrythomas/rokkit holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (90/100) and lowest on Security (34/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

71
overall / 100
Good

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.

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

Ownership

Jerry ThomasPersonal account
11 followers98 public repossince May 2012@senecaglobalinc

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

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
18/18Commit volume1,434 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,434
human_commit_share
days_since_last_push1
active_weeks_last_year27

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 1 days ago
27/27Release cadencea release every ~3.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv1.3.6
releases_from_tagsno
days_since_latest_release1
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?

54Moderate · 17% of overall
How it's scored
24.2/60Stars32 stars
2.5/25Forks3 forks
0/15Watchers1 watchers
Inputs used
forks3
stars32
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/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_conductyes
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

41Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.1/22.5Commit distributiontop contributor authored 100% of commits
5.4/13.5Contributor breadth4 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.995
How it's scored
42/42Issue resolution100% of issues closed
6.4/30PR acceptance9/42 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs9
open_issues0
closed_issues99
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs33
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
7.8/25Owner reach11 followers of jerrythomas
25/25Track record98 public repos, account ~14 yr old
Inputs used
followers11
owner_typeUser
is_verified
owner_loginjerrythomas
public_repos98
account_age_days5,174
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter configeslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://rokkit.vercel.app
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicssvelte, sveltekit, ui-components
has_wikiyes
homepagehttps://rokkit.vercel.app
docs_sitehttps://rokkit.vercel.app
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

34At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
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.5Maintained30 commit(s) and 4 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/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities55 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): CI-Tests, 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.

71Good · 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_bytes3,910
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.mjs
11/11Static type checkingapps/learn/jsconfig.json, packages/app/tsconfig.json, packages/blocks/tsconfig.json, packages/chart/tsconfig.json, packages/forms/tsconfig.json, packages/ui/tsconfig.json, tsconfig.json
0/10Reproducible environment
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
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsapps/learn/jsconfig.json, packages/app/tsconfig.json, packages/blocks/tsconfig.json, packages/chart/tsconfig.json, packages/forms/tsconfig.json, packages/ui/tsconfig.json, tsconfig.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
27/45Type-checkable codeJavaScript with type-check config (apps/learn/jsconfig.json, packages/app/tsconfig.json, packages/blocks/tsconfig.json, packages/chart/tsconfig.json, packages/forms/tsconfig.json, packages/ui/tsconfig.json, tsconfig.json)
55/55Manageable file sizes0/794 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes54,060
source_files_sampled794
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
40/40Runnable examplesdemos, examples
Inputs used
example_dirsdemos, examples
has_mcp_signalyes
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

32GitHub stars
4contributors
1,434commits, last 12 months
1days since last push
100releases
1bus factor
0open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 3.4 / 10
3.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-07-18 07:13 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 4 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
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities55 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npm@types/ramda^0.31.1package.json
npmdompurify^3.3.3package.json
All dependencies 95

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

RegistryPackageVersionRelation
npm@types/ramda^0.31.1direct
npmdompurify^3.0.0direct
npmdompurify^3.3.3direct
npm@fontsource/caveat^5.2.8indirect
npm@fontsource/fraunces^5.2.9indirect
npm@fontsource/inter^5.2.8indirect
npm@fontsource/jetbrains-mono^5.2.8indirect
npm@fontsource/open-sans^5.2.7indirect
npm@fontsource/overpass^5.2.8indirect
npm@iconify-json/mdi^1.2.3indirect
npm@iconify-json/solar^1.2.5indirect
npm@iconify/tools5.0.3indirect
npm@iconify/types*indirect
npm@iconify/types^2.0.0indirect
npm@inlang/paraglide-js^2.16.1indirect
npm@lukeed/uuid^2.0.1indirect
npm@mdi/svg^7.4.47indirect
npm@mlc-ai/web-llm^0.2.83indirect
npm@playwright/test^1.59.1indirect
npm@sveltejs/adapter-auto^6.1.0indirect
npm@sveltejs/adapter-cloudflare^7.2.8indirect
npm@sveltejs/kit^2.42.1indirect
npm@sveltejs/package^2.5.8indirect
npm@sveltejs/vite-plugin-svelte^6.2.0indirect
npm@sveltejs/vite-plugin-svelte^6.2.4indirect
npm@testing-library/jest-dom^6.9.1indirect
npm@testing-library/svelte^5.2.8indirect
npm@testing-library/svelte^5.3.1indirect
npm@testing-library/user-event^14.6.1indirect
npm@types/bun^1.2.22indirect
npm@types/d3-array^3.2.2indirect
npm@types/d3-axis^3.0.6indirect
npm@types/d3-format^3.0.4indirect
npm@types/d3-scale^4.0.9indirect
npm@types/d3-scale-chromatic^3.1.0indirect
npm@types/d3-selection^3.0.11indirect
npm@types/d3-shape^3.1.8indirect
npm@types/d3-transition^3.0.9indirect
npm@types/d3-zoom^3.0.8indirect
npm@types/dompurify^3.2.0indirect
npm@unocss/extractor-svelte^66.5.1indirect
npm@unocss/extractor-svelte^66.6.1indirect
npm@unocss/preset-icons^66.7.0indirect
npm@unocss/preset-mini^66.6.1indirect
npm@unocss/reset66.5.1indirect
npm@vitest/browser^3.2.4indirect
npm@vitest/browser^4.0.18indirect
npm@vitest/browser^4.1.6indirect
npm@vitest/coverage-v8^3.2.4indirect
npm@vitest/expect^4.0.18indirect
npmbumpp^10.2.3indirect
npmd3-array^3.2.4indirect
npmd3-axis^3.0.0indirect
npmd3-collection^1.0.7indirect
npmd3-format^3.1.2indirect
npmd3-scale^4.0.2indirect
npmd3-scale-chromatic^3.1.0indirect
npmd3-selection^3.0.0indirect
npmd3-shape^3.2.0indirect
npmd3-transition^3.0.1indirect
npmd3-zoom^3.0.0indirect
npmdate-fns^4.1.0indirect
npmeslint^9.35.0indirect
npmeslint-plugin-svelte^3.12.3indirect
npmglobals^17.3.0indirect
npmiconify^1.4.0indirect
npmjsdom^27.0.0indirect
npmjsdom^29.1.1indirect
npmmagic-string^0.30.21indirect
npmmarked^15.0.0indirect
npmminisearch^7.2.0indirect
npmplaywright^1.58.2indirect
npmplaywright^1.59.1indirect
npmprettier^3.6.2indirect
npmprettier-plugin-svelte^3.5.1indirect
npmprettier-plugin-tailwindcss^0.7.2indirect
npmprompts^2.4.2indirect
npmramda^0.32.0indirect
npmrimraf^6.0.1indirect
npmsade^1.8.1indirect
npmsimple-icons^16.11.0indirect
npmsvelte^5.39.2indirect
npmsvelte^5.53.3indirect
npmsvelte^5.53.5indirect
npmsvelte-check^4.4.3indirect
npmsvelte-eslint-parser^1.5.1indirect
npmtypescript^5.9.3indirect
npmtypescript-eslint^8.56.1indirect
npmunocss^66.5.1indirect
npmunocss^66.6.1indirect
npmvite^7.1.6indirect
npmvite^7.3.1indirect
npmvitest^3.2.4indirect
npmvitest^4.0.18indirect
npmvitest^4.1.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.12.0 — full methodology · metrics wiki.

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