ensure-array
Ensure that an object is an array. Moves error checking out of your code.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage is in Jakefile.js (dev build tool), not in runtime code. Stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): cp.spawn() is in Jakefile.js for running dev tasks only, not in the published runtime module. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package is 14+ years old, predating Sigstore provenance. No provenance is expected and not a risk signal here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 0 / 2 | |
| 0.0.5 | 0 / 2 | |
| 0.0.4 | 0 / 2 | |
| 0.0.3 | 0 / 2 | |
| 0.0.2 | 0 / 1 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.