array.prototype.flatmap
An ES2019 spec-compliant `Array.prototype.flatMap` 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package from a highly trusted publisher; lack of provenance is not a meaningful risk signal here. | ai | |
| dependencies | unvetted-dep:define-properties | AI (dependencies): define-properties is a standard es-shims ecosystem dependency by the same maintainer (ljharb); stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:es-shim-unscopables | AI (dependencies): es-shim-unscopables is a standard es-shims ecosystem dependency by the same maintainer (ljharb); stable false positive for this package family. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.3.3 | 4 / 14 | |
| 1.3.2 | 4 / 15 | |
| 1.3.1 | 4 / 15 | |
| 1.3.0 | 4 / 13 | |
| 1.2.5 | 3 / 12 | |
| 1.2.4 | 4 / 12 | |
| 1.2.3 | 3 / 10 | |
| 1.2.2 | 3 / 10 | |
| 1.2.1 | 3 / 11 | |
| 1.2.0 | 3 / 11 | |
| 1.1.1 | 3 / 11 | |
| 1.1.0 | 3 / 10 | |
| 1.0.1 | 3 / 10 | |
| 1.0.0 | 3 / 10 |
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
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.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.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.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.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.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.