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
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
Should the source track treat open and closed source projects differently?
#1018
opened Jan 25, 2024 by
kpk47
Allow exploded package descriptor as alternative to resource descriptor URI
#1017
opened Jan 19, 2024 by
laurentsimon
Update supply-chain-threats.svg to reflect current 1.0 scope
clarification
Clarification of the spec, without changing meaning
#1004
opened Nov 30, 2023 by
cqueern
Clarify threat model by highlighting trust boundaries
clarification
Clarification of the spec, without changing meaning
#992
opened Oct 23, 2023 by
MarkLodato
Clarify Provenance is Unforgeable requirements at Build L3
#986
opened Oct 12, 2023 by
marcelamelara
Workstream: Build Platform Operations Track
workstream
Major effort comprising multiple sub-issues
#985
opened Oct 11, 2023 by
MarkLodato
Workstream: SLSA Build L4
workstream
Major effort comprising multiple sub-issues
#977
opened Oct 9, 2023 by
MarkLodato
3 tasks
Workstream: Hardware Attested Platforms
workstream
Major effort comprising multiple sub-issues
#975
opened Oct 3, 2023 by
chkimes
1 task
Clarify where to use SLSA Provenance vs. VSA
clarification
Clarification of the spec, without changing meaning
#974
opened Oct 3, 2023 by
joshuagl
Previous Next
ProTip!
no:milestone will show everything without a milestone.