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

turbopuffer / turbopuffer-python

Official Python API client library for turbopuffer

PythonMIT★ 168 stars⑂ 11 forkssince Dec 2023View on GitHub ↗

turbopuffer/turbopuffer-python holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on Security (65/100). It was last updated 5 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

turbopufferOrganization · verified domain
280 followers23 public repossince Nov 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIturbopuffer2.9.04,893,14013825 days ago

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 5 days ago
28.4/36Commit cadence41/52 weeks with commits
18/18Commit volume237 commits in the last year
10/10OpenSSF Scorecard: Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year237
human_commit_share0.24
days_since_last_push5
active_weeks_last_year41

Release discipline

100Exceptional
How it's scored
27/27Ships releases98 releases published
36/36Release recencylatest release 25 days ago
27/27Release cadencea release every ~9.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count98
latest_release_tagv2.9.0
releases_from_tagsno
days_since_latest_release25
mean_days_between_releases9.4
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?

68Good · 17% of overall
How it's scored
36.1/60Stars168 stars
8.3/25Forks11 forks
1.7/15Watchers3 watchers
Inputs used
forks11
stars168
watchers3
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_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads4,893,140 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesturbopuffer
dependents
ecosystemspypi
total_downloads
monthly_downloads4,893,140
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?

83Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
15.7/22.5Commit distributiontop contributor authored 30% of commits
13.5/13.5Contributor breadth14 contributors
10/10OpenSSF Scorecard: Contributorsproject has 13 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled14
top_contributor_share0.302
How it's scored
42/42Issue resolution100% of issues closed
25.7/30PR acceptance219/256 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs219
open_issues0
closed_issues3
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio1
closed_unmerged_prs37
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, OpenSSF Scorecard: Code-Review. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
17.6/25Owner reach280 followers of turbopuffer
15.7/25Track record23 public repos, account ~2 yr old
Inputs used
followers280
owner_typeOrganization
is_verifiedyes
owner_loginturbopuffer
public_repos23
account_age_days1,035

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 25 days ago
20/20Version history138 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesturbopuffer
ecosystemspypi
any_deprecatedno
min_days_since_publish25

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
16/16Linter configpyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests9 out of 9 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://turbopuffer.com
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://turbopuffer.com
docs_sitehttps://turbopuffer.com
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
6/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests9 out of 9 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
0/7.5Code-Reviewno data
2.5/2.5Contributorsproject has 13 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
4/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities30 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Code-Review, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages23
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:turbopuffer@2.9.0 runtime dependency closure — what installing the published package pulls in — 23 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.

71Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://turbopuffer.com/llms.txt)
40/40Legible commit history18 of 24 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://turbopuffer.com/llms.txt
legible_history_share0.75
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.ruff])
11/11Static type checkingsrc/turbopuffer/py.typed
10/10Reproducible environmentdevcontainer, Dockerfile, lockfile
6/10Demonstrated agent practice3 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
8/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock, uv.lock
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontaineryes
has_linter_configyes
typecheck_configssrc/turbopuffer/py.typed
agent_commit_share0.03
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codePython with type-check config (src/turbopuffer/py.typed)
53.9/55Manageable file sizes3/151 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes82,391
source_files_sampled151
oversized_source_files3
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

168GitHub stars
14contributors
237commits, last 12 months
5days since last push
98releases
2bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 11 ⇿
0Stars
11Forks
92Releases

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.

0246810121112024-012025-042026-07
Major 2Minor 28Patch 36

Each point covers 3 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-09-16 05:44 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests9 out of 9 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
n/aCode-ReviewFound no human activity in the last 9 changesets
10Contributorsproject has 13 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
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
0Vulnerabilities30 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
PyPIhttpx>=0.23.0, <1pyproject.toml
PyPIaiohttp>=3.10.11, <4pyproject.toml
PyPIpydantic>=1.9.0, <3pyproject.toml
PyPIpybase64>=1.4.1, <2pyproject.toml
PyPItyping-extensions>=4.13, <5pyproject.toml
PyPItyping-extensions>=4.14, <5pyproject.toml
PyPIanyio>=3.5.0, <5pyproject.toml
PyPIdistro>=1.7.0, <2pyproject.toml
PyPIsniffiopyproject.toml
PyPIorjson>=3.10.15, <4pyproject.toml
All dependencies 72

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

RegistryPackageVersionRelation
PyPIaiohttp3.13.3direct
PyPIanyio4.12.1direct
PyPIanyio4.5.2direct
PyPIdistro1.9.0direct
PyPIhttpx0.28.1direct
PyPIorjson3.11.5direct
PyPIorjson3.11.7direct
PyPIpybase641.4.3direct
PyPIpydantic1.10.26direct
PyPIpydantic2.10.6direct
PyPIpydantic2.12.5direct
PyPIsniffio1.3.1direct
PyPItyping-extensions4.13.2direct
PyPItyping-extensions4.15.0direct
PyPIaiohappyeyeballs2.6.1indirect
PyPIaiosignal1.4.0indirect
PyPIannotated-types0.7.0indirect
PyPIasync-timeout5.0.1indirect
PyPIattrs25.4.0indirect
PyPIbackports-asyncio-runner1.2.0indirect
PyPIcertifi2025.4.26indirect
PyPIcertifi2026.1.4indirect
PyPIcolorama0.4.6indirect
PyPIdirty-equals0.11indirect
PyPIexceptiongroup1.3.0indirect
PyPIexceptiongroup1.3.1indirect
PyPIexecnet2.1.2indirect
PyPIfrozenlist1.8.0indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpx-aiohttp0.1.12indirect
PyPIidna3.10indirect
PyPIidna3.11indirect
PyPIimportlib-metadata8.7.1indirect
PyPIiniconfig2.1.0indirect
PyPIiniconfig2.3.0indirect
PyPImarkdown-it-py3.0.0indirect
PyPImarkdown-it-py4.0.0indirect
PyPImdurl0.1.2indirect
PyPImultidict6.7.0indirect
PyPImypy1.17.0indirect
PyPImypy-extensions1.1.0indirect
PyPInodeenv1.10.0indirect
PyPInumpy2.0.2indirect
PyPInumpy2.2.6indirect
PyPInumpy2.4.3indirect
PyPIpackaging25.0indirect
PyPIpathspec1.0.3indirect
PyPIpluggy1.6.0indirect
PyPIpropcache0.4.1indirect
PyPIpydantic-core2.27.2indirect
PyPIpydantic-core2.41.5indirect
PyPIpygments2.19.2indirect
PyPIpyright1.1.399indirect
PyPIpytest8.4.2indirect
PyPIpytest9.0.2indirect
PyPIpytest-asyncio1.2.0indirect
PyPIpytest-asyncio1.3.0indirect
PyPIpytest-xdist3.8.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIrespx0.22.0indirect
PyPIrich14.2.0indirect
PyPIruff0.14.13indirect
PyPIsix1.17.0indirect
PyPItime-machine2.19.0indirect
PyPItime-machine3.2.0indirect
PyPItomli2.4.0indirect
PyPIturbopuffer2.6.0indirect
PyPItyping-inspection0.4.2indirect
PyPIurllib32.6.3indirect
PyPIyarl1.22.0indirect
PyPIzipp3.23.0indirect
Dependency advisories 0

Installing pypi:turbopuffer@2.9.0 pulls in 23 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 statisticsPyPI.