Add Zyphe AML Enforcement Tracker to Regulatory Data Sources - #69
Open
michelangelo-zyphe wants to merge 1 commit into
Open
Add Zyphe AML Enforcement Tracker to Regulatory Data Sources#69michelangelo-zyphe wants to merge 1 commit into
michelangelo-zyphe wants to merge 1 commit into
Conversation
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
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 an open, primary-source-cited dataset of AML, sanctions, GDPR and identity-breach
enforcement actions to the Regulatory Data Sources section.
Why it fits the section: the existing entries cover programmatic access to filings and
registries for KYC/AML due diligence. This is the enforcement side of the same workflow:
what regulators actually penalised, with the announcement linked per row, usable as
reference data for risk assessments and control testing.
normalised USD value, date, summary, primary source URL
rather than a single region. The Contents TOC indexes only h2 and h3, so no TOC change
Ran
npx awesome-lintagainst the modified readme before opening. The new entry is clean.It does surface one pre-existing error unrelated to this change: the LLM ISO27001 entry
at line 191 has no closing period. Happy to fix that here too if you would like it folded in.
Disclosure: I maintain the dataset.