flatten
Flatten arbitrarily nested arrays into a non-nested list of non-array items. Maintained for legacy compatibility.
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is 13+ years old; 0.0.0 was common in early npm era. Publisher has strong track record. Not a malware indicator for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Tiny payload and no deps are consistent with a simple array-flatten utility. Legitimate minimal package from a trusted long-standing publisher. | ai | |
| provenance | publisher-changed | AI (provenance): mk-pmb is the documented new maintainer; repo URL points to their fork, description explicitly states legacy maintenance. Legitimate handoff, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mk-pmb added as maintainer is consistent with the documented ownership transfer; no malicious indicators present. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by mk-pmb's publish is explained by the original author abandoning the package and mk-pmb adopting it for legacy compatibility. No code changes introduced. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 0 / 0 | |
| 1.0.2 | 0 / 0 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 | |
| 0.0.1 | 0 / 0 | |
| 0.0.0 | 0 / 0 |
v1.0.3
2 findingsThis version was published by a different npm account than previous versions on 2019-10-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-01-20. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.