Resources

@scruple/resources checks resource ownership, cleanup, and retries.

pnpm add -D @scruple/resources

import { defineConfig } from "@scruple/core";
import { resources } from "@scruple/resources";

export default defineConfig({
  parser,
  provider,
  plugins: { resources: resources() },
  rules: { "resources/no-leaked-resources": "warn" },
});

Rule	Checks
resources/no-leaked-resources	Owned resources left unreleased
resources/require-bounded-retries	Retry behavior without a finite bound
resources/require-cleanup-on-failure	Cleanup that is not failure-safe
resources/require-complete-resource-cleanup	Partial cleanup of multiple resources
resources/require-retry-backoff-with-jitter	Retry timing without backoff and jitter
resources/require-retry-time-budget	Retry work without an overall deadline

resources/no-leaked-resources

Reviews functions containing using or recognized lifecycle calls for paths that finish while still owning an acquired file, stream, socket, connection, subscription, watcher, lock, transaction, or handle. Release, scoped management, and visible ownership transfer are accepted. Options: threshold defaults to { warning: 0.65, error: 0.9 }; minConfidence to 0.5; lifecycleCallPatterns defaults to built-in acquisition and scoped-helper patterns and replaces them when supplied.

resources/require-bounded-retries

Reviews functions with recognized retry calls, or retry language plus failure handling, for retries lacking a finite attempt, elapsed-time, or deadline bound. Cancellation alone is not a guaranteed bound. Options: threshold defaults to { warning: 0.9, error: 0.97 }; minConfidence to 0.7; retryCallPatterns defaults to built-in retry patterns and replaces them when supplied.

resources/require-cleanup-on-failure

Uses the same lifecycle candidate selection as no-leaked-resources, but checks for potentially failing work followed by cleanup only on the success path. using, await using, finally, scoped helpers, and ownership transfer are accepted. Options: threshold defaults to { warning: 0.9, error: 0.97 }; minConfidence to 0.7; lifecycleCallPatterns behaves as above.

resources/require-complete-resource-cleanup

Reviews functions with at least two explicit acquisitions and checks cleanup across later-acquisition, work, and cleanup-failure paths. Managed lifetimes and ownership transfer are accepted.

resources/require-retry-backoff-with-jitter

Reviews retry timing for progressive backoff plus randomization. Immediate retries, fixed delays, and backoff without jitter are findings; opaque framework defaults cause abstention.

resources/require-retry-time-budget

Requires a total elapsed deadline or visibly inherited deadline-backed context. A finite attempt count or arbitrary external AbortSignal does not by itself prove a total budget.

rules: { "resources/require-bounded-retries": ["warn", { retryCallPatterns: [/^again$/u] }] }