
Research
Malicious npm Package Brand-Squats TanStack to Exfiltrate Environment Variables
A brand-squatted TanStack npm package used postinstall scripts to steal .env files and exfiltrate developer secrets to an attacker-controlled endpoint.
abortcontroller-chain
Advanced tools
Simple utility to chain an AbortController to one or more AbortSignals.
AbortController to multiple AbortSignalsWorks with browsers, NodeJS (16+), and spec-compliant polyfills.
At a minimum, you must pass one or more AbortSignals. However, the controller is optional: if a controller is not passed in, one will be created and returned.
import { chainAbortController } from "abortcontroller-chain";
// use your own controller
chainAbortController(controller, signal1, signal2, signal3);
// auto-create the controller
const controller = chainAbortController(signal1, signal2, signal3);
Say you're passing an AbortSignal into a long-running piece of code so you can end early if needed:
async function pollSomething(signal: AbortSignal) {
while (!signal.aborted) {
// keep polling until the signal says stop
}
}
But wait! You want to make an HTTP request with a deadline of 10 seconds:
const TEN_SECONDS = 10 * 1000; // ms
async function pollSomething(signal: AbortSignal) {
while (!signal.aborted) {
// abort after 500ms
const abortController = new AbortController();
setTimeout(() => abortController.abort(), TEN_SECONDS);
// do the fetch...
const result = await fetch("/something-something", {
// wait, this doesn't take into account the signal
// passed to pollSomething()
signal: abortController.signal,
});
/* ... */
}
}
Wouldn't it be great if the fetch-specific abortController could be aborted by the outer signal? That's easy with the abortcontroller-chain package:
import { chainAbortController } from "abortcontroller-chain";
const TEN_SECONDS = 10 * 1000; // ms
async function pollSomething(signal: AbortSignal) {
while (!signal.aborted) {
const abortController = new AbortController();
chainAbortController(abortController, signal);
setTimeout(() => abortController.abort(), TEN_SECONDS);
// do the fetch...
const result = await fetch("/something-something", {
// hooray! both signals are now respected
signal: abortController.signal,
});
/* ... */
}
}
You can further simplify the creation:
const abortController = chainAbortController(signal);
setTimeout(() => abortController.abort(), TEN_SECONDS);
FAQs
Simple utility to chain an AbortController to one or more AbortSignals.
The npm package abortcontroller-chain receives a total of 11 weekly downloads. As such, abortcontroller-chain popularity was classified as not popular.
We found that abortcontroller-chain 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 brand-squatted TanStack npm package used postinstall scripts to steal .env files and exfiltrate developer secrets to an attacker-controlled endpoint.

Research
Compromised SAP CAP npm packages download and execute unverified binaries, creating urgent supply chain risk for affected developers and CI/CD environments.

Company News
Socket has acquired Secure Annex to expand extension security across browsers, IDEs, and AI tools.