-
Notifications
You must be signed in to change notification settings - Fork 214
Issues: slsa-framework/slsa
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
should the source track focus on "proposed changes" or "sequences of revisions?"
source-track
#1095
opened Jul 10, 2024 by
zachariahcox
Clarify what must be retained during source migrations
source-track
#1079
opened Jun 17, 2024 by
TomHennen
Create guidance for consumers on how to evaluate the source platform
source-track
#1078
opened Jun 17, 2024 by
TomHennen
VCS and SCP concerns are mixed or too prescriptive
source-track
#1076
opened Jun 17, 2024 by
TomHennen
Should the source track mention 'administrator robots'?
source-track
#1073
opened Jun 17, 2024 by
TomHennen
Structure & formatting don't match the build track
source-track
#1069
opened Jun 17, 2024 by
TomHennen
[docs] clarify which build level one will reach when using a provided GitHub Action
#1063
opened Jun 1, 2024 by
norbjd
Clarify what "control plane" means
clarification
Clarification of the spec, without changing meaning
#1062
opened May 30, 2024 by
MarkLodato
In spec address of tie-ins with OpenChain ISO 18974 and S2C2F
#1061
opened May 28, 2024 by
camaleon2016
Google preferring v0.1 instead of v1.0
website
Issues with the slsa.dev website
#1047
opened Apr 15, 2024 by
MarkLodato
SLSA YouTube playlist not updating
website
Issues with the slsa.dev website
#1043
opened Apr 8, 2024 by
MarkLodato
How should the Source track address merge strategies?
source-track
#1040
opened Mar 28, 2024 by
kpk47
Previous Next
ProTip!
Updated in the last three days: updated:>2024-07-09.