Align with SLSA3+ for verifiable provenance

Open
#32 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd, security

Research direction

Read the referenced SLSA generic builder README and the linked Google Security Blog post first. Then identify the repository's current build and release configuration, which is not named in the issue, and define the SLSA 3+ provenance requirements before implementing them. Done means the project's artifacts produce verifiable provenance meeting the selected SLSA level.

Written by the indexing model from the issue text.

Description

see: https://github.com/slsa-framework/slsa-github-generator/blob/3d27f18a67e12a251517ca9af35771a93da39526/internal/builders/generic/README.md
see: https://security.googleblog.com/2022/04/improving-software-supply-chain.html

Dominant language
TypeScript
Stars
4
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from loopbackio/security

All issues in loopbackio/security

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.