Include FSCT3 information in README #226
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add information about Framing Software Component Transparency (FSCT) and its experimental support - Update command line usage and examples - Use `sbomcheck` in the examples - Add option `--comply` - Also fix Markdown warnings - The use of both `-` and `*` for list (fixed to use only `-`) - The doc should started with H1 heading (fixed by moving badges to show just immediately under the title heading) - The doc should have only one H1 heading (fixed by making others to H2) Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
sbomcheckin the examples--comply-and*for list (fixed to use only-)To should only get merged after PR #224 is sorted.
A review is also requested to look at the use of these words:
"comply", "compliance", "conformance", "standard", "document", "specification"
as I am not sure about the preference and the specific/different meaning that they may have within the project.