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

open-metadata / collate-sqlfluff

A modular SQL linter and auto-formatter with support for multiple dialects and templated code.

Python · SQLMIT★ 0 stars⑂ 1 forksince Mar 2025forkView on GitHub ↗
KindCommand-line toolPluginLibraryhow this is determined

open-metadata/collate-sqlfluff holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on AI Readiness (93/100) and lowest on Security (21/100). It was last updated 112 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

OpenMetadataOrganization
466 followers32 public repossince Jun 2021

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?

59Moderate · 21% of overall
How it's scored
9.9/36Push recency — last push 112 days ago
8.3/36Commit cadence — 12/52 weeks with commits
16.2/18Commit volume — 63 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year63
human_commit_share0.99
days_since_last_push112
active_weeks_last_year12
How it's scored
27/27Ships releases — 7 releases published
27/36Release recency — latest release 112 days ago
27/27Release cadence — a release every ~39.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tag3.5.3-release
releases_from_tagsno
days_since_latest_release112
mean_days_between_releases39.8

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

32At Risk · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/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_readmeno
has_licenseno
readme_badges10
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
73.8/80Monthly downloads — 344,957 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagescollate-sqlfluff
dependents—
ecosystemspypi
total_downloads—
monthly_downloads344,957
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?

78Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.2/22.5Commit distribution — top contributor authored 46% of commits
13.5/13.5Contributor breadth — 99 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.456
How it's scored
0/42Issue resolution — no issues or no data
27.3/30PR acceptance — 10/11 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs10
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
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): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
19.2/25Owner reach — 466 followers of open-metadata
21.5/25Track record — 32 public repos, account ~5 yr old
Inputs used
followers466
owner_typeOrganization
is_verifiedno
owner_loginopen-metadata
public_repos32
account_age_days1,916

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 112 days ago
20/20Version history — 11 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescollate-sqlfluff
ecosystemspypi
any_deprecatedno
min_days_since_publish112

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows — 11 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff]), tox.ini
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

50Moderate
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage site — https://www.sqlfluff.com
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://www.sqlfluff.com
docs_sitehttps://www.sqlfluff.com
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

21At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestsdocs/requirements.txt, pyproject.toml, requirements_dev.txt
has_codeql_workflowno
has_security_policyno
has_dependabot_configno

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_packages17
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 pypi:collate-sqlfluff@3.5.3 runtime dependency closure — what installing the published package pulls in — 17 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.

93Exceptional · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.databricks.com/llms.txt)
40/40Legible commit history — 83 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.databricks.com/llms.txt
legible_history_share0.838
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes4,470
How it's scored
18/18One-command bootstrap — Makefile, docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff]), tox.ini
11/11Static type checking — src/sqlfluff/py.typed
10/10Reproducible environment — Dockerfile
8/10Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile, docs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/sqlfluff/py.typed
agent_commit_share0.04
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (src/sqlfluff/py.typed)
52.9/55Manageable file sizes — 15/397 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes315,701
source_files_sampled397
oversized_source_files15
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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

0GitHub stars
99contributors
63commits, last 12 months
112days since last push
7releases
2bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Community profile unavailable
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Direct dependencies 13
RegistryPackageVersion constraintManifest
PyPIplatformdirs—pyproject.toml
PyPIchardet—pyproject.toml
PyPIclick<8.4.0pyproject.toml
PyPIcolorama>=0.3pyproject.toml
PyPIdiff-cover>=2.5.0pyproject.toml
PyPIJinja2—pyproject.toml
PyPIpathspec—pyproject.toml
PyPIpytest—pyproject.toml
PyPIpyyaml>=5.1pyproject.toml
PyPIregex—pyproject.toml
PyPItblib—pyproject.toml
PyPItomli—pyproject.toml
PyPItqdm—pyproject.toml
All dependencies 46

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

RegistryPackageVersionRelation
PyPIchardet—direct
PyPIclick—direct
PyPIcolorama—direct
PyPIdiff-cover—direct
PyPIjinja2—direct
PyPIpathspec—direct
PyPIplatformdirs—direct
PyPIpytest—direct
PyPIpyyaml—direct
PyPIregex—direct
PyPItblib—direct
PyPItomli—direct
PyPItqdm—direct
PyPIblack25.1.0indirect
PyPIcollate-sqlfluff—indirect
PyPIcoverage—indirect
PyPIdbt-core—indirect
PyPIdbt-postgres—indirect
PyPIdoc8—indirect
PyPIflake8—indirect
PyPIflake8-black—indirect
PyPIflake8-docstrings—indirect
PyPIghapi—indirect
PyPIhypothesis—indirect
PyPIimport-linter—indirect
PyPIjinja2-simple-tags—indirect
PyPImypy—indirect
PyPIpydocstyle—indirect
PyPIpygments—indirect
PyPIpytest-cov—indirect
PyPIpytest-xdist—indirect
PyPIrequests—indirect
PyPIruff—indirect
PyPIsetuptools—indirect
PyPIsphinx—indirect
PyPIsphinx-click—indirect
PyPIsphinx-reredirects—indirect
PyPIsqlfluff3.5.0indirect
PyPItox—indirect
PyPItypes-appdirs—indirect
PyPItypes-chardet—indirect
PyPItypes-colorama—indirect
PyPItypes-pyyaml—indirect
PyPItypes-regex—indirect
PyPItypes-tqdm—indirect
PyPIyamllint—indirect
Dependency advisories 0

Installing pypi:collate-sqlfluff@3.5.3 pulls in 17 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 — PyPI.