Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Assess signing/provenance needs of our published Wasm #35

Open
Tracked by #24
kingdonb opened this issue Jun 27, 2023 · 0 comments
Open
Tracked by #24

Assess signing/provenance needs of our published Wasm #35

kingdonb opened this issue Jun 27, 2023 · 0 comments

Comments

@kingdonb
Copy link
Owner

kingdonb commented Jun 27, 2023 •
edited
Loading

If there is something we can do to conform to standards like SLSA, let's do it

This issue has only the Rust library (and WASI target) in its scope. The Ruby technology is covered by #36.
@kingdonb kingdonb mentioned this issue Jun 27, 2023
Closed
6 tasks
@kingdonb kingdonb changed the title Assess what kind of provenance makes sense to add in the context of our Wasm module Assess signing/provenance needs of our published Wasm Jun 27, 2023
@kingdonb kingdonb mentioned this issue Jun 27, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kingdonb