Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 15:23 UTC

mdomke / schwifty

IBAN parsing and validation

PythonMIT★ 261 stars⑂ 106 forkssince Mar 2016View on GitHub ↗

mdomke/schwifty holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (95/100) and lowest on Security (54/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Martin DomkePersonal account
43 followers53 public repossince Mar 2011Qwist GmbH

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 publish
PyPIschwifty2026.10.0994,607910 days ago

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
11.1/36Commit cadence — 16/52 weeks with commits
17.7/18Commit volume — 93 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year93
human_commit_share1
days_since_last_push0
active_weeks_last_year16
How it's scored
27/27Ships releases — 69 releases published
36/36Release recency — latest release 0 days ago
19.8/27Release cadence — a release every ~54.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count69
latest_release_tag2026.10.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases54.9
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?

74Good · 17% of overall
How it's scored
39.2/60Stars — 261 stars
16.8/25Forks — 106 forks
5.6/15Watchers — 11 watchers
Inputs used
forks106
stars261
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesreadthedocs.org, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 994,607 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesschwifty
dependents—
ecosystemspypi
total_downloads—
monthly_downloads994,607
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?

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6/22.5Commit distribution — top contributor authored 74% of commits
13.5/13.5Contributor breadth — 71 contributors
10/10OpenSSF Scorecard: Contributors — project has 11 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled71
top_contributor_share0.735
How it's scored
35.6/42Issue resolution — 85% of issues closed
24.2/30PR acceptance — 168/208 decided PRs merged
13/13Newcomer PR acceptance — 14/14 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-Review — Found 20/30 approved changesets -- score normalized to 6
Inputs used
merged_prs168
open_issues15
closed_issues83
prs_merged_7d11
prs_decided_7d11
prs_merged_30d20
prs_decided_30d20
issue_closed_ratio0.847
closed_unmerged_prs40
first_time_authors_30d6
first_time_prs_merged_30d14
first_time_prs_decided_30d14
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
11.8/25Owner reach — 43 followers of mdomke
24.6/25Track record — 53 public repos, account ~15 yr old
Inputs used
followers43
owner_typeUser
is_verified—
owner_loginmdomke
public_repos53
account_age_days5,688
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

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 — 91 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesschwifty
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 — 2 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 — 19 out of 20 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://schwifty.readthedocs.io
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsiban, bic, python, swift
has_wikiyes
homepagehttps://schwifty.readthedocs.io
docs_sitehttps://schwifty.readthedocs.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.2/2.5CI-Tests — 19 out of 20 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
4.5/7.5Code-Review — Found 20/30 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 11 contributing companies or organizations
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
7.5/7.5Maintained — 30 commit(s) and 1 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
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 78 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.3
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 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
advisories251
affected_packages6
assessed_packages61
unassessed_packages9
affected_by_severitycritical 2, high 4
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 61 resolved dependencies against OSV. 9 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.

81Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
34.1/40Legible commit history — 64 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.64
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes2,004
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — schwifty/py.typed
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 6 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_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configsschwifty/py.typed
agent_commit_share0.06
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (schwifty/py.typed)
55/55Manageable file sizes — 0/55 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes21,779
source_files_sampled55
oversized_source_files0

Key facts

261GitHub stars
71contributors
93commits, last 12 months
0days since last push
69releases
1bus factor
15open 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:schwifty@2026.10.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 106 ⇿
0Stars
106Forks
68Releases

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.

02040608010012010632016-112021-102026-10
Major 0Minor 32Patch 34

Each point covers 10 days.

OpenSSF Scorecard 4.3 / 10
4.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-19 15:23 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
9CI-Tests19 out of 20 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 20/30 approved changesets -- score normalized to 6
10Contributorsproject has 11 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 1 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities78 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
PyPIimportlib_resources>=5.10pyproject.toml
PyPItyping-extensions>=4.4.0pyproject.toml
PyPIpycountry—pyproject.toml
PyPIrstr—pyproject.toml
All dependencies 70

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

RegistryPackageVersionRelation
PyPIimportlib-resources6.5.2direct
PyPIpycountry26.2.16direct
PyPIrstr3.2.2direct
PyPItyping-extensions4.16.0direct
PyPIannotated-types0.7.0indirect
PyPIanyio4.14.2indirect
PyPIbeautifulsoup4—indirect
PyPIbeautifulsoup44.14.3indirect
PyPIboltons25.0.0indirect
PyPIcamelot-py—indirect
PyPIcamelot-py1.0.9indirect
PyPIcffi2.0.0indirect
PyPIchardet6.0.0.post1indirect
PyPIcharset-normalizer3.4.4indirect
PyPIclick8.3.1indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.15.0indirect
PyPIcryptography46.0.5indirect
PyPIdoc82.0.0indirect
PyPIdocutils0.21.2indirect
PyPIet-xmlfile2.0.0indirect
PyPIfreezegun1.5.5indirect
PyPIfuro—indirect
PyPIh110.16.0indirect
PyPIhttpcore22.13.1indirect
PyPIhttpx2—indirect
PyPIhttpx22.13.1indirect
PyPIhttpx2-jsfetch1.0indirect
PyPIidna3.18indirect
PyPIiniconfig2.3.0indirect
PyPIlxml—indirect
PyPIlxml6.0.2indirect
PyPInumpy2.4.2indirect
PyPIopencv-python-headless4.13.0.92indirect
PyPIopenpyxl—indirect
PyPIopenpyxl3.1.5indirect
PyPIpackaging26.0indirect
PyPIpandas—indirect
PyPIpandas3.0.1indirect
PyPIpastel0.2.1indirect
PyPIpdfminer-six20260107indirect
PyPIpillow12.1.1indirect
PyPIpluggy1.6.0indirect
PyPIpoethepoet0.38.0indirect
PyPIprek0.4.8indirect
PyPIpycparser3.0indirect
PyPIpydantic2.14.1indirect
PyPIpydantic-core2.50.1indirect
PyPIpygments2.20.0indirect
PyPIpypdf3.17.4indirect
PyPIpypdf5.9.0indirect
PyPIpypdfium25.5.0indirect
PyPIpyrefly1.1.1indirect
PyPIpytest9.1.1indirect
PyPIpytest-cov7.1.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpyyaml6.0.3indirect
PyPIrestructuredtext-lint2.0.2indirect
PyPIruff0.15.4indirect
PyPIsix1.17.0indirect
PyPIsoupsieve2.8.3indirect
PyPIsphinx—indirect
PyPIstevedore5.7.0indirect
PyPItabulate0.9.0indirect
PyPItomli2.4.0indirect
PyPItruststore0.10.4indirect
PyPItyping-inspection0.4.4indirect
PyPItzdata2025.3indirect
PyPIxlrd—indirect
PyPIxlrd2.0.2indirect
Dependency advisories 6

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

PackageVersionRelationSeverityAdvisoriesFixed in
cryptography46.0.5indirectcritical1150.0.0
pillow12.1.1indirectcritical3612.3.0
lxml6.0.2indirecthigh26.1.0
pypdf3.17.4indirecthigh976.19.0
pypdf5.9.0indirecthigh976.19.0
soupsieve2.8.3indirecthigh82.9.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.