>>1859we had a similar scare when a malicious actor pushed a minor update to an internal npm package we were using for linting. we've since moved to
pinning exact versions and using a private registry to vet everything first.
>trust nothing that isn't cryptographically signed.