Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-07 11:42 UTC

burnash / gspread

Google Sheets Python API

PythonMIT★ 7,492 stars⑂ 979 forkssince Dec 2011View on GitHub ↗

burnash/gspread holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (94/100) and lowest on AI Readiness (46/100). It was last updated 8 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

Anton BurnashevPersonal account
402 followers40 public repossince May 2010

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIgspread6.2.145,076,00783449 days agospreadsheetsgoogle-spreadsheetsgoogle-sheets

Metrics by category

Vitality

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

60Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 8 days ago
10.4/36Commit cadence15/52 weeks with commits
14.9/18Commit volume45 commits in the last year
10/10OpenSSF Scorecard: Maintained22 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year45
human_commit_share1
days_since_last_push8
active_weeks_last_year15
How it's scored
27/27Ships releases66 releases published
7.2/36Release recencylatest release 449 days ago
19.8/27Release cadencea release every ~51.5 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count66
latest_release_tagv6.2.1
releases_from_tagsno
days_since_latest_release449
mean_days_between_releases51.5

Community & Adoption

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

94Exceptional · 17% of overall
How it's scored
60/60Stars7,492 stars
24.9/25Forks979 forks
12.1/15Watchers154 watchers
Inputs used
forks979
stars7,492
watchers154
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges7
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads45,076,007 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesgspread
dependents
ecosystemspypi
total_downloads
monthly_downloads45,076,007
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?

72Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
15.5/22.5Commit distributiontop contributor authored 31% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 45 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.313
How it's scored
39.8/42Issue resolution95% of issues closed
22.9/30PR acceptance477/626 decided PRs merged
10.8/13Newcomer PR acceptance5/6 first-time contributors' PRs merged in 30d
10.5/15OpenSSF Scorecard: Code-ReviewFound 8/11 approved changesets -- score normalized to 7
Inputs used
merged_prs477
open_issues49
closed_issues899
prs_merged_7d0
prs_decided_7d1
prs_merged_30d5
prs_decided_30d6
issue_closed_ratio0.948
closed_unmerged_prs149
first_time_authors_30d4
first_time_prs_merged_30d5
first_time_prs_decided_30d6
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
18.7/25Owner reach402 followers of burnash
23.7/25Track record40 public repos, account ~16 yr old
Inputs used
followers402
owner_typeUser
is_verified
owner_loginburnash
public_repos40
account_age_days5,938
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on pypi
14/35Publish recencylatest publish 449 days ago
20/20Version history83 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgspread
ecosystemspypi
any_deprecatedno
min_days_since_publish449

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configtox.ini
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests11 out of 11 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

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://docs.gspread.org
10/10Repository description
10/10Topics6 topics
10/10Wiki
Inputs used
topicsgspread, google-sheets, google-sheets-api-v4, google-sheets-api, spreadsheets, spreadsheet
has_wikiyes
homepagehttps://docs.gspread.org
docs_sitehttps://docs.gspread.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

56Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests11 out of 11 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 8/11 approved changesets -- score normalized to 7
2.5/2.5Contributorsproject has 45 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained22 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities12 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.5
Excluded from scoring (no data or not applicable): Packaging. 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_packages14
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:gspread@6.2.1 runtime dependency closure — what installing the published package pulls in — 14 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
21.9/40Legible commit history41 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.41
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configtox.ini
11/11Static type checkinggspread/py.typed
0/10Reproducible environment
4/10Demonstrated agent practice2 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsgspread/py.typed
agent_commit_share0.02
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codePython with type-check config (gspread/py.typed)
49.2/55Manageable file sizes2/19 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes134,943
source_files_sampled19
oversized_source_files2

Key facts

7,492GitHub stars
99contributors
45commits, last 12 months
8days since last push
66releases
2bus factor
49open 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 ★ / 979 ⇿
0Stars
979Forks
66Releases

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.

02004006008001,000959102012-012019-042026-07
Major 5Minor 25Patch 35

Each point covers 14 days.

OpenSSF Scorecard 4.5 / 10
4.5aggregate

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-07 11:41 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests11 out of 11 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 8/11 approved changesets -- score normalized to 7
10Contributorsproject has 45 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained22 commit(s) and 7 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
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities12 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
PyPIgoogle-auth>=1.12.0pyproject.toml
PyPIgoogle-auth-oauthlib>=0.4.1pyproject.toml
All dependencies 19

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

RegistryPackageVersionRelation
PyPIgoogle-authdirect
PyPIgoogle-auth1.12.0direct
PyPIgoogle-auth-oauthlibdirect
PyPIgoogle-auth-oauthlib0.4.1direct
PyPIbandit1.7.10indirect
PyPIblack24.8.0indirect
PyPIcodespell2.2.5indirect
PyPIflake87.1.1indirect
PyPIisort5.12.0indirect
PyPImypy1.11.2indirect
PyPImypy-extensions1.0.0indirect
PyPIpytestindirect
PyPIpytest-vcrindirect
PyPIsphinx6.2.1indirect
PyPIsphinx-rtd-themeindirect
PyPIsphinx-toolboxindirect
PyPItyping-extensions4.12.2indirect
PyPIurllib31.26.15indirect
PyPIvcrpyindirect
Dependency advisories 0

Installing pypi:gspread@6.2.1 pulls in 14 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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.