Add dora-lei-check (DORA Register of Information — LEI/GLEIF pre-submission check) - #64
Open
kakoullig-hue wants to merge 1 commit into
Open
Add dora-lei-check (DORA Register of Information — LEI/GLEIF pre-submission check)#64kakoullig-hue wants to merge 1 commit into
kakoullig-hue wants to merge 1 commit into
Conversation
A local pre-submission check for the LEIs in a DORA Register of Information: resolves each LEI against the live GLEIF register and names the EBA rule code the failure will trigger.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds dora-lei-check under Tools & Platforms → Open Source Platforms, next to the existing DORA entries.
What it does. The LEI check in a DORA Register of Information is an external lookup: the ESAs resolve every LEI against the live GLEIF register after you submit. A lapsed LEI is perfectly well formed — it passes the ISO 17442 checksum and offline XBRL validation — and is still a hard rejection. This runs that lookup locally beforehand and names the EBA rule code each failure will trigger (VR_2, VR_12, VR_23, VR_71, VR_77).
Why it is not a duplicate of the DORA ROI Validator already listed. That one covers the schema/data-quality checks and does not perform a GLEIF lookup. This one does only the identifier layer. They complement each other rather than overlap.
Privacy. A Register of Information maps an entire ICT third-party estate. The tool reads it locally and sends only the public 20-character LEI codes;
--offlinewith GLEIF's daily golden-copy file sends nothing at all.MIT, Python 3.10+, zero dependencies, on PyPI, 66 tests.