2 ms·
The trick is to change the package-lock. What you do it fork a popular package that the project uses and make some changes. Then update the package-lock so th
by vorticalbox 3y ago
The trick is to change the package-lock.
What you do it fork a popular package that the project uses and make some changes.
Then update the package-lock so that it points to your GitHub fork.
This file is normally ignored in PR due to the amount of line changes in there so you can have quite a bit of fun.
- leipert 3y agoWe‘ve been writing a tool to check lock files against the registry: https://www.npmjs.com/package/@gitlab/untamper-my-lockfile https://www.npmjs.com/package/@gitlab/untamper-my-lockfile For now it only supports yarn, but npm support shouldn’t be too hard.
- louislang 3y agoThis is really cool work, glad to see someone tackling this! Can I assume this will get rolled out into gitlab natively?
- leipert 3y agoActually good point, will talk to the respective PMs next week. Mainly been using it in CI in order to protect our own projects (thus yarn only for now)