Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 17:30 UTC

doctrine / sql-formatter

A lightweight php class for formatting sql statements. Handles automatic indentation and syntax highlighting.

HTML · PHPMIT★ 1,865 stars⑂ 29 forkssince Mar 2020View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

doctrine/sql-formatter holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (79/100) and lowest on AI Readiness (46/100). It was last updated 77 days ago. 2 contributors account for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

DoctrineOrganization · verified domain
346 followers77 public repossince Feb 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistdoctrine/sql-formatter1.5.46,162,51415200 days agosqlhighlight

Metrics by category

Vitality

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

49Weak · 21% of overall
How it's scored
18/36Push recencylast push 77 days ago
9/36Commit cadence13/52 weeks with commits
14.4/18Commit volume39 commits in the last year
0/10OpenSSF Scorecard: Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year39
human_commit_share0.75
days_since_last_push77
active_weeks_last_year13
How it's scored
27/27Ships releases15 releases published
16.2/36Release recencylatest release 200 days ago
12.6/27Release cadencea release every ~147.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count15
latest_release_tag1.5.4
releases_from_tagsno
days_since_latest_release200
mean_days_between_releases147.9
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?

75Good · 17% of overall
How it's scored
53.1/60Stars1,865 stars
12.1/25Forks29 forks
3.9/15Watchers6 watchers
Inputs used
forks29
stars1,865
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Monthly downloads6,162,514 downloads/month across packagist
12.6/20Registry dependents76 packages depend on it
Inputs used
packagesdoctrine/sql-formatter
dependents76
ecosystemspackagist
total_downloads193,034,981
monthly_downloads6,162,514
unverified_packages_excluded

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

79Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.5/22.5Commit distributiontop contributor authored 45% of commits
13.5/13.5Contributor breadth29 contributors
10/10OpenSSF Scorecard: Contributorsproject has 35 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled29
top_contributor_share0.446
How it's scored
30.2/42Issue resolution72% of issues closed
27/30PR acceptance133/148 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-ReviewFound 3/4 approved changesets -- score normalized to 7
Inputs used
merged_prs133
open_issues9
closed_issues23
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.719
closed_unmerged_prs15
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 backingorganization-owned
20/20Verified domain
18.3/25Owner reach346 followers of doctrine
25/25Track record77 public repos, account ~16 yr old
Inputs used
followers346
owner_typeOrganization
is_verifiedyes
owner_logindoctrine
public_repos77
account_age_days6,029
How it's scored
25/25Published & resolvable1 package(s) on packagist
26/35Publish recencylatest publish 200 days ago
20/20Version history15 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesdoctrine/sql-formatter
ecosystemspackagist
any_deprecatedno
min_days_since_publish200

Engineering Quality

Are baseline engineering and documentation practices in place?

57Moderate · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests18 out of 18 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

65Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests18 out of 18 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-ReviewFound 3/4 approved changesets -- score normalized to 7
2.5/2.5Contributorsproject has 35 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Branch-Protection, 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 advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages36
unassessed_packages5
affected_by_severityhigh 1
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 36 resolved dependencies against OSV. 5 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
31.3/40Legible commit history44 of 75 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.587
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
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance25 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.25
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeHTML without a type-check config
55/55Manageable file sizes0/12 source files over 60KB
Inputs used
primary_languageHTML
largest_source_bytes37,000
source_files_sampled12
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

1,865GitHub stars
29contributors
39commits, last 12 months
77days since last push
15releases
2bus factor
9open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 29 ⇿
0Stars
29Forks
15Releases

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.

0510152025302822020-032023-052026-07
Major 1Minor 5Patch 9

Each point covers 6 days.

OpenSSF Scorecard 5.6 / 10
5.6aggregate

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-27 17:29 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests18 out of 18 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 3/4 approved changesets -- score normalized to 7
10Contributorsproject has 35 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 41

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

RegistryPackageVersionRelation
Packagistamphp/amp2.6.1indirect
Packagistamphp/byte-stream1.8.1indirect
Packagistcomposer/package-versions-deprecated1.11.99.4indirect
Packagistcomposer/semver3.2.6indirect
Packagistcomposer/xdebug-handler2.0.2indirect
Packagistdealerdirect/phpcodesniffer-composer-installer0.7.1indirect
Packagistdnoegel/php-xdg-base-dir0.1.1indirect
Packagistdoctrine/coding-standardindirect
Packagistdoctrine/coding-standard9.0.0indirect
Packagistergebnis/phpunit-slow-test-detectorindirect
Packagistfelixfbecker/advanced-json-rpc3.2.1indirect
Packagistfelixfbecker/language-server-protocol1.5.1indirect
Packagistnetresearch/jsonmapper4.0.0indirect
Packagistnikic/php-parser4.13.1indirect
Packagistopenlss/lib-array2xml1.0.0indirect
Packagistphpindirect
Packagistphpdocumentor/reflection-common2.2.0indirect
Packagistphpdocumentor/reflection-docblock5.3.0indirect
Packagistphpdocumentor/type-resolver1.5.1indirect
Packagistphpstan/phpdoc-parser1.2.0indirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan1.0.2indirect
Packagistphpunit/phpunitindirect
Packagistpsr/container1.1.1indirect
Packagistpsr/log1.1.4indirect
Packagistsebastian/diff4.0.4indirect
Packagistslevomat/coding-standard7.0.16indirect
Packagistsquizlabs/php_codesniffer3.6.1indirect
Packagistsymfony/console5.3.10indirect
Packagistsymfony/deprecation-contracts2.4.0indirect
Packagistsymfony/polyfill-ctype1.23.0indirect
Packagistsymfony/polyfill-intl-grapheme1.23.1indirect
Packagistsymfony/polyfill-intl-normalizer1.23.0indirect
Packagistsymfony/polyfill-mbstring1.23.1indirect
Packagistsymfony/polyfill-php731.23.0indirect
Packagistsymfony/polyfill-php801.23.1indirect
Packagistsymfony/service-contracts2.4.0indirect
Packagistsymfony/string5.3.10indirect
Packagistvimeo/psalm4.11.2indirect
Packagistwebmozart/assert1.10.0indirect
Packagistwebmozart/path-util2.3.0indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
squizlabs/php_codesniffer3.6.1indirecthigh14.0.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 statisticsPackagist.