Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-20 01:02 UTC

bigcommerce-labs / node-sass

:rainbow: Node.js bindings to libsass

C++ · JavaScriptMIT★ 1 star⑂ 6 forkssince Apr 2017forkView on GitHub ↗
KindCommand-line toolLibraryhow this is determined

bigcommerce-labs/node-sass holds a health index of 47 out of 100, placing it in the Weak band. It scores highest on AI Readiness (70/100) and lowest on Community & Adoption (31/100). It was last updated 319 days ago. 3 contributors account for most of its recent work.

47
overall / 100
Weak

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.

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

Ownership

BigCommerce LabsOrganization
60 followers70 public repossince Sep 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@bigcommerce/node-sass10.0.24,9593319 days agocsslibsasspreprocessorsassscssstyle

Metrics by category

Vitality

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

31At Risk · 21% of overall
How it's scored
3.6/36Push recencylast push 319 days ago
2.1/36Commit cadence3/52 weeks with commits
8.1/18Commit volume7 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year7
human_commit_share0.71
days_since_last_push319
active_weeks_last_year3
How it's scored
27/27Ships releases10 releases published
16.2/36Release recencylatest release 319 days ago
12.6/27Release cadencea release every ~345.9 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count10
latest_release_tagv10.0.2
releases_from_tagsno
days_since_latest_release319
mean_days_between_releases345.9

Community & Adoption

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

31At Risk · 17% of overall
How it's scored
0/60Stars1 stars
5.8/25Forks6 forks
10.4/15Watchers74 watchers
Inputs used
forks6
stars1
watchers74
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges7
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesci.appveyor.com, coveralls.io, github.com
has_pull_request_templateno
How it's scored
49.3/80Monthly downloads4,959 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@bigcommerce/node-sass
dependents
ecosystemsnpm
total_downloads
monthly_downloads4,959
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?

64Moderate · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
16.1/22.5Commit distributiontop contributor authored 28% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 97 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled99
top_contributor_share0.283
How it's scored
0/42Issue resolutionno issues or no data
14.1/30PR acceptance23/49 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs23
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs26
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
12.8/25Owner reach60 followers of bigcommerce-labs
25/25Track record70 public repos, account ~12 yr old
Inputs used
followers60
owner_typeOrganization
is_verifiedno
owner_loginbigcommerce-labs
public_repos70
account_age_days4,742
How it's scored
25/25Published & resolvable1 package(s) on npm
26/35Publish recencylatest publish 319 days ago
12/20Version history3 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@bigcommerce/node-sass
ecosystemsnpm
any_deprecatedno
min_days_since_publish319

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

15Critical
How it's scored
0/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://npmjs.org/package/node-sass
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://npmjs.org/package/node-sass
docs_sitehttps://npmjs.org/package/node-sass
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

48Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 97 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
10/25Indirect dependencies free of known advisories1 affected: minimatch 3.0.8 (high 7.5)
33.7/40No advisories left outstanding1 advisory-carrying package(s) unaddressed past 90 days; oldest published 213 days ago
Inputs used
sourceosv
advisories3
affected_packages1
assessed_packages205
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages0
Matched the npm:@bigcommerce/node-sass@10.0.2 runtime dependency closure — what installing the published package pulls in — 205 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.

70Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://nodejs.org/llms.txt)
40/40Legible commit history55 of 71 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://nodejs.org/llms.txt
legible_history_share0.775
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapmise.toml, src/libsass/Makefile
22/22Automated tests
11/11Lint / format config.eslintrc.json
11/11Static type checkingC++ (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance29 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_filesmise.toml, src/libsass/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.29
How it's scored
45/45Type-checkable codeC++ (statically typed)
53.3/55Manageable file sizes6/189 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes109,288
source_files_sampled189
oversized_source_files6

Key facts

1GitHub stars
99contributors
7commits, last 12 months
319days since last push
10releases
3bus factor
0open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 6 ⇿
0Stars
6Forks
5Releases

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.

123456612019-072022-032024-11
Major 0Minor 2Patch 3

Each point covers 5 days.

OpenSSF Scorecard 4.0 / 10
4.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-09-20 01:02 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests2 out of 2 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/30 approved changesets -- score normalized to 0
10Contributorsproject has 97 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
Direct dependencies 14
RegistryPackageVersion constraintManifest
npmasync-foreach^0.1.3package.json
npmchalk^4.1.2package.json
npmcross-spawn^7.0.3package.json
npmgaze^1.0.0package.json
npmget-stdin^4.0.1package.json
npmglob^7.0.3package.json
npmlodash^4.17.15package.json
npmmake-fetch-happen^15.0.2package.json
npmmeow^9.0.0package.json
npmnan^2.17.0package.json
npmnode-gyp^11.4.2package.json
npmsass-graph^4.0.1package.json
npmstdout-stream^1.4.0package.json
npmtrue-case-path^2.2.1package.json
All dependencies 20

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

RegistryPackageVersionRelation
npmasync-foreach^0.1.3direct
npmchalk^4.1.2direct
npmcross-spawn^7.0.3direct
npmgaze^1.0.0direct
npmget-stdin^4.0.1direct
npmglob^7.0.3direct
npmlodash^4.17.15direct
npmmake-fetch-happen^15.0.2direct
npmmeow^9.0.0direct
npmnan^2.17.0direct
npmnode-gyp^11.4.2direct
npmsass-graph^4.0.1direct
npmstdout-stream^1.4.0direct
npmtrue-case-path^2.2.1direct
npmeslint^8.0.0indirect
npmfs-extra^10.0.0indirect
npmmocha^11.7.4indirect
npmnyc^15.1.0indirect
npmrimraf^3.0.2indirect
npmunique-temp-dir^1.0.0indirect
Dependency advisories 1

Installing npm:@bigcommerce/node-sass@10.0.2 pulls in 205 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
minimatch3.0.8indirecthigh310.2.3

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