Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-05 23:22 UTC

Getsoren / design-system

Soren Design System

TypeScriptISC★ 5 stars⑂ 1 forksince Jul 2022View on GitHub ↗

Getsoren/design-system holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (95/100) and lowest on Community & Adoption (47/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

SorenOrganization
3 followers14 public repossince May 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@getsoren/design-system4.80.08,331711 day ago

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
27/36Commit cadence — 39/52 weeks with commits
18/18Commit volume — 519 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year519
human_commit_share0.63
days_since_last_push1
active_weeks_last_year39

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~2.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag4.80.0
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases2.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?

47Weak · 17% of overall
How it's scored
9.8/60Stars — 5 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars5
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (ISC)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes
How it's scored
52.3/80Monthly downloads — 8,331 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@getsoren/design-system
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads8,331
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 factor — 1 contributor(s) cover half of all commits
3.4/22.5Commit distribution — top contributor authored 85% of commits
9.5/13.5Contributor breadth — 7 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.849
How it's scored
42/42Issue resolution — 100% of issues closed
28/30PR acceptance — 170/182 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs170
open_issues0
closed_issues3
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs12
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 backing — organization-owned
0/20Verified domain
4.3/25Owner reach — 3 followers of Getsoren
9.2/25Track record — 14 public repos, account ~0 yr old
Inputs used
followers3
owner_typeOrganization
is_verifiedno
owner_loginGetsoren
public_repos14
account_age_days115

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 1 days ago
20/20Version history — 71 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@getsoren/design-system
ecosystemsnpm
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — biome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no 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.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://storybook.tracktor.fr/
10/10Repository description
10/10Topics — 5 topics
10/10Wiki
Inputs used
topicsdesign-system, library, material-ui, react, storybook
has_wikiyes
homepagehttps://storybook.tracktor.fr/
docs_sitehttps://storybook.tracktor.fr/
has_readmeyes
has_docs_dirno
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-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 26 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate3.5
Excluded from scoring (no data or not applicable): Branch-Protection, CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages82
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:@getsoren/design-system@4.80.0 runtime dependency closure — what installing the published package pulls in — 82 packages. 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.

60Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 51 of 63 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.81
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — biome.json
11/11Static type checking — .storybook/tsconfig.json, tsconfig.json
10/10Reproducible environment — Dockerfile
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs.storybook/tsconfig.json, tsconfig.json
agent_commit_share0.03
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/378 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes53,742
source_files_sampled378
oversized_source_files0

Key facts

5GitHub stars
7contributors
519commits, last 12 months
1days since last push
100releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package '.husky' from its registry

More detail

OpenSSF Scorecard 3.5 / 10
3.5aggregate

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-05 23:22 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
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
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 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
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities26 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
npm@emotion/react^11.0.0package.json
npm@emotion/styled^11.0.0package.json
npm@mui/material^7.0.0package.json
npm@tanstack/react-virtual^3.13.26package.json
npm@getsoren/react-utils^1.30.1package.json
All dependencies 37

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

RegistryPackageVersionRelation
npm@emotion/react^11.0.0direct
npm@emotion/styled^11.0.0direct
npm@getsoren/react-utils^1.30.1direct
npm@mui/material^7.0.0direct
npm@tanstack/react-virtual^3.13.26direct
npm@babel/core^7.22.9indirect
npm@getsoren/biome-config-react^1.4.1indirect
npm@storybook/addon-docs^10.2.15indirect
npm@storybook/addon-links^10.2.15indirect
npm@storybook/addon-onboarding^10.2.15indirect
npm@storybook/builder-vite^10.2.15indirect
npm@storybook/react-vite^10.2.15indirect
npm@storybook/testing-library^0.2.2indirect
npm@testing-library/jest-dom^5.17.0indirect
npm@testing-library/react^14.0.0indirect
npm@testing-library/react-hooks^8.0.1indirect
npm@testing-library/user-event^14.4.3indirect
npm@types/node^18.19.61indirect
npm@types/react^19.1.0indirect
npm@types/react-dom^19.1.0indirect
npm@types/react-window^1.8.8indirect
npm@vitejs/plugin-react^6.0.1indirect
npm@vitest/ui^0.34.4indirect
npmbabel-loader^9.1.3indirect
npmchromatic^13.3.0indirect
npmcommit-and-tag-version^12.6.0indirect
npmhusky^8.0.3indirect
npmjsdom^22.1.0indirect
npmreact^19.0.0indirect
npmreact-dom^19.0.0indirect
npmreact-test-renderer^19.0.0indirect
npmsass^1.80.5indirect
npmstorybook^10.2.15indirect
npmtypescript^5.8.3indirect
npmunplugin-dts^1.0.1indirect
npmvite8.0.14indirect
npmvitest^1.6.1indirect
Dependency advisories 0

Installing npm:@getsoren/design-system@4.80.0 pulls in 82 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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 — npm.