Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-19 05:21 UTC

georust / geo

Rust geospatial primitives & algorithms

RustCustom license★ 1,969 stars⑂ 279 forkssince Jan 2015View on GitHub ↗

georust/geo holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (88/100) and lowest on Engineering Quality (52/100). It was last updated 4 days ago. 3 contributors account for most of its recent work.

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

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

Ownership

GeoRustOrganization · verified domain
942 followers38 public repossince Dec 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iogeo0.33.11,854,15492212 days agogeogeographygeospatialgis
crates.iogeo-types0.7.202,460,53835108 days agogeogeographygeospatialgis
crates.iogeo-traits0.3.0730,5765559 days agogeogeographygeospatialgis

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
24.2/36Commit cadence — 35/52 weeks with commits
18/18Commit volume — 112 commits in the last year
10/10OpenSSF Scorecard: Maintained — 17 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year112
human_commit_share0.99
days_since_last_push4
active_weeks_last_year35
How it's scored
16.2/27Ships releases — 3 version tags (no GitHub releases)
0/36Release recency — latest release 1,337 days ago
5.4/27Release cadence — a release every ~744.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tag0.24.1
releases_from_tagsyes
days_since_latest_release1,337
mean_days_between_releases744.8
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?

88Excellent · 17% of overall
How it's scored
53.4/60Stars — 1,969 stars
20.4/25Forks — 279 forks
8.6/15Watchers — 36 watchers
Inputs used
forks279
stars1,969
watchers36
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
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_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 5,045,268 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesgeo, geo-types, geo-traits
dependents—
ecosystemscrates
total_downloads63,822,902
monthly_downloads5,045,268
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?

87Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
17/22.5Commit distribution — top contributor authored 24% of commits
13.5/13.5Contributor breadth — 97 contributors
10/10OpenSSF Scorecard: Contributors — project has 73 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled97
top_contributor_share0.243
How it's scored
33.1/42Issue resolution — 79% of issues closed
25.2/30PR acceptance — 911/1,085 decided PRs merged
8.7/13Newcomer PR acceptance — 4/6 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs911
open_issues105
closed_issues389
prs_merged_7d7
prs_decided_7d8
prs_merged_30d13
prs_decided_30d17
issue_closed_ratio0.787
closed_unmerged_prs174
first_time_authors_30d5
first_time_prs_merged_30d4
first_time_prs_decided_30d6
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
21.4/25Owner reach — 942 followers of georust
23.6/25Track record — 38 public repos, account ~11 yr old
Inputs used
followers942
owner_typeOrganization
is_verifiedyes
owner_logingeorust
public_repos38
account_age_days4,345

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 3 package(s) on crates
35/35Publish recency — latest publish 108 days ago
20/20Version history — 92 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgeo, geo-types, geo-traits
ecosystemscrates
any_deprecatedno
min_days_since_publish108

Engineering Quality

Are baseline engineering and documentation practices in place?

52Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
0/24Tests present
0/16Linter config
0/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_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://crates.io/crates/geo
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicsrust, geospatial, geography, geometry, gis
has_wikino
homepagehttps://crates.io/crates/geo
docs_sitehttps://crates.io/crates/geo
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-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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 73 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
5/5Fuzzing — project is fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 17 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.1
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
7.5/25Indirect dependencies free of known advisories — 4 affected: tar 0.4.40 (high 8.1), atty 0.2.14 (low), humantime 1.3.0 (unknown), +1 more
32.6/40No advisories left outstanding — 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,963 days ago
Inputs used
sourceosv
advisories10
affected_packages4
assessed_packages73
unassessed_packages0
affected_by_severityhigh 1, low 1, unknown 2
direct_affected_packages0
Matched the crates:geo@0.33.1 runtime dependency closure — what installing the published package pulls in — 73 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.

72Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 86 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.869
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes2,573
How it's scored
12.6/18One-command bootstrap — Cargo.toml, geo-benches/Cargo.toml, geo-test-fixtures/Cargo.toml (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
10/10Demonstrated agent practice — 8 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.08
toolchain_manifestsCargo.toml, geo-benches/Cargo.toml, geo-test-fixtures/Cargo.toml, geo-traits/Cargo.toml, geo-types/Cargo.toml, geo/Cargo.toml, geo/fuzz/Cargo.toml, jts-test-runner/Cargo.toml
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable code — Rust (statically typed)
54.7/55Manageable file sizes — 2/322 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes79,016
source_files_sampled322
oversized_source_files2
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,969GitHub stars
97contributors
112commits, last 12 months
4days since last push
3releases
3bus factor
105open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'geo-benches' from its registry
  • Could not fetch crates package 'jts-test-runner' from its registry
  • Could not fetch crates package 'geo-test-fixtures' from its registry

More detail

Star and fork history 0 ★ / 279 ⇿
0Stars
279Forks
3Releases

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.

05010015020025030027552015-102021-052026-11
Major 0Minor 0Patch 3

Each point covers 11 days.

OpenSSF Scorecard 7.1 / 10
7.1aggregate

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-11-19 05:21 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
10Code-Reviewall changesets reviewed
10Contributorsproject has 73 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
9Licenselicense file detected
10Maintained17 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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 63
RegistryPackageVersion constraintManifest
crates.ioanyhow1.0.57geo-benches/Cargo.toml
crates.ioapprox>= 0.4.0, < 0.6.0geo-benches/Cargo.toml
crates.iocriterion0.4geo-benches/Cargo.toml
crates.iogeo—geo-benches/Cargo.toml
crates.iogeo-booleanop0.3.2geo-benches/Cargo.toml
crates.iogeo-test-fixtures—geo-benches/Cargo.toml
crates.iogeo-types—geo-benches/Cargo.toml
crates.iogeojson0.24.0geo-benches/Cargo.toml
crates.ioglob0.3.0geo-benches/Cargo.toml
crates.iogt_prev0.6.2geo-benches/Cargo.toml
crates.iojts-test-runner—geo-benches/Cargo.toml
crates.iolog0.4.11geo-benches/Cargo.toml
crates.ionum-traits0.2geo-benches/Cargo.toml
crates.iopretty_env_logger0.4geo-benches/Cargo.toml
crates.iorand0.10.0geo-benches/Cargo.toml
crates.iorand_distr0.6.0geo-benches/Cargo.toml
crates.iorstar0.14.0geo-benches/Cargo.toml
crates.ioserde1.0.137geo-benches/Cargo.toml
crates.ioserde_derive1.0.137geo-benches/Cargo.toml
crates.ioserde_json1.0.81geo-benches/Cargo.toml
crates.iowkt0.14.0geo-benches/Cargo.toml
crates.iowkt0.14.0geo-test-fixtures/Cargo.toml
crates.iogeo-types—geo-test-fixtures/Cargo.toml
crates.iogeo—geo-test-fixtures/Cargo.toml
crates.iogeo-types0.7.17geo-traits/Cargo.toml
crates.iorayon1.10.0geo-types/Cargo.toml
crates.ioapprox>= 0.4.0, < 0.6.0geo-types/Cargo.toml
crates.ioarbitrary1.2.0geo-types/Cargo.toml
crates.ionum-traits0.2geo-types/Cargo.toml
crates.iorstar_0_80.8geo-types/Cargo.toml
crates.iorstar_0_90.9geo-types/Cargo.toml
crates.iorstar_0_100.10geo-types/Cargo.toml
crates.iorstar_0_110.11geo-types/Cargo.toml
crates.iorstar_0_120.12geo-types/Cargo.toml
crates.iorstar_0_130.13geo-types/Cargo.toml
crates.iorstar_0_140.14geo-types/Cargo.toml
crates.ioserde1geo-types/Cargo.toml
crates.iospade_22geo-types/Cargo.toml
crates.iothiserror2.0.19geo-types/Cargo.toml
crates.ioearcut0.4.11geo/Cargo.toml
crates.iospade2.10.0geo/Cargo.toml
crates.iofloat_next_after2.0.0geo/Cargo.toml
crates.iogeo-types0.7.19geo/Cargo.toml
crates.iogeographiclib-rs0.2.3geo/Cargo.toml
crates.iolog0.4.11geo/Cargo.toml
crates.ionum-traits0.2geo/Cargo.toml
crates.ioproj0.31.0geo/Cargo.toml
crates.iorobust1.1.0geo/Cargo.toml
crates.iorstar0.14.0geo/Cargo.toml
crates.ioserde1.0geo/Cargo.toml
crates.iothiserror2.0.19geo/Cargo.toml
crates.ioi_overlay4.5.1, < 4.6.0geo/Cargo.toml
crates.iosif-itree0.4.0geo/Cargo.toml
crates.iorand0.10.0geo/Cargo.toml
crates.iorand_pcg0.10.1geo/Cargo.toml
crates.ioapprox>= 0.4.0, < 0.6.0jts-test-runner/Cargo.toml
crates.iogeo—jts-test-runner/Cargo.toml
crates.ioinclude_dir0.7.2jts-test-runner/Cargo.toml
crates.iolog0.4.14jts-test-runner/Cargo.toml
crates.ioserde1.0.105jts-test-runner/Cargo.toml
crates.ioserde-xml-rs0.6.0jts-test-runner/Cargo.toml
crates.iothiserror2.0.19jts-test-runner/Cargo.toml
crates.iowkt0.14.0jts-test-runner/Cargo.toml
All dependencies 31

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

RegistryPackageVersionRelation
crates.ioanyhow—direct
crates.ioapprox—direct
crates.ioarbitrary—direct
crates.iocriterion—direct
crates.ioearcut—direct
crates.iofloat_next_after—direct
crates.iogeo-booleanop—direct
crates.iogeo-types—direct
crates.iogeographiclib-rs—direct
crates.iogeojson—direct
crates.ioglob—direct
crates.ioinclude_dir—direct
crates.iolog—direct
crates.ionum-traits—direct
crates.iopretty_env_logger—direct
crates.ioproj—direct
crates.iorand—direct
crates.iorand_distr—direct
crates.iorand_pcg—direct
crates.iorayon—direct
crates.iorobust—direct
crates.iorstar—direct
crates.ioserde—direct
crates.ioserde-xml-rs—direct
crates.ioserde_derive—direct
crates.ioserde_json—direct
crates.iosif-itree—direct
crates.iospade—direct
crates.iothiserror—direct
crates.iowkt—direct
crates.iolibfuzzer-sys—indirect
Dependency advisories 4

Installing crates:geo@0.33.1 pulls in 73 packages, direct and transitive: 4 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
tar0.4.40indirecthigh50.4.46
atty0.2.14indirectlow3—
humantime1.3.0indirectunknown1—
libsqlite3-sys0.35.0indirectunknown10.39.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 — crates.io.