sbomqs
sbomqs copied to clipboard
Support for strict specification adherence with analysis
This is to track the implementation of checking strict adherence to the specifications and reporting issues in an actionable format.
Examples:
- https://sbombenchmark.dev/score/bom-v0.4.0_rails-5.0.0.1.spdx.tv , Issues tab: finds
Creatortool without version. - https://sbombenchmark.dev/score/trivy-0.39.0_debian-bookworm-20230320-slim.spdx.tv, Issues tab: finds various Licenses in inaccurate format.
- https://sbombenchmark.dev/score/bom-v0.4.0_debian-bookworm-20230320-slim.spdx.tv, Issues tab: package download location is incorrect.
Rules to check {WIP} SPDX
- License expressions are valid as per SPDX license expression rules.
- SPDXVersion is valid
- SPDXData License is valid
- Docnaamespace is a valid URL
- ExternalDocRef is a valid reference
- LicenseList follows Major/Minor versioning
- LicenseID incorporates only valid set of characters
- Creator is limited to Person/Organization and Tool
- Timestamp is valid
- SPDXID starts with SPDXRef and has valid characters
- Package Provider (Supplier/Originator) is a valid Person/Organization string
- Package Download Location is a valid URI
Hi @surendrapathak , this has to be implemented under score command itself or other any separate command ?
I recommend a new 'validate' command for ensuring adherence to spec. The command validates basic structure and then rules setup above.
I recommend a new 'validate' command for ensuring adherence to spec. The command validates basic structure and then rules setup above.
@riteshnoronha your thoughts on this ?