Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request relates to https://github.com/weekendesk/tech-management/issues/1603.
Scope
Lately there has been many supply-chain attacks to NPM libraries:
https://www.reddit.com/r/programming/comments/1nbqt4d/largest_npm_compromise_in_history_supply_chain/
https://x.com/feross/status/1967732902256579014
https://x.com/feross/status/1967942264182935811
Solution
CI/CD
Add the --ignore-scripts command during the dependency installation process
Enforce the use of modern engines setting up minor versions for npm and node through package.json
LOCAL
Add an .npmrc file per project with the following configuration:
ignore-scripts=true: Prevents npm from executing lifecycle scripts (preinstall, postinstall, etc.), protecting against supply chain attacks that inject malicious code during package installation.
package-lock=true: Forces npm to generate and use package-lock.json, ensuring reproducible builds and enabling precise auditing of dependency versions.
save-exact=false: Saves dependencies with semver ranges instead of exact versions, allowing automatic patch updates while maintaining compatibility.
Since this security breach has been causing vulnerabilities since September and still persists, a script can be added to download the list of exposed packages and verify that none of the affected versions are part of the installed dependencies, alerting and stopping the current build.