@bundled-es-modules/memfs
mirror of memfs, bundled and exposed as ES module
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:path | AI (phantom-deps): Phantom deps are expected in bundled modules; these are polyfills bundled into output, not direct imports. | ai | |
| phantom-deps | phantom-dep:util | AI (phantom-deps): Phantom deps are expected in bundled modules; these are polyfills bundled into output, not direct imports. | ai | |
| phantom-deps | phantom-dep:assert | AI (phantom-deps): Phantom deps are expected in bundled modules; these are polyfills bundled into output, not direct imports. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Phantom deps are expected in bundled modules; these are polyfills bundled into output, not direct imports. | ai | |
| phantom-deps | phantom-dep:events | AI (phantom-deps): Phantom deps are expected in bundled modules; these are polyfills bundled into output, not direct imports. | ai | |
| phantom-deps | phantom-dep:stream | AI (phantom-deps): Phantom deps are expected in bundled modules; these are polyfills bundled into output, not direct imports. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.17.0 | 7 / 2 | |
| 4.9.4 | 7 / 2 | |
| 4.9.3 | 7 / 2 | |
| 4.8.1 | 7 / 1 | |
| 4.2.3 | 8 / 1 | |
| 4.2.2 | 7 / 1 | |
| 4.2.1 | 7 / 1 |
v4.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.