You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm packages have a content-specific "integrity" hash for all their contained files. This comes from the npmjs repository, and so if any files are different from what was in the package, then npm can notice. These integrity hashes are stored in package-lock.json. https://docs.npmjs.com/cli/v6/configuring-npm/package-lock-json#integrity
Sometimes these are missing, and we should know when that happens.
This may involve:
a GitHub Action or npm package that checks for missing integrity hashes in package-lock.json during CI, or
some flag in npm that enforces strictness (??), or
Not sure how we want to handle this. Technically, this could be a collector issue for the remaining steps, but I understand if people want the endorphin rush of closing it, and we can treat those new tickets as standalone :)
Wondering if maybe this is helpful to show what we're trying to cover, that for some reason it seems npm cli is not doing for us right now: (we assume NPM website is trusted)
npm packages have a content-specific "integrity" hash for all their contained files. This comes from the npmjs repository, and so if any files are different from what was in the package, then npm can notice. These integrity hashes are stored in package-lock.json.
https://docs.npmjs.com/cli/v6/configuring-npm/package-lock-json#integrity
Sometimes these are missing, and we should know when that happens.
This may involve:
package-lock.json
during CI, orRelated issue: npm/cli#4460
Related: No pressure to pollute our labels, but do you think it's worth having a
security
label to make security tasks more visible, @tristan-orourke?To Do
research npm packages that validate integrityresearch npm flags that force thissecurity
labelThe text was updated successfully, but these errors were encountered: