Public record
Software health reportschema 0.27.0 · metrics 2.5.0 · 2026-07-30 10:38 UTC

carbon-design-system / carbon-preprocess-svelte

Svelte preprocessors for the Carbon Design System

TypeScriptApache-2.0★ 81 stars⑂ 8 forkssince May 2021View on GitHub ↗

carbon-design-system/carbon-preprocess-svelte holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (96/100) and lowest on AI Readiness (54/100). It was last updated today. A single contributor accounts 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

913 followers120 public repossince Jan 2017

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

Package ecosystems

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 206 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_year206
human_commit_share1
days_since_last_push0
active_weeks_last_year43

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 58 releases published
36/36Release recency — latest release 8 days ago
27/27Release cadence — a release every ~12.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count58
latest_release_tagv0.11.38
releases_from_tagsno
days_since_latest_release8
mean_days_between_releases12.6
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?

66Good · 17% of overall
How it's scored
30.9/60Stars — 81 stars
7/25Forks — 8 forks
2.7/15Watchers — 4 watchers
Inputs used
forks8
stars81
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
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
How it's scored
63.9/80Monthly downloads — 62,181 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagescarbon-preprocess-svelte
dependents
ecosystemsnpm
total_downloads
monthly_downloads62,181
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?

65Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.2/22.5Commit distribution — top contributor authored 99% of commits
5.4/13.5Contributor breadth — 4 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.993
How it's scored
42/42Issue resolution — 100% of issues closed
27.2/30PR acceptance — 105/116 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/26 approved changesets -- score normalized to 0
Inputs used
merged_prs105
open_issues0
closed_issues34
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
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 backing — organization-owned
0/20Verified domain
21.3/25Owner reach — 913 followers of carbon-design-system
25/25Track record — 120 public repos, account ~9 yr old
Inputs used
followers913
owner_typeOrganization
is_verified
owner_logincarbon-design-system
public_repos120
account_age_days3,480

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 8 days ago
20/20Version history — 58 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescarbon-preprocess-svelte
ecosystemsnpm
any_deprecatedno
min_days_since_publish8

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 6 topics
0/10Wiki
Inputs used
topicssvelte, svelte-preprocessor, preprocess, carbon, carbon-design-system, carbon-preprocess
has_wikino
homepage
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 18 out of 18 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/26 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
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
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 — 44 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): 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
advisories41
affected_packages5
assessed_packages24
unassessed_packages15
affected_by_severitycritical 1, high 3, moderate 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 24 resolved dependencies against OSV. 15 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

54Moderate · 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 — 88 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.88
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 — examples/sveltekit/tsconfig.json, examples/vite/tsconfig.json, examples/vite@svelte-5/tsconfig.json, examples/webpack/tsconfig.json, examples/webpack@svelte-5/tsconfig.json, tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsexamples/sveltekit/tsconfig.json, examples/vite/tsconfig.json, examples/vite@svelte-5/tsconfig.json, examples/webpack/tsconfig.json, examples/webpack@svelte-5/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
53.9/55Manageable file sizes — 1/52 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes178,229
source_files_sampled52
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files

Key facts

81GitHub stars
4contributors
206commits, last 12 months
0days since last push
58releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 8 ⇿
0Stars
8Forks
29Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

02468812022-042024-032026-02
Major 0Minor 3Patch 26

Each point covers 4 days.

OpenSSF Scorecard 4.3 / 10
4.3aggregate

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-30 10:38 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests18 out of 18 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/26 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
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities44 existing vulnerabilities detected
All dependencies 39

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

RegistryPackageVersionRelation
npm@biomejs/biome2.5.5indirect
npm@rollup/plugin-commonjslatestindirect
npm@rollup/plugin-node-resolvelatestindirect
npm@sveltejs/adapter-staticlatestindirect
npm@sveltejs/kitlatestindirect
npm@sveltejs/vite-plugin-svelte^3.1.2indirect
npm@sveltejs/vite-plugin-sveltelatestindirect
npm@types/bun^1.3.14indirect
npm@types/jest^30.0.0indirect
npm@typescript/typescript6^6.0.2indirect
npmcarbon-components-svelte0.110.1indirect
npmcarbon-components-svelte0.85.0indirect
npmcarbon-components-sveltelatestindirect
npmcss-loaderlatestindirect
npmculls^0.2.0indirect
npmestree-walker^2.0.2indirect
npmhtml-webpack-pluginlatestindirect
npmmagic-string^0.30.17indirect
npmmini-css-extract-pluginlatestindirect
npmpostcss^8.5.15indirect
npmpostcss-discard-empty^8.0.0indirect
npmrolluplatestindirect
npmrollup-plugin-css-onlylatestindirect
npmrollup-plugin-sveltelatestindirect
npmrollup-plugin-terserlatestindirect
npmsvelte^4.2.20indirect
npmsvelte^5.56.2indirect
npmsveltelatestindirect
npmsvelte-loaderlatestindirect
npmsvelte-preprocesslatestindirect
npmtypescript^6.0.3indirect
npmtypescriptlatestindirect
npmvite^5.4.21indirect
npmvite^8.0.16indirect
npmvitelatestindirect
npmwebpack^5.107.2indirect
npmwebpacklatestindirect
npmwebpack-clilatestindirect
npmwebpack-dev-serverlatestindirect
Dependency advisories 5

This repository publishes no package the index resolves, so its own dependency graph was assessed — 24 packages, which also include development and test pins that never ship: 5 carry known advisories, of which 0 are direct. 15 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
rolluplatestindirectcritical24.59.0
@sveltejs/kitlatestindirecthigh82.69.1
vitelatestindirecthigh168.0.16
webpack-dev-serverlatestindirecthigh75.2.6
sveltelatestindirectmoderate85.55.7

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

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.5.0, schema v0.27.0 — full methodology · metrics wiki.

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