Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 18:26 UTC

GenericMappingTools / pygmt

A Python interface for the Generic Mapping Tools.

PythonBSD-3-Clause★ 874 stars⑂ 255 forkssince Mar 2017View on GitHub ↗
KindLibraryPluginhow this is determined

GenericMappingTools/pygmt holds a health index of 94 out of 100, placing it in the Exceptional band. It scores highest on Vitality (93/100) and lowest on AI Readiness (61/100). It was last updated today. 2 contributors account 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

378 followers51 public repossince Feb 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIpygmt0.19.08,5652869 days agocartographygeodesygeologygeophysicsgeospatialoceanographyseismology

Metrics by category

Vitality

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

93Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recency — last push 0 days ago
36/36Commit cadence — 52/52 weeks with commits
18/18Commit volume — 598 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year598
human_commit_share0.9
days_since_last_push0
active_weeks_last_year52
How it's scored
27/27Ships releases — 27 releases published
36/36Release recency — latest release 69 days ago
19.8/27Release cadence — a release every ~88.6 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count27
latest_release_tagv0.19.0
releases_from_tagsno
days_since_latest_release69
mean_days_between_releases88.6

Community & Adoption

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

79Good · 17% of overall
How it's scored
47.7/60Stars — 874 stars
20/25Forks — 255 forks
7.7/15Watchers — 25 watchers
Inputs used
forks255
stars874
watchers25
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 (BSD-3-Clause)
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_badges10
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateyes
How it's scored
52.4/80Monthly downloads — 8,565 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespygmt
dependents—
ecosystemspypi
total_downloads—
monthly_downloads8,565
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?

76Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.4/22.5Commit distribution — top contributor authored 49% of commits
13.5/13.5Contributor breadth — 54 contributors
10/10OpenSSF Scorecard: Contributors — project has 42 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled54
top_contributor_share0.494
How it's scored
37.5/42Issue resolution — 89% of issues closed
28.4/30PR acceptance — 3,430/3,628 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 11/28 approved changesets -- score normalized to 3
Inputs used
merged_prs3,430
open_issues128
closed_issues1,056
prs_merged_7d5
prs_decided_7d5
prs_merged_30d35
prs_decided_30d37
issue_closed_ratio0.892
closed_unmerged_prs198
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
0/20Verified domain
18.5/25Owner reach — 378 followers of GenericMappingTools
24.5/25Track record — 51 public repos, account ~9 yr old
Inputs used
followers378
owner_typeOrganization
is_verifiedno
owner_loginGenericMappingTools
public_repos51
account_age_days3,491

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 69 days ago
20/20Version history — 28 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespygmt
ecosystemspypi
any_deprecatedno
min_days_since_publish69

Engineering Quality

Are baseline engineering and documentation practices in place?

92Excellent · 19% of overall
How it's scored
24/24CI workflows — 16 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/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_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://www.pygmt.org
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicspython, geoscience, earth-science, geophysics, maps, seismology, hacktoberfest
has_wikino
homepagehttps://www.pygmt.org
docs_sitehttps://www.pygmt.org
has_readmeyes
has_docs_diryes
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-Artifacts — no binaries found in the repo
6/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
2.2/7.5Code-Review — Found 11/28 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 42 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 19 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
3/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
5/5SAST — SAST tool is run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate6.5

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.

61Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
29/40Legible commit history — 49 of 90 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.544
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile, doc/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
0/10Reproducible environment
8/10Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 10 of the last 100 commits are automated dependency updates
6/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesMakefile, doc/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.04
toolchain_manifests—
dependency_bot_commit_share0.1
How it's scored
0/45Type-checkable code — Python without a type-check config
54.9/55Manageable file sizes — 1/386 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes93,142
source_files_sampled386
oversized_source_files1
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

874GitHub stars
54contributors
598commits, last 12 months
0days since last push
27releases
2bus factor
128open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • OSV advisory lookup failed: [Errno 101] Network is unreachable

More detail

Star and fork history 0 ★ / 255 ⇿
0Stars
255Forks
27Releases

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.

05010015020025024882017-062022-012026-09
Major 0Minor 19Patch 8

Each point covers 9 days.

OpenSSF Scorecard 6.5 / 10
6.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-09-14 18:25 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-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
3Code-ReviewFound 11/28 approved changesets -- score normalized to 3
10Contributorsproject has 42 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 19 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
6Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
10SASTSAST tool is run on all commits
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
PyPInumpy>=2.2pyproject.toml
PyPIpandas>=2.3pyproject.toml
PyPIxarray>=2024.10pyproject.toml
PyPIpackaging>=24.2pyproject.toml
All dependencies 9

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

RegistryPackageVersionRelation
PyPInumpy—direct
PyPIpackaging—direct
PyPIpandas—direct
PyPIxarray—direct
PyPIcontextily—indirect
PyPIgeopandas—indirect
PyPIpyarrow—indirect
PyPIsetuptools—indirect
PyPIsetuptools-scm—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: OSV advisory lookup failed: [Errno 101] Network is unreachable

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 — PyPI.