Skip to content
This repository was archived by the owner on Dec 18, 2025. It is now read-only.

Commit 73e8c67

Browse files
committed
Add call to action for community contribution of supply chain tool mappings
1 parent 21dd9ea commit 73e8c67

File tree

6 files changed

+12
-0
lines changed

6 files changed

+12
-0
lines changed

community/publications/supply-chain-security-tools/README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@
44
Find out what tools are used to secure the supply chain. Explore the general requirement categories below.
55
{{% /blocks/lead %}}
66

7+
This mapping is community maintained. Feel free to add tools by opening a PR.
8+
79
1. [Securing the Source Code](securing-source-code.md)
810
2. [Securing Materials](securing-materials.md)
911
3. [Securing Build Pipelines](securing-build-pipelines.md)

community/publications/supply-chain-security-tools/securing-artifacts.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@
44
Here are the list of requirements for securing artifacts. Each one has a list of tools used to achieve it.
55
{{% /blocks/lead %}}
66

7+
This mapping is community maintained. Feel free to add tools by opening a PR.
8+
79
## 1. Sign Every Step in the Build Process
810

911
### Tool capability

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@
44
Here are the list of requirements for securing build pipelines. Each one has a list of tools used to achieve it.
55
{{% /blocks/lead %}}
66

7+
This mapping is community maintained. Feel free to add tools by opening a PR.
8+
79
## 1. Cryptographically guarantee policy adherence
810

911
### Tool capability

community/publications/supply-chain-security-tools/securing-deployments.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@
44
Here are the list of requirements for securing deployments. Each one has a list of tools used to achieve it.
55
{{% /blocks/lead %}}
66

7+
This mapping is community maintained. Feel free to add tools by opening a PR.
8+
79
## 1. Ensure clients can perform Verification of Artefacts and associated metadata
810

911
### Tool capability

community/publications/supply-chain-security-tools/securing-materials.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@
44
Here are the list of requirements for securing materials. Each one has a list of tools used to achieve it.
55
{{% /blocks/lead %}}
66

7+
This mapping is community maintained. Feel free to add tools by opening a PR.
8+
79
## 1. Verify third party artefacts and open source libraries
810

911
### Tool capability

community/publications/supply-chain-security-tools/securing-source-code.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@
44
Here are the list of requirements for securing the source code, which is a subcategory of the overall requirements for supply chain security. For each requirement is a list of tools used to meet that requirement.
55
{{% /blocks/lead %}}
66

7+
This mapping is community maintained. Feel free to add tools by opening a PR.
8+
79
## 1. Require signed commits
810

911
### Tool capability

0 commit comments

Comments
 (0)