
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.
path-browserify-es
Advanced tools
The
pathmodule from Node.js for browsers
This implements the Node.js path module for environments that do not have it, like browsers.
However, path-browserify does not work well with ES Module, for example, you cannot use named imports.
This fork aims to enable path-browserify to support the format of ES Module, and additionally add some new methods.
# npm
npm install path-browserify-es
# yarn
yarn add path-browserify-es
# pnpm
pnpm add path-browserify-es
This is already fully TypeScript based, there is no need to install any additional type packages.
import path from "path-browserify-es";
const filename = "logo.png";
const logo = path.join("./assets/img", filename);
document.querySelector("#logo").src = logo;
You can do it directly like this:
import { resolve } from "path-browserify-es";
console.log(resolve("var/lib", "../", "file")); // "var/file"
Without:
import path from "path-browserify-es";
const { resolve } = path;
console.log(resolve("var/lib", "../", "file")); // "var/file"
// or
console.log(path.resolve("var/lib", "../", "file")); // "var/file"
fileRootGet the file name without an extension.
console.log(path.basename("path/to/file.txt")); // "file.txt"
console.log(path.fileRoot("path/to/file.txt")); // "file"
Before this, you could only achieve it by parse("path/to/file.txt").name.
The function name comes from this post. It mentioned Vim calls it file root (:help filename-modifiers). I used to name it filenameWithoutExtension, but it was too long.
extGet the file extension name but without the leading dot.
console.log(path.extname("path/to/file.txt")); // ".txt"
console.log(path.ext("path/to/file.txt")); // "txt"
I used to name it extnameWithoutDot, but it was too long. And it's more commonly used than extname method. There is currently no widely accepted consensus on whether the extension needs to include the leading dot. If it's not for compatibility, it's best to rename the function that gets the extension with dot to dotExtname.
See the Node.js path docs. path-browserify currently matches the Node.js 10.3 API.
path-browserify only implements the POSIX functions, not the win32 ones.
path-browserify-es is available under the MIT License. See the LICENSE file for more info.
FAQs
The path module from node core for browsers
We found that path-browserify-es demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 0 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.