Package: ibcyclonediff
IBCycloneDiffIBCycloneDiff is a tool to compare two Software Bill of Materials (SBOM) files and
reports the differences. It supports SBOMs created in bothSPDXandCycloneDXformats.The following differences are detected:Package version changesPackage licence changesPackage removedPackage addedInstallationTo install use the following command:pip install ibcyclonediffThe tool requires Python 3 (3.7+). It is recommended to use a virtual python environment especially
if you are using different versions of python.virtualenvis a tool for setting up virtual python environments which
allows you to have all the dependencies for the tool set up in a single environment, or have different environments set
up for testing using different versions of Python.Usageusage: ibcyclonediff [-h] [--sbom {auto,spdx,cyclonedx}] [--exclude-license] [-d] [-o OUTPUT_FILE] [-V] FILE1 FILE2

SBOMDiff compares two Software Bill of Materials and reports the differences.

positional arguments:
  FILE1                 first SBOM file
  FILE2                 second SBOM file

optional arguments:
  -h, --help            show this help message and exit
  -V, --version         show program's version number and exit

Input:
  --sbom {auto,spdx,cyclonedx}
                        specify type of sbom to compare (default: auto)
  --exclude-license     suppress reporting differences in the license of components

Output:
  -d, --debug           show debug information
  -o OUTPUT_FILE, --output-file OUTPUT_FILE
                        output filename (default: output to stdout)OperationThe--sbomoption is used to specify the format of the SBOM files. The default is for the type and format of the SBOM to be
automatically detected based on the extension of the file name.SBOM TypeVersionExtensionFormatSPDX2.3.spdxTagValueSPDX2.3.spdx.rdfRDFSPDX2.3.spdx.jsonJSONSPDX2.3.spdx.ymlYAMLSPDX2.3.spdx.yamlYAMLSPDX2.3.spdx.xmlXMLCycloneDX1.4.xmlXMLCycloneDX1.4.jsonJSONDetails of the formats for each of the supported SBOM formats are available forSPDXandCycloneDX.For SPDX SBOM files, it is assumed that the name of a Package precedes the version information for the package.
Only modules with a package name and associated version information shall be processed.The--output-fileoption is used to control the destination of the output generated by the tool. The
default is to report to the console but can be stored in a file (specified using--output-fileoption).Implementation NotesThe following design decisions have been made in processing the SBOM files:The comparison only considers package names, package versions and licenses. Other differences are not detected.It is assumed that the SBOM is valid and contains syntactically valid data. Invalid files will be silently ignored.SBOMs which do not match the format of the SBOM to be processed when specified using the--sbomoption is likely to result in incorrect differences being reported.In SPDX format, the tool assumes that the name of a package is followed by the version and license of the package.If there are multiple instances of a package included in the SBOM, only the first instance will be processed.If a license cannot be detected, the tool uses 'NOT FOUND' as the license to be used in the difference comparison.A non-zero return value indicates that differences were detected.Sample Output[LICENSE] glibc: License changed from GPL-2.0-only to (LGPL-2.0-only OR LicenseRef-3)
[LICENSE] Saxon: License changed from Apache-2.0 to MPL-1.0
[VERSION] rich: Version changed from 11.0.0 to 12.5.1
[REMOVED] colorama: Module removed (Version 0.4.4)
[VERSION] pygments: Version changed from 2.11.2 to 2.13.0

Summary
-------
Version changes:  2
License changes:  2
Removed packages: 1
New packages:     0LicenseLicensed under the Apache 2.0 Licence.LimitationsThis tool is meant to support software development and security audit functions. However the usefulness of the tool is dependent on the SBOM data
which is provided to the tool. Unfortunately, the tool is unable to determine the validity or completeness of such a SBOM file; users of the tool
are therefore reminded that they should assert the quality of any data which is provided to the tool.Feedback and ContributionsBugs and feature requests can be made via GitHub Issues.