You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
L<SBOM::CycloneDX> is a library for generate valid CycloneDX BOM file.
330
+
L<SBOM::CycloneDX> is a library for generate valid OWASP CycloneDX BOM file.
331
331
332
-
CycloneDX (ECMA-424) is a modern standard for the software supply chain. At its core,
333
-
CycloneDX is a general-purpose Bill of Materials (BOM) standard capable of
334
-
representing software, hardware, services, and other types of inventory.
335
-
The CycloneDX standard began in 2017 in the Open Worldwide Application Security
336
-
Project (OWASP) community. CycloneDX is an OWASP flagship project, has a formal
337
-
standardization process and governance model, and is supported by the global
338
-
information security community.
332
+
OWASP CycloneDX (ECMA-424) is a modern standard for the software supply chain.
333
+
At its core, CycloneDX is a general-purpose Bill of Materials (BOM) standard
334
+
capable of representing software, hardware, services, and other types of
335
+
inventory. The CycloneDX standard began in 2017 in the Open Worldwide
336
+
Application Security Project (OWASP) community. CycloneDX is an OWASP flagship
337
+
project, has a formal standardization process and governance model, and is
338
+
supported by the global information security community.
339
339
340
340
CycloneDX far exceeds the L<Minimum Elements for Software Bill of Materials|https://www.ntia.gov/files/ntia/publications/sbom_minimum_elements_report.pdf>
341
341
as defined by the L<National Telecommunications and Information Administration (NTIA)|https://www.ntia.gov/>
@@ -661,6 +661,8 @@ This is the class hierarchy of the L<SBOM::CycloneDX> distribution.
661
661
662
662
=item* L<SBOM::CycloneDX::List>
663
663
664
+
=item* L<SBOM::CycloneDX::Lite>
665
+
664
666
=item* L<SBOM::CycloneDX::Timestamp>
665
667
666
668
=item* L<SBOM::CycloneDX::Util>
@@ -676,6 +678,26 @@ and implements the following new ones.
676
678
677
679
=itemSBOM::CycloneDX->new( %PARAMS )
678
680
681
+
Create new CycloneDX instance.
682
+
683
+
my $bom = SBOM::CycloneDX->new(
684
+
spec_version => '1.5',
685
+
version => 1,
686
+
serial_number => $serial_number
687
+
);
688
+
689
+
$bom->components->add($component);
690
+
691
+
say $bom;
692
+
693
+
=item$bom->spec_version
694
+
695
+
The version of the CycloneDX specification the BOM conforms to.
696
+
697
+
Default version is B<1.7>.
698
+
699
+
$bom->spec_version('1.5');
700
+
679
701
=item$bom->version
680
702
681
703
Whenever an existing BOM is modified, either manually or through
@@ -684,6 +706,15 @@ incremented by 1. When a system is presented with multiple BOMs
684
706
with identical serial numbers, the system SHOULD use the most
685
707
recent version of the BOM. The default version is '1'.
686
708
709
+
=item$bom->serial_number
710
+
711
+
Every BOM generated SHOULD have a unique serial number, even if the contents of
712
+
the BOM have not changed over time. If specified, the serial number must
713
+
conform to L<RFC 4122|https://www.ietf.org/rfc/rfc4122.html>. Use of serial
0 commit comments