array.prototype.every
An ES5 spec-compliant `Array.prototype.every` shim/polyfill/replacement that works as far down as ES3.
Supply chain provenance
Status for the latest visible version.
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.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:is-string | AI (dependencies): is-string is a standard es-shims ecosystem package maintained by ljharb; its use here is expected and appropriate. | ai | |
| dependencies | unvetted-dep:call-bound | AI (dependencies): call-bound is a standard es-shims ecosystem package maintained by ljharb; its use here is expected and appropriate. | ai | |
| dependencies | unvetted-dep:es-abstract | AI (dependencies): es-abstract is the core es-shims utility library maintained by ljharb; its use in any es-shims polyfill is expected. | ai | |
| dependencies | unvetted-dep:define-properties | AI (dependencies): define-properties is a standard es-shims ecosystem package maintained by ljharb; its use here is expected and appropriate. | ai | |
| provenance | no-provenance | AI (provenance): Established package from a highly reputable publisher; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.1.7 | 5 / 15 | |
| 1.1.6 | 5 / 14 | |
| 1.1.5 | 4 / 14 | |
| 1.1.4 | 4 / 14 | |
| 1.1.3 | 4 / 14 | |
| 1.1.2 | 4 / 13 | |
| 1.1.1 | 4 / 13 | |
| 1.1.0 | 3 / 13 | |
| 1.0.0 | 3 / 12 |
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.