Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@visx/vendor
Advanced tools
This package consists of vendored packages for other visx
packages. It is meant to enable dual
support for export of CommonJS and ESM formats by re-exporting some visx
dependencies, and even
some transitive dependencies, which are ESM-only.
This package is heavily based off of
victory-vendor
which aims to solve the same problem.
All vendored packages are listed as dependencies
in the package.json
of this package (note that
the yarn
nohoist
option is set for this package to guarantee version specificity in this large
monorepo where we may have mixed versions of d3
packages). For each (non-types) package <pkg>
,
we generate the following:
esm/<pkg>.js
lib/<pkg>.js
vendor-cjs/vendor-<pkg>/src/index.js
vendor-cjs/vendor-<pkg>/LICENSE
contains the upstream license of the vendored package<pkg2>
) that are referenced by <pkg>
are updated to point to
vendor-cjs/vendor-<pkg2>/src/index.js
@types/<pkg>
as root <pkg>.d.ts
files (when available as specified in
the package.json
dependencies
)<pkg>.js
file (pointing to the CJS version of the lib) for tooling that doesn't yet
support package.json:exports
(conditional exports)We provide two alternate paths and behaviors -- for ESM and CommonJS
When you use a module import
syntax like the following, it will resolve to a re-exported version
of node_modules/d3-interpolate
, the unmodified ESM library from D3.
import { interpolate } from '@visx/vendor/d3-interpolate';
If you use a CJS require
syntax like the following, it will resolve to an alternate path that
contains the transpiled version of the underlying d3-*
(or other) library to be found at
@visx/vendor/vendor-cjs/d3-interpolate/**/*.js
.
const { interpolate } = require('@visx/vendor/d3-interpolate');
Such transpiled versions have internally consistent import references to other other
@visx/vendor/vendor-cjs/<pkg-name>
paths that need to be transpiled.
For tooling that doesn't yet support package.json:exports
(conditional exports), we include root
index files for all vendored packages, e.g., @visx/vendor/d3-array.js
.
Type declaration files are also included in the root, e.g., @types/d3-array
is exported as
@visx/vendor/d3-array.d.ts
.
FAQs
vendored packages for visx
The npm package @visx/vendor receives a total of 306,329 weekly downloads. As such, @visx/vendor popularity was classified as popular.
We found that @visx/vendor demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 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.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.