Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 14:00 UTC

3liz / proj4rs

Rust adaptation of Proj4

RustNo license detected★ 86 stars⑂ 23 forkssince Jun 2023View on GitHub ↗
KindLibraryApplicationhow this is determined

3liz/proj4rs holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (75/100) and lowest on Engineering Quality (50/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

3LizOrganization · verified domain
129 followers114 public repossince Feb 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.ioproj4rs0.3.1168,471151 day agogeographygeospatialgisprojprojection
crates.ioproj4rs-clib0.1.18240 days agogeographygeospatialgisprojprojection
crates.ioproj4rs-geodesic0.2.016,340322 days agogeographygeospatialgisprojprojection

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
8.3/36Commit cadence — 12/52 weeks with commits
18/18Commit volume — 102 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year102
human_commit_share1
days_since_last_push1
active_weeks_last_year12
How it's scored
16.2/27Ships releases — 12 version tags (no GitHub releases)
36/36Release recency — latest release 40 days ago
19.8/27Release cadence — a release every ~97.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count12
latest_release_tag0.2.1
releases_from_tagsyes
days_since_latest_release40
mean_days_between_releases97.1
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?

59Moderate · 17% of overall
How it's scored
31.3/60Stars — 86 stars
11.2/25Forks — 23 forks
3.3/15Watchers — 5 watchers
Inputs used
forks23
stars86
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
70.2/80Monthly downloads — 184,819 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesproj4rs, proj4rs-clib, proj4rs-geodesic
dependents—
ecosystemscrates
total_downloads1,534,879
monthly_downloads184,819
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?

75Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.7/22.5Commit distribution — top contributor authored 75% of commits
13.5/13.5Contributor breadth — 18 contributors
10/10OpenSSF Scorecard: Contributors — project has 13 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled18
top_contributor_share0.747
How it's scored
42/42Issue resolution — 100% of issues closed
25.4/30PR acceptance — 33/39 decided PRs merged
13/13Newcomer PR acceptance — 4/4 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 6/28 approved changesets -- score normalized to 2
Inputs used
merged_prs33
open_issues0
closed_issues25
prs_merged_7d4
prs_decided_7d4
prs_merged_30d11
prs_decided_30d11
issue_closed_ratio1
closed_unmerged_prs6
first_time_authors_30d2
first_time_prs_merged_30d4
first_time_prs_decided_30d4
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
15.2/25Owner reach — 129 followers of 3liz
25/25Track record — 114 public repos, account ~13 yr old
Inputs used
followers129
owner_typeOrganization
is_verifiedyes
owner_login3liz
public_repos114
account_age_days5,033

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 3 package(s) on crates
35/35Publish recency — latest publish 1 days ago
20/20Version history — 15 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesproj4rs, proj4rs-clib, proj4rs-geodesic
ecosystemscrates
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — proj4rs-clib/pyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 6 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/proj4rs/
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://docs.rs/proj4rs/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

53Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 6 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 6/28 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 13 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
7.5/7.5Maintained — 30 commit(s) and 5 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
4.5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages2
unassessed_packages16
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 2 resolved dependencies against OSV. 16 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

67Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
13.9/40Legible commit history — 26 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.26
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — proj4rs-clib/examples/Makefile
22/22Automated tests
11/11Lint / format config — proj4rs-clib/pyproject.toml ([tool.ruff])
11/11Static type checking — Rust (statically typed)
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 14 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageyes
bootstrap_filesproj4rs-clib/examples/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.14
toolchain_manifestsCargo.toml, proj4rs-clib/Cargo.toml, proj4rs-geodesic/Cargo.toml, proj4rs-php/Cargo.toml, proj4rs/Cargo.toml, run-wasm/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Rust (statically typed)
54.5/55Manageable file sizes — 1/118 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes62,718
source_files_sampled118
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

86GitHub stars
18contributors
102commits, last 12 months
1days since last push
12releases
1bus factor
0open issues
crates.io, Packagist, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'run-wasm' from its registry
  • Could not fetch crates package 'proj4rs-php' from its registry
  • Could not fetch packagist package '3liz/proj4rs-php-ext-tests' from its registry
  • Could not fetch pypi package 'proj4rs' from its registry
  • deps.dev does not index crates:proj4rs@0.3.1; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 23 ⇿
0Stars
23Forks
12Releases

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.

048121620242322023-082025-042026-11
Major 0Minor 1Patch 11

Each point covers 3 days.

OpenSSF Scorecard 4.1 / 10
4.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-18 14:00 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 6 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 6/28 approved changesets -- score normalized to 2
10Contributorsproject has 13 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 5 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
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
crates.ioproj4rs0.2proj4rs-clib/Cargo.toml
crates.iolibc0.2proj4rs-clib/Cargo.toml
PyPIcffi—proj4rs-clib/pyproject.toml
crates.ioproj4rs—proj4rs-php/Cargo.toml
crates.ioext-php-rs0.16proj4rs-php/Cargo.toml
crates.iothiserror2.0proj4rs/Cargo.toml
crates.iocrs-definitions0.6proj4rs/Cargo.toml
crates.iogeo-types0.7.12proj4rs/Cargo.toml
crates.iolog0.4proj4rs/Cargo.toml
crates.ioproj4rs-geodesic—proj4rs/Cargo.toml
crates.iotiff0.11proj4rs/Cargo.toml
crates.iocargo-run-wasm0.4.0run-wasm/Cargo.toml
All dependencies 18

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

RegistryPackageVersionRelation
crates.iocargo-run-wasm—direct
crates.iocrs-definitions—direct
crates.iogeo-types—direct
crates.iolibc—direct
crates.iolog—direct
crates.ioproj4rs—direct
crates.iothiserror—direct
crates.iotiff—direct
PyPIcffi2.1.1direct
crates.ioapprox—indirect
crates.ioclap—indirect
crates.ioconsole_log—indirect
crates.ioenv_logger—indirect
crates.iojs-sys—indirect
crates.iorand—indirect
crates.iowasm-bindgen—indirect
crates.ioweb-sys—indirect
PyPIpycparser3.11indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 2 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 16 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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 statistics — crates.io.