Help keep the register current and useful.
The register is open and built to be built on. It stays valuable only if it tracks the sources it maps and if practitioners adopt it as a shared reference. Below is where volunteers can help; each item is a real, self-contained piece of work.
Extend the framework crosswalk
Map the register to more standards and control frameworks, so a DARR risk traces straight into the controls a team already runs. First up: the Cloud Security Alliance AI Controls Matrix (AICM), 247 control objectives across 18 domains. Good follow-ons include further ISO/IEC standards, sector regulations, and national AI frameworks.
Automate freshness with CI/CD
Every source the register draws on is versioned and public. Build pipelines that watch these upstreams and open a pull request when one changes, so the crosswalk never falls behind the frameworks it maps.
Make DARR a common language for developers
Help AI tool builders and application teams reference DARR risk ids (MR-001 to MR-082) as a shared vocabulary, in scanners, evaluations, model cards, and governance tooling. Linters, plugins, SDK mappings, and any integration that emits or consumes DARR ids are welcome.
Grow the community
Connect the register with the groups working the same problem, so each mapping is reviewed by the people who maintain the source it points to. Know a community that should be involved? Open an issue and say so.
Improve the register itself
Corrections, new sub-risks, sharper descriptions, and additional cross-checks. Every risk has a stable id and a permanent page; propose changes against the open dataset.
Ready to pick something up?
Open an issue or a pull request on GitHub to claim a roadmap item or propose another, or contact MindXO. Contributions are licensed CC BY 4.0, the same as the register.