Public record
Software health reportschema 0.31.0 · metrics 2.6.0 · 2026-08-13 00:53 UTC

sql-formatter-org / sql-formatter

A whitespace formatter for different query languages

TypeScriptMIT★ 2,886 stars⑂ 457 forkssince Sep 2016View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

sql-formatter-org/sql-formatter holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (92/100) and lowest on AI Readiness (50/100). It was last updated 20 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

sql-formatter-orgOrganization
31 followers2 public repossince May 2022

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

Package ecosystems

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 20 days ago
17.3/36Commit cadence — 25/52 weeks with commits
18/18Commit volume — 137 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year137
human_commit_share1
days_since_last_push20
active_weeks_last_year25

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 52 days ago
27/27Release cadence — a release every ~21.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv15.8.2
releases_from_tagsno
days_since_latest_release52
mean_days_between_releases21.5
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?

84Excellent · 17% of overall
How it's scored
56.1/60Stars — 2,886 stars
22.2/25Forks — 457 forks
7.6/15Watchers — 24 watchers
Inputs used
forks457
stars2,886
watchers24
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescoveralls.io, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 15,988,075 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagessql-formatter
dependents
ecosystemsnpm
total_downloads
monthly_downloads15,988,075
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 factor — 1 contributor(s) cover half of all commits
6.9/22.5Commit distribution — top contributor authored 69% of commits
13.5/13.5Contributor breadth — 61 contributors
10/10OpenSSF Scorecard: Contributors — project has 26 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled61
top_contributor_share0.692
How it's scored
36.5/42Issue resolution — 87% of issues closed
23/30PR acceptance — 290/378 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 7/20 approved changesets -- score normalized to 3
Inputs used
merged_prs290
open_issues72
closed_issues479
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.869
closed_unmerged_prs88
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
10.8/25Owner reach — 31 followers of sql-formatter-org
12/25Track record — 2 public repos, account ~4 yr old
Inputs used
followers31
owner_typeOrganization
is_verified
owner_loginsql-formatter-org
public_repos2
account_age_days1,556

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 52 days ago
20/20Version history — 177 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagessql-formatter
ecosystemsnpm
any_deprecatedno
min_days_since_publish52

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://sql-formatter-org.github.io/sql-formatter/
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicssql, formatter, n1ql, javascript
has_wikiyes
homepagehttps://sql-formatter-org.github.io/sql-formatter/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

62Moderate · 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 — 6 out of 7 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
2.2/7.5Code-Review — Found 7/20 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 26 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 6 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.3
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_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:sql-formatter@15.8.2 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
13.3/40Legible commit history — 25 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.25
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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.02
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/170 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes52,487
source_files_sampled170
oversized_source_files0

Key facts

2,886GitHub stars
61contributors
137commits, last 12 months
20days since last push
100releases
1bus factor
72open 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 ★ / 457 ⇿
0Stars
457Forks
100Releases

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.

012525037537452017-012021-102026-08
Major 5Minor 17Patch 62

Each point covers 9 days.

OpenSSF Scorecard 5.3 / 10
5.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-08-13 00:53 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests6 out of 7 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 7/20 approved changesets -- score normalized to 3
10Contributorsproject has 26 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 6 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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 2
RegistryPackageVersion constraintManifest
npmargparse^2.0.1package.json
npmnearley^2.20.1package.json
All dependencies 19

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

RegistryPackageVersionRelation
npm@pnpm/exe11.9.0indirect
npm@pnpm/linux-arm6411.9.0indirect
npm@pnpm/linux-x6411.9.0indirect
npm@pnpm/linuxstatic-arm6411.9.0indirect
npm@pnpm/linuxstatic-x6411.9.0indirect
npm@pnpm/macos-arm6411.9.0indirect
npm@pnpm/win-arm6411.9.0indirect
npm@pnpm/win-x6411.9.0indirect
npm@reflink/reflink0.1.19indirect
npm@reflink/reflink-darwin-arm640.1.19indirect
npm@reflink/reflink-darwin-x640.1.19indirect
npm@reflink/reflink-linux-arm64-gnu0.1.19indirect
npm@reflink/reflink-linux-arm64-musl0.1.19indirect
npm@reflink/reflink-linux-x64-gnu0.1.19indirect
npm@reflink/reflink-linux-x64-musl0.1.19indirect
npm@reflink/reflink-win32-arm64-msvc0.1.19indirect
npm@reflink/reflink-win32-x64-msvc0.1.19indirect
npmdetect-libc2.1.2indirect
npmpnpm11.9.0indirect
Dependency advisories 0

Installing npm:sql-formatter@15.8.2 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

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.6.0, schema v0.31.0 — full methodology · metrics wiki.

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