ICSbom

This application downloads data from the nvd api and creates a local Vulnerability Database.
If the database already exists it will be updated with changes since your last update.
It then uses that data to check the provided sbom file and give you a Vulnerability report. This tool is used by SBOMGuard ICS' open source, web-based cloud service.
Usage
icsbom [OPTIONS] INPUTFILE
Options
-h Help
- Shows the Application Help
--log set the log level of the application
- Valid levels:
NOTSET,DEBUG,INFO,WARNING,ERROR,CRITICAL - Default value:
WARNING
--cache_dir the path where the application will write
- Any path you can Read and Write to is valid
- Default:
$HOME/.cache/icsbom
--api_key API_KEY
- Use the API_KEY to access the NVD Api
- A Key is NOT required, providing one allows more api queries per second
- If the file
$CACHE_DIR/api_key.txtexists its contents will be used as the api key
--save_keySave the api key used by the api_key option
- Writes the used api key to
api_key.txtin the Cache Directory
--db_file filename for the database
- The filename used will be written into the cache directory
- Default:
nvd_v#.dbWhere # is the revision of the database format.
-o Output file to write
- File format depending on extention of the output file
- Valid extentions are *.txt, *.csv, *.html, *.json.vex
-i, --interactive Enter interactive mode after matching
-s, --skip-db-update
- This option will skip the database update and go right to scanning the file using the existing database.
--filter_file FILTER_FILE
- Override the builtin filters with the contents of
FILTER_FILE FILTER_FILEmust be a json file
--write_filters FILTER_OUT
- Write the default filters to a file
FILTER_OUTshould end in .json- Useful to adjust the filters for your projects needs.
-t TAR_DIR_PATTERN
- Used when the input file is a tarball crated by a yocto build process
- process the contents of the subdir matching the TAR_DIR_PATTERN
- Valid Patterns: recipies, packages
- Default: packages
INPUTFILE The input file
- File can be a sbom or tarball
Requirements
requires ics_sbom_libs
Metadata
Release files for icsbom 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| icsbom-1.2.0.tar.gz | 37.5 kB | Without provenance | Details for icsbom-1.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| icsbom-1.2.0-py3-none-any.whl | Python 3 | none | any | Details for icsbom-1.2.0-py3-none-any.whl |
Total release size: 77.3 kB
Release files / icsbom-1.2.0.tar.gz
| Download URL | icsbom-1.2.0.tar.gz |
|---|---|
| Size | 37.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9937ad4fe71524a8b9f2e553f7301debcdad38ae10c3f95844ed37e671553e98
|
|
BLAKE2b-256 checksum How to use checksums |
ac65df97d1fa950557988a6f8b5a9e10120712c1fb53bd11ca2fc79341bec1f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.21
|
Release files / icsbom-1.2.0-py3-none-any.whl
| Download URL | icsbom-1.2.0-py3-none-any.whl |
|---|---|
| Size | 39.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d04e83fe310ae306e9044c149313ebacc622527dce151b5b4c87b2cf7862f838
|
|
BLAKE2b-256 checksum How to use checksums |
b148d1ccabfdff1d4875f5381a75e7e4e5a1538645547eb32f9e69da1e9bf822
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.21
|
Security for icsbom 1.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.