
Research
Supply Chain Attack on Axios Pulls Malicious Dependency from npm
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.
svn-modules
Advanced tools
Command-line tool for installing node module dependencies from SVN repositories
I am open to suggestions, improvements, and pull requests for those interested. This is currently very much a minimally viable (yet functional) approach.
npm install svn-modules --global
npm install svn-modules --save-dev
Append an object named svnDependencies to your package.json file. Each property of the object will reference a node package dependency stored in a SVN repository.
Example:
"svnDependencies": {
"my-first-package": "svn://path/to/my/repo/my-first-package/trunk",
"my-other-package": "svn://path/to/my/repo/my-other-package/trunk"
}
It is recommended to add the following npm scripts to your package.json file.
"scripts": {
"install": "svn-modules install",
"uninstall": "svn-modules uninstall"
}
This will cause npm to automatically install your SVN dependencies before your package is installed, as well as uninstalling them before your package is uninstalled. You can simply run npm install and your SVN dependencies will also be installed.
Alternatively, you can install your SVN dependencies manually via svn-modules install. You can uninstall them via svn-modules uninstall.
NOTE: Similar to npm, you should be inside your project folder when executing these commands.
svn_modules? Do I need them?Installing SVN dependencies will temporarily create a svn_modules local cache in your project folder. This folder is deleted upon completing an install or uninstall operation. If it is not deleted automatically, you can safely delete it manually. It is recommended to add this folder to your source control's ignore list (.gitignore) as a precaution.
No. The svn export command is used to copy the remote repo to your local computer. Unlike the svn checkout command, svn export does not create SVN source control folders (.svn). This acts as a simple copy operation rather than a full checkout.
node_modules properly?Yes. They will be installed (along with their own dependencies) insides your project's node_modules folder as you would expect any other node package. This follows npm 3.x convention.
-r --revision <rev> option) to install-b --branch <name> option) to install-t --tag <name> option) to install-k --trunk option) to installFAQs
Allows node module dependencies to be installed from SVN repositories
We found that svn-modules demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.

Research
Malicious versions of the Telnyx Python SDK on PyPI delivered credential-stealing malware via a multi-stage supply chain attack.

Security News
TeamPCP is partnering with ransomware group Vect to turn open source supply chain attacks on tools like Trivy and LiteLLM into large-scale ransomware operations.