Maintainership#
Pain001 is created and maintained by Sebastien Rousseau, a London-based fintech engineering leader. Development is public: issues, pull requests, and releases are all on GitHub. Community contributions are reviewed and merged by the maintainer.
This is a single-maintainer project. That is a real concentration risk, and pretending otherwise would undermine everything else on this page. What makes the risk assessable rather than disqualifying:
- Permissive licences with no CLA barrier — the core is Apache-2.0 or MIT; any organisation can fork, patch, and redistribute indefinitely without permission.
- Reproducible pipeline — pinned dependencies, deterministic builds, 100% branch-covered tests, and a fully documented build mean a competent team can take over maintenance from the repository alone.
- No hidden infrastructure — there is no server, database, or service whose loss would strand users; everything runs from the published packages.
- Protected supply chain — signed commits, SHA-pinned CI, least-privilege tokens, and release provenance limit what a compromised account could silently ship.
Decision-making#
Feature and design decisions are made by the maintainer, in public, with rationale recorded in commits, pull requests, and changelogs. Breaking changes are documented in release notes. There is no formal steering committee; if sustained organisational adoption creates demand for one, an advisory structure is the stated path.
Funding and conflicts of interest#
Development is currently self-funded. There is no sponsor, no investor, no commercial edition, and no revenue relationship with any bank, vendor, or standards body mentioned on this site. The comparison page names commercial competitors' genuine advantages precisely because no commercial interest prevents it. If sponsorship or paid support offerings are introduced, they will be disclosed on this page before launch.
Trademark#
"Pain001" is used as a project name; no trademark registration is claimed. pain.001 itself is an ISO 20022 message identifier that belongs to the standard, not to this project.
Corrections and editorial policy#
Every research page carries a "last reviewed" date, and regulatory claims cite primary sources (SWIFT, central banks, EU institutions) rather than press coverage. Errors are corrected in place: open an issue describing the inaccuracy, and material corrections are noted in the page's git history, which is public. Dated deadlines are re-verified against sources at each review; anything scheduled beyond the current year is explicitly marked revisable.
Continuity commitments#
- Releases remain on PyPI and GitHub independent of any infrastructure this project operates.
- The website's full source, build pipeline, and content are public and rebuildable with two open-source tools.
- If the project is ever discontinued, the repositories will be archived in place — readable, forkable, and installable — rather than deleted.