npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@noctcore/eslint-plugin-async-safety

v0.1.0

Published

ESLint rules for async correctness: fetch timeouts, AbortSignal forwarding, and shared-state / concurrency races.

Readme

@noctcore/eslint-plugin-async-safety

Async-correctness rules TypeScript can't catch: unbounded fetch, dropped AbortSignals, and shared-state / concurrency races. Flat-config only, ESLint 9+.

Install

bun add -D @noctcore/eslint-plugin-async-safety   # or npm i -D / pnpm add -D

Use

// eslint.config.js
import asyncSafety from '@noctcore/eslint-plugin-async-safety';

export default [
  asyncSafety.configs.recommended,
];

Or wire rules individually:

import asyncSafety from '@noctcore/eslint-plugin-async-safety';

export default [
  {
    plugins: { 'noctcore-async-safety': asyncSafety },
    rules: {
      'noctcore-async-safety/require-fetch-timeout': ['error', { callees: ['undici.request'] }],
      // Off until you point it at server files:
      'noctcore-async-safety/no-shared-mutable-module-state': ['error', { include: ['**/server/**'] }],
    },
  },
];

Rules

| Rule | Description | 💡 | | --- | --- | --- | | require-fetch-timeout | A fetch (or configured wrapper) call must carry a signal/timeout — an unbounded request can hang forever. | 💡 | | forward-abort-signal | A function that accepts an AbortSignal but awaits a call without forwarding it leaves that work uncancellable. | | | no-shared-mutable-module-state | A module-scoped mutable binding written from an exported async/handler function is shared across concurrent requests (opt in via include). | | | prefer-parallel-awaits | Consecutive independent awaits can run concurrently with Promise.all. | 💡 | | no-concurrent-shared-mutation | A read-modify-write of an outer binding inside a concurrent Promise.all(map(async …)) callback can lose updates. | |

recommended preset

| Rule | Severity | Notes | | --- | --- | --- | | require-fetch-timeout | error | Precise and syntactic. | | no-shared-mutable-module-state | error | Inert until you set include globs, so it ships enabled but off by default. | | forward-abort-signal | warn | Heuristic — advisory. | | prefer-parallel-awaits | warn | Heuristic — advisory suggestion. | | no-concurrent-shared-mutation | warn | Heuristic — advisory. |

The 💡 rules provide editor suggestions (not autofixes) — parallelizing awaits and adding a timeout both change runtime behavior, so they are never applied automatically.