Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 22:48 UTC

sebastienrousseau / bankstatementparser

Parse bank statements — CAMT/ISO 20022, PAIN.001, CSV (EN/DE/FR/ES), OFX/QFX, MT940, PDFs (digital + scanned) — into unified Transactions. Deterministic parsers, LLM/vision fallback, Golden Rule + multi-currency + continuity verification, page provenance, dedupe, review, accuracy evals, CLI + REST API. 100% test coverage.

PythonCustom license★ 50 stars⑂ 11 forkssince Nov 2023View on GitHub ↗
KindCommand-line toolLibraryNetwork servicehow this is determined

sebastienrousseau/bankstatementparser holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (90/100) and lowest on Sustainability & Governance (54/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Sebastien RousseauPersonal account
155 followers207 public repossince Jan 2012

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
PyPIbankstatementparser0.0.19-1013 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 5 days ago
11.8/36Commit cadence — 17/52 weeks with commits
18/18Commit volume — 203 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year203
human_commit_share0.55
days_since_last_push5
active_weeks_last_year17
How it's scored
27/27Ships releases — 13 releases published
36/36Release recency — latest release 13 days ago
27/27Release cadence — a release every ~17 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count13
latest_release_tagv0.0.19
releases_from_tagsno
days_since_latest_release13
mean_days_between_releases17

Community & Adoption

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

56Moderate · 17% of overall
How it's scored
27.4/60Stars — 50 stars
8.3/25Forks — 11 forks
0/15Watchers — 2 watchers
Inputs used
forks11
stars50
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
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
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges19
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

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

54Moderate · 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
42/42Issue resolution — 100% of issues closed
11.2/30PR acceptance — 74/199 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/4 approved changesets -- score normalized to 0
Inputs used
merged_prs74
open_issues0
closed_issues7
prs_merged_7d0
prs_decided_7d0
prs_merged_30d4
prs_decided_30d4
issue_closed_ratio1
closed_unmerged_prs125
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
15.8/25Owner reach — 155 followers of sebastienrousseau
25/25Track record — 207 public repos, account ~14 yr old
Inputs used
followers155
owner_typeUser
is_verified—
owner_loginsebastienrousseau
public_repos207
account_age_days5,340
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 13 days ago
20/20Version history — 10 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesbankstatementparser
ecosystemspypi
any_deprecatedno
min_days_since_publish13

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
16/16Linter config — .pylintrc, pyproject.toml ([tool.ruff], [tool.black], [tool.isort])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 14 out of 14 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — http://docs.bankstatementparser.com/
10/10Repository description
10/10Topics — 20 topics
10/10Wiki
Inputs used
topicsbanking, camt, finance, iso20022, pain001, bank-statements, cli, csv, mt940, ofx, parser, categorization, deduplication, litellm, llm, ollama, pdf, fintech, rest-api, treasury
has_wikiyes
homepagehttp://docs.bankstatementparser.com/
docs_sitehttp://docs.bankstatementparser.com/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

75Good · 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
2.5/2.5CI-Tests — 14 out of 14 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/4 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
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
3.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 7
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate6.9

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages13
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:bankstatementparser@0.0.19 runtime dependency closure — what installing the published package pulls in — 13 packages. 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.

61Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 55 of 55 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile, mise.toml
22/22Automated tests
11/11Lint / format config — .pylintrc, pyproject.toml ([tool.ruff], [tool.black], [tool.isort])
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 11 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 45 of the last 100 commits are automated dependency updates
7/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 7
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile, mise.toml
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.11
toolchain_manifests—
dependency_bot_commit_share0.45
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/123 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes52,786
source_files_sampled123
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

50GitHub stars
1contributors
203commits, last 12 months
5days since last push
13releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'bankstatementparser' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced

More detail

Star and fork history 0 ★ / 11 ⇿
0Stars
11Forks
10Releases

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.

0246810121112024-102025-092026-08
Major 0Minor 0Patch 10

Each point covers 2 days.

OpenSSF Scorecard 6.9 / 10
6.9aggregate

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-09-14 22:48 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests14 out of 14 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/4 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
7Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 17
RegistryPackageVersion constraintManifest
PyPIlxml>=5.0pyproject.toml
PyPIopenpyxl^3.1.5pyproject.toml
PyPIpandas^2.3.3pyproject.toml
PyPIdefusedxml^0.7.1pyproject.toml
PyPIpydantic^2.11.0pyproject.toml
PyPIpolars^1.32.0pyproject.toml
PyPIlitellm>=1.83.10pyproject.toml
PyPIpypdf>=4.0.0pyproject.toml
PyPIpdfplumber>=0.11.0pyproject.toml
PyPIpypdfium2>=4.30.0pyproject.toml
PyPIfastapi>=0.115.0pyproject.toml
PyPIuvicorn>=0.34.0pyproject.toml
PyPIpyarrow>=14.0.0pyproject.toml
PyPIlxml>=4.9.3setup.cfg
PyPIopenpyxl>=3.1.2setup.cfg
PyPIpandas>=2.1.1setup.cfg
PyPIdefusedxml>=0.7.1setup.cfg
All dependencies 129

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

RegistryPackageVersionRelation
PyPIdefusedxml0.7.1direct
PyPIfastapi0.141.1direct
PyPIlitellm1.98.0direct
PyPIlxml6.1.1direct
PyPIlxml6.1.2direct
PyPIopenpyxl3.1.5direct
PyPIpandas2.3.3direct
PyPIpdfplumber0.11.10direct
PyPIpolars1.43.2direct
PyPIpyarrow25.0.1direct
PyPIpydantic2.13.4direct
PyPIpypdf6.16.1direct
PyPIpypdfium25.13.0direct
PyPIuvicorn0.52.4direct
PyPIaiohappyeyeballs2.6.2indirect
PyPIaiohttp3.14.3indirect
PyPIaiosignal1.4.0indirect
PyPIannotated-doc0.0.4indirect
PyPIannotated-types0.7.0indirect
PyPIanyio4.13.0indirect
PyPIast-serialize0.8.0indirect
PyPIasync-timeout5.0.1indirect
PyPIattrs26.1.0indirect
PyPIbabel2.18.0indirect
PyPIbackrefs7.0indirect
PyPIbandit1.9.4indirect
PyPIboto31.43.80indirect
PyPIbotocore1.43.80indirect
PyPIcertifi2026.5.20indirect
PyPIcffi2.0.0indirect
PyPIcharset-normalizer3.4.7indirect
PyPIclick8.4.2indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.15.4indirect
PyPIcryptography50.0.0indirect
PyPIdistro1.9.0indirect
PyPIet-xmlfile2.0.0indirect
PyPIexceptiongroup1.3.1indirect
PyPIfastuuid0.14.0indirect
PyPIfilelock3.29.3indirect
PyPIfrozenlist1.8.0indirect
PyPIfsspec2026.4.0indirect
PyPIghp-import2.1.0indirect
PyPIgriffelib2.0.2indirect
PyPIh110.16.0indirect
PyPIhf-xet1.5.1indirect
PyPIhttpcore1.0.9indirect
PyPIhttpx0.28.1indirect
PyPIhuggingface-hub1.18.0indirect
PyPIhypothesis6.165.1indirect
PyPIhypothesis6.165.10indirect
PyPIidna3.18indirect
PyPIimportlib-metadata8.9.0indirect
PyPIiniconfig2.3.0indirect
PyPIinterrogate1.7.0indirect
PyPIjinja23.1.6indirect
PyPIjiter0.15.0indirect
PyPIjmespath1.1.0indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPIlibrt0.13.0indirect
PyPImarkdown3.10.2indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.3indirect
PyPImdurl0.1.2indirect
PyPImergedeep1.3.4indirect
PyPImkdocs1.6.1indirect
PyPImkdocs-autorefs1.4.4indirect
PyPImkdocs-get-deps0.2.2indirect
PyPImkdocs-material9.7.7indirect
PyPImkdocs-material-extensions1.3.1indirect
PyPImkdocstrings1.0.6indirect
PyPImkdocstrings-python2.0.4indirect
PyPImultidict6.7.1indirect
PyPImypy2.3.1indirect
PyPImypy-extensions1.1.0indirect
PyPInumpy2.2.6indirect
PyPIopenai2.41.1indirect
PyPIpackaging26.3indirect
PyPIpaginate0.5.7indirect
PyPIpathspec1.1.1indirect
PyPIpdfminer-six20260107indirect
PyPIpillow12.3.0indirect
PyPIplatformdirs4.10.0indirect
PyPIpluggy1.6.0indirect
PyPIpolars-runtime-321.43.2indirect
PyPIpropcache0.5.2indirect
PyPIpy1.11.0indirect
PyPIpy-cpuinfo9.0.0indirect
PyPIpycparser3.0indirect
PyPIpydantic-core2.48.0indirect
PyPIpydantic-settings2.15.0indirect
PyPIpygments2.21.0indirect
PyPIpymdown-extensions11.0.1indirect
PyPIpytest9.1.1indirect
PyPIpytest-benchmark5.2.3indirect
PyPIpytest-cov7.1.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-dotenv1.2.2indirect
PyPIpytz2026.2indirect
PyPIpyyaml6.0.3indirect
PyPIpyyaml-env-tag1.1indirect
PyPIreferencing0.37.0indirect
PyPIregex2026.5.9indirect
PyPIrequests2.34.2indirect
PyPIrich15.0.0indirect
PyPIrpds-py0.30.0indirect
PyPIruff0.16.1indirect
PyPIruff0.16.4indirect
PyPIs3transfer0.19.2indirect
PyPIshellingham1.5.4indirect
PyPIsix1.17.0indirect
PyPIsniffio1.3.1indirect
PyPIsortedcontainers2.4.0indirect
PyPIstarlette1.3.1indirect
PyPIstevedore5.8.0indirect
PyPItabulate0.10.0indirect
PyPItiktoken0.13.0indirect
PyPItokenizers0.23.1indirect
PyPItomli2.4.1indirect
PyPItqdm4.68.2indirect
PyPItyper0.25.1indirect
PyPItyping-extensions4.16.0indirect
PyPItyping-inspection0.4.4indirect
PyPItzdata2026.3indirect
PyPIurllib32.7.0indirect
PyPIwatchdog6.0.0indirect
PyPIyarl1.24.2indirect
PyPIzipp4.1.0indirect
Dependency advisories 0

Installing pypi:bankstatementparser@0.0.19 pulls in 13 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.