@nxtedition/scheduler
A high-performance, priority-based task scheduler for Node.js with support for concurrency limiting, byte-rate throttling, and multi-worker coordination via `SharedArrayBuffer`.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@nxtedition/trace | AI (dependencies): Same-org first-party dependency, not a third-party unvetted package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Metadata-only signals; no repo/keywords is common for small internal libs. | ai |
Versions (showing 66 of 66)
| Version | Deps | Published |
|---|---|---|
| 5.0.2 | 1 / 3 | |
| 5.0.1 | 1 / 3 | |
| 5.0.0 | 1 / 3 | |
| 4.2.6 | 1 / 5 | |
| 4.2.5 | 1 / 5 | |
| 4.2.4 | 1 / 5 | |
| 4.2.3 | 1 / 5 | |
| 4.2.2 | 1 / 5 | |
| 4.2.1 | 1 / 5 | |
| 4.2.0 | 1 / 5 | |
| 4.1.18 | 0 / 5 | |
| 4.1.17 | 0 / 5 | |
| 4.1.16 | 0 / 5 | |
| 4.1.15 | 0 / 5 | |
| 4.1.14 | 0 / 5 | |
| 4.1.13 | 0 / 5 | |
| 4.1.12 | 0 / 5 | |
| 4.1.11 | 0 / 5 | |
| 4.1.10 | 0 / 5 | |
| 4.1.9 | 0 / 6 | |
| 4.1.8 | 0 / 6 | |
| 4.1.7 | 0 / 6 | |
| 4.1.6 | 0 / 6 | |
| 4.1.5 | 0 / 6 | |
| 4.1.4 | 0 / 6 | |
| 4.1.3 | 0 / 6 | |
| 4.1.2 | 0 / 6 | |
| 4.1.1 | 0 / 6 | |
| 4.1.0 | 0 / 6 | |
| 4.0.2 | 0 / 6 | |
| 4.0.1 | 0 / 6 | |
| 4.0.0 | 0 / 6 | |
| 3.1.9 | 0 / 6 | |
| 3.1.8 | 0 / 6 | |
| 3.1.7 | 0 / 6 | |
| 3.1.6 | 0 / 5 | |
| 3.1.5 | 0 / 5 | |
| 3.1.4 | 0 / 5 | |
| 3.1.3 | 0 / 5 | |
| 3.1.2 | 0 / 5 | |
| 3.1.1 | 0 / 5 | |
| 3.1.0 | 0 / 5 | |
| 3.0.12 | 0 / 5 | |
| 3.0.11 | 0 / 5 | |
| 3.0.10 | 0 / 5 | |
| 3.0.9 | 0 / 5 | |
| 3.0.8 | 0 / 5 | |
| 3.0.6 | 0 / 5 | |
| 3.0.5 | 0 / 5 | |
| 3.0.4 | 0 / 5 | |
| 3.0.3 | 0 / 5 | |
| 3.0.2 | 0 / 3 | |
| 3.0.1 | 0 / 3 | |
| 3.0.0 | 0 / 3 | |
| 2.0.4 | 0 / 3 | |
| 2.0.3 | 0 / 3 | |
| 2.0.2 | 0 / 3 | |
| 2.0.1 | 0 / 3 | |
| 1.0.8 | 0 / 3 | |
| 1.0.7 | 0 / 3 | |
| 1.0.6 | 0 / 3 | |
| 1.0.5 | 0 / 3 | |
| 1.0.4 | 0 / 3 | |
| 1.0.3 | 0 / 3 | |
| 1.0.2 | 0 / 3 | |
| 1.0.1 | 0 / 3 |
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gnz) than the most recent previously approved version (ronag) on 2026-02-26, but gnz is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.