Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 09:04 UTC

supabase / supabase-swift

A Swift SDK for Supabase. Query your Supabase database, subscribe to realtime events, upload and download files, browse Swift examples, invoke postgres functions via rpc, invoke supabase edge functions, query pgvector.

SwiftMIT★ 1,302 stars⑂ 269 forkssince May 2021View on GitHub ↗

supabase/supabase-swift holds a health index of 94 out of 100, placing it in the Exceptional band. It scores highest on Vitality (96/100) and lowest on Security (70/100). It was last updated today. A single contributor accounts for most of its recent work.

94
overall / 100
Exceptional

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.

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

Ownership

SupabaseOrganization · verified domain
12,336 followers174 public repossince Aug 2019

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 0 days ago
29.1/36Commit cadence — 42/52 weeks with commits
18/18Commit volume — 528 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year528
human_commit_share0.98
days_since_last_push0
active_weeks_last_year42

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 6 days ago
27/27Release cadence — a release every ~10.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv2.55.4
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases10.7
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?

85Excellent · 17% of overall
How it's scored
50.5/60Stars — 1,302 stars
20.2/25Forks — 269 forks
8.4/15Watchers — 34 watchers
Inputs used
forks269
stars1,302
watchers34
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescoveralls.io, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

70Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.1/22.5Commit distribution — top contributor authored 73% of commits
13.5/13.5Contributor breadth — 47 contributors
10/10OpenSSF Scorecard: Contributors — project has 14 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled47
top_contributor_share0.73
How it's scored
40.7/42Issue resolution — 97% of issues closed
25.9/30PR acceptance — 1,051/1,218 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_prs1,051
open_issues9
closed_issues290
prs_merged_7d53
prs_decided_7d54
prs_merged_30d56
prs_decided_30d57
issue_closed_ratio0.97
closed_unmerged_prs167
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
25/25Owner reach — 12,336 followers of supabase
25/25Track record — 174 public repos, account ~7 yr old
Inputs used
followers12,336
owner_typeOrganization
is_verifiedyes
owner_loginsupabase
public_repos174
account_age_days2,613

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://supabase.com/docs/reference/swift
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicsios, supabase, swift, database
has_wikino
homepagehttps://supabase.com/docs/reference/swift
docs_sitehttps://supabase.com/docs/reference/swift
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
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 14 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 1 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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.2
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
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages108
unassessed_packages0
affected_by_severitymoderate 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 108 resolved dependencies against OSV. 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.

88Excellent · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md, AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://supabase.com/llms.txt)
40/40Legible commit history — 98 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://supabase.com/llms.txt
legible_history_share1
agent_instruction_files.github/copilot-instructions.md, AGENTS.md, CLAUDE.md
agent_instruction_max_bytes2,591
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Swift (statically typed)
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 14 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 2 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.14
toolchain_manifests—
dependency_bot_commit_share0.02
How it's scored
45/45Type-checkable code — Swift (statically typed)
54.6/55Manageable file sizes — 4/547 source files over 60KB
Inputs used
primary_languageSwift
largest_source_bytes135,859
source_files_sampled547
oversized_source_files4
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

1,302GitHub stars
47contributors
528commits, last 12 months
0days since last push
100releases
1bus factor
9open issues
—package ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 269 ⇿
0Stars
269Forks
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.

05010015020025030026552021-052024-022026-10
Major 0Minor 47Patch 53

Each point covers 5 days.

OpenSSF Scorecard 6.2 / 10
6.2aggregate

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-10-20 09:04 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 14 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 1 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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 108

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

RegistryPackageVersionRelation
npm@cspell/cspell-bundled-dicts10.0.1indirect
npm@cspell/cspell-json-reporter10.0.1indirect
npm@cspell/cspell-performance-monitor10.0.1indirect
npm@cspell/cspell-pipe10.0.1indirect
npm@cspell/cspell-resolver10.0.1indirect
npm@cspell/cspell-service-bus10.0.1indirect
npm@cspell/cspell-types10.0.1indirect
npm@cspell/cspell-worker10.0.1indirect
npm@cspell/dict-ada4.1.1indirect
npm@cspell/dict-al1.1.1indirect
npm@cspell/dict-aws4.0.17indirect
npm@cspell/dict-bash4.2.3indirect
npm@cspell/dict-companies3.2.11indirect
npm@cspell/dict-cpp7.0.2indirect
npm@cspell/dict-cryptocurrencies5.0.5indirect
npm@cspell/dict-csharp4.0.8indirect
npm@cspell/dict-css4.1.2indirect
npm@cspell/dict-dart2.3.2indirect
npm@cspell/dict-data-science2.0.14indirect
npm@cspell/dict-django4.1.6indirect
npm@cspell/dict-docker1.1.17indirect
npm@cspell/dict-dotnet5.0.13indirect
npm@cspell/dict-elixir4.0.8indirect
npm@cspell/dict-en-common-misspellings2.1.12indirect
npm@cspell/dict-en-gb-mit3.1.24indirect
npm@cspell/dict-en_us4.4.35indirect
npm@cspell/dict-filetypes3.0.18indirect
npm@cspell/dict-flutter1.1.1indirect
npm@cspell/dict-fonts4.0.6indirect
npm@cspell/dict-fsharp1.1.1indirect
npm@cspell/dict-fullstack3.2.9indirect
npm@cspell/dict-gaming-terms1.1.2indirect
npm@cspell/dict-git3.1.0indirect
npm@cspell/dict-golang6.0.26indirect
npm@cspell/dict-google1.0.9indirect
npm@cspell/dict-haskell4.0.6indirect
npm@cspell/dict-html4.0.15indirect
npm@cspell/dict-html-symbol-entities4.0.5indirect
npm@cspell/dict-java5.0.12indirect
npm@cspell/dict-julia1.1.1indirect
npm@cspell/dict-k8s1.0.12indirect
npm@cspell/dict-kotlin1.1.1indirect
npm@cspell/dict-latex5.1.0indirect
npm@cspell/dict-lorem-ipsum4.0.5indirect
npm@cspell/dict-lua4.0.8indirect
npm@cspell/dict-makefile1.0.5indirect
npm@cspell/dict-markdown2.0.17indirect
npm@cspell/dict-monkeyc1.0.12indirect
npm@cspell/dict-node5.0.9indirect
npm@cspell/dict-npm5.2.41indirect
npm@cspell/dict-php4.1.1indirect
npm@cspell/dict-powershell5.0.15indirect
npm@cspell/dict-public-licenses2.0.16indirect
npm@cspell/dict-python4.2.27indirect
npm@cspell/dict-r2.1.1indirect
npm@cspell/dict-ruby5.1.1indirect
npm@cspell/dict-rust4.1.2indirect
npm@cspell/dict-scala5.0.9indirect
npm@cspell/dict-shell1.2.0indirect
npm@cspell/dict-software-terms5.2.2indirect
npm@cspell/dict-sql2.2.1indirect
npm@cspell/dict-svelte1.0.7indirect
npm@cspell/dict-swift2.0.6indirect
npm@cspell/dict-terraform1.1.3indirect
npm@cspell/dict-typescript3.2.3indirect
npm@cspell/dict-vue3.0.5indirect
npm@cspell/dict-zig1.0.0indirect
npm@cspell/dynamic-import10.0.1indirect
npm@cspell/filetypes10.0.1indirect
npm@cspell/rpc10.0.1indirect
npm@cspell/strong-weak-map10.0.1indirect
npm@cspell/url10.0.1indirect
npmansi-regex6.2.2indirect
npmarray-timsort1.0.3indirect
npmchalk5.6.2indirect
npmchalk-template1.1.2indirect
npmcommander14.0.3indirect
npmcomment-json5.0.0indirect
npmcspell10.0.1indirect
npmcspell-config-lib10.0.1indirect
npmcspell-dictionary10.0.1indirect
npmcspell-gitignore10.0.1indirect
npmcspell-glob10.0.1indirect
npmcspell-grammar10.0.1indirect
npmcspell-io10.0.1indirect
npmcspell-lib10.0.1indirect
npmcspell-trie-lib10.0.1indirect
npmenv-paths4.0.0indirect
npmesprima4.0.1indirect
npmfast-equals6.0.0indirect
npmfast-json-stable-stringify2.1.0indirect
npmfdir6.5.0indirect
npmflatted3.4.2indirect
npmgensequence8.0.8indirect
npmglobal-directory5.0.0indirect
npmimport-fresh4.0.0indirect
npmimport-meta-resolve4.2.0indirect
npmini6.0.0indirect
npmis-safe-filename0.1.1indirect
npmpicomatch4.0.5indirect
npmresolve-from5.0.0indirect
npmsemver7.8.5indirect
npmsmol-toml1.8.0indirect
npmtinyglobby0.2.17indirect
npmvscode-languageserver-textdocument1.0.12indirect
npmvscode-uri3.1.0indirect
npmxdg-basedir5.1.0indirect
npmyaml2.9.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 108 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
smol-toml1.8.0indirectmoderate11.9.0

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.