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
Copy file name to clipboardExpand all lines: sbom-github.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
-
# Adding SBOMs to your GitHub Releases with Jreleaser
1
+
# Adding SBOMs to your GitHub and Maven Central Releases with Jreleaser
2
2
3
3
## Motivation
4
4
Software Bill of Materials (SBOMs) are critical to modern software development and supply chain management.
5
5
An SBOM is a complete inventory of all the components and dependencies of a software product.
6
6
It provides a detailed list of all the open-source and third-party components used in a software product, their versions and any known vulnerabilities.
7
7
SBOMs are essential for ensuring the security and integrity of software products, as they enable developers and security teams to identify and remediate vulnerabilities in a timely manner.
8
-
In this blog post, we will discuss how to add SBOMs to your GitHub releases and JReleaser, and why it is essential.
8
+
In this blog post, we will discuss how to add SBOMs to your GitHub and Maven Central releases and JReleaser, and why it is essential.
9
9
10
10
## Requirements
11
11
@@ -15,8 +15,8 @@ Here we show how to do it with maven and cyclonedx-maven-plugin.
15
15
16
16
## Goal
17
17
18
-
This blog post provides a step-by-step guide on adding SBOMs to your GitHub releases using Maven and JReleaser.
19
-
We will cover the requirements for adding SBOMs, the benefits of doing so, and the steps involved in generating and adding an SBOM to your GitHub release.
18
+
This blog post provides a step-by-step guide on adding SBOMs to your GitHub and Maven Central releases using Maven and JReleaser.
19
+
We will cover the requirements for adding SBOMs, the benefits of doing so, and the steps involved in generating and adding an SBOM to your GitHub and Maven Central release.
20
20
By the end of this post, you will clearly understand how to add SBOMs to your software releases and why it is crucial to do so.
21
21
22
22
## Steps
@@ -67,18 +67,18 @@ By the end of this post, you will clearly understand how to add SBOMs to your so
67
67
If running JReleaser locally, make sure to use atleast version 1.6.0 and the SBOMs generated by `cyclonedx-maven-plugin` will be uploaded to Maven Central.
68
68
If using the `jreleaser/release-action` action, be aware that even if you use the latest version of the action it can pull different versions of JReleaser. If using atleast version 1.6.0 it will upload the SBOMs to Maven Central.
The final result looks like this: https://repo1.maven.org/maven2/io/github/chains-project/maven-lockfile/5.3.5/
82
82
83
83
## Conclusion
84
84
In conclusion, adding SBOMs to your GitHub and Maven Central releases is a simple and effective way to improve the security and integrity of your software products. Following the steps outlined in this blog post, you can easily generate and add an SBOM to your GitHub and Maven Central release using Maven and JReleaser. With an SBOM, you can identify and remediate vulnerabilities in your software products on time, reducing the risk of security breaches and ensuring the trust of your users. We hope this post has helped guide you through adding SBOMs to your GitHub and Maven Central releases, and we encourage you to continue exploring ways to improve the security and quality of your software products.
0 commit comments