Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 08:52 UTC

electricitymaps / electricitymaps-contrib

The open source repository for Electricity Maps data parsers that powers the world's most comprehensive electricity data platform

PythonAGPL-3.0★ 4,026 stars⑂ 1,057 forkssince May 2016View on GitHub ↗
KindCommand-line toolhow this is determined

electricitymaps/electricitymaps-contrib holds a health index of 98 out of 100, placing it in the Exceptional band. It scores highest on Vitality (95/100) and lowest on AI Readiness (67/100). It was last updated today. 3 contributors account for most of its recent work.

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

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

Ownership

Electricity MapsOrganization · verified domain
374 followers17 public repossince Dec 2016

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

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
34.6/36Commit cadence50/52 weeks with commits
18/18Commit volume377 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year377
human_commit_share0.94
days_since_last_push0
active_weeks_last_year50
How it's scored
27/27Ships releases100 releases published
27/36Release recencylatest release 121 days ago
27/27Release cadencea release every ~17.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv1.322.0
releases_from_tagsno
days_since_latest_release121
mean_days_between_releases17.2
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?

93Exceptional · 17% of overall
How it's scored
58.5/60Stars4,026 stars
25/25Forks1,057 forks
10.4/15Watchers74 watchers
Inputs used
forks1,057
stars4,026
watchers74
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (AGPL-3.0)
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

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

84Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
15.3/22.5Commit distributiontop contributor authored 32% of commits
13.5/13.5Contributor breadth98 contributors
10/10OpenSSF Scorecard: Contributorsproject has 18 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled98
top_contributor_share0.32
How it's scored
40.4/42Issue resolution96% of issues closed
25.6/30PR acceptance4,790/5,624 decided PRs merged
10.4/13Newcomer PR acceptance4/5 first-time contributors' PRs merged in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 21/26 approved changesets -- score normalized to 8
Inputs used
merged_prs4,790
open_issues114
closed_issues2,816
prs_merged_7d6
prs_decided_7d12
prs_merged_30d20
prs_decided_30d26
issue_closed_ratio0.961
closed_unmerged_prs834
first_time_authors_30d5
first_time_prs_merged_30d4
first_time_prs_decided_30d5
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
18.5/25Owner reach374 followers of electricitymaps
21.1/25Track record17 public repos, account ~9 yr old
Inputs used
followers374
owner_typeOrganization
is_verifiedyes
owner_loginelectricitymaps
public_repos17
account_age_days3,534

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter configpyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests25 out of 25 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://app.electricitymaps.com
10/10Repository description
10/10Topics11 topics
10/10Wiki
Inputs used
topicssustainability, data-visualization, climate-change, hacktoberfest, app, electricity, electricity-consumption, electricity-prices, map, electricitymaps, electricitymap
has_wikiyes
homepagehttps://app.electricitymaps.com
docs_sitehttps://app.electricitymaps.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

74Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests25 out of 25 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 21/26 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 18 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 14 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.8
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages64
unassessed_packages7
affected_by_severityhigh 1
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 64 resolved dependencies against OSV. 7 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 instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
36.3/40Legible commit history64 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.681
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.ruff])
11/11Static type checkingelectricitymap/contrib/config/py.typed, electricitymap/contrib/py.typed, geo/tsconfig.json
10/10Reproducible environmentdevcontainer, Dockerfile, lockfile
10/10Demonstrated agent practice28 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance6 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontaineryes
has_linter_configyes
typecheck_configselectricitymap/contrib/config/py.typed, electricitymap/contrib/py.typed, geo/tsconfig.json
agent_commit_share0.28
toolchain_manifests
dependency_bot_commit_share0.06
How it's scored
27/45Type-checkable codePython with type-check config (electricitymap/contrib/config/py.typed, electricitymap/contrib/py.typed, geo/tsconfig.json)
54.6/55Manageable file sizes2/293 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes72,118
source_files_sampled293
oversized_source_files2
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
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

4,026GitHub stars
98contributors
377commits, last 12 months
0days since last push
100releases
3bus factor
114open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • First-time contributor figures cover 12 of 13 authors (cap 12)
  • Could not fetch pypi package 'electricitymap-contrib' from its registry
  • Could not fetch pypi package 'electricitymap-contrib-types' from its registry

More detail

Star and fork history 0 ★ / 1,057 ⇿
0Stars
1,057Forks
100Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

02004006008001,0001,2001,057432017-052022-012026-08
Major 0Minor 100Patch 0

Each point covers 9 days.

OpenSSF Scorecard 6.8 / 10
6.8aggregate

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-08-28 08:51 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests25 out of 25 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 21/26 approved changesets -- score normalized to 8
10Contributorsproject has 18 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 14 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
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
npm@turf/bbox^7.3.4geo/package.json
npm@turf/buffer^7.3.4geo/package.json
npm@turf/centroid^7.3.4geo/package.json
npm@turf/point-on-feature^7.3.4geo/package.json
npm@turf/union^7.3.4geo/package.json
PyPIelectricitymap-contrib-typespyproject.toml
PyPIpydantic>=1.10.17,<2pyproject.toml
PyPIPyYAML>=6.0,<7pyproject.toml
PyPIruamel-yaml>=0.17.24,<0.18pyproject.toml
PyPItzdata>=2025.2pyproject.toml
PyPInumpy>=2.0.0,<3pyproject.toml
PyPIpydantic>=1.10.17,<2libs/types/pyproject.toml
All dependencies 71

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

RegistryPackageVersionRelation
npm@turf/bbox^7.3.4direct
npm@turf/buffer^7.3.4direct
npm@turf/centroid^7.3.4direct
npm@turf/point-on-feature^7.3.4direct
npm@turf/union^7.3.4direct
PyPIelectricitymap-contrib-types1.6.0direct
PyPInumpy2.2.6direct
PyPInumpy2.4.4direct
PyPIpydanticdirect
PyPIpydantic1.10.26direct
PyPIpyyaml6.0.3direct
PyPIruamel-yaml0.17.40direct
PyPItzdata2025.3direct
npm@types/bunlatestindirect
PyPIaiohappyeyeballs2.6.1indirect
PyPIaiohttp3.14.3indirect
PyPIaiosignal1.4.0indirect
PyPIasync-timeout5.0.1indirect
PyPIasyncio4.0.0indirect
PyPIattrs25.4.0indirect
PyPIbeautifulsoup44.6.3indirect
PyPIcertifi2026.1.4indirect
PyPIcharset-normalizer3.4.4indirect
PyPIclick8.3.1indirect
PyPIcolorama0.4.6indirect
PyPIdefusedxml0.7.1indirect
PyPIdemjson33.0.6indirect
PyPIelectricitymap-contrib2.8.4indirect
PyPIet-xmlfile2.0.0indirect
PyPIexceptiongroup1.3.1indirect
PyPIfreezegun0.3.15indirect
PyPIfrozenlist1.8.0indirect
PyPIhatchlingindirect
PyPIidna3.15indirect
PyPIimageio2.37.2indirect
PyPIiniconfig2.3.0indirect
PyPIlxml6.1.0indirect
PyPImultidict6.7.0indirect
PyPInest-asyncio1.6.0indirect
PyPIodfpy1.4.1indirect
PyPIopencv-python4.13.0.92indirect
PyPIopenpyxl3.1.5indirect
PyPIpackaging25.0indirect
PyPIpandas2.3.3indirect
PyPIpillow12.3.0indirect
PyPIpluggy1.6.0indirect
PyPIpropcache0.4.1indirect
PyPIpycountry22.3.5indirect
PyPIpydataxm0.3.16indirect
PyPIpygments2.20.0indirect
PyPIpytesseract0.2.0indirect
PyPIpytest9.0.3indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpytz2025.2indirect
PyPIrequests2.33.0indirect
PyPIrequests-mock1.12.1indirect
PyPIruamel-yaml-clib0.2.15indirect
PyPIruff0.16.3indirect
PyPIsetuptools83.0.0indirect
PyPIsignalr-client-threads0.0.12indirect
PyPIsix1.17.0indirect
PyPIsseclient0.0.27indirect
PyPIsyrupy5.1.0indirect
PyPItestfixtures7.2.2indirect
PyPItomli2.4.0indirect
PyPItyping-extensions4.15.0indirect
PyPIurllib32.7.0indirect
PyPIwebsocket-client1.9.0indirect
PyPIxlrd2.0.2indirect
PyPIxmltodict0.13.0indirect
PyPIyarl1.22.0indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
click8.3.1indirecthigh18.3.3

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.