Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 08:53 UTC

browserslist / update-db

CLI tool to update caniuse-lite to refresh target browsers from Browserslist config

JavaScriptMIT★ 841 stars⑂ 226 forkssince Jun 2022View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

browserslist/update-db holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Vitality (79/100) and lowest on AI Readiness (33/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

34
overall / 100
At Risk

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.

34
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). High-Risk Jurisdiction Policy applies a 75% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

BrowserslistOrganization
273 followers17 public repossince Mar 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmupdate-browserslist-db1.3.3665,009,527305 days agobrowserscaniusetarget

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
36/36Push recency — last push 5 days ago
8.3/36Commit cadence — 12/52 weeks with commits
16/18Commit volume — 60 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year60
human_commit_share1
days_since_last_push5
active_weeks_last_year12
How it's scored
27/27Ships releases — 16 releases published
36/36Release recency — latest release 5 days ago
19.8/27Release cadence — a release every ~62.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count16
latest_release_tag1.3.3
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases62.3
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?

72Good · 17% of overall
How it's scored
47.4/60Stars — 841 stars
19.6/25Forks — 226 forks
7/15Watchers — 19 watchers
Inputs used
forks226
stars841
watchers19
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
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 — 665,009,527 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesupdate-browserslist-db
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads665,009,527
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?

65Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.1/22.5Commit distribution — top contributor authored 86% of commits
13.5/13.5Contributor breadth — 15 contributors
10/10OpenSSF Scorecard: Contributors — project has 10 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled15
top_contributor_share0.863
How it's scored
36.3/42Issue resolution — 86% of issues closed
17.8/30PR acceptance — 22/37 decided PRs merged
10.8/13Newcomer PR acceptance — 5/6 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 6/30 approved changesets -- score normalized to 2
Inputs used
merged_prs22
open_issues7
closed_issues45
prs_merged_7d0
prs_decided_7d0
prs_merged_30d5
prs_decided_30d6
issue_closed_ratio0.865
closed_unmerged_prs15
first_time_authors_30d2
first_time_prs_merged_30d5
first_time_prs_decided_30d6
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
17.5/25Owner reach — 273 followers of browserslist
21.1/25Track record — 17 public repos, account ~8 yr old
Inputs used
followers273
owner_typeOrganization
is_verifiedno
owner_loginbrowserslist
public_repos17
account_age_days3,103

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 5 days ago
20/20Version history — 30 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesupdate-browserslist-db
ecosystemsnpm
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 5 out of 6 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://browsersl.ist/
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://browsersl.ist/
docs_sitehttps://browsersl.ist/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

47Weak · 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/2.5CI-Tests — 5 out of 6 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 6/30 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 10 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
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 3 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
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
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 16 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.9
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier75
security_posture_after_multiplier37
security_posture_before_jurisdiction49
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 75% multiplier and gives Security posture an At risk ceiling of 34.

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_packages2
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:update-browserslist-db@1.3.3 runtime dependency closure — what installing the published package pulls in — 2 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.

33At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
9.1/40Legible commit history — 17 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.17
agent_instruction_files—
agent_instruction_max_bytes—
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 agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesbun.lockb, package-lock.json, pnpm-lock.yaml, yarn.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/10 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes18,000
source_files_sampled10
oversized_source_files0

Key facts

841GitHub stars
15contributors
60commits, last 12 months
5days since last push
16releases
1bus factor
7open 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 ★ / 226 ⇿
0Stars
226Forks
16Releases

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.

0408012016020024022262022-082024-082026-09
Major 0Minor 3Patch 13

Each point covers 4 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-16 08:53 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests5 out of 6 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 6/30 approved changesets -- score normalized to 2
10Contributorsproject has 10 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities16 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmescalade^3.2.0package.json
npmpicocolors^1.1.1package.json
All dependencies 118

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

RegistryPackageVersionRelation
npmescalade3.2.0direct
npmpicocolors1.1.1direct
npm@bcoe/v8-coverage1.0.2indirect
npm@istanbuljs/schema0.1.6indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@logux/oxc-configs1.2.0indirect
npm@oxlint-tsgolint/darwin-arm647.0.2001indirect
npm@oxlint-tsgolint/darwin-x647.0.2001indirect
npm@oxlint-tsgolint/linux-arm647.0.2001indirect
npm@oxlint-tsgolint/linux-x647.0.2001indirect
npm@oxlint-tsgolint/win32-arm647.0.2001indirect
npm@oxlint-tsgolint/win32-x647.0.2001indirect
npm@oxlint/binding-android-arm-eabi1.82.0indirect
npm@oxlint/binding-android-arm641.82.0indirect
npm@oxlint/binding-darwin-arm641.82.0indirect
npm@oxlint/binding-darwin-x641.82.0indirect
npm@oxlint/binding-freebsd-x641.82.0indirect
npm@oxlint/binding-linux-arm-gnueabihf1.82.0indirect
npm@oxlint/binding-linux-arm-musleabihf1.82.0indirect
npm@oxlint/binding-linux-arm64-gnu1.82.0indirect
npm@oxlint/binding-linux-arm64-musl1.82.0indirect
npm@oxlint/binding-linux-ppc64-gnu1.82.0indirect
npm@oxlint/binding-linux-riscv64-gnu1.82.0indirect
npm@oxlint/binding-linux-riscv64-musl1.82.0indirect
npm@oxlint/binding-linux-s390x-gnu1.82.0indirect
npm@oxlint/binding-linux-x64-gnu1.82.0indirect
npm@oxlint/binding-linux-x64-musl1.82.0indirect
npm@oxlint/binding-openharmony-arm641.82.0indirect
npm@oxlint/binding-win32-arm64-msvc1.82.0indirect
npm@oxlint/binding-win32-ia32-msvc1.82.0indirect
npm@oxlint/binding-win32-x64-msvc1.82.0indirect
npm@types/istanbul-lib-coverage2.0.6indirect
npm@typescript/typescript-aix-ppc647.0.2indirect
npm@typescript/typescript-darwin-arm647.0.2indirect
npm@typescript/typescript-darwin-x647.0.2indirect
npm@typescript/typescript-freebsd-arm647.0.2indirect
npm@typescript/typescript-freebsd-x647.0.2indirect
npm@typescript/typescript-linux-arm7.0.2indirect
npm@typescript/typescript-linux-arm647.0.2indirect
npm@typescript/typescript-linux-loong647.0.2indirect
npm@typescript/typescript-linux-mips64el7.0.2indirect
npm@typescript/typescript-linux-ppc647.0.2indirect
npm@typescript/typescript-linux-riscv647.0.2indirect
npm@typescript/typescript-linux-s390x7.0.2indirect
npm@typescript/typescript-linux-x647.0.2indirect
npm@typescript/typescript-netbsd-arm647.0.2indirect
npm@typescript/typescript-netbsd-x647.0.2indirect
npm@typescript/typescript-openbsd-arm647.0.2indirect
npm@typescript/typescript-openbsd-x647.0.2indirect
npm@typescript/typescript-sunos-x647.0.2indirect
npm@typescript/typescript-win32-arm647.0.2indirect
npm@typescript/typescript-win32-x647.0.2indirect
npmansi-regex6.3.0indirect
npmansi-styles6.2.3indirect
npmbalanced-match4.0.4indirect
npmbaseline-browser-mapping2.11.21indirect
npmbrace-expansion5.0.9indirect
npmbrowserslist4.28.9indirect
npmc812.0.0indirect
npmcaniuse-lite1.0.30001810indirect
npmcliui9.0.1indirect
npmconvert-source-map2.0.0indirect
npmcross-spawn7.0.6indirect
npmdequal2.0.3indirect
npmdiff5.2.2indirect
npmelectron-to-chromium1.5.425indirect
npmemoji-regex10.6.0indirect
npmeslint-plugin-prefer-let4.2.2indirect
npmfind-up5.0.0indirect
npmforeground-child3.3.1indirect
npmget-caller-file2.0.5indirect
npmget-east-asian-width1.6.0indirect
npmglob13.0.6indirect
npmhas-flag4.0.0indirect
npmhtml-escaper2.0.2indirect
npmisexe2.0.0indirect
npmistanbul-lib-coverage3.2.2indirect
npmistanbul-lib-report3.0.1indirect
npmistanbul-reports3.2.0indirect
npmkleur4.1.5indirect
npmlocate-path6.0.0indirect
npmlru-cache11.5.2indirect
npmmake-dir4.0.0indirect
npmminimatch10.2.6indirect
npmminipass7.1.3indirect
npmmri1.2.0indirect
npmnode-releases2.0.55indirect
npmoxlint1.82.0indirect
npmoxlint-tsgolint7.0.2001indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpath-scurry2.0.2indirect
npmrequireindex1.2.0indirect
npmsade1.8.1indirect
npmsemver7.8.5indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmstring-width7.2.0indirect
npmstring-width8.2.2indirect
npmstrip-ansi7.2.0indirect
npmsupports-color7.2.0indirect
npmtest-exclude8.0.0indirect
npmtypescript7.0.2indirect
npmupdate-browserslist-db1.3.2indirect
npmuvu0.5.6indirect
npmv8-to-istanbul9.3.0indirect
npmwhich2.0.2indirect
npmwrap-ansi9.0.2indirect
npmy18n5.0.8indirect
npmyargs18.1.0indirect
npmyargs-parser21.1.1indirect
npmyargs-parser22.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:update-browserslist-db@1.3.3 pulls in 2 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.