make releases immutable for supply chain attack security
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
Research direction
Start with the GitHub immutable releases documentation linked in the issue, then inspect this repository's release settings and existing release process. Done means determining whether immutable releases can be enabled here and documenting or applying the setting so future releases cannot be modified.
Written by the indexing model from the issue text.
Description
TL;DR
Can we consider enabling "immutable" releases on this repo to reduce the risk of supply chain security attacks?
Detailed design
No response
Additional information
No response
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 533
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from google-github-actions/setup-gcloud
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
google-github-actions/setup-gcloud#735 · 1 reaction ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
google-github-actions/setup-gcloud#731 · 1 comment · 2 reactions ·
All issues in google-github-actions/setup-gcloud
Similar issues
-
Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenNSW/nsw-srilanka#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
0xMiden/bridge-portal#132 ·
-
react-doctor severity:warning tech-debt
Difficulty 1/5 Under an hour Newbie friendliness 88/100
digidem/comapeo-cloud-app#403 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100