Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-05 21:08 UTC

ryo-manba / stylelint-plugin-use-baseline

A Stylelint plugin that enforces Baseline CSS features.

JavaScriptMIT★ 36 stars⑂ 7 forkssince Feb 2025View on GitHub ↗

ryo-manba/stylelint-plugin-use-baseline holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on AI Readiness (52/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Ryo MatsukawaPersonal account
111 followers119 public repossince Dec 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmstylelint-plugin-use-baseline1.4.542,8114711 days agobaselinecsslintstylelintstylelint-plugin

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
22.2/36Commit cadence32/52 weeks with commits
18/18Commit volume122 commits in the last year
10/10OpenSSF Scorecard: Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year122
human_commit_share0.56
days_since_last_push3
active_weeks_last_year32

Release discipline

100Exceptional
How it's scored
27/27Ships releases50 releases published
36/36Release recencylatest release 11 days ago
27/27Release cadencea release every ~16.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count50
latest_release_tagv1.4.5
releases_from_tagsno
days_since_latest_release11
mean_days_between_releases16.1
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?

57Moderate · 17% of overall
How it's scored
25/60Stars36 stars
6.5/25Forks7 forks
0/15Watchers2 watchers
Inputs used
forks7
stars36
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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
61.8/80Monthly downloads42,811 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesstylelint-plugin-use-baseline
dependents
ecosystemsnpm
total_downloads
monthly_downloads42,811
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.1/22.5Commit distributiontop contributor authored 73% of commits
6.8/13.5Contributor breadth5 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.731
How it's scored
36.5/42Issue resolution87% of issues closed
25.9/30PR acceptance115/133 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/11 approved changesets -- score normalized to 0
Inputs used
merged_prs115
open_issues3
closed_issues20
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.87
closed_unmerged_prs18
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
14.7/25Owner reach111 followers of ryo-manba
24.3/25Track record119 public repos, account ~5 yr old
Inputs used
followers111
owner_typeUser
is_verified
owner_loginryo-manba
public_repos119
account_age_days2,055
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 11 days ago
20/20Version history47 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesstylelint-plugin-use-baseline
ecosystemsnpm
any_deprecatedno
min_days_since_publish11

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests16 out of 24 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://www.npmjs.com/package/stylelint-plugin-use-baseline
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsbaseline, css, linter, stylelint, stylelint-plugin
has_wikiyes
homepagehttps://www.npmjs.com/package/stylelint-plugin-use-baseline
docs_sitehttps://www.npmjs.com/package/stylelint-plugin-use-baseline
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1.5/2.5CI-Tests16 out of 24 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/11 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
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
7.5/7.5Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
5/5Pinned-Dependenciesall dependencies are pinned
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
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_aggregate6.2
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages8
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:stylelint-plugin-use-baseline@1.4.5 runtime dependency closure — what installing the published package pulls in — 8 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.

52Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history56 of 56 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.js
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice19 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance10 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.19
toolchain_manifests
dependency_bot_commit_share0.1
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
51.3/55Manageable file sizes1/15 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes100,089
source_files_sampled15
oversized_source_files1

Key facts

36GitHub stars
5contributors
122commits, last 12 months
3days since last push
50releases
1bus factor
3open 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 ★ / 7 ⇿
0Stars
7Forks
46Releases

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.

1234567722025-042025-112026-06
Major 1Minor 12Patch 33

Each point covers 2 days.

OpenSSF Scorecard 6.2 / 10
6.2aggregate

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 21:08 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
6CI-Tests16 out of 24 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/11 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
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 4
RegistryPackageVersion constraintManifest
npmcss-tree^3.1.0package.json
npmis-plain-object^5.0.0package.json
npmpostcss^8.5.5package.json
npmpostcss-value-parser^4.2.0package.json
All dependencies 20

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

RegistryPackageVersionRelation
npmcss-tree^3.1.0direct
npmis-plain-object^5.0.0direct
npmpostcss^8.5.5direct
npmpostcss-value-parser^4.2.0direct
npm@rollup/plugin-commonjs^29.0.0indirect
npm@rollup/plugin-node-resolve^16.0.1indirect
npm@rollup/plugin-terser^0.4.4indirect
npm@stylelint/prettier-config^3.0.0indirect
npmcommon-tags^1.8.2indirect
npmeslint^9.29.0indirect
npmeslint-config-stylelint^25.0.0indirect
npmeslint-plugin-import^2.31.0indirect
npmeslint-plugin-jest^29.0.0indirect
npmjest^30.0.2indirect
npmjest-preset-stylelint^8.0.0indirect
npmmdn-data^2.29.0indirect
npmprettier^3.5.3indirect
npmrollup^4.43.0indirect
npmstylelint^17.0.0indirect
npmweb-features^3.34.0indirect
Dependency advisories 0

Installing npm:stylelint-plugin-use-baseline@1.4.5 pulls in 8 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.31.0 — full methodology · metrics wiki.

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