Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 12:48 UTC

SQLAnvil / sqlanvil

Analytics engineering for Postgres & Supabase — Dataform-style SQL workflows (SQLX, refs, assertions, incremental tables, materialized views), with first-class BigQuery and MySQL/MariaDB support.

TypeScriptApache-2.0★ 1 star⑂ 0 forkssince May 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

SQLAnvil/sqlanvil holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (96/100) and lowest on Community & Adoption (33/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

SQLAnvilOrganization · verified domain
0 followers7 public repossince May 2026

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

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 506 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year506
human_commit_share0.96
days_since_last_push2
active_weeks_last_year43

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 54 releases published
36/36Release recency — latest release 2 days ago
27/27Release cadence — a release every ~4.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count54
latest_release_tagv1.32.5
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases4.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?

33At Risk · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
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

Sustainability & Governance

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

57Moderate · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15.5/22.5Commit distribution — top contributor authored 31% of commits
13.5/13.5Contributor breadth — 68 contributors
10/10OpenSSF Scorecard: Contributors — project has 13 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled68
top_contributor_share0.311
How it's scored
30.7/42Issue resolution — 73% of issues closed
13/30PR acceptance — 10/23 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs10
open_issues10
closed_issues27
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.73
closed_unmerged_prs13
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
20/20Verified domain
0/25Owner reach — 0 followers of SQLAnvil
7.2/25Track record — 7 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedyes
owner_loginSQLAnvil
public_repos7
account_age_days105

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://sqlanvil.com/docs
10/10Repository description
10/10Topics — 12 topics
10/10Wiki
Inputs used
topicsanalytics-engineering, bigquery, cli, data-transformation, dataform, dbt-alternative, elt, postgres, sql, supabase, mariadb, mysql
has_wikiyes
homepagehttps://sqlanvil.com/docs
docs_sitehttps://sqlanvil.com/docs
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

44Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 13 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 28 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 — no SAST tool detected
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 — 56 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): CI-Tests, 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.

89Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md, GEMINI.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://sqlanvil.com/llms.txt)
40/40Legible commit history — 91 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://sqlanvil.com/llms.txt
legible_history_share0.948
agent_instruction_filesAGENTS.md, CLAUDE.md, GEMINI.md
agent_instruction_max_bytes25,759
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc.js
11/11Static type checking — tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 64 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 4 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json, yarn.lock
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.64
toolchain_manifests—
dependency_bot_commit_share0.04
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.6/55Manageable file sizes — 2/250 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes103,277
source_files_sampled250
oversized_source_files2
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — protos/configs.proto, protos/core.proto, protos/db_adapter.proto, protos/evaluation.proto, protos/execution.proto, protos/extension.proto, protos/jit.proto, protos/profiles.proto
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples, notebooks
Inputs used
example_dirsexamples, notebooks
has_mcp_signalno
api_schema_filesprotos/configs.proto, protos/core.proto, protos/db_adapter.proto, protos/evaluation.proto, protos/execution.proto, protos/extension.proto, protos/jit.proto, protos/profiles.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

1GitHub stars
68contributors
506commits, last 12 months
2days since last push
54releases
2bus factor
10open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-06-19: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 1 stars today.
  • Could not fetch npm package 'sqlanvil' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-12 12:48 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 13 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 28 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
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities56 existing vulnerabilities detected
Direct dependencies 96
RegistryPackageVersion constraintManifest
npm@bazel/hide-bazel-files1.0.0package.json
npm@bazel/ibazel^0.9.1package.json
npm@bazel/labs^0.42.3package.json
npm@bazel/rollup^3.0.0package.json
npm@bazel/typescript^3.0.0package.json
npm@google-cloud/bigquery~8.3.0package.json
npm@google-cloud/storage^7.19.0package.json
npmgoogle-auth-library^9.15.1package.json
npm@rollup/plugin-node-resolve^7.1.3package.json
npm@types/chai^4.1.7package.json
npm@types/diff^4.0.2package.json
npm@types/es6-shim^0.31.37package.json
npm@types/fs-extra^8.1.0package.json
npm@types/glob^8.1.0package.json
npm@types/js-beautify^1.8.1package.json
npm@types/js-yaml^4.0.5package.json
npm@types/json-stable-stringify^1.0.32package.json
npm@types/long^4.0.0package.json
npm@types/moo^0.5.0package.json
npm@types/node^16.16.0package.json
npm@types/pg^8.11.0package.json
npm@types/readline-sync^1.4.3package.json
npm@types/request^2.48.3package.json
npm@types/rimraf^2.0.2package.json
npm@types/semver^7.3.13package.json
npm@types/tmp^0.2.0package.json
npm@types/uuid^9.0.0package.json
npm@types/vscode^1.45.1package.json
npm@types/yargs^15.0.5package.json
npm@typescript-eslint/parser^5.62.0package.json
npmchai^4.2.0package.json
npmchalk^4.0.0package.json
npmchokidar^3.5.3package.json
npmdeepmerge^4.2.2package.json
npmdiff^8.0.3package.json
npm@duckdb/node-api^1.5.4-r.1package.json
npmescodegen^1.13.0package.json
npmeslint^8.57.0package.json
npmespree^7.0.0package.json
npmestraverse^5.1.0package.json
npmfs-extra^9.0.0package.json
npmglob13.0.6package.json
npmgoogle-sql-syntax-ts^1.0.3package.json
npmjs-beautify^1.10.2package.json
npmjs-yaml^4.2.0package.json
npmjsdoc^3.6.11package.json
npmjson-stable-stringify^1.0.1package.json
npmlong^4.0.0package.json
npmminimist^1.2.6package.json
npmmoo^0.5.0package.json
npmmysql2^3.11.0package.json
npmobject-sizeof^1.6.1package.json
npmparse-duration^1.0.0package.json
npmpg^8.11.3package.json
npmpg-query-stream^4.5.3package.json
npmprettier^1.14.2package.json
npmpromise-pool-executor^1.1.1package.json
npmprotobufjs^7.6.5package.json
npmprotobufjs-cli^1.3.3package.json
npmreadline-sync^1.4.9package.json
npmrequest^2.88.0package.json
npmrimraf^2.6.2package.json
npmrollup^2.80.0package.json
npmrollup-plugin-dts^1.4.0package.json
npmsemver^7.5.2package.json
npmsource-map-support^0.5.21package.json
npmtarjan-graph^2.0.0package.json
npmtmp^0.2.7package.json
npmts-loader^5.3.1package.json
npmts-mockito^2.6.1package.json
npmtslint^5.14.0package.json
npmtslint-config-prettier^1.18.0package.json
npmtslint-config-security^1.16.0package.json
npmtypedoc0.17.8package.json
npmtypedoc-plugin-markdown2.2.17package.json
npmtypeid-js0.3.0package.json
npmtypescript^3.8.3package.json
npmuglify-es^3.3.9package.json
npmuglify-js^3.7.7package.json
npmuntildify^4.0.0package.json
npmurl^0.11.0package.json
npmuuid^9.0.0package.json
npmvm23.11.6package.json
npmvsce^1.79.5package.json
npmvscode-jsonrpc^5.0.1package.json
npmvscode-languageclient^6.1.3package.json
npmvscode-languageserver^6.1.1package.json
npmvscode-languageserver-protocol^3.15.3package.json
npmvscode-languageserver-textdocument^1.0.1package.json
npmvscode-languageserver-types3.15.1package.json
npmwebpack5.104.1package.json
npmwebpack-cli4.10.0package.json
npmyargs^16.2.0package.json
npmvscode-languageclient^6.1.3vscode/package.json
npmvscode-languageserver^6.1.1vscode/package.json
npmvscode-languageserver-textdocument^1.0.1vscode/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.