Skip to content

use of the word unknown for default values #75

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ptdropper opened this issue Apr 1, 2025 · 1 comment
Open

use of the word unknown for default values #75

ptdropper opened this issue Apr 1, 2025 · 1 comment

Comments

@ptdropper
Copy link
Contributor

Default values are assigned to the value "unknown" for input arguments. Review this feature for possible change if necessary.

@jkowalleck
Copy link
Member

jkowalleck commented Apr 1, 2025

all thse switches are optional, right, and they default to 'unknown'.

parser.add_argument('-i', action='store', dest='input_file', default='manifest.csv',
help='comma separated value (csv) file of buildroot manifest data')
parser.add_argument('-o', action='store', dest='output_file', default='buildroot_IOT_sbom',
help='SBOM output file name for json and xml')
parser.add_argument('-n', action='store', dest='product_name', default='unknown', help='name of the product')
parser.add_argument('-v', action='store', dest='product_version', default='unknown', help='product version string')
parser.add_argument('-m', action='store', dest='manufacturer_name', default='unknown',
help='name of product manufacturer')
parser.add_argument('-c', action='store', dest='cpe_input_file', default='unknown',
help='cpe file from make show-info')

having all thse "unknown' in an SBOM, especially in optional fields and properties - makes no sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants