philips-software / philips-software/SPDXMerge
the documentNamespace argument should be checked for compliance
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 53
- Forks
- 10
- Avg merge
- 2h 56m
- Merged PRs (30d)
- 1
Description
SPDX is very precise about the syntax of the docNamespace field
https://spdx.github.io/spdx-spec/v2.3/document-creation-information/#651-description
The current SPDXmerger accepts any content for this field as input and replicates it in the output document. The program should rather check for syntax compliance before merging the document, refuse to merge if not compliant, with an error message that allows to fix the issue and understand the expectation.
Contributor 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.
Research direction
Read the linked SPDX v2.3 documentNamespace syntax requirements, then trace the existing documentNamespace input and merge validation flow in SPDXMerge. Done means non-compliant values are rejected before merging with an error message that explains the expected syntax, while compliant values still merge successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100