GoogleChromeLabs / GoogleChromeLabs/jsvu

integrity validation?

Open
#159 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
2k
Forks
98
PR merge metrics
No merged PRs in 30d

Description

npm and other package managers provide that via lockfiles

Another example is what `@electron/get` does with sha256 checksums when downloading electron binaries upon npm install: https://github.com/electron/get/blob/main/src/index.ts (that is also problematic though)

Otherwise there is no way to ensure that the downloaded bin is what was actually expected

Relying on github-hosted content and version tags to not change is problematic, it's not immutable like npm

Also see #158, integrity validation would have prevented that

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.