Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 16:21 UTC

saadeghi / daisyui

🌼 🌼 🌼 🌼 🌼  The most popular, free and open-source Tailwind CSS component library

JavaScript · Svelte · HTMLMIT★ 42,393 stars⑂ 1,685 forkssince Nov 2020View on GitHub ↗

saadeghi/daisyui holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Vitality (94/100) and lowest on Security (47/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Pouya SaadeghiPersonal account
3,481 followers86 public repossince Apr 2014@daisyui. prev: @manasky @atbox

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

Package ecosystems

Metrics by category

Vitality

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

94Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
33.2/36Commit cadence — 48/52 weeks with commits
18/18Commit volume — 666 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 16 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year666
human_commit_share1
days_since_last_push1
active_weeks_last_year48
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~1.4 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv5.7.38
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases1.4

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

88Excellent · 17% of overall
How it's scored
60/60Stars — 42,393 stars
25/25Forks — 1,685 forks
12.4/15Watchers — 168 watchers
Inputs used
forks1,685
stars42,393
watchers168
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
How it's scored
80/80Monthly downloads — 3,687,347 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesdaisyui
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads3,687,347
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?

68Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.6/22.5Commit distribution — top contributor authored 88% of commits
13.5/13.5Contributor breadth — 100 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled100
top_contributor_share0.884
How it's scored
41.6/42Issue resolution — 99% of issues closed
23.7/30PR acceptance — 648/819 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-Review — Found 18/30 approved changesets -- score normalized to 6
Inputs used
merged_prs648
open_issues19
closed_issues2,192
prs_merged_7d14
prs_decided_7d14
prs_merged_30d44
prs_decided_30d46
issue_closed_ratio0.991
closed_unmerged_prs171
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
25/25Owner reach — 3,481 followers of saadeghi
25/25Track record — 86 public repos, account ~12 yr old
Inputs used
followers3,481
owner_typeUser
is_verified—
owner_loginsaadeghi
public_repos86
account_age_days4,533
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 1 days ago
20/20Version history — 820 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesdaisyui
ecosystemsnpm
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 17 out of 18 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://daisyui.com
10/10Repository description
10/10Topics — 20 topics
0/10Wiki
Inputs used
topicstailwind-css, ui-library, design-system, ui-pattern, ui-framework, css-components, css-framework, ui-kit, ui-design, design-systems, tailwind, css, postcss, tailwindcss, component, components, component-library, daisyui, svelte, front-end
has_wikino
homepagehttps://daisyui.com
docs_sitehttps://daisyui.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

47Weak · 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.2/2.5CI-Tests — 17 out of 18 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-Review — Found 18/30 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 6 contributing companies or organizations
0/10Dangerous-Workflow — 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 16 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
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): Packaging. 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
advisories1
affected_packages1
assessed_packages29
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 29 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.

53Moderate · 4% of overall
How it's scored
45/45Agent instructions — .github/instructions/code_generation.instructions.md, .github/instructions/code_generation_with_git.instructions.md, .github/instructions/communication.instructions.md, .github/instructions/packages.daisyui.instructions.md, .github/instructions/packages.docs.instructions.md, .github/instructions/workspace.instructions.md, packages/AGENTS.md, packages/daisyui/AGENTS.md, packages/docs/AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://daisyui.com/llms.txt)
40/40Legible commit history — 80 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://daisyui.com/llms.txt
legible_history_share0.8
agent_instruction_files.github/instructions/code_generation.instructions.md, .github/instructions/code_generation_with_git.instructions.md, .github/instructions/communication.instructions.md, .github/instructions/packages.daisyui.instructions.md, .github/instructions/packages.docs.instructions.md, .github/instructions/workspace.instructions.md, packages/AGENTS.md, packages/daisyui/AGENTS.md, packages/docs/AGENTS.md
agent_instruction_max_bytes5,377
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
2/10Demonstrated agent practice — 1 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_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
54.5/55Manageable file sizes — 2/225 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes350,881
source_files_sampled225
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
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

42,393GitHub stars
100contributors
666commits, last 12 months
1days since last push
100releases
1bus factor
19open 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 ★ / 1,685 ⇿
0Stars
1,685Forks
99Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

5007501,0001,2501,5001,7501,685402023-052025-012026-09
Major 0Minor 5Patch 94

Each point covers 4 days.

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-09-16 16:20 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
9CI-Tests17 out of 18 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 18/30 approved changesets -- score normalized to 6
10Contributorsproject has 6 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 16 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
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 29

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

RegistryPackageVersionRelation
npm@minimal-analytics/ga41.8.7indirect
npm@neoconfetti/svelte2.2.2indirect
npm@sveltejs/adapter-static3.0.10indirect
npm@sveltejs/kit2.70.1indirect
npm@sveltejs/vite-plugin-svelte7.2.0indirect
npm@tailwindcss/cli4.3.3indirect
npm@tailwindcss/typography0.5.20indirect
npm@tailwindcss/vite4.3.3indirect
npmculori4.0.2indirect
npmjs-yaml5.2.2indirect
npmjson-diff1.0.6indirect
npmlightningcss1.33.0indirect
npmmdsvex0.12.8indirect
npmpako3.0.1indirect
npmpostcss8.5.24indirect
npmpostcss-js5.1.0indirect
npmpostcss-selector-parser7.1.4indirect
npmprettier3.9.6indirect
npmprettier-plugin-svelte4.1.1indirect
npmprettier-plugin-tailwindcss0.8.1indirect
npmsuper-sitemap2.0.6indirect
npmsvelte5.56.8indirect
npmsvelte-countdown1.1.2indirect
npmsvelte-countup0.2.8indirect
npmtailwindcss4.3.3indirect
npmtheme-change3.0.4indirect
npmvite8.1.5indirect
npmvscode-oniguruma2.0.1indirect
npmvscode-textmate9.3.2indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
@sveltejs/kit2.70.1indirectmoderate12.70.2

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.