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
Some private repositories, such as Azure Artifacts, do not support integrity sha's such as shar512 (default for NPM) but instead only use sha1. In turn, when snyker removes these properties, the subsequent npm install is not reinstated the sha1
Details
Using a repository that uses Azure Artifacts, run npx @asos/snyker --lockfile package-lock.json, you will see that all integrity properties get removed from the package-lock.json and not re-added.
The suggestion here is to add a flag, e.g. --preserve-integrity which in the instance of sha1 does not remove them.
The text was updated successfully, but these errors were encountered:
Issue
Some private repositories, such as Azure Artifacts, do not support integrity sha's such as shar512 (default for NPM) but instead only use sha1. In turn, when snyker removes these properties, the subsequent
npm install
is not reinstated the sha1Details
Using a repository that uses Azure Artifacts, run
npx @asos/snyker --lockfile package-lock.json
, you will see that allintegrity
properties get removed from thepackage-lock.json
and not re-added.The suggestion here is to add a flag, e.g.
--preserve-integrity
which in the instance ofsha1
does not remove them.The text was updated successfully, but these errors were encountered: