Public record
Software health reportschema 0.31.0 · metrics 2.5.0 · 2026-08-05 08:40 UTC

sass / dart-sass

The reference implementation of Sass, written in Dart.

Dart · TypeScriptMIT★ 4,213 stars⑂ 379 forkssince Oct 2016View on GitHub ↗

sass/dart-sass holds a health index of 96 out of 100, placing it in the Exceptional band. It scores highest on Community & Adoption (91/100) and lowest on AI Readiness (59/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

96
overall / 100
Exceptional

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.

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

Ownership

SassOrganization
986 followers30 public repossince Jun 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmsass1.102.0121,452,34932111 days agostylescsssasspreprocessorcss

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 1 days ago
26.3/36Commit cadence — 38/52 weeks with commits
18/18Commit volume — 124 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_year124
human_commit_share0.63
days_since_last_push1
active_weeks_last_year38
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 11 days ago
27/27Release cadence — a release every ~15.1 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tag1.102.0
releases_from_tagsno
days_since_latest_release11
mean_days_between_releases15.1

Community & Adoption

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

91Excellent · 17% of overall
How it's scored
58.8/60Stars — 4,213 stars
21.5/25Forks — 379 forks
10.3/15Watchers — 71 watchers
Inputs used
forks379
stars4,213
watchers71
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 (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 121,452,349 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagessass
dependents
ecosystemsnpm
total_downloads
monthly_downloads121,452,349
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?

73Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.6/22.5Commit distribution — top contributor authored 84% of commits
13.5/13.5Contributor breadth — 65 contributors
10/10OpenSSF Scorecard: Contributors — project has 27 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled65
top_contributor_share0.841
How it's scored
39.9/42Issue resolution — 95% of issues closed
27.8/30PR acceptance — 1,421/1,535 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs1,421
open_issues60
closed_issues1,172
prs_merged_7d1
prs_decided_7d1
prs_merged_30d13
prs_decided_30d13
issue_closed_ratio0.951
closed_unmerged_prs114
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
21.5/25Owner reach — 986 followers of sass
22.9/25Track record — 30 public repos, account ~16 yr old
Inputs used
followers986
owner_typeOrganization
is_verified
owner_loginsass
public_repos30
account_age_days5,880

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows — 8 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 27 out of 27 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

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://sass-lang.com/dart-sass
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicssass, css-preprocessor, dart, dart-sass
has_wikiyes
homepagehttps://sass-lang.com/dart-sass
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

76Good · 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 — 27 out of 27 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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 27 contributing companies or organizations
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
3/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
4/5SAST — SAST tool is not run on all commits -- score normalized to 8
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7
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
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_packages22
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:sass@1.102.0 runtime dependency closure — what installing the published package pulls in — 22 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.

59Moderate · 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 — 55 of 63 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.873
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.mjs
11/11Static type checking — pkg/sass-parser/tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 37 of the last 100 commits are automated dependency updates
6/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configspkg/sass-parser/tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.37
How it's scored
45/45Type-checkable code — Dart (statically typed)
54.5/55Manageable file sizes — 6/621 source files over 60KB
Inputs used
primary_languageDart
largest_source_bytes167,876
source_files_sampled621
oversized_source_files6

Key facts

4,213GitHub stars
65contributors
124commits, last 12 months
1days since last push
100releases
1bus factor
60open 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 ★ / 379 ⇿
0Stars
379Forks
100Releases

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.

010020030040037872016-102021-092026-07
Major 0Minor 35Patch 65

Each point covers 9 days.

OpenSSF Scorecard 7.0 / 10
7.0aggregate

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-08-05 08:39 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests27 out of 27 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 27 contributing companies or organizations
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
6Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
8SASTSAST tool is not run on all commits -- score normalized to 8
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmchokidar^5.0.0package/package.json
npmimmutable^5.1.5package/package.json
npmsource-map-js>=0.6.2 <2.0.0package/package.json
All dependencies 24

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

RegistryPackageVersionRelation
npmchokidar^5.0.0direct
npmimmutable^5.1.5direct
npmsource-map-js>=0.6.2 <2.0.0direct
npm@eslint/eslintrc^3.3.3indirect
npm@eslint/js^9.39.2indirect
npm@parcel/watcher^2.4.1indirect
npm@types/jest^30.0.0indirect
npm@typescript-eslint/eslint-plugin^8.53.0indirect
npm@typescript/typescript6^6.0.2indirect
npmcopyfiles^2.4.1indirect
npmeslint^10.0.1indirect
npmexpect^30.0.5indirect
npmgts^7.0.0indirect
npmintercept-stdout^0.1.2indirect
npmjest^30.0.4indirect
npmjest-extended^7.0.0indirect
npmnpm-run-all^4.1.5indirect
npmpostcss8.5.23indirect
npmrimraf^6.0.1indirect
npmts-jest^29.4.11indirect
npmts-node^10.2.1indirect
npmtypedoc^0.28.0indirect
npmtypescript^7.0.2indirect
npmtypescript-eslint^8.53.0indirect
Dependency advisories 0

Installing npm:sass@1.102.0 pulls in 22 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

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.31.0 — full methodology · metrics wiki.

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