Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-13 03:37 UTC

postcss / postcss-cli

CLI for postcss

JavaScriptCustom license★ 856 stars⑂ 91 forkssince Jan 2016View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

postcss/postcss-cli holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (75/100) and lowest on AI Readiness (43/100). It was last updated 38 days ago. A single contributor accounts for most of its recent work.

75
overall / 100
Good

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.

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

Ownership

PostCSSOrganization · verified domain
432 followers58 public repossince Jul 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmpostcss-cli12.0.05,119,6185938 days agoclipostcsspostcss-runner

Metrics by category

Vitality

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

46Weak · 21% of overall
How it's scored
18/36Push recency — last push 38 days ago
4.8/36Commit cadence — 7/52 weeks with commits
14.1/18Commit volume — 36 commits in the last year
10/10OpenSSF Scorecard: Maintained — 28 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year36
human_commit_share0.48
days_since_last_push38
active_weeks_last_year7
How it's scored
27/27Ships releases — 15 releases published
0/36Release recency — latest release 2,212 days ago
12.6/27Release cadence — a release every ~140.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count15
latest_release_tag8.0.0
releases_from_tagsno
days_since_latest_release2,212
mean_days_between_releases140.7
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?

68Good · 17% of overall
How it's scored
47.6/60Stars — 856 stars
16.3/25Forks — 91 forks
5.6/15Watchers — 11 watchers
Inputs used
forks91
stars856
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 5,119,618 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespostcss-cli
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads5,119,618
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?

75Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
11/22.5Commit distribution — top contributor authored 51% of commits
13.5/13.5Contributor breadth — 44 contributors
10/10OpenSSF Scorecard: Contributors — project has 35 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled44
top_contributor_share0.513
How it's scored
41.6/42Issue resolution — 99% of issues closed
20.8/30PR acceptance — 210/303 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/19 approved changesets -- score normalized to 0
Inputs used
merged_prs210
open_issues2
closed_issues228
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.991
closed_unmerged_prs93
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
20/20Verified domain
19/25Owner reach — 432 followers of postcss
24.9/25Track record — 58 public repos, account ~12 yr old
Inputs used
followers432
owner_typeOrganization
is_verifiedyes
owner_loginpostcss
public_repos58
account_age_days4,458

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
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

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 3 topics
10/10Wiki
Inputs used
topicscli, postcss, postcss-runner
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
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
0/7.5Code-Review — Found 1/19 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 35 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.2/2.5License — license file detected
7.5/7.5Maintained — 28 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
1/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.7
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, 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
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_packages28
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:postcss-cli@12.0.0 runtime dependency closure — what installing the published package pulls in — 28 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.

43Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
31.1/40Legible commit history — 28 of 48 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.583
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
0/11Static type checking
0/10Reproducible environment
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 51 of the last 100 commits are automated dependency updates
2/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.02
toolchain_manifests—
dependency_bot_commit_share0.51
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/33 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes13,165
source_files_sampled33
oversized_source_files0

Key facts

856GitHub stars
44contributors
36commits, last 12 months
38days since last push
15releases
1bus factor
2open 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 ★ / 91 ⇿
0Stars
91Forks
15Releases

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.

0204060801009032016-022021-022026-02
Major 6Minor 5Patch 3

Each point covers 10 days.

OpenSSF Scorecard 5.7 / 10
5.7aggregate

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

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
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
0Code-ReviewFound 1/19 approved changesets -- score normalized to 0
10Contributorsproject has 35 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained28 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
npmchokidar^5.0.0package.json
npmdependency-graph^1.0.0package.json
npmpicocolors^1.0.0package.json
npmpostcss-load-config^6.0.0package.json
npmpostcss-reporter^7.0.0package.json
npmpretty-hrtime^1.0.3package.json
npmread-cache^1.0.0package.json
npmslash^5.0.0package.json
npmtinyglobby^0.2.12package.json
npmyargs^18.0.0package.json
All dependencies 20

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

RegistryPackageVersionRelation
npmchokidar^5.0.0direct
npmdependency-graph^1.0.0direct
npmpicocolors^1.0.0direct
npmpostcss-load-config^6.0.0direct
npmpostcss-reporter^7.0.0direct
npmpretty-hrtime^1.0.3direct
npmread-cache^1.0.0direct
npmslash^5.0.0direct
npmtinyglobby^0.2.12direct
npmyargs^18.0.0direct
npmava^8.0.0indirect
npmc8^12.0.0indirect
npmeslint^10.0.0indirect
npmeslint-config-problems10.0.1indirect
npmglobals^17.0.0indirect
npmpostcss^8.0.4indirect
npmpostcss-import^17.0.0indirect
npmprettier~3.9.0indirect
npmsugarss^5.0.0indirect
npmuuid^14.0.0indirect
Dependency advisories 0

Installing npm:postcss-cli@12.0.0 pulls in 28 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

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.