Cross-reference OpenChain CRA Compliance Checklist
@PaulitePavitra is already working on this.
Since Oct 8, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation
Research direction
No specific files are named, so start with the documentation site referenced in the repo description (aboutcode.readthedocs.io) and locate the appropriate compliance/SBOM guidance pages. Add a cross-reference to the OpenChain CRA checklist and Annex D URLs in the most relevant guidance section, matching the docs style. Mark the issue done when the docs include the new references in a sensible place and the links are valid; no tests are identified in the report.
Written by the indexing model from the issue text.
Description
Hello AboutCode maintainers,
We are reaching out around the OpenChain CRA Compliance Requirements & Checklist.
We would like to cross-reference relevant CRA, SBOM, and open source compliance resources so users can find community material that helps with CRA evidence planning. Would you be open to referencing the OpenChain CRA checklist from the relevant AboutCode or ScanCode documentation/guidance, where it fits?
OpenChain CRA checklist:
https://github.com/OpenChain-Project/CRA-Compliance
Annex D external references/adoption section:
https://github.com/OpenChain-Project/CRA-Compliance/blob/main/ANNEX_D_EXTERNAL_REFERENCES_AND_ADOPTION.md
This is only a cross-reference request, not a legal endorsement or conformity assessment claim. If GitHub is not the right place for this, please point us to the best channel.
Thank you.
- Dominant language
- Batchfile
- Stars
- 316
- Forks
- 257
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aboutcode-org/aboutcode
-
scancode-next: Plan federated software supply chain data infrastructurePossibly taken @ziadhany claimed this 6 days ago. Openmaintainers-only
Difficulty 4/5 3-5 days Newbie friendliness 45/100
aboutcode-org/aboutcode#325 · 2 comments · 2 assignees ·
-
scancode-next: Improve documentation, review documentation issues and pull requestsPossibly taken @hesa claimed this 8 days ago. Openmaintainers-only
aboutcode-org/aboutcode#324 · 1 assignee ·
-
scancode-next: Gather requirements through interviews with key usersPossibly taken @hesa claimed this 8 days ago. Openmaintainers-only
Difficulty 5/5 Over a week Newbie friendliness 25/100
aboutcode-org/aboutcode#323 · 1 assignee ·
-
scancode-next: Prepare ScanCode and AboutCode workshopsPossibly taken @adaaaam claimed this 6 days ago. Openmaintainers-only
aboutcode-org/aboutcode#322 · 1 assignee ·
-
scancode-next: Create contribution documentationPossibly taken @hesa claimed this 8 days ago. Openmaintainers-only
aboutcode-org/aboutcode#321 · 1 assignee ·
All issues in aboutcode-org/aboutcode
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
tronprotocol/tips#950 · 2 comments ·
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
enhancement follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
crosspoint-reader/crosspoint-reader#4535 ·
Maintainers usually reply within 1 day
-
sweep
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
bketelsen/pi-pocket-team#277 ·
Maintainers usually reply within 1 day