Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-18 23:11 UTC

w3c / browser-specs

A machine-readable list of Web specifications

JavaScriptCustom license★ 326 stars⑂ 55 forkssince Jan 2020View on GitHub ↗
KindLibraryhow this is determined

w3c/browser-specs holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (81/100) and lowest on AI Readiness (32/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

19
overall / 100
Critical

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.

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

Ownership

World Wide Web ConsortiumOrganization
7,671 followers1,096 public repossince Aug 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmbrowser-specs⚠ This package is no longer being maintained. Please switch to the web-specs package (same info with more specs).5.3.027,63228629 days ago

Metrics by category

Vitality

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

80Excellent · 21% of overall

Development activity

94Exceptional
How it's scored
36/36Push recency — last push 2 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 324 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year324
human_commit_share—
days_since_last_push2
active_weeks_last_year43

Release discipline

60Moderate
How it's scored
27/27Ships releases — 100 releases published
0/36Release recency — latest release 1,627 days ago
27/27Release cadence — a release every ~6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag2.27.0
releases_from_tagsno
days_since_latest_release1,627
mean_days_between_releases6
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?

71Good · 17% of overall

Popularity & adoption

62Moderate
How it's scored
40.7/60Stars — 326 stars
14.4/25Forks — 55 forks
7.4/15Watchers — 22 watchers
Inputs used
forks55
stars326
watchers22
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

79Good
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges—
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

74Good
How it's scored
59.2/80Monthly downloads — 27,632 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesbrowser-specs
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads27,632
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?

81Excellent · 23% of overall

Maintainer resilience (bus factor)

63Moderate
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
14.2/22.5Commit distribution — top contributor authored 37% of commits
13.5/13.5Contributor breadth — 26 contributors
10/10OpenSSF Scorecard: Contributors — project has 15 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled26
top_contributor_share0.368

Issue & PR responsiveness

84Excellent
How it's scored
37.5/42Issue resolution — 89% of issues closed
26.3/30PR acceptance — 1,631/1,862 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-Review — Found 11/17 approved changesets -- score normalized to 6
Inputs used
merged_prs1,631
open_issues75
closed_issues620
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio0.892
closed_unmerged_prs231
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

100Exceptional
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
25/25Owner reach — 7,671 followers of w3c
25/25Track record — 1,096 public repos, account ~15 yr old
Inputs used
followers7,671
owner_typeOrganization
is_verified—
owner_loginw3c
public_repos1,096
account_age_days5,803
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

80Excellent
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 29 days ago
20/20Version history — 286 published versions
0/20Not deprecated — browser-specs: This package is no longer being maintained. Please switch to the web-specs package (same info with more specs).
Inputs used
packagesbrowser-specs
ecosystemsnpm
any_deprecatedyes
min_days_since_publish29

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 19% of overall

Engineering practices

62Moderate
How it's scored
24/24CI workflows — 9 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests — 20 out of 26 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

65Good
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://w3c.github.io/browser-specs/
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://w3c.github.io/browser-specs/
docs_sitehttps://w3c.github.io/browser-specs/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

50Moderate · 16% of overall

Security posture

50Moderate
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
1.8/2.5CI-Tests — 20 out of 26 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-Review — Found 11/17 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 15 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 — 30 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
2.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
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
0/7.5Vulnerabilities — 10 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

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.

32At Risk · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

Verify loop (build / test / typecheck)

47Weak
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no data
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
5/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.

Code legibility for models

55Moderate
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/54 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes31,258
source_files_sampled54
oversized_source_files0

Key facts

326GitHub stars
26contributors
324commits, last 12 months
2days since last push
100releases
2bus factor
75open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 5.0 / 10
5.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-07-18 23:10 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
7CI-Tests20 out of 26 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 11/17 approved changesets -- score normalized to 6
10Contributorsproject has 15 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
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
0Vulnerabilities10 existing vulnerabilities detected
All dependencies 135

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

RegistryPackageVersionRelation
npm@actions/core3.0.1indirect
npm@actions/exec3.0.0indirect
npm@actions/http-client4.0.0indirect
npm@actions/io3.0.2indirect
npm@isaacs/cliui8.0.2indirect
npm@isaacs/cliui9.0.0indirect
npm@isaacs/fs-minipass4.0.1indirect
npm@jsdevtools/npm-publish4.1.5indirect
npm@octokit/auth-token6.0.0indirect
npm@octokit/core7.0.6indirect
npm@octokit/endpoint11.0.2indirect
npm@octokit/graphql9.0.3indirect
npm@octokit/openapi-types27.0.0indirect
npm@octokit/plugin-paginate-rest14.0.0indirect
npm@octokit/plugin-request-log6.0.0indirect
npm@octokit/plugin-rest-endpoint-methods17.0.0indirect
npm@octokit/plugin-throttling11.0.3indirect
npm@octokit/request10.0.6indirect
npm@octokit/request-error7.0.2indirect
npm@octokit/rest22.0.1indirect
npm@octokit/types16.0.0indirect
npm@pkgjs/parseargs0.11.0indirect
npm@puppeteer/browsers3.0.4indirect
npm@puppeteer/browsers3.0.6indirect
npm@types/semver7.7.1indirect
npmajv8.20.0indirect
npmajv-formats3.0.1indirect
npmansi-regex5.0.1indirect
npmansi-regex6.0.1indirect
npmansi-regex6.2.2indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.1indirect
npmansi-styles6.2.3indirect
npmarray-back6.2.2indirect
npmbalanced-match1.0.2indirect
npmbalanced-match4.0.2indirect
npmbefore-after-hook4.0.0indirect
npmbottleneck2.19.5indirect
npmbrace-expansion2.0.2indirect
npmbrace-expansion5.0.2indirect
npmchownr3.0.0indirect
npmchromium-bidi16.0.1indirect
npmcliui8.0.1indirect
npmcliui9.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcommand-line-args6.0.1indirect
npmcommander15.0.0indirect
npmcross-spawn7.0.6indirect
npmdevtools-protocol0.0.1624250indirect
npmdevtools-protocol0.0.1638949indirect
npmeastasianwidth0.2.0indirect
npmemoji-regex10.6.0indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmescalade3.2.0indirect
npmescape-string-regexp1.0.5indirect
npmfast-content-type-parse3.0.0indirect
npmfast-deep-equal3.1.3indirect
npmfast-uri3.1.2indirect
npmfetch-filecache-for-crawling5.1.1indirect
npmfilename-reserved-regex2.0.0indirect
npmfilenamify4.3.0indirect
npmfilenamify-url2.1.2indirect
npmfind-replace5.0.2indirect
npmforeground-child3.3.1indirect
npmget-caller-file2.0.5indirect
npmget-east-asian-width1.6.0indirect
npmglob10.5.0indirect
npmglob13.0.3indirect
npmhumanize-url2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmisexe2.0.0indirect
npmjackspeak3.4.3indirect
npmjackspeak4.2.3indirect
npmjson-schema-traverse1.0.0indirect
npmlilconfig3.1.3indirect
npmlodash.camelcase4.3.0indirect
npmlru-cache10.4.3indirect
npmlru-cache11.2.6indirect
npmminimatch10.2.4indirect
npmminimatch9.0.9indirect
npmminipass7.1.2indirect
npmminizlib3.1.0indirect
npmmitt3.0.1indirect
npmmodern-tar0.7.6indirect
npmnormalize-url4.5.1indirect
npmpackage-json-from-dist1.0.1indirect
npmpath-key3.1.1indirect
npmpath-scurry1.11.1indirect
npmpath-scurry2.0.1indirect
npmpuppeteer25.1.0indirect
npmpuppeteer25.3.0indirect
npmpuppeteer-core25.1.0indirect
npmpuppeteer-core25.3.0indirect
npmreffy21.0.4indirect
npmrequire-directory2.1.1indirect
npmrequire-from-string2.0.2indirect
npmrimraf5.0.10indirect
npmrimraf6.1.3indirect
npmsemver7.7.3indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstring-width7.2.0indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.1.0indirect
npmstrip-ansi7.2.0indirect
npmstrip-outer1.0.1indirect
npmtar7.5.7indirect
npmtrim-repeated1.0.0indirect
npmtunnel0.0.6indirect
npmtyped-query-selector2.12.2indirect
npmtypical7.3.0indirect
npmundici6.24.1indirect
npmundici8.7.0indirect
npmuniversal-user-agent7.0.3indirect
npmvalidate-npm-package-name7.0.1indirect
npmweb-specs4.2.0indirect
npmwebdriver-bidi-protocol0.4.2indirect
npmwebidl224.5.0indirect
npmwhich2.0.2indirect
npmwrap-ansi7.0.0indirect
npmwrap-ansi8.1.0indirect
npmwrap-ansi9.0.2indirect
npmws8.21.0indirect
npmy18n5.0.8indirect
npmyallist5.0.0indirect
npmyargs17.7.3indirect
npmyargs18.0.0indirect
npmyargs-parser21.1.1indirect
npmyargs-parser22.0.0indirect
npmzod3.25.76indirect
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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with w3c/browser-specs. Read them side by side →

100zephyrproject-rtos/zephyrPrimary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.Exceptional100supabase/supabase-jsAn isomorphic Javascript client for Supabase. Query your Supabase database, subscribe to realtime events, upload and download files, browse typescript examples, invoke postgres functions via rpc, invoke supabase edge functions, query pgvector.Exceptional100Azure/azure-sdk-for-jsThis repository is for active development of the Azure SDK for JavaScript (NodeJS & Browser). For consumers of the SDK we recommend visiting our public developer docs at https://docs.microsoft.com/javascript/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-js. Exceptional100hashicorp/consulConsul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.Exceptional100RocketChat/Rocket.ChatThe Secure CommsOS™ for mission-critical operationsExceptional100risingwavelabs/risingwaveEvent streaming platform for agentic AI. Continuously ingest, transform, and serve event streams in real time, at scale.Exceptional

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.14.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.