-
As discussed in the community call on July 1st, we should create a dedicated draft specification directory. We have been using the 1.1 specification as a scratchpad for work that we don't want to rele…
-
See https://github.com/cli/cli/pull/8698/ for required code changes
-
Please add [SLSA provenance ](https://slsa.dev/)to your releases.
It is quick and easy to do on on Github:
https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/gen…
-
@mkulke @Xynnn007 @zvonkok and I got together to list the current state of provenance management in CoCo, gaps and next steps.
A Google doc describing the current PoC, including open questions, is…
-
This was discussed at the Chains WG on July 18th.
Since SLSAv1.0 was released, Chains provided support for it starting with provenance format `slsa/v2alpha2`. At this point, it is `slsa/v2alpha4` (w…
-
### Summary
Hi there! I wonder if scicookie as a cookiecutter template could generate SLSA3 provenance for Python-based build artifacts (the source distribution and wheels) in the template files by d…
-
@hythloda proposed using Infrastructure as Code approach to codify organization and repositories, we need to start automating manual work.
-
après Conversion, Filtre (contaminants) , Normalisation (quantile).
J'arrive sur imputation, Interface indique :
Err : 'x' must be an array of at least two dimensions + Err : dim(X) must have a po…
-
Builds have provenance. Source track doesn’t (it was explicitly removed from this PR).
@Nikokrock says:
> I missed the time when the idea of the provenance for sources was removed. I think that w…
-
Please add [SLSA provenance ](https://slsa.dev/)to your releases.
It is easy to do on on Github, for example:
https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/…