Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-08 02:35 UTC

amptimal / surge

AC/DC power flow solver

RustCustom license★ 14 stars⑂ 4 forkssince Mar 2026View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

amptimal/surge holds a health index of 50 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (74/100) and lowest on Security (33/100). It was last updated 156 days ago. A single contributor accounts for most of its recent work.

50
overall / 100
Moderate

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.

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

Ownership

AmptimalOrganization
5 followers1 public reposince Feb 2026

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

Package ecosystems

Metrics by category

Vitality

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

50Moderate · 21% of overall
How it's scored
9.9/36Push recency — last push 156 days ago
2.8/36Commit cadence — 4/52 weeks with commits
10/18Commit volume — 12 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year12
human_commit_share—
days_since_last_push156
active_weeks_last_year4
How it's scored
27/27Ships releases — 10 releases published
27/36Release recency — latest release 156 days ago
27/27Release cadence — a release every ~4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count10
latest_release_tagv0.1.9
releases_from_tagsno
days_since_latest_release156
mean_days_between_releases4
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?

51Moderate · 17% of overall
How it's scored
18.1/60Stars — 14 stars
4/25Forks — 4 forks
0/15Watchers — 1 watchers
Inputs used
forks4
stars14
watchers1
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_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
38.7/80Monthly downloads — 795 downloads/month across crates, pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagessurge-ac, surge-dc, surge-io, surge-opf, surge-hvdc, surge-market, surge-py
dependents—
ecosystemscrates, pypi
total_downloads3,792
monthly_downloads795
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?

40Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution — 0% of issues closed
27.3/30PR acceptance — 10/11 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/12 approved changesets -- score normalized to 0
Inputs used
merged_prs10
open_issues1
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0
closed_unmerged_prs1
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
5.6/25Owner reach — 5 followers of amptimal
3.4/25Track record — 1 public repos, account ~0 yr old
Inputs used
followers5
owner_typeOrganization
is_verifiedno
owner_loginamptimal
public_repos1
account_age_days229

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 7 package(s) on crates, pypi
35/35Publish recency — latest publish 156 days ago
20/20Version history — 11 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagessurge-ac, surge-dc, surge-io, surge-opf, surge-hvdc, surge-market, surge-py
ecosystemscrates, pypi
any_deprecatedno
min_days_since_publish156

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — .rustfmt.toml, clippy.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 10 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://amptimal.com
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicsenergy, opf, power-flow, power-systems, rust
has_wikino
homepagehttps://amptimal.com
docs_sitehttps://amptimal.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

33At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — 0 out of 10 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
0/7.5Code-Review — Found 0/12 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
5/5Packaging — packaging workflow detected
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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 17 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.3
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

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.

65Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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 bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — .rustfmt.toml, clippy.toml
11/11Static type checking — src/surge-py/python/surge/py.typed
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no data
0/8Automated maintenance — no data
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, uv.lock
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/surge-py/python/surge/py.typed
agent_commit_share—
toolchain_manifestsCargo.toml, src/surge-ac/Cargo.toml, src/surge-bindings/Cargo.toml, src/surge-contingency/Cargo.toml, src/surge-dc/Cargo.toml, src/surge-dispatch/Cargo.toml, src/surge-hvdc/Cargo.toml, src/surge-io/Cargo.toml, src/surge-market/Cargo.toml, src/surge-network/Cargo.toml, src/surge-opf/Cargo.toml, src/surge-py/Cargo.toml, src/surge-solution/Cargo.toml, src/surge-sparse/Cargo.toml, src/surge-topology/Cargo.toml, src/surge-transfer/Cargo.toml
dependency_bot_commit_share—
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — Rust (statically typed)
49.6/55Manageable file sizes — 66/668 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes464,543
source_files_sampled668
oversized_source_files66
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, 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

14GitHub stars
1contributors
12commits, last 12 months
156days since last push
10releases
1bus factor
1open 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 'surge-py' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 4 ⇿
0Stars
4Forks
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.

1223344412026-042026-052026-06
Major 0Minor 0Patch 3
OpenSSF Scorecard 3.3 / 10
3.3aggregate

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-10-08 02:35 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 10 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/12 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities17 existing vulnerabilities detected
Direct dependencies 171
RegistryPackageVersion constraintManifest
crates.iosurge-network—src/surge-ac/Cargo.toml
crates.iosurge-solution—src/surge-ac/Cargo.toml
crates.iosurge-sparse—src/surge-ac/Cargo.toml
crates.iosurge-topology—src/surge-ac/Cargo.toml
crates.iofaer—src/surge-ac/Cargo.toml
crates.iorayon—src/surge-ac/Cargo.toml
crates.iotracing—src/surge-ac/Cargo.toml
crates.iothiserror—src/surge-ac/Cargo.toml
crates.ionum-complex—src/surge-ac/Cargo.toml
crates.ioserde—src/surge-ac/Cargo.toml
crates.iosurge-network—src/surge-bindings/Cargo.toml
crates.iosurge-solution—src/surge-bindings/Cargo.toml
crates.iosurge-dc—src/surge-bindings/Cargo.toml
crates.iosurge-ac—src/surge-bindings/Cargo.toml
crates.iosurge-io—src/surge-bindings/Cargo.toml
crates.iosurge-contingency—src/surge-bindings/Cargo.toml
crates.iosurge-opf—src/surge-bindings/Cargo.toml
crates.iosurge-hvdc—src/surge-bindings/Cargo.toml
crates.iosurge-transfer—src/surge-bindings/Cargo.toml
crates.ioanyhow—src/surge-bindings/Cargo.toml
crates.ioclap—src/surge-bindings/Cargo.toml
crates.ioserde—src/surge-bindings/Cargo.toml
crates.ioserde_json—src/surge-bindings/Cargo.toml
crates.iotracing—src/surge-bindings/Cargo.toml
crates.iotracing-subscriber—src/surge-bindings/Cargo.toml
crates.iozstd0.13src/surge-bindings/Cargo.toml
crates.iosurge-network—src/surge-contingency/Cargo.toml
crates.iosurge-solution—src/surge-contingency/Cargo.toml
crates.iosurge-dc—src/surge-contingency/Cargo.toml
crates.iosurge-ac—src/surge-contingency/Cargo.toml
crates.iosurge-sparse—src/surge-contingency/Cargo.toml
crates.iosurge-hvdc—src/surge-contingency/Cargo.toml
crates.iosurge-opf—src/surge-contingency/Cargo.toml
crates.iofaer—src/surge-contingency/Cargo.toml
crates.iosurge-topology—src/surge-contingency/Cargo.toml
crates.iorayon—src/surge-contingency/Cargo.toml
crates.iotracing—src/surge-contingency/Cargo.toml
crates.iothiserror—src/surge-contingency/Cargo.toml
crates.ioserde—src/surge-contingency/Cargo.toml
crates.ioserde_json—src/surge-contingency/Cargo.toml
crates.ionum-complex—src/surge-contingency/Cargo.toml
crates.iosurge-network—src/surge-dc/Cargo.toml
crates.iosurge-solution—src/surge-dc/Cargo.toml
crates.iosurge-topology—src/surge-dc/Cargo.toml
crates.iosurge-sparse—src/surge-dc/Cargo.toml
crates.iofaer—src/surge-dc/Cargo.toml
crates.iotracing—src/surge-dc/Cargo.toml
crates.iothiserror—src/surge-dc/Cargo.toml
crates.ioserde—src/surge-dc/Cargo.toml
crates.iosurge-network—src/surge-dispatch/Cargo.toml
crates.iosurge-solution—src/surge-dispatch/Cargo.toml
crates.iosurge-ac—src/surge-dispatch/Cargo.toml
crates.iosurge-dc—src/surge-dispatch/Cargo.toml
crates.iosurge-hvdc—src/surge-dispatch/Cargo.toml
crates.iosurge-opf—src/surge-dispatch/Cargo.toml
crates.iosurge-sparse—src/surge-dispatch/Cargo.toml
crates.iofaer—src/surge-dispatch/Cargo.toml
crates.iorayon—src/surge-dispatch/Cargo.toml
crates.iotracing—src/surge-dispatch/Cargo.toml
crates.iothiserror—src/surge-dispatch/Cargo.toml
crates.ioserde—src/surge-dispatch/Cargo.toml
crates.ioserde_json—src/surge-dispatch/Cargo.toml
crates.ioschemars—src/surge-dispatch/Cargo.toml
crates.iochrono—src/surge-dispatch/Cargo.toml
crates.iocsv—src/surge-dispatch/Cargo.toml
crates.ioparquet57.3.0src/surge-dispatch/Cargo.toml
crates.ioarrow-array57.3.0src/surge-dispatch/Cargo.toml
crates.ioarrow-schema57.3.0src/surge-dispatch/Cargo.toml
crates.iosurge-network—src/surge-hvdc/Cargo.toml
crates.iosurge-solution—src/surge-hvdc/Cargo.toml
crates.iosurge-ac—src/surge-hvdc/Cargo.toml
crates.iosurge-sparse—src/surge-hvdc/Cargo.toml
crates.iotracing—src/surge-hvdc/Cargo.toml
crates.iothiserror—src/surge-hvdc/Cargo.toml
crates.ioserde—src/surge-hvdc/Cargo.toml
crates.ionum-complex—src/surge-hvdc/Cargo.toml
crates.iofaer—src/surge-hvdc/Cargo.toml
crates.iosurge-network—src/surge-io/Cargo.toml
crates.iosurge-solution—src/surge-io/Cargo.toml
crates.iosurge-topology—src/surge-io/Cargo.toml
crates.ioserde—src/surge-io/Cargo.toml
crates.ioserde_json—src/surge-io/Cargo.toml
crates.ioserde-value0.7src/surge-io/Cargo.toml
crates.iociborium0.2src/surge-io/Cargo.toml
crates.iotoml—src/surge-io/Cargo.toml
crates.ionum-complex—src/surge-io/Cargo.toml
crates.iotracing—src/surge-io/Cargo.toml
crates.iothiserror—src/surge-io/Cargo.toml
crates.iocrc32fast1src/surge-io/Cargo.toml
crates.ioquick-xml0.37src/surge-io/Cargo.toml
crates.iorayon—src/surge-io/Cargo.toml
crates.iocsv—src/surge-io/Cargo.toml
crates.iozip2src/surge-io/Cargo.toml
crates.iozstd0.13src/surge-io/Cargo.toml
crates.iotempfile3src/surge-io/Cargo.toml
crates.iosurge-dispatch—src/surge-market/Cargo.toml
crates.iosurge-io—src/surge-market/Cargo.toml
crates.iosurge-network—src/surge-market/Cargo.toml
crates.iosurge-opf—src/surge-market/Cargo.toml
crates.ioserde—src/surge-market/Cargo.toml
crates.ioserde_json—src/surge-market/Cargo.toml
crates.iothiserror—src/surge-market/Cargo.toml
crates.iotracing—src/surge-market/Cargo.toml
crates.ioserde—src/surge-network/Cargo.toml
crates.ioserde_json—src/surge-network/Cargo.toml
crates.iotracing—src/surge-network/Cargo.toml
crates.iothiserror—src/surge-network/Cargo.toml
crates.ionum-complex—src/surge-network/Cargo.toml
crates.iochrono—src/surge-network/Cargo.toml
crates.iosurge-sparse—src/surge-network/Cargo.toml
crates.iosurge-network—src/surge-opf/Cargo.toml
crates.iosurge-solution—src/surge-opf/Cargo.toml
crates.iosurge-dc—src/surge-opf/Cargo.toml
crates.iosurge-ac—src/surge-opf/Cargo.toml
crates.iosurge-sparse—src/surge-opf/Cargo.toml
crates.iosurge-hvdc—src/surge-opf/Cargo.toml
crates.iofaer—src/surge-opf/Cargo.toml
crates.iorayon—src/surge-opf/Cargo.toml
crates.iotracing—src/surge-opf/Cargo.toml
crates.iothiserror—src/surge-opf/Cargo.toml
crates.ioanyhow—src/surge-opf/Cargo.toml
crates.ionum-complex—src/surge-opf/Cargo.toml
crates.ioserde—src/surge-opf/Cargo.toml
crates.ioserde_json—src/surge-opf/Cargo.toml
crates.iolibloading—src/surge-opf/Cargo.toml
crates.ioclarabel—src/surge-opf/Cargo.toml
crates.iosurge-network—src/surge-py/Cargo.toml
crates.iosurge-solution—src/surge-py/Cargo.toml
crates.iosurge-dc—src/surge-py/Cargo.toml
crates.iosurge-ac—src/surge-py/Cargo.toml
crates.iosurge-io—src/surge-py/Cargo.toml
crates.iosurge-contingency—src/surge-py/Cargo.toml
crates.iosurge-dispatch—src/surge-py/Cargo.toml
crates.iosurge-market—src/surge-py/Cargo.toml
crates.iosurge-opf—src/surge-py/Cargo.toml
crates.iosurge-hvdc—src/surge-py/Cargo.toml
crates.iosurge-topology—src/surge-py/Cargo.toml
crates.iosurge-transfer—src/surge-py/Cargo.toml
crates.iofaer—src/surge-py/Cargo.toml
crates.ionum-complex—src/surge-py/Cargo.toml
crates.iopyo30.28src/surge-py/Cargo.toml
crates.ionumpy0.28src/surge-py/Cargo.toml
crates.iochrono—src/surge-py/Cargo.toml
crates.iorayon—src/surge-py/Cargo.toml
crates.ioserde—src/surge-py/Cargo.toml
crates.ioserde_ignored—src/surge-py/Cargo.toml
crates.ioserde_json—src/surge-py/Cargo.toml
crates.iozstd0.13src/surge-py/Cargo.toml
crates.iotracing—src/surge-py/Cargo.toml
crates.iotracing-subscriber—src/surge-py/Cargo.toml
PyPInumpy>=1.20src/surge-py/pyproject.toml
crates.ioserde—src/surge-solution/Cargo.toml
crates.iothiserror—src/surge-solution/Cargo.toml
crates.iosurge-network—src/surge-solution/Cargo.toml
crates.ionum-complex—src/surge-sparse/Cargo.toml
crates.iofaer—src/surge-sparse/Cargo.toml
crates.iothiserror—src/surge-sparse/Cargo.toml
crates.iosurge-network—src/surge-topology/Cargo.toml
crates.iotracing—src/surge-topology/Cargo.toml
crates.iothiserror—src/surge-topology/Cargo.toml
crates.iosurge-network—src/surge-transfer/Cargo.toml
crates.iosurge-solution—src/surge-transfer/Cargo.toml
crates.iosurge-dc—src/surge-transfer/Cargo.toml
crates.iosurge-ac—src/surge-transfer/Cargo.toml
crates.iosurge-opf—src/surge-transfer/Cargo.toml
crates.iosurge-sparse—src/surge-transfer/Cargo.toml
crates.iofaer—src/surge-transfer/Cargo.toml
crates.iorayon—src/surge-transfer/Cargo.toml
crates.iotracing—src/surge-transfer/Cargo.toml
crates.iothiserror—src/surge-transfer/Cargo.toml
crates.ioserde—src/surge-transfer/Cargo.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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