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

winduum / winduum

🎨 Modern, modular, small modest CSS component framework built on top of TailwindCSS

HTML · CSS · JavaScriptMIT★ 168 stars⑂ 4 forkssince Nov 2022View on GitHub ↗
KindLibraryhow this is determined
#css#css-framework#html#tailwindcss#javascript#postcss

winduum/winduum holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on Vitality (65/100) and lowest on AI Readiness (40/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

53
overall / 100
Moderate

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.

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

Ownership

WinduumOrganization
1 follower7 public repossince Dec 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmwinduum2.2.283,47624756 days ago

Metrics by category

Vitality

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

65Good · 21% of overall

Development activity

69Good
How it's scored
36/36Push recency — last push 1 days ago
8.3/36Commit cadence — 12/52 weeks with commits
14.8/18Commit volume — 43 commits in the last year
10/10OpenSSF Scorecard: Maintained — 16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year43
human_commit_share—
days_since_last_push1
active_weeks_last_year12

Release discipline

60Moderate
How it's scored
27/27Ships releases — 15 releases published
7.2/36Release recency — latest release 443 days ago
19.8/27Release cadence — a release every ~50.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count15
latest_release_tag2.2.0
releases_from_tagsno
days_since_latest_release443
mean_days_between_releases50.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?

50Moderate · 17% of overall

Popularity & adoption

44Weak
How it's scored
36.1/60Stars — 168 stars
4/25Forks — 4 forks
3.9/15Watchers — 6 watchers
Inputs used
forks4
stars168
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

59Moderate
How it's scored
47.2/80Monthly downloads — 3,476 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageswinduum
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads3,476
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

Maintainer resilience (bus factor)

22At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.1/22.5Commit distribution — top contributor authored 100% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.995

Issue & PR responsiveness

71Good
How it's scored
31.5/42Issue resolution — 75% of issues closed
30/30PR acceptance — 18/18 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_prs18
open_issues1
closed_issues3
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio0.75
closed_unmerged_prs0
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.

Ownership & stewardship

57Moderate
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
2.2/25Owner reach — 1 followers of winduum
13.7/25Track record — 7 public repos, account ~3 yr old
Inputs used
followers1
owner_typeOrganization
is_verified—
owner_loginwinduum
public_repos7
account_age_days1,295
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 56 days ago
20/20Version history — 247 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageswinduum
ecosystemsnpm
any_deprecatedno
min_days_since_publish56

Engineering Quality

Are baseline engineering and documentation practices in place?

42Weak · 19% of overall

Engineering practices

20At Risk
How it's scored
0/24CI workflows
0/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

75Good
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://winduum.dev
10/10Repository description
10/10Topics — 6 topics
10/10Wiki
Inputs used
topicscss, css-framework, html, tailwindcss, javascript, postcss
has_wikiyes
homepagehttps://winduum.dev
docs_sitehttps://winduum.dev
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

41Weak · 16% of overall

Security posture

41Weak
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
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
2.5/2.5Contributors — project has 5 contributing companies or organizations
0/10Dangerous-Workflow — no data
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 — 16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

40Weak · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

Verify loop (build / test / typecheck)

31At Risk
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — examples/astro/tsconfig.json, examples/next/tsconfig.json, examples/nuxt/tsconfig.json, examples/vite-svelte/jsconfig.json, tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practice — no data
0/8Automated maintenance — no data
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsexamples/astro/tsconfig.json, examples/next/tsconfig.json, examples/nuxt/tsconfig.json, examples/vite-svelte/jsconfig.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, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

82Excellent
How it's scored
27/45Type-checkable code — HTML with type-check config (examples/astro/tsconfig.json, examples/next/tsconfig.json, examples/nuxt/tsconfig.json, examples/vite-svelte/jsconfig.json, tsconfig.json)
55/55Manageable file sizes — 0/98 source files over 60KB
Inputs used
primary_languageHTML
largest_source_bytes10,885
source_files_sampled98
oversized_source_files0

Machine-readable interfaces

100Exceptional
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

168GitHub stars
2contributors
43commits, last 12 months
1days since last push
15releases
1bus factor
1open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 4.1 / 10
4.1aggregate

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 03:10 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/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
10Contributorsproject has 5 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 56

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

RegistryPackageVersionRelation
npm@builder.io/qwiklatestindirect
npm@eslint/js^10.0.1indirect
npm@floating-ui/dom^1.7.6indirect
npm@stylistic/eslint-plugin^5.10.0indirect
npm@stylistic/stylelint-config^5.0.0indirect
npm@sveltejs/vite-plugin-sveltelatestindirect
npm@tailwindcss/vite^4.3.0indirect
npm@types/nodelatestindirect
npm@types/react^18indirect
npm@types/reactlatestindirect
npm@types/react-dom^18indirect
npm@types/react-domlatestindirect
npm@vitejs/plugin-reactlatestindirect
npm@vitejs/plugin-vue^6.0.7indirect
npm@vitejs/plugin-vuelatestindirect
npmastrolatestindirect
npmautoprefixer^10indirect
npmautoprefixer^10.5.0indirect
npmcss-has-pseudo^6indirect
npmdts-buddy^0.8.0indirect
npmeslint^10.4.0indirect
npmeslintlatestindirect
npmeslint-config-nextlatestindirect
npmfast-glob^3.3.3indirect
npmglobals^17.6.0indirect
npmlesslatestindirect
npmlit^3indirect
npmnextlatestindirect
npmnuxtlatestindirect
npmpostcss^8indirect
npmpostcss^8.5.15indirect
npmpostcss-custom-media^10indirect
npmpostcss-custom-media^12.0.1indirect
npmpostcss-import^16indirect
npmpostcss-import^16.1.1indirect
npmpostcss-nesting^12indirect
npmpostcss-nesting^14.0.0indirect
npmreactlatestindirect
npmreact-domlatestindirect
npmsass^1indirect
npmservelatestindirect
npmslide-element^2.3.1indirect
npmsolid-jslatestindirect
npmstylelint^17.12.0indirect
npmstylelint-config-standard^40.0.0indirect
npmsveltelatestindirect
npmtailwindcss^3indirect
npmtailwindcss^4.3.0indirect
npmtypescript^5indirect
npmtypescript^6indirect
npmvite^8.0.14indirect
npmvitelatestindirect
npmvite-plugin-solidlatestindirect
npmvue^3.5.34indirect
npmvuelatestindirect
npmwinduum^2indirect
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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with winduum/winduum. Read them side by side →

100carbon-design-system/carbonA design system built by IBMExceptional99electron/electron:electron: Build cross-platform desktop apps with JavaScript, HTML, and CSSExceptional98prettier/prettierPrettier is an opinionated code formatter.Exceptional99stylelint/stylelintA mighty CSS linter that helps you avoid errors and enforce conventions.Exceptional99processing/p5.jsp5.js is a client-side JS platform that empowers artists, designers, students, and anyone to learn to code and express themselves creatively on the web. It is based on the core principles of Processing. Looking for p5.js 2.0? http://beta.p5js.orgExceptional98storybookjs/storybookStorybook is the industry standard workshop for building, documenting, and testing UI components in isolationExceptional

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