
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.
@builder.io/dev-tools
Advanced tools
Setup and integrate Builder.io Visual CMS during development using the Dev Tools plugin. Builder Dev Tools can be integrated with a project's development through either a Next.js config, Vite plugin, or Webpack plugin.
Builder's Dev tools can be installed and initialized using:
npm init @builder.io@latest
This command will update the config file (such as next.config.js, or vite.config.js) and install the @builder.io/dev-tools package. Once installed, you can start your app's dev server:
npm run dev
Alternatively, you can manually install Builder's Dev Tools, and update the config files following the steps below.
npm install -D @builder.io/dev-tools
Next step is to add the Dev Tools plugin to your build tool's config file. For example, if you're using Next.js, see the docs below on how to import and add Dev Tools to a Next.js app.
A utility function is provided to update your next config in order to run Dev Tools during development. Wrap your existing next config using the withBuilderDevTools() function that's created when it is required at the top of the config.
// next config file
const withBuilderDevTools = require("@builder.io/dev-tools/next")({
// Builder Dev Tools Options
});
module.exports = withBuilderDevTools({
// next config
});
Or configuration as a function:
module.exports = (phase, defaultConfig) => {
return withBuilderDevTools(defaultConfig);
};
The Vite plugin for Dev Tools is meant for frameworks using Vite for its development. Currently, Dev Tools supports Qwik integrated with Vite. Import builderDevTools from @builder.io/dev-tools/vite and place it as the the first plugin to ensure it runs before others.
// vite config file
import { defineConfig } from "vite";
import { builderDevTools } from "@builder.io/dev-tools/vite";
export default defineConfig(() => {
return {
plugins: [builderDevTools()],
};
});
The Dev Tools webpack plugin is for React projects. If your project is using Next.js, please see the Next.js docs above on how to add the Dev Tools plugin to the next config. Below is a general webpack config for a React project.
// webpack config file
const { BuilderDevToolsPlugin } = require("@builder.io/dev-tools/webpack");
module.exports = {
plugins: [new BuilderDevToolsPlugin()],
};
FAQs
Builder.io Visual CMS Devtools
The npm package @builder.io/dev-tools receives a total of 23,930 weekly downloads. As such, @builder.io/dev-tools popularity was classified as popular.
We found that @builder.io/dev-tools demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 23 open source maintainers 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.