sbom4python 0.12.5__py3-none-any.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- sbom4python/__init__.py +2 -0
- sbom4python/cli.py +215 -0
- sbom4python/license.py +54 -0
- sbom4python/license_data/spdx_licenses.json +6258 -0
- sbom4python/scanner.py +788 -0
- sbom4python/version.py +4 -0
- sbom4python-0.12.5.dist-info/LICENSE +201 -0
- sbom4python-0.12.5.dist-info/METADATA +192 -0
- sbom4python-0.12.5.dist-info/RECORD +14 -0
- sbom4python-0.12.5.dist-info/WHEEL +5 -0
- sbom4python-0.12.5.dist-info/entry_points.txt +2 -0
- sbom4python-0.12.5.dist-info/top_level.txt +1 -0
- test/__init__.py +2 -0
- test/test_license.py +62 -0
sbom4python/version.py
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
|
@@ -0,0 +1,192 @@
|
|
|
1
|
+
Metadata-Version: 2.1
|
|
2
|
+
Name: sbom4python
|
|
3
|
+
Version: 0.12.5
|
|
4
|
+
Summary: SBOM generator for Python modules
|
|
5
|
+
Home-page: https://github.com/anthonyharrison/sbom4python
|
|
6
|
+
Author: Anthony Harrison
|
|
7
|
+
Author-email: anthony.p.harrison@gmail.com
|
|
8
|
+
Maintainer: Anthony Harrison
|
|
9
|
+
Maintainer-email: anthony.p.harrison@gmail.com
|
|
10
|
+
License: Apache-2.0
|
|
11
|
+
Keywords: security,tools,SBOM,DevSecOps,SPDX,CycloneDX
|
|
12
|
+
Classifier: Development Status :: 4 - Beta
|
|
13
|
+
Classifier: Intended Audience :: Developers
|
|
14
|
+
Classifier: License :: OSI Approved :: Apache Software License
|
|
15
|
+
Classifier: Natural Language :: English
|
|
16
|
+
Classifier: Operating System :: OS Independent
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.7
|
|
18
|
+
Classifier: Programming Language :: Python :: 3.8
|
|
19
|
+
Classifier: Programming Language :: Python :: 3.9
|
|
20
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
21
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
22
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
23
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
24
|
+
Classifier: Programming Language :: Python :: Implementation :: CPython
|
|
25
|
+
Classifier: Programming Language :: Python :: Implementation :: PyPy
|
|
26
|
+
Requires-Python: >=3.7
|
|
27
|
+
Description-Content-Type: text/markdown
|
|
28
|
+
License-File: LICENSE
|
|
29
|
+
Requires-Dist: lib4package (>=0.3.3)
|
|
30
|
+
Requires-Dist: lib4sbom (>=0.8.0)
|
|
31
|
+
Requires-Dist: sbom2dot (>=0.3.0)
|
|
32
|
+
Requires-Dist: sbom4files (>=0.4.4)
|
|
33
|
+
Requires-Dist: importlib-metadata (>=3.6) ; python_version < "3.10"
|
|
34
|
+
Requires-Dist: toml ; python_version < "3.11"
|
|
35
|
+
|
|
36
|
+
# SBOM4Python
|
|
37
|
+
|
|
38
|
+
The SBOM4Python is a free, open source tool to generate a
|
|
39
|
+
SBOM (Software Bill of Materials) for an installed Python module in a number of formats including
|
|
40
|
+
[SPDX](https://www.spdx.org) and [CycloneDX](https://www.cyclonedx.org).
|
|
41
|
+
It identifies all of the dependent components which are
|
|
42
|
+
explicity defined (typically via requirements.txt file) or implicitly as a
|
|
43
|
+
hidden dependency.
|
|
44
|
+
|
|
45
|
+
It can also be used to create a SBOM from a requirements.txt file. In this case no transitive components will be identified.
|
|
46
|
+
|
|
47
|
+
It is intended to be used as part of a continuous integration system to enable accurate records of SBOMs to be maintained
|
|
48
|
+
and also to support subsequent audit needs to determine if a particular component (and version) has been used.
|
|
49
|
+
|
|
50
|
+
## Installation
|
|
51
|
+
|
|
52
|
+
To install use the following command:
|
|
53
|
+
|
|
54
|
+
`pip install sbom4python`
|
|
55
|
+
|
|
56
|
+
Alternatively, just clone the repo and install dependencies using the following command:
|
|
57
|
+
|
|
58
|
+
`pip install -U -r requirements.txt`
|
|
59
|
+
|
|
60
|
+
The tool requires Python 3 (3.7+). It is recommended to use a virtual python environment especially
|
|
61
|
+
if you are using different versions of python. `virtualenv` is a tool for setting up virtual python environments which
|
|
62
|
+
allows you to have all the dependencies for the tool set up in a single environment, or have different environments set
|
|
63
|
+
up for testing using different versions of Python.
|
|
64
|
+
|
|
65
|
+
### Issues with Installation
|
|
66
|
+
|
|
67
|
+
If you get the following error
|
|
68
|
+
|
|
69
|
+
`ImportError: failed to find libmagic. Check your installation`
|
|
70
|
+
|
|
71
|
+
This is because of a mismatch with the installation of the magic library. To resolve, please issue the following commands depending on your environment
|
|
72
|
+
|
|
73
|
+
#### Windows
|
|
74
|
+
|
|
75
|
+
```bash
|
|
76
|
+
pip uninstall python-magic
|
|
77
|
+
pip uninstall python-magic-bin
|
|
78
|
+
|
|
79
|
+
pip install python-magic
|
|
80
|
+
pip install python-magic-bin
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
#### Linux based system
|
|
84
|
+
|
|
85
|
+
Install `libmagic` using a package manager, for example
|
|
86
|
+
|
|
87
|
+
```bash
|
|
88
|
+
apt install libmagic-dev
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
#### MacOS
|
|
92
|
+
|
|
93
|
+
Install `libmagic` using a package manager, for example
|
|
94
|
+
|
|
95
|
+
```bash
|
|
96
|
+
brew install libmagic
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
## Usage
|
|
100
|
+
|
|
101
|
+
```bash
|
|
102
|
+
usage: sbom4python [-h] [-m MODULE] [-r REQUIREMENT] [--system] [--exclude-license] [--include-file] [--include-service] [--use-pip] [--python PYTHON] [-d] [--sbom {spdx,cyclonedx}] [--format {tag,json,yaml}] [-o OUTPUT_FILE]
|
|
103
|
+
[-g GRAPH] [-V]
|
|
104
|
+
|
|
105
|
+
SBOM4Python generates a Software Bill of Materials for the specified installed Python module identifying all of the dependent components which are explicity defined (typically via requirements.txt file) or implicitly as a hidden
|
|
106
|
+
dependency.
|
|
107
|
+
|
|
108
|
+
options:
|
|
109
|
+
-h, --help show this help message and exit
|
|
110
|
+
-V, --version show program's version number and exit
|
|
111
|
+
|
|
112
|
+
Input:
|
|
113
|
+
-m MODULE, --module MODULE
|
|
114
|
+
identity of python module
|
|
115
|
+
-r REQUIREMENT, --requirement REQUIREMENT
|
|
116
|
+
name of requirements file
|
|
117
|
+
--system include all installed python modules within system
|
|
118
|
+
--exclude-license suppress detecting the license of components
|
|
119
|
+
--include-file include reporting files associated with module
|
|
120
|
+
--include-service include reporting of endpoints
|
|
121
|
+
--use-pip use pip for package management
|
|
122
|
+
--python PYTHON use specified Python interpreter for pip
|
|
123
|
+
|
|
124
|
+
Output:
|
|
125
|
+
-d, --debug add debug information
|
|
126
|
+
--sbom {spdx,cyclonedx}
|
|
127
|
+
specify type of sbom to generate (default: spdx)
|
|
128
|
+
--format {tag,json,yaml}
|
|
129
|
+
specify format of software bill of materials (sbom) (default: tag)
|
|
130
|
+
-o OUTPUT_FILE, --output-file OUTPUT_FILE
|
|
131
|
+
output filename (default: output to stdout)
|
|
132
|
+
-g GRAPH, --graph GRAPH
|
|
133
|
+
filename for dependency graph
|
|
134
|
+
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
## Operation
|
|
138
|
+
|
|
139
|
+
The `--module` option is used to identify the Python module. The `--system` option is used to indicate that the SBOM is to include all installed
|
|
140
|
+
Python modules.
|
|
141
|
+
|
|
142
|
+
The `--requirement` option is used to create an SBOM from a pylock.toml, requirements.txt, pyproject.toml, setup.cfg or setup.py file.
|
|
143
|
+
Whilst the filenames may be different e.g. requirements_test.txt can be specified, it is the file extension which determines the identification of
|
|
144
|
+
the dependencies. Using this option will normally result in no transitive dependencies being identified.
|
|
145
|
+
|
|
146
|
+
One of `--module`, `--requirement` or `--system` must be specified. If multiple options are specified, the order of priority is `--module`, `--system` and `--requirement`.
|
|
147
|
+
|
|
148
|
+
The `--python` option is to speficy the path to a different python installation e.g. when using venv. This option should also be used with the `--use-pip` option.
|
|
149
|
+
|
|
150
|
+
The `--sbom` option is used to specify the format of the generated SBOM (the default is SPDX). The `--format` option
|
|
151
|
+
can be used to specify the formatting of the SBOM (the default is Tag Value format for a SPDX SBOM). JSON format is supported for both
|
|
152
|
+
SPDX and CycloneDX SBOMs).
|
|
153
|
+
|
|
154
|
+
The `--output-file` option is used to control the destination of the output generated by the tool. The
|
|
155
|
+
default is to report to the console but can be stored in a file (specified using `--output-file` option).
|
|
156
|
+
|
|
157
|
+
The tool attempts to determine the license of each module. This can be suppressed using the `--exclude-license` option in
|
|
158
|
+
which case all licences are reported as 'NOASSERTION'.
|
|
159
|
+
|
|
160
|
+
The tool can optionally include the files associated with the installed module. This can be specified using the `--include-file` option. As the filenames are
|
|
161
|
+
relative to the directory in which the tool is invoked, it is recommended that the tool is launched in a directory where the source files are available.
|
|
162
|
+
|
|
163
|
+
The `--graph` option is used to generate a dependency graph of the components within the SBOM. The format of the graph
|
|
164
|
+
file is compatible with the [DOT language](https://graphviz.org/doc/info/lang.html) used by the
|
|
165
|
+
[GraphViz](https://graphviz.org/) application.
|
|
166
|
+
|
|
167
|
+
## Licence
|
|
168
|
+
|
|
169
|
+
Licenced under the Apache 2.0 Licence.
|
|
170
|
+
|
|
171
|
+
The tool uses a local copy of the [SPDX Licenses List](https://github.com/spdx/license-list-data) which is released under
|
|
172
|
+
[Creative Commons Attribution 3.0 (CC-BY-3.0)](http://creativecommons.org/licenses/by/3.0/).
|
|
173
|
+
|
|
174
|
+
## Limitations
|
|
175
|
+
|
|
176
|
+
This tool is meant to support software development and security audit functions. However the usefulness of the tool is dependent on the SBOM data
|
|
177
|
+
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
|
|
178
|
+
are therefore reminded that they should assert the quality of any data which is provided to the tool.
|
|
179
|
+
|
|
180
|
+
The `--requirement` option will only report the package version for pinned dependencies.
|
|
181
|
+
|
|
182
|
+
When processing and validating licenses, the application will use a set of synonyms to attempt to map some license identifiers to the correct [SPDX License Identifiers](https://spdx.org/licenses/). However, the
|
|
183
|
+
user of the tool is reminded that they should assert the quality of any data which is provided by the tool particularly where the license identifier has been modified.
|
|
184
|
+
|
|
185
|
+
Whilst [PURL](https://github.com/package-url/purl-spec) and [CPE](https://nvd.nist.gov/products/cpe) references are automatically generated for each Python module, the accuracy
|
|
186
|
+
of such references cannot be guaranteed as they are dependent on the validity of the data associated with the Python module.
|
|
187
|
+
|
|
188
|
+
Network access is required to populate some of the package metadata. If this is not available, a limited amount of package metadata will be included.
|
|
189
|
+
|
|
190
|
+
## Feedback and Contributions
|
|
191
|
+
|
|
192
|
+
Bugs and feature requests can be made via GitHub Issues.
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
sbom4python/__init__.py,sha256=UXoScW29szuUhsP-AvPIJLEPeX_U31M1gxYUSooemy8,76
|
|
2
|
+
sbom4python/cli.py,sha256=dkuA_VGfvQbiluCkkEIgK7wzAP-a4oX6P72cc26SRqc,6168
|
|
3
|
+
sbom4python/license.py,sha256=5XRAwuvRNd4nt2T7shMQr3jUo9dEMstZF5Hov3IzvIw,1820
|
|
4
|
+
sbom4python/scanner.py,sha256=lTY1tIyYv5FfaEld1d3gAN9pr1Hzxu98W4H9R0BuvOY,34296
|
|
5
|
+
sbom4python/version.py,sha256=RlmE_Ji3D2uVSbml9hgrRrfFoWUxFHxh7SCmXrmr9ug,101
|
|
6
|
+
sbom4python/license_data/spdx_licenses.json,sha256=mj836L9ndKZMZBORMqUkjzP0n23RRhleuBdXlER0pVE,222585
|
|
7
|
+
test/__init__.py,sha256=Jdm3si-iktHDtKWwHpYgVfLYF-l1bE6TQDJASgkVpQU,75
|
|
8
|
+
test/test_license.py,sha256=stWDum_UwVGZZsTyjrVICgBh3Azb6dUqZIMK_DUQe4s,1976
|
|
9
|
+
sbom4python-0.12.5.dist-info/LICENSE,sha256=xx0jnfkXJvxRnG63LTGOxlggYnIysveWIZ6H3PNdCrQ,11357
|
|
10
|
+
sbom4python-0.12.5.dist-info/METADATA,sha256=B5td4HuOnONcOl3R0Ci-61oNmXv6U_9CP-slZkqPMbo,8984
|
|
11
|
+
sbom4python-0.12.5.dist-info/WHEEL,sha256=2wepM1nk4DS4eFpYrW1TTqPcoGNfHhhO_i5m4cOimbo,92
|
|
12
|
+
sbom4python-0.12.5.dist-info/entry_points.txt,sha256=_83UfxTjM06vaj0t1XlOO3YmniXkM1jsyvTdkee7tmk,53
|
|
13
|
+
sbom4python-0.12.5.dist-info/top_level.txt,sha256=udvkgWvzv7RUbiqpZ-ANkgXwwk5fFhl2LiQkh8dJGQg,12
|
|
14
|
+
sbom4python-0.12.5.dist-info/RECORD,,
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
sbom4python
|
test/__init__.py
ADDED
test/test_license.py
ADDED
|
@@ -0,0 +1,62 @@
|
|
|
1
|
+
import pytest
|
|
2
|
+
|
|
3
|
+
from sbom4python.scanner import SBOMScanner
|
|
4
|
+
from lib4sbom.license import LicenseScanner
|
|
5
|
+
|
|
6
|
+
|
|
7
|
+
class TestLicense:
|
|
8
|
+
@pytest.mark.parametrize(
|
|
9
|
+
"expression, result",
|
|
10
|
+
(
|
|
11
|
+
("bad", "NOASSERTION"),
|
|
12
|
+
("", "NOASSERTION"),
|
|
13
|
+
("NONE", "NONE"),
|
|
14
|
+
("NOASSERTION", "NOASSERTION"),
|
|
15
|
+
("MIT and Apache-2.0", "MIT and Apache-2.0"),
|
|
16
|
+
("MIT and Apache", "MIT and Apache-2.0"),
|
|
17
|
+
("LicenseRef-100", "LicenseRef-100"),
|
|
18
|
+
("ASL 2.0", "Apache-2.0"),
|
|
19
|
+
("Apache", "Apache-2.0"),
|
|
20
|
+
("MIT", "MIT"),
|
|
21
|
+
),
|
|
22
|
+
)
|
|
23
|
+
def test_license(self, expression, result):
|
|
24
|
+
test_item = SBOMScanner(debug=True)
|
|
25
|
+
license = test_item.process_license_expression(expression)
|
|
26
|
+
assert license == result
|
|
27
|
+
|
|
28
|
+
# def test_find_license_id(self, license, result):
|
|
29
|
+
# test_item = SBOMScanner(debug=True)
|
|
30
|
+
# license_id = test_item.license_ident(license)
|
|
31
|
+
# assert license_id == result
|
|
32
|
+
|
|
33
|
+
# @pytest.mark.parametrize(
|
|
34
|
+
# "expression, result",
|
|
35
|
+
# (
|
|
36
|
+
# ("bad", "NOASSERTION"),
|
|
37
|
+
# ("apache", "Apache-2.0"),
|
|
38
|
+
# ("MIT and Apache-2.0", "MIT and Apache-2.0"),
|
|
39
|
+
# ("(MIT or BSD) and Apache-2.0", "(MIT or BSD-3-Clause) and Apache-2.0"),
|
|
40
|
+
# )
|
|
41
|
+
# )
|
|
42
|
+
|
|
43
|
+
@pytest.mark.parametrize(
|
|
44
|
+
"license, result",
|
|
45
|
+
(
|
|
46
|
+
("bad", "UNKNOWN"),
|
|
47
|
+
("", "UNKNOWN"),
|
|
48
|
+
("NONE", "NONE"),
|
|
49
|
+
("NOASSERTION", "NOASSERTION"),
|
|
50
|
+
("Apache-2.0", "Apache-2.0"),
|
|
51
|
+
("LicenseRef-100", "LicenseRef-100"),
|
|
52
|
+
("ASL 2.0", "Apache-2.0"),
|
|
53
|
+
("Apache", "Apache-2.0"),
|
|
54
|
+
("MIT", "MIT"),
|
|
55
|
+
),
|
|
56
|
+
)
|
|
57
|
+
def test_find_license(self, license, result):
|
|
58
|
+
test_item = LicenseScanner()
|
|
59
|
+
x = test_item.get_synonym()
|
|
60
|
+
assert (len(x) > 0)
|
|
61
|
+
licenseid = test_item.find_license(license)
|
|
62
|
+
assert licenseid == result
|