← Home

throttleit

npm Repository Homepage

Throttle a function to limit its execution rate

6
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Keywords

throttleratelimitlimitedrate-limitratelimitthrottlingoptimizationperformancefunctionexecutionintervalbatch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Package was legitimately transferred to sindresorhus; repo URL in package.json confirms ownership. This is a stable, documented transition. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers (sindresorhus et al.) reflect the documented transfer to sindresorhus's stewardship; no compromise indicators. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of prior maintainers is consistent with the legitimate ownership transfer to sindresorhus. ai

Versions (showing 6 of 6)

Version Deps Published
2.1.0 0 / 2
2.0.0 0 / 2
1.0.1 0 / 1
1.0.0 0 / 1
0.0.2 0 / 0
0.0.1 0 / 0

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

2 findings
HIGH Publisher changed: dominicbarnes → sindresorhus (on 2023-11-17) provenance

This version was published by a different npm account than previous versions on 2023-11-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: tootallnate → dominicbarnes (on 2015-02-27) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-02-27. This could indicate a legitimate maintainer transition or an account compromise.