Releases: RetireJS/retire.js
Releases · RetireJS/retire.js
Release list
5.7.0
[5.7.0]
Improvements
- Added CycloneDX 1.7 output:
--outputformat cyclonedxJSON1_7andcyclonedxJSON1_7_VEX. - CycloneDX 1.7 reports every resolved license, each as its own SPDX expression. Earlier spec versions only allow a single expression per component, so 1.4/1.6 output still reports the first license only.
- The CycloneDX 1.6 and 1.7 reports now include:
$schema, pointing at the schema for the emitted spec version.metadata.toolsin the object form introduced in 1.5, replacing the deprecated legacy array.metadata.component, describing the scanned path as the subject of the BOM.dependencies, linking the scan target to every detected component.evidence.identity, reporting how the version was detected (filecontent,filename,hash,ast, ...) as a CycloneDX identity technique and confidence.vulnerabilities[].detail, when the repository suppliesdetails(VEX variants only).
Bugfixes
- CycloneDX 1.6 output threw when a vulnerability in a custom
--jsrepohad nocwe, and could throw on a vulnerability with noidentifiers.
5.6.0
[5.6.0]
Improvements
- Report when repository certificate errors are ignored (
--insecure): asignoreRepositoryCertificateErrorsin the JSON report, and as aretirejs:ignore-repository-certificate-errorsentry undermetadata.propertiesin all CycloneDX reports. The entry is only present when the option is set.
5.5.0
[5.5.0]
Improvements
- Include the vulnerability repositories used for the scan in the output: as
vulnerabilityRepositoriesin the JSON report, and asretirejs:vulnerability-repositoryentries undermetadata.propertiesin all CycloneDX reports. - CycloneDX 1.6 VEX output now identifies Retire.js as the source of each vulnerability and rating, including the repository URL when a single repository is used.
Bugfixes
- CycloneDX 1.6 VEX output was not schema valid:
ratings[].sourcewas a string rather than an object, and version ranges were reported asaffects[].rangerather than nested underaffects[].versions[].