Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-15 11:23 UTC

overturemaps / overturemaps-py

Overture's Python CLI

Python · Jupyter NotebookMIT★ 255 stars⑂ 44 forkssince Apr 2024View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

overturemaps/overturemaps-py holds a health index of 91 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (86/100) and lowest on AI Readiness (52/100). It was last updated today. 3 contributors account for most of its recent work.

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

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

Ownership

Overture MapsOrganization
975 followers21 public repossince Dec 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIoverturemaps1.0.169,1982114 days agogisgeojsongeospatialmappingmapsopendataovertureparquetshapely

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
18.7/36Commit cadence27/52 weeks with commits
18/18Commit volume183 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year183
human_commit_share
days_since_last_push0
active_weeks_last_year27
How it's scored
27/27Ships releases5 releases published
36/36Release recencylatest release 14 days ago
19.8/27Release cadencea release every ~50.9 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count5
latest_release_tagv1.0.1
releases_from_tagsno
days_since_latest_release14
mean_days_between_releases50.9

Community & Adoption

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

75Good · 17% of overall
How it's scored
39/60Stars255 stars
13.6/25Forks44 forks
10/15Watchers64 watchers
Inputs used
forks44
stars255
watchers64
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_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
64.5/80Monthly downloads69,198 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesoverturemaps
dependents
ecosystemspypi
total_downloads
monthly_downloads69,198
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?

86Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
14.8/22.5Commit distributiontop contributor authored 34% of commits
13.5/13.5Contributor breadth23 contributors
10/10OpenSSF Scorecard: Contributorsproject has 11 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled23
top_contributor_share0.343
How it's scored
39.4/42Issue resolution94% of issues closed
24.9/30PR acceptance68/82 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 4/5 approved changesets -- score normalized to 8
Inputs used
merged_prs68
open_issues3
closed_issues45
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.938
closed_unmerged_prs14
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
21.5/25Owner reach975 followers of OvertureMaps
16.9/25Track record21 public repos, account ~3 yr old
Inputs used
followers975
owner_typeOrganization
is_verified
owner_loginOvertureMaps
public_repos21
account_age_days1,307
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://pypi.org/project/overturemaps/
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicscli, geospatial-analysis, maps, overture-maps
has_wikiyes
homepagehttps://pypi.org/project/overturemaps/
docs_sitehttps://pypi.org/project/overturemaps/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

72Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests10 out of 10 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
6/7.5Code-ReviewFound 4/5 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 11 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.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
5/5Pinned-Dependenciesall dependencies are pinned
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
3.8/7.5Vulnerabilities5 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate7.2

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.

52Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapjustfile
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesjustfile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePython without a type-check config
55/55Manageable file sizes0/24 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes19,020
source_files_sampled24
oversized_source_files0
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, notebooks
Inputs used
example_dirsexamples, notebooks
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

255GitHub stars
23contributors
183commits, last 12 months
0days since last push
5releases
3bus factor
3open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 7.2 / 10
7.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-07-15 11:22 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 4/5 approved changesets -- score normalized to 8
10Contributorsproject has 11 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 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
5Vulnerabilities5 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
PyPIclick>=8.3.0pyproject.toml
PyPIcolorama>=0.4.6pyproject.toml
PyPIorjson>=3.9.0pyproject.toml
PyPIpyfiglet>=1.0.2pyproject.toml
PyPIpyarrow>=15.0.2pyproject.toml
PyPIshapely>=2.1.0pyproject.toml
PyPInumpy>=1.26.4pyproject.toml
PyPItqdm>=4.67.3pyproject.toml
All dependencies 38

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

RegistryPackageVersionRelation
PyPIclick8.3.1direct
PyPIcolorama0.4.6direct
PyPInumpy2.2.6direct
PyPInumpy2.4.1direct
PyPIorjson3.11.7direct
PyPIpyarrow22.0.0direct
PyPIpyfiglet1.0.4direct
PyPIshapely2.1.2direct
PyPItqdm4.67.3direct
PyPIaltgraph0.17.5indirect
PyPIcertifi2026.1.4indirect
PyPIexceptiongroup1.3.1indirect
PyPIgeopandas1.1.2indirect
PyPIiniconfig2.3.0indirect
PyPImacholib1.16.4indirect
PyPIoverturemaps0.20.0indirect
PyPIpackaging25.0indirect
PyPIpandas2.3.3indirect
PyPIpefile2024.8.26indirect
PyPIpluggy1.6.0indirect
PyPIpy-cpuinfo9.0.0indirect
PyPIpygments2.19.2indirect
PyPIpyinstaller6.20.0indirect
PyPIpyinstaller-hooks-contrib2026.4indirect
PyPIpyogrio0.12.1indirect
PyPIpyproj3.7.2indirect
PyPIpyproj3.7.1indirect
PyPIpytest9.0.2indirect
PyPIpytest-benchmark5.2.3indirect
PyPIpytest-mock3.15.1indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpytz2025.2indirect
PyPIpywin32-ctypes0.2.3indirect
PyPIsetuptools82.0.1indirect
PyPIsix1.17.0indirect
PyPItomli2.4.0indirect
PyPItyping-extensions4.15.0indirect
PyPItzdata2025.3indirect
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.11.0 — full methodology · metrics wiki.

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