Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 15:57 UTC

NordcomInc / nordstar

the nordstar component library — a modern, accessible, beautiful, and flexible design system for building human-centric user interfaces.

TypeScriptMIT★ 8 stars⑂ 0 forkssince Oct 2023View on GitHub ↗

NordcomInc/nordstar holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (90/100) and lowest on Community & Adoption (40/100). It was last updated 5 days 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

nordcomOrganization
8 followers17 public repossince Sep 2022

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

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 recency — last push 5 days ago
18.7/36Commit cadence — 27/52 weeks with commits
18/18Commit volume — 657 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_year657
human_commit_share0.3
days_since_last_push5
active_weeks_last_year27

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 50 days ago
27/27Release cadence — a release every ~0 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag@nordcom/nordstar-accented@0.2.1
releases_from_tagsno
days_since_latest_release50
mean_days_between_releases0
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?

40Weak · 17% of overall
How it's scored
13.7/60Stars — 8 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars8
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/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_templateno

Sustainability & Governance

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

53Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
11.2/22.5Commit distribution — top contributor authored 50% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.501
How it's scored
38.5/42Issue resolution — 92% of issues closed
26.2/30PR acceptance — 1,265/1,447 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/21 approved changesets -- score normalized to 0
Inputs used
merged_prs1,265
open_issues1
closed_issues11
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.917
closed_unmerged_prs182
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
6.9/25Owner reach — 8 followers of NordcomInc
17.5/25Track record — 17 public repos, account ~4 yr old
Inputs used
followers8
owner_typeOrganization
is_verifiedno
owner_loginNordcomInc
public_repos17
account_age_days1,532

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://nordcominc.github.io/nordstar/
10/10Repository description
10/10Topics — 12 topics
0/10Wiki
Inputs used
topicscomponent-library, next, opinionated, react, components, nextjs, reactjs, react-components, ui, ui-design, next-ui, nextjs14
has_wikino
homepagehttps://nordcominc.github.io/nordstar/
docs_sitehttps://nordcominc.github.io/nordstar/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 21 out of 21 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/21 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — 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 — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.2
Excluded from scoring (no data or not applicable): Branch-Protection, 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
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories7
affected_packages1
assessed_packages57
unassessed_packages0
affected_by_severitymoderate 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 57 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

65Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
3.6/40Legible commit history — 2 of 30 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.067
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes9,302
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — docs/tsconfig.json, e2e/tsconfig.json, packages/components/accented/tsconfig.json, packages/components/accordion/tsconfig.json, packages/components/button/tsconfig.json, packages/components/card/tsconfig.json, packages/components/details/tsconfig.json, packages/components/dropdown-menu/tsconfig.json, packages/components/header/tsconfig.json, packages/components/heading/tsconfig.json, packages/components/input/tsconfig.json, packages/components/kbd/tsconfig.json, packages/components/label/tsconfig.json, packages/components/select/tsconfig.json, packages/components/separator/tsconfig.json, packages/components/switch/tsconfig.json, packages/components/tooltip/tsconfig.json, packages/components/view/tsconfig.json, packages/core/nordstar/tsconfig.json, packages/core/system/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 70 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configsdocs/tsconfig.json, e2e/tsconfig.json, packages/components/accented/tsconfig.json, packages/components/accordion/tsconfig.json, packages/components/button/tsconfig.json, packages/components/card/tsconfig.json, packages/components/details/tsconfig.json, packages/components/dropdown-menu/tsconfig.json, packages/components/header/tsconfig.json, packages/components/heading/tsconfig.json, packages/components/input/tsconfig.json, packages/components/kbd/tsconfig.json, packages/components/label/tsconfig.json, packages/components/select/tsconfig.json, packages/components/separator/tsconfig.json, packages/components/switch/tsconfig.json, packages/components/tooltip/tsconfig.json, packages/components/view/tsconfig.json, packages/core/nordstar/tsconfig.json, packages/core/system/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.7
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/205 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes11,862
source_files_sampled205
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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

8GitHub stars
3contributors
657commits, last 12 months
5days since last push
100releases
1bus factor
1open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 6.2 / 10
6.2aggregate

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-11-21 15:56 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-Tests21 out of 21 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 0/21 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
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
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 57

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

RegistryPackageVersionRelation
npm@mdx-js/loader3.1.1indirect
npm@mdx-js/react3.1.1indirect
npm@next/mdx16.4.2indirect
npm@pnpm/exe.android-arm6412.15.0indirect
npm@pnpm/exe.android-x6412.15.0indirect
npm@pnpm/exe.darwin-arm6412.15.0indirect
npm@pnpm/exe.darwin-x6412.15.0indirect
npm@pnpm/exe.freebsd-x6412.15.0indirect
npm@pnpm/exe.linux-arm6412.15.0indirect
npm@pnpm/exe.linux-arm64-musl12.15.0indirect
npm@pnpm/exe.linux-ppc6412.15.0indirect
npm@pnpm/exe.linux-riscv6412.15.0indirect
npm@pnpm/exe.linux-s390x12.15.0indirect
npm@pnpm/exe.linux-x6412.15.0indirect
npm@pnpm/exe.linux-x64-musl12.15.0indirect
npm@pnpm/exe.win32-arm6412.15.0indirect
npm@pnpm/exe.win32-x6412.15.0indirect
npm@radix-ui/react-accordion1.3.1indirect
npm@radix-ui/react-dropdown-menu2.2.1indirect
npm@radix-ui/react-select2.4.1indirect
npm@radix-ui/react-switch1.4.1indirect
npm@radix-ui/react-tooltip1.4.1indirect
npm@tailwindcss/cli4.3.3indirect
npm@tailwindcss/postcss4.3.3indirect
npm@types/mdx2.0.14indirect
npm@types/node25.9.9indirect
npm@types/prop-types15.7.15indirect
npm@types/react19.3.0indirect
npm@types/react-dom19.3.0indirect
npmclass-variance-authority0.7.1indirect
npmclsx2.1.1indirect
npmconcurrently10.0.6indirect
npmgeist1.8.2indirect
npmglobals17.13.0indirect
npmhex-to-hsl1.0.2indirect
npmnext16.4.2indirect
npmnext-mdx-remote6.0.0indirect
npmpnpm12.15.0indirect
npmpostcss8.5.31indirect
npmpostcss-load-config6.0.1indirect
npmreact19.3.1indirect
npmreact-dom19.3.1indirect
npmrehype13.0.2indirect
npmrehype-autolink-headings7.1.0indirect
npmrehype-parse9.0.1indirect
npmrehype-pretty-code0.14.5indirect
npmrehype-slug6.0.0indirect
npmremark15.0.1indirect
npmremark-gfm4.0.1indirect
npmrimraf6.1.3indirect
npmshiki4.5.0indirect
npmtailwind-merge3.7.0indirect
npmtailwindcss4.3.3indirect
npmtsx4.23.15indirect
npmtypescript6.0.3indirect
npmvite8.3.5indirect
npmvite-plugin-dts5.0.3indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 57 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
next16.4.2indirectmoderate716.4.5

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.