Add ExploitCatalogVulnAssessmentRelationship to the FullSpdxV3Example
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Java
- Stars
- 101
- Forks
- 46
- Avg merge
- 9h 43m
- Merged PRs (30d)
- 8
Description
This was not completed due to an incompatibility between the current published JSON schema and the generated Java code.
Specifically, the Java code has a property securityLocator while the schema has the property named locator.
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
Start with FullSpdxV3Example and compare the generated Java property's securityLocator with the published JSON schema's locator. Resolve the incompatibility and add the ExploitCatalogVulnAssessmentRelationship to the example, verifying that the example and schema agree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100