Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-11 16:15 UTC

anyblades / blades

Fully compatible and actively maintained successor to Pico CSS. Introduces float labels, breakout container and other modern, opt-out helpers. Simply switch `pico.css` to `blades.css` OR use `blades.standalone.css` with other frameworks 🥷✨

CSSMIT★ 359 stars⑂ 32 forkssince Oct 2016View on GitHub ↗

anyblades/blades holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Vitality (94/100) and lowest on AI Readiness (25/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

59
overall / 100
Moderate

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.

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

Ownership

Blades CSSOrganization
10 followers16 public repossince Apr 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@anyblades/blades3.0.05,5913237 days agobladesclasslesscss-frameworkcssdark-modedark-themelightweightminimalnative-htmlsemantic

Metrics by category

Vitality

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

94Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
26.3/36Commit cadence — 38/52 weeks with commits
18/18Commit volume — 704 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year704
human_commit_share1
days_since_last_push2
active_weeks_last_year38

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 44 releases published
36/36Release recency — latest release 37 days ago
27/27Release cadence — a release every ~9.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count44
latest_release_tagv3.0.0
releases_from_tagsno
days_since_latest_release37
mean_days_between_releases9.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?

61Moderate · 17% of overall
How it's scored
41.4/60Stars — 359 stars
12.4/25Forks — 32 forks
4.3/15Watchers — 7 watchers
Inputs used
forks32
stars359
watchers7
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/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_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno
How it's scored
50/80Monthly downloads — 5,591 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@anyblades/blades
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads5,591
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?

53Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.1/22.5Commit distribution — top contributor authored 100% of commits
5.4/13.5Contributor breadth — 4 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.995
How it's scored
29.1/42Issue resolution — 69% of issues closed
26.2/30PR acceptance — 7/8 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs7
open_issues19
closed_issues43
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.694
closed_unmerged_prs1
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
7.5/25Owner reach — 10 followers of anyblades
10/25Track record — 16 public repos, account ~0 yr old
Inputs used
followers10
owner_typeOrganization
is_verifiedno
owner_loginanyblades
public_repos16
account_age_days187

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 37 days ago
20/20Version history — 32 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@anyblades/blades
ecosystemsnpm
any_deprecatedno
min_days_since_publish37

Engineering Quality

Are baseline engineering and documentation practices in place?

27At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://blades.dev
10/10Repository description
10/10Topics — 11 topics
0/10Wiki
Inputs used
topicscss, pico-css, float-label, classless, picocss, nunjucks, liquid, blades-css, twig, jinja, html
has_wikino
homepagehttps://blades.dev
docs_sitehttps://blades.dev
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

46Weak · 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
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
3.8/7.5Vulnerabilities — 5 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.3
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories5
affected_packages3
assessed_packages91
unassessed_packages1
affected_by_severityhigh 3
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 91 resolved dependencies against OSV. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

25At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
28.8/40Legible commit history — 54 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.54
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — CSS without a type-check config
55/55Manageable file sizes — 0/1 source files over 60KB
Inputs used
primary_languageCSS
largest_source_bytes499
source_files_sampled1
oversized_source_files0

Key facts

359GitHub stars
4contributors
704commits, last 12 months
2days since last push
44releases
1bus factor
19open 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 ★ / 32 ⇿
0Stars
32Forks
40Releases

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.

01325383242016-102021-102026-10
Major 1Minor 5Patch 13

Each point covers 10 days.

OpenSSF Scorecard 3.3 / 10
3.3aggregate

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-11 16:15 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
5Vulnerabilities5 existing vulnerabilities detected
All dependencies 92

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

RegistryPackageVersionRelation
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmanymatch3.1.3indirect
npmautoprefixer10.5.4indirect
npmbalanced-match1.0.2indirect
npmbaseline-browser-mapping2.11.20indirect
npmbinary-extensions2.3.0indirect
npmbrace-expansion1.1.18indirect
npmbraces3.0.3indirect
npmbrowserslist4.28.8indirect
npmcaniuse-lite1.0.30001810indirect
npmchokidar3.6.0indirect
npmclean-css5.3.3indirect
npmclean-css-cli5.6.3indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcommander7.2.0indirect
npmconcat-map0.0.1indirect
npmcss-declaration-sorter7.4.0indirect
npmcssesc3.0.0indirect
npmdependency-graph1.0.0indirect
npmelectron-to-chromium1.5.420indirect
npmemoji-regex8.0.0indirect
npmes-errors1.3.0indirect
npmescalade3.2.0indirect
npmfdir6.5.0indirect
npmfill-range7.1.1indirect
npmfraction.js5.3.4indirect
npmfs-extra11.4.0indirect
npmfs.realpath1.0.0indirect
npmfsevents2.3.3indirect
npmfunction-bind1.1.2indirect
npmget-caller-file2.0.5indirect
npmglob7.2.3indirect
npmglob-parent5.1.2indirect
npmgraceful-fs4.2.11indirect
npmhasown2.0.4indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-binary-path2.1.0indirect
npmis-core-module2.16.2indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmjsonfile6.2.1indirect
npmlilconfig3.1.3indirect
npmminimatch3.1.5indirect
npmnanoid3.3.18indirect
npmnode-releases2.0.54indirect
npmnormalize-path3.0.0indirect
npmonce1.4.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-parse1.0.7indirect
npmpicocolors1.1.1indirect
npmpicomatch2.3.2indirect
npmpicomatch4.0.7indirect
npmpostcss8.5.28indirect
npmpostcss-cli11.0.1indirect
npmpostcss-import16.2.0indirect
npmpostcss-load-config5.1.0indirect
npmpostcss-nested7.0.2indirect
npmpostcss-reporter7.1.0indirect
npmpostcss-selector-parser7.1.6indirect
npmpostcss-value-parser4.2.0indirect
npmprettier3.9.6indirect
npmprettier-plugin-jinja-template2.2.0indirect
npmpretty-hrtime1.0.3indirect
npmread-cache1.0.2indirect
npmreaddirp3.6.0indirect
npmrequire-directory2.1.1indirect
npmresolve1.22.12indirect
npmslash5.1.0indirect
npmsource-map0.6.1indirect
npmsource-map-js1.2.1indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmthenby1.4.1indirect
npmtinyglobby0.2.17indirect
npmto-regex-range5.0.1indirect
npmuniversalify2.0.1indirect
npmupdate-browserslist-db1.3.2indirect
npmutil-deprecate1.0.2indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmy18n5.0.8indirect
npmyaml2.9.0indirect
npmyargs17.7.3indirect
npmyargs-parser21.1.1indirect
RubyGemsjekyll—indirect
Dependency advisories 3

This repository publishes no package the index resolves, so its own dependency graph was assessed — 91 packages, which also include development and test pins that never ship: 3 carry known advisories, of which 0 are direct. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion1.1.18indirecthigh35.0.12
braces3.0.3indirecthigh1—
source-map-js1.2.1indirecthigh11.2.2

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.