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

danielroe / beasties

A library to inline your app's critical CSS and lazy-load the rest.

TypeScriptApache-2.0★ 696 stars⑂ 25 forkssince Oct 2024View on GitHub ↗

danielroe/beasties holds a health index of 95 out of 100, placing it in the Exceptional band. It scores highest on Vitality (96/100) and lowest on AI Readiness (66/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

Daniel RoePersonal account
6,006 followers897 public repossince May 2017

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
npmbeasties0.5.413,518,558194 days agocritical-cssinline-csscriticalbeastieswebpack-pluginperformance
npmvite-plugin-beasties0.5.416,343164 days ago—
npmbeasties-webpack-plugin0.5.424,510194 days agocritical-cssinline-csscriticalbeastieswebpack-pluginperformance

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
33.9/36Commit cadence — 49/52 weeks with commits
18/18Commit volume — 237 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year237
human_commit_share0.33
days_since_last_push0
active_weeks_last_year49
How it's scored
27/27Ships releases — 18 releases published
36/36Release recency — latest release 4 days ago
19.8/27Release cadence — a release every ~47 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count18
latest_release_tagv0.5.4
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases47
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?

79Good · 17% of overall
How it's scored
46.1/60Stars — 696 stars
11.5/25Forks — 25 forks
3.3/15Watchers — 5 watchers
Inputs used
forks25
stars696
watchers5
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 (Apache-2.0)
18/18CONTRIBUTING guide
13.5/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_conductyes
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 13,559,411 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesbeasties, vite-plugin-beasties, beasties-webpack-plugin
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads13,559,411
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?

76Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.2/22.5Commit distribution — top contributor authored 41% of commits
13.5/13.5Contributor breadth — 32 contributors
10/10OpenSSF Scorecard: Contributors — project has 25 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled32
top_contributor_share0.413
How it's scored
36.8/42Issue resolution — 88% of issues closed
28.2/30PR acceptance — 369/392 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 14/19 approved changesets -- score normalized to 7
Inputs used
merged_prs369
open_issues4
closed_issues28
prs_merged_7d14
prs_decided_7d14
prs_merged_30d18
prs_decided_30d21
issue_closed_ratio0.875
closed_unmerged_prs23
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 — 6,006 followers of danielroe
25/25Track record — 897 public repos, account ~9 yr old
Inputs used
followers6,006
owner_typeUser
is_verified—
owner_logindanielroe
public_repos897
account_age_days3,403
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 3 package(s) on npm
35/35Publish recency — latest publish 4 days ago
20/20Version history — 19 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesbeasties, vite-plugin-beasties, beasties-webpack-plugin
ecosystemsnpm
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 29 out of 29 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://npmx.dev/beasties
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicscritical-css, css, inlining-critical-fonts, webpack, webpack-plugin, vite, vite-plugin
has_wikiyes
homepagehttps://npmx.dev/beasties
docs_sitehttps://npmx.dev/beasties
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

80Excellent · 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 — 29 out of 29 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
5.2/7.5Code-Review — Found 14/19 approved changesets -- score normalized to 7
2.5/2.5Contributors — project has 25 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 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
4.5/5SAST — SAST tool is not run on all commits -- score normalized to 9
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.5
Excluded from scoring (no data or not applicable): 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_packages16
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:beasties@0.5.4 runtime dependency closure — what installing the published package pulls in — 16 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.

66Good · 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 — 33 of 33 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 config — eslint.config.mjs
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 61 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.61
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/52 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes44,093
source_files_sampled52
oversized_source_files0

Key facts

696GitHub stars
32contributors
237commits, last 12 months
0days since last push
18releases
2bus factor
4open 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 ★ / 25 ⇿
0Stars
25Forks
11Releases

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.

05101520252522024-102025-092026-08
Major 0Minor 3Patch 8

Each point covers 2 days.

OpenSSF Scorecard 7.5 / 10
7.5aggregate

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-09 02:04 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests29 out of 29 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 14/19 approved changesets -- score normalized to 7
10Contributorsproject has 25 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 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
9SASTSAST tool is not run on all commits -- score normalized to 9
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
npmbeastiesworkspace:*packages/beasties-webpack-plugin/package.json
npmminimatch^10.0.1packages/beasties-webpack-plugin/package.json
npmcss-select^7.0.0packages/beasties/package.json
npmcss-what^8.0.0packages/beasties/package.json
npmdom-serializer^3.0.0packages/beasties/package.json
npmdomhandler^6.0.0packages/beasties/package.json
npmhtmlparser2^12.0.0packages/beasties/package.json
npmpicocolors^1.1.1packages/beasties/package.json
npmpostcss^8.4.49packages/beasties/package.json
npmpostcss-media-query-parser^0.2.3packages/beasties/package.json
npmpostcss-safe-parser^7.0.1packages/beasties/package.json
npmbeastiesworkspace:^packages/vite-plugin-beasties/package.json
All dependencies 33

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

RegistryPackageVersionRelation
npmcss-select^7.0.0direct
npmcss-what^8.0.0direct
npmdom-serializer^3.0.0direct
npmdomhandler^6.0.0direct
npmhtmlparser2^12.0.0direct
npmminimatch^10.0.1direct
npmpicocolors^1.1.1direct
npmpostcss^8.4.49direct
npmpostcss-media-query-parser^0.2.3direct
npmpostcss-safe-parser^7.0.1direct
npm@pnpm/exe.darwin-arm6412.3.4indirect
npm@pnpm/exe.darwin-x6412.3.4indirect
npm@pnpm/exe.linux-arm6412.3.4indirect
npm@pnpm/exe.linux-arm64-musl12.3.4indirect
npm@pnpm/exe.linux-x6412.3.4indirect
npm@pnpm/exe.linux-x64-musl12.3.4indirect
npm@pnpm/exe.win32-arm6412.3.4indirect
npm@pnpm/exe.win32-x6412.3.4indirect
npm@rspack/core2.2.1indirect
npm@types/jsdom30.0.0indirect
npm@types/postcss-media-query-parser0.2.5indirect
npmcss-loader7.1.5indirect
npmdocumentation14.0.3indirect
npmfile-loader6.2.0indirect
npmhtml-rspack-plugin6.1.9indirect
npmhtml-webpack-plugin5.6.8indirect
npmmini-css-extract-plugin2.10.2indirect
npmpnpm12.3.4indirect
npmrolldown1.2.6indirect
npmrollup4.63.1indirect
npmtsdown0.22.14indirect
npmvite8.2.2indirect
npmwebpack5.110.2indirect
Dependency advisories 0

Installing npm:beasties@0.5.4 pulls in 16 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.