Skip to content

Commit 225e7d3

Browse files
add maven-lockfile (#1368)
* add maven-lockfile Signed-off-by: Martin Monperrus <martin.monperrus@gnieh.org> * Update securing-build-pipelines.md Signed-off-by: Martin Monperrus <martin.monperrus@gnieh.org> --------- Signed-off-by: Martin Monperrus <martin.monperrus@gnieh.org> Co-authored-by: Brandt Keller <43887158+brandtkeller@users.noreply.github.com>
1 parent c740847 commit 225e7d3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

community/publications/supply-chain-security-tools/securing-build-pipelines.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,6 @@ Here are the list of requirements for securing build pipelines. Each one has a l
1717
- SLSA (level 1)
1818
- in-toto
1919

20-
2120
## 2. Validate environments and dependencies before usage
2221

2322
### Tool capability
@@ -69,6 +68,7 @@ Here are the list of requirements for securing build pipelines. Each one has a l
6968
### Tools
7069

7170
- apko
71+
- [maven-lockfile](https://github.com/chains-project/maven-lockfile/) for Java/Maven
7272

7373
## 6. Find and Eliminate Sources Of Non-Determinism
7474

@@ -162,7 +162,7 @@ Here are the list of requirements for securing build pipelines. Each one has a l
162162
- in-toto (can be validated via runtime trace attestations)
163163
- Tekton (Pipelines)
164164

165-
## 14. Ensure Software Factory has minimal network connectivity.
165+
## 14. Ensure Software Factory has minimal network connectivity
166166

167167
### Tool capability
168168

0 commit comments

Comments
 (0)