ossf/sbom-everywhere
Improve Software Bill of Materials (SBOM) tooling and training to encourage adoption
VueApache-2.0
Issues
- 0
- 3
[catalog] No description of `Language` field
#63 opened by funnelfiasco - 0
Create a getting involved guide
#70 opened by joshbressers - 0
- 1
Create a getting started guide
#68 opened by joshbressers - 0
Please add an Analyze "Bubble"
#59 opened by rjb4standards - 2
[catalog] No description of License field
#64 opened by funnelfiasco - 0
Create some issue templates for new issues
#58 opened by joshbressers - 0
- 3
being specific on directory structure
#33 opened by idunbarh - 4
Using SBOM Everywhere to amplify guidance through other public workstreams
#46 opened by joshbressers - 7
SBOM Naming
#34 opened by anthonyharrison - 3
SBOM naming: optional mandatory?
#40 opened by david-a-wheeler - 2
SBOM Naming - SBOMs required for all ecosystems?
#44 opened by idunbarh - 1
Naming document next steps
#38 opened by joshbressers - 5
specification for sbom filename
#32 opened by ctcpip - 11
SBOM standards for ESM Modules in the JS Ecosystem
#24 opened by Grunet - 15
What are our barriers to adoption?
#13 opened by joshbressers - 12
Better document goals and purpose
#12 opened by joshbressers - 4
Document SBOM use cases
#3 opened by joshbressers - 18
- 1
SBOM tools test suite
#22 opened by tsteenbe - 5
Create SBOM one page overview
#4 opened by joshbressers - 2
Consider dependency graphing tooling that can produce standardized output for downstream tools
#21 opened by mrutkows - 0
Tooling output standards
#20 opened by anoncam - 2
- 3
- 0
Create CODEOWNERS for repo
#9 opened by anoncam - 2
Funding the SPDX python library
#6 opened by joshbressers - 2
Document the current work in flight
#1 opened by joshbressers - 1
Figure out github repo permissions
#7 opened by joshbressers - 3
Protect the main branch
#8 opened by joshbressers