slsa-github-generator icon indicating copy to clipboard operation
slsa-github-generator copied to clipboard

Language-agnostic SLSA provenance generation for Github Actions

Results 279 slsa-github-generator issues
Sort by recently updated
recently updated
newest added

Adopt OpenSSF best practices as described on the website. https://bestpractices.coreinfrastructure.org/en Basics: - #892 - #893 - #617 Change Control - #894 Reporting - #541 Quality - #895 - #896 -...

type:discussion

From [OpenSSF best practices](https://bestpractices.coreinfrastructure.org/en/criteria/0#0.crypto_published): *The software produced by the project MUST use, by default, only cryptographic protocols and algorithms that are publicly published and reviewed by experts (if cryptographic protocols...

type:documentation

Add simple code coverage metrics. From OpenSSF best practices: *It is SUGGESTED that the test suite cover most (or ideally all) the code branches, input fields, and functionality. [[test_most](https://bestpractices.coreinfrastructure.org/en/criteria/0#0.test_most)]*

type:feature
area:tooling

- yamllint is not currently run in strict mode - shellcheck should explicitly set minimum severity - eslint should set max-warnings to 0

type:feature
area:tooling

*The project MUST have a general policy (formal or not) that as major new functionality is added to the software produced by the project, tests of that functionality should be...

type:documentation

Add a CHANGELOG file so that changes across versions are easier to parse.

type:documentation

We could have a simple website with docs that are a bit easier to navigate. Maybe using [GitHub Pages](https://pages.github.com/).

type:documentation
type:feature