q-advanced-throttle

A throttling object built on top of the Q.js package that provides an easy way set the maximum concurrency (parallel operations) of promised tasks. derived from christopther down's q-throttle gist (https://gist.github.com/1725325) this version incorporat

q-advanced-throttle@1.0.3 was published on 2016-07-06. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All q-advanced-throttle versions · Permanent reference to 1.0.3

Package specifications

Version1.0.3
License declarationMIT
Published2016-07-06T23:46:26.006Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryq-advanced-throttle.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars0
Repository forks0

Install q-advanced-throttle 1.0.3

npm install q-advanced-throttle@1.0.3
pnpm add q-advanced-throttle@1.0.3
yarn add q-advanced-throttle@1.0.3

Runtime dependencies

  • q ^1.4.1

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

SAST0/10 — no SAST tool detected
Code-Review0/10 — Found 0/4 approved changesets -- score normalized to 0
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License0/10 — license file not detected
Branch-Protection0/10 — branch protection not enabled on development/release branches

Evidence and freshness