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
- If you are unsure about the name of the `SPDX-TOP-LEVEL-PACKAGE`, take a look at the source SBOM to identify packages (under key `packages` in the SBOM).
203
204
-`description`: a brief description of what this vendor library does.
204
205
-`copyrightText`: copyright text associated with the top-level package/library/3pp using [SPDX License Identifiers](https://spdx.org/licenses/).
205
-
-`downloadLocation`: URI of the vendor library to download.
206
+
-`downloadLocation`: URI of the vendor library to download. If using Github, use preferably `https//` rather than `git+https//` or similars.
207
+
This is because the download location is used for vulnerability scanning in `.github/scripts/otp-compliance.es`.
206
208
-`homepage`: homepage of the vendor library.
207
209
-`licenseDeclared`: license as declared by the vendor, following a [SPDX license identifier](https://spdx.org/licenses/).
208
210
-`name`: name of the library.
209
211
-`versionInfo`: version of the library/project/3pp. In case of no version number being available, write the commit sha.
212
+
-`sha`: sha commit for `versionInfo`, they need to be updated together!
213
+
-`ecosystem`: List of valid ecosystems in [OSV Ecosystems](https://ossf.github.io/osv-schema/#defined-ecosystems)
214
+
where this value is omitted for C/C++ code (e.g., `asmjit`, `pcre2`, `zlib`, `zstd`, etc), and used in `vendor.json` for `jquery`.
210
215
-`path`: path to the vendor library inside Erlang/OTP. This can point to a folder or a list of files.
211
216
- Folder: any file inside the folder is considered part of the vendor library (e.g., asmjit [vendor.info](../erts/emulator/asmjit/vendor.info)).
212
217
- List of files: only the files listed here are part of a vendor library (e.g., erts-config [vendor.info](../erts/autoconf/vendor.info)).
@@ -225,8 +230,7 @@ and re-run the source SBOM generation steps ([Erlang/OTP source SBOM]).
225
230
### Add a New Vendor Dependency
226
231
227
232
Follow the same steps as in [Update SPDX Vendor Packages].
228
-
When running the SBOM generator, make sure to check that the new vendor dependency exists
229
-
in its own package.
233
+
When running the SBOM generator, make sure to check that the new vendor dependency exists in its own package.
230
234
231
235
The [`renovate.json5`](../renovate.json5) file also needs to be updated
232
236
to make sure that the new vendored dependency gets updated as it should.
0 commit comments