Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-18 12:36 UTC

jab / bidict

The bidirectional mapping library for Python.

PythonMPL-2.0★ 1,584 stars⑂ 69 forkssince Sep 2014View on GitHub ↗

jab/bidict holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (100/100) and lowest on Sustainability & Governance (58/100). It was last updated 7 days ago. A single contributor accounts 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

Joshua BronsonPersonal account
313 followers240 public repossince Mar 2009

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIbidict0.23.1-42880 days agobidictbimapbidirectionaldictdictionarymappingcollections

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 recencylast push 7 days ago
13.2/36Commit cadence19/52 weeks with commits
17.4/18Commit volume85 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year85
human_commit_share
days_since_last_push7
active_weeks_last_year19
How it's scored
27/27Ships releases38 releases published
0/36Release recencylatest release 880 days ago
12.6/27Release cadencea release every ~139.9 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count38
latest_release_tagv0.23.1
releases_from_tagsno
days_since_latest_release880
mean_days_between_releases139.9

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

78Good · 17% of overall
How it's scored
51.9/60Stars1,584 stars
15.3/25Forks69 forks
5.3/15Watchers10 watchers
Inputs used
forks69
stars1,584
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MPL-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

58Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.5/22.5Commit distributiontop contributor authored 93% of commits
13.5/13.5Contributor breadth18 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled18
top_contributor_share0.933
How it's scored
42/42Issue resolution100% of issues closed
20.9/30PR acceptance222/318 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/14 approved changesets -- score normalized to 0
Inputs used
merged_prs222
open_issues0
closed_issues63
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs96
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
18/25Owner reach313 followers of jab
25/25Track record240 public repos, account ~17 yr old
Inputs used
followers313
owner_typeUser
is_verified
owner_loginjab
public_repos240
account_age_days6,329
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on pypi
4/35Publish recencylatest publish 880 days ago
20/20Version history42 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesbidict
ecosystemspypi
any_deprecatedno
min_days_since_publish880

Engineering Quality

Are baseline engineering and documentation practices in place?

100Exceptional · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows10 workflow(s)
24/24Tests present
16/16Linter configtox.ini
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests12 out of 12 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

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://bidict.readthedocs.io
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicspython, bidict, bimap, data-structures
has_wikiyes
homepagehttps://bidict.readthedocs.io
docs_sitehttps://bidict.readthedocs.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

62Moderate · 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-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
1.2/2.5CII-Best-Practicesbadge detected: Passing
0/7.5Code-ReviewFound 1/14 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 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 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
4.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
0/5SASTSAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.2
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. 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.

88Excellent · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes3,461
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapdocs/Makefile
22/22Automated tests
11/11Lint / format configtox.ini
11/11Static type checkingbidict/py.typed
10/10Reproducible environmentNix, lockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
9/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixyes
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configsbidict/py.typed
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
27/45Type-checkable codePython with type-check config (bidict/py.typed)
55/55Manageable file sizes0/20 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes27,039
source_files_sampled20
oversized_source_files0

Key facts

1,584GitHub stars
18contributors
85commits, last 12 months
7days since last push
38releases
1bus factor
0open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 6.2 / 10
6.2aggregate

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-07-18 12:35 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-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
5CII-Best-Practicesbadge detected: Passing
0Code-ReviewFound 1/14 approved changesets -- score normalized to 0
10Contributorsproject has 6 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 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
9Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPItyping_extensions>=4.0pyproject.toml
All dependencies 66

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

RegistryPackageVersionRelation
PyPItyping-extensions4.16.0direct
PyPIaccessible-pygments0.0.5indirect
PyPIalabaster1.0.0indirect
PyPIbabel2.18.0indirect
PyPIbeautifulsoup44.15.0indirect
PyPIbidict0.23.2.dev0indirect
PyPIcachetools7.1.4indirect
PyPIcertifi2026.6.17indirect
PyPIcharset-normalizer3.4.8indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.15.0indirect
PyPIdistlib0.4.3indirect
PyPIdocutils0.22.4indirect
PyPIexecnet2.1.2indirect
PyPIfilelock3.29.6indirect
PyPIfuro2025.12.19indirect
PyPIhypothesis6.156.1indirect
PyPIicdiff2.0.10indirect
PyPIidna3.18indirect
PyPIimagesize2.0.0indirect
PyPIiniconfig2.3.0indirect
PyPIjinja23.1.6indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.3indirect
PyPImdurl0.1.2indirect
PyPIpackaging26.2indirect
PyPIplatformdirs4.10.0indirect
PyPIpluggy1.6.0indirect
PyPIpprintpp0.4.0indirect
PyPIpy-cpuinfo9.0.0indirect
PyPIpygments2.20.0indirect
PyPIpyproject-api1.10.1indirect
PyPIpytest9.1.1indirect
PyPIpytest-benchmark5.2.3indirect
PyPIpytest-clarity1.0.1indirect
PyPIpytest-icdiff0.9indirect
PyPIpytest-sphinx0.7.1indirect
PyPIpytest-sugar1.1.1indirect
PyPIpytest-xdist3.8.0indirect
PyPIpython-discovery1.4.3indirect
PyPIrequests2.34.2indirect
PyPIrich15.0.0indirect
PyPIroman-numerals4.1.0indirect
PyPIsnowballstemmer3.1.1indirect
PyPIsortedcollections2.1.0indirect
PyPIsortedcontainers2.4.0indirect
PyPIsoupsieve2.8.4indirect
PyPIsphinx9.0.4indirect
PyPIsphinx9.1.0indirect
PyPIsphinx-basic-ng1.0.0b2indirect
PyPIsphinx-copybutton0.5.2indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPItermcolor3.3.0indirect
PyPItomli-w1.2.0indirect
PyPItox4.56.1indirect
PyPItox-uv1.35.2indirect
PyPItox-uv-bare1.35.2indirect
PyPIty0.0.58indirect
PyPIurllib32.7.0indirect
PyPIuv0.11.27indirect
PyPIvirtualenv21.6.0indirect
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.12.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.