Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-13 22:42 UTC

OCHA-DAP / hdx-python-utilities

A range of helpful utilities for Python developers including streaming tabular data, date parsing, JSON and YAML handling, dictionary and list utilities

PythonMIT★ 10 stars⑂ 7 forkssince Oct 2017View on GitHub ↗

OCHA-DAP/hdx-python-utilities holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Engineering Quality (95/100) and lowest on Security (49/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

275 followers556 public repossince Jul 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIhdx-python-utilities4.2.162,5972700 days agohdxdatedatetimedictjsonlibraryliststreamingtabular-datatimetimezoneutilitiesyaml

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 0 days ago
8.3/36Commit cadence — 12/52 weeks with commits
14.1/18Commit volume — 36 commits in the last year
1/10OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year36
human_commit_share1
days_since_last_push0
active_weeks_last_year12

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 96 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~29 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count96
latest_release_tag4.2.1
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases29
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?

49Weak · 17% of overall
How it's scored
15.5/60Stars — 10 stars
6.5/25Forks — 7 forks
6.2/15Watchers — 14 watchers
Inputs used
forks7
stars10
watchers14
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescoveralls.io, github.com, shields.io
has_pull_request_templateno
How it's scored
64/80Monthly downloads — 62,597 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageshdx-python-utilities
dependents—
ecosystemspypi
total_downloads—
monthly_downloads62,597
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.1/22.5Commit distribution — top contributor authored 95% of commits
4.1/13.5Contributor breadth — 3 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.95
How it's scored
42/42Issue resolution — 100% of issues closed
26.4/30PR acceptance — 51/58 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs51
open_issues0
closed_issues3
prs_merged_7d1
prs_decided_7d1
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio1
closed_unmerged_prs7
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
17.5/25Owner reach — 275 followers of OCHA-DAP
25/25Track record — 556 public repos, account ~13 yr old
Inputs used
followers275
owner_typeOrganization
is_verifiedno
owner_loginOCHA-DAP
public_repos556
account_age_days4,828

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 0 days ago
20/20Version history — 270 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageshdx-python-utilities
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

95Exceptional · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 11 out of 12 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://hdx-python-utilities.readthedocs.io/en/latest/
10/10Repository description
10/10Topics — 8 topics
10/10Wiki
Inputs used
topicsdatetime, hdx, json, logging, utilities, yaml, stream-processing, tabular-data
has_wikiyes
homepagehttps://hdx-python-utilities.readthedocs.io/en/latest/
docs_sitehttps://hdx-python-utilities.readthedocs.io/en/latest/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

49Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.2/2.5CI-Tests — 11 out of 12 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0.8/7.5Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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
6/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 22 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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
advisories44
affected_packages10
assessed_packages100
unassessed_packages0
affected_by_severitycritical 1, high 4, moderate 4, low 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 100 resolved dependencies against OSV. 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.

53Moderate · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
18.7/40Legible commit history — 35 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.35
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes4,422
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — lockfile
2/10Demonstrated agent practice — 1 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_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/50 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes59,973
source_files_sampled50
oversized_source_files0

Key facts

10GitHub stars
3contributors
36commits, last 12 months
0days since last push
96releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:hdx-python-utilities@4.2.1; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 7 ⇿
0Stars
7Forks
94Releases

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.

1234567712018-092022-082026-07
Major 1Minor 9Patch 84

Each point covers 8 days.

OpenSSF Scorecard 3.6 / 10
3.6aggregate

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-13 22:42 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests11 out of 12 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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
8Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities22 existing vulnerabilities detected
Direct dependencies 16
RegistryPackageVersion constraintManifest
PyPIfrictionless>=5.19.0pyproject.toml
PyPIopenpyxl>=3.1.2pyproject.toml
PyPItableschema-to-template>=0.0.13pyproject.toml
PyPIxlrd>=2.0.1pyproject.toml
PyPIxlwt>=1.3.0pyproject.toml
PyPIijson>=3.5.0pyproject.toml
PyPIjsonlines>=4.0.0pyproject.toml
PyPItyping_extensions—pyproject.toml
PyPIloguru—pyproject.toml
PyPIpyphonetics—pyproject.toml
PyPIrapidfuzz—pyproject.toml
PyPIpython-dateutil>=2.9.0, <2.9.1pyproject.toml
PyPIratelimit—pyproject.toml
PyPIrequests-file—pyproject.toml
PyPIruamel.yaml—pyproject.toml
PyPIxlsx2csv==0.8.4pyproject.toml
All dependencies 100

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

RegistryPackageVersionRelation
PyPIfrictionless5.19.0direct
PyPIijson3.5.0direct
PyPIjsonlines4.0.0direct
PyPIloguru0.7.3direct
PyPIopenpyxl3.1.5direct
PyPIpyphonetics0.5.3direct
PyPIpython-dateutil2.9.0.post0direct
PyPIrapidfuzz3.14.5direct
PyPIrapidfuzz3.14.6direct
PyPIratelimit2.2.1direct
PyPIrequests-file3.0.1direct
PyPIruamel-yaml0.19.1direct
PyPItableschema-to-template0.0.13direct
PyPItyping-extensions4.15.0direct
PyPIxlrd2.0.2direct
PyPIxlsx2csv0.8.4direct
PyPIxlwt1.3.0direct
PyPIannotated-types0.7.0indirect
PyPIastdoc1.3.2indirect
PyPIattrs25.4.0indirect
PyPIbabel2.17.0indirect
PyPIbackrefs6.1indirect
PyPIbeautifulsoup44.14.3indirect
PyPIcertifi2026.1.4indirect
PyPIcfgv3.5.0indirect
PyPIchardet7.4.3indirect
PyPIcharset-normalizer3.4.4indirect
PyPIclick8.3.1indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.13.2indirect
PyPIcydifflib1.2.0indirect
PyPIdistlib0.4.0indirect
PyPIdnspython2.8.0indirect
PyPIemail-validator2.3.0indirect
PyPIet-xmlfile2.0.0indirect
PyPIexceptiongroup1.3.1indirect
PyPIfilelock3.20.3indirect
PyPIghp-import2.1.0indirect
PyPIhtml5lib1.1indirect
PyPIhumanize4.15.0indirect
PyPIidentify2.6.16indirect
PyPIidna3.11indirect
PyPIiniconfig2.3.0indirect
PyPIisodate0.7.2indirect
PyPIjinja23.1.6indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPImarkdown3.10.1indirect
PyPImarkdown-it-py4.0.0indirect
PyPImarko2.2.2indirect
PyPImarkupsafe3.0.3indirect
PyPImdurl0.1.2indirect
PyPImergedeep1.3.4indirect
PyPImkapi4.5.0indirect
PyPImkdocs1.6.1indirect
PyPImkdocs-get-deps0.2.0indirect
PyPImkdocs-material9.7.1indirect
PyPImkdocs-material-extensions1.3.1indirect
PyPInodeenv1.10.0indirect
PyPIpackaging26.0indirect
PyPIpaginate0.5.7indirect
PyPIpathspec1.0.3indirect
PyPIpetl1.7.17indirect
PyPIplatformdirs4.5.1indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.5.1indirect
PyPIpydantic2.12.5indirect
PyPIpydantic-core2.41.5indirect
PyPIpygments2.19.2indirect
PyPIpymdown-extensions10.20.1indirect
PyPIpytest9.0.2indirect
PyPIpytest-cov7.0.0indirect
PyPIpytest-loguru0.4.0indirect
PyPIpytest-mock3.15.1indirect
PyPIpython-slugify8.0.4indirect
PyPIpyyaml6.0.3indirect
PyPIpyyaml-env-tag1.1indirect
PyPIreferencing0.37.0indirect
PyPIrequests2.32.5indirect
PyPIrfc39862.0.0indirect
PyPIrich14.3.1indirect
PyPIrpds-py0.30.0indirect
PyPIruff0.14.13indirect
PyPIshellingham1.5.4indirect
PyPIsimpleeval1.0.3indirect
PyPIsix1.17.0indirect
PyPIsoupsieve2.8.3indirect
PyPItabulate0.9.0indirect
PyPItext-unidecode1.3indirect
PyPItomli2.4.0indirect
PyPItyper0.21.1indirect
PyPItyping-inspection0.4.2indirect
PyPIunidecode1.4.0indirect
PyPIurllib32.6.3indirect
PyPIvalidators0.35.0indirect
PyPIvirtualenv20.36.1indirect
PyPIwatchdog6.0.0indirect
PyPIwebencodings0.5.1indirect
PyPIwin32-setctime1.2.0indirect
PyPIxlsxwriter3.2.9indirect
Dependency advisories 10

This repository publishes no package the index resolves, so its own dependency graph was assessed — 100 packages, which also include development and test pins that never ship: 10 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
simpleeval1.0.3indirectcritical21.0.5
pymdown-extensions10.20.1indirecthigh611.0.1
soupsieve2.8.3indirecthigh82.9.0
urllib32.6.3indirecthigh102.8.0
virtualenv20.36.1indirecthigh821.7.13
idna3.11indirectmoderate23.15
mkdocs-material9.7.1indirectmoderate29.7.7
pytest9.0.2indirectmoderate29.0.3
requests2.32.5indirectmoderate22.33.0
pygments2.19.2indirectlow22.20.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 — PyPI.