DORA evidence map#
The EU Digital Operational Resilience Act (Regulation (EU) 2022/2554) asks a financial entity to manage the risk of the ICT services and software it uses. This page maps the questions a reviewer typically asks about a third-party component to the evidence Pain001 publishes.
This is not a claim of compliance. DORA obligations fall on the financial entity, not on an open-source project. Pain001 has no contract with you, offers no service, and is not certified against DORA or any other standard. The map only shows where to find evidence for your own assessment.
What the reviewer asks |
Evidence |
Where |
|---|---|---|
What does the component do, and what data does it touch? |
Data-handling statement: runs on your infrastructure, no hosted service, no telemetry, network use only by explicit command or configuration |
|
Is there a provider relationship or contract? |
None. Free open-source software under Apache-2.0 or MIT; no paid tier, no SLA, no commercial partners |
|
Where is data processed and stored? |
Only where you run it; Pain001 operates no servers |
|
What does the component depend on? |
CycloneDX SBOM and licence report for every release |
|
Can we verify what we install? |
Signed tags, SHA256SUMS, GitHub build attestations, SLSA Build Level 3 provenance, PyPI trusted publishing with attestations |
|
How are vulnerabilities reported and handled? |
Private disclosure through GitHub, published advisories, acknowledgement goal of 5 working days (a goal, not a guarantee) |
|
How is the software kept secure? |
CI on every change: pip-audit, Bandit, CodeQL, secret scanning with push protection, Dependabot, OpenSSF Scorecard; 100% line and branch test coverage |
|
What maintenance can we expect? |
Fixes ship in the next release and arrive by upgrading; no long-term support line at present; no SLA |
|
What happens if the maintainer stops? |
Permissive licence, public source and history, a documented release process in CI, a written continuity plan |
|
Can we exit or replace it? |
Outputs are standard ISO 20022 XML validated against the official schemas; inputs are CSV, SQLite, JSON and Parquet; nothing is proprietary or hosted |
|
Can we audit it? |
The full source, tests, CI logs and design decisions (ADRs) are public |
|
Are there subcontractors? |
No. Third-party code is listed in the SBOM; build and hosting run on GitHub Actions and PyPI |
SBOM, Verify a release |
How is incident information shared? |
Fixed vulnerabilities are published as GitHub Security Advisories, mirrored to OSV and the PyPI advisory database |