memfs
In-memory file-system with Node's fs API.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Published via GitHub Actions with SLSA provenance; gitHead absence is a CI config detail, not a risk. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing with SLSA provenance; stable for this package. | ai | |
| phantom-deps | phantom-dep:glob-to-regex.js | AI (phantom-deps): Declared dep used transitively; stable false positive for this monorepo-style package. | ai | |
| phantom-deps | phantom-dep:@jsonjoy.com/util | AI (phantom-deps): Declared dep used transitively; stable false positive for this monorepo-style package. | ai | |
| phantom-deps | phantom-dep:@jsonjoy.com/fs-print | AI (phantom-deps): Declared dep used transitively; stable false positive for this monorepo-style package. | ai | |
| phantom-deps | phantom-dep:thingies | AI (phantom-deps): Declared dep used transitively; stable false positive for this monorepo-style package. | ai | |
| phantom-deps | phantom-dep:@jsonjoy.com/fs-snapshot | AI (phantom-deps): Declared dep used transitively; stable false positive for this monorepo-style package. | ai | |
| phantom-deps | phantom-dep:@jsonjoy.com/fs-node-builtins | AI (phantom-deps): Declared dep used transitively; stable false positive for this monorepo-style package. | ai | |
| phantom-deps | phantom-dep:@jsonjoy.com/json-pack | AI (phantom-deps): Declared dep used transitively; stable false positive for this monorepo-style package. | ai | |
| phantom-deps | phantom-dep:tree-dump | AI (phantom-deps): Declared dep used transitively; stable false positive for this monorepo-style package. | ai |
Versions (showing 100 of 218)
| Version | Deps | Published |
|---|---|---|
| 4.57.3 | 14 / 27 | |
| 4.57.2 | 14 / 27 | |
| 4.57.1 | 14 / 27 | |
| 4.57.0 | 14 / 27 | |
| 4.56.11 | 14 / 27 | |
| 4.56.10 | 14 / 27 | |
| 4.56.9 | 14 / 27 | |
| 4.56.8 | 14 / 27 | |
| 4.56.7 | 14 / 27 | |
| 4.54.0 | 6 / 31 | |
| 4.53.0 | 6 / 31 | |
| 4.52.0 | 6 / 31 | |
| 4.51.1 | 6 / 31 | |
| 4.51.0 | 6 / 31 | |
| 4.50.0 | 6 / 31 | |
| 4.49.0 | 6 / 31 | |
| 4.48.1 | 6 / 31 | |
| 4.48.0 | 6 / 31 | |
| 4.47.0 | 6 / 31 | |
| 4.46.1 | 6 / 31 | |
| 4.46.0 | 6 / 31 | |
| 4.45.0 | 6 / 31 | |
| 4.44.0 | 6 / 31 | |
| 4.43.1 | 6 / 31 | |
| 4.43.0 | 6 / 31 | |
| 4.42.0 | 6 / 31 | |
| 4.41.0 | 6 / 31 | |
| 4.40.0 | 6 / 31 | |
| 4.39.0 | 6 / 31 | |
| 4.38.3 | 6 / 31 | |
| 4.38.2 | 6 / 31 | |
| 4.38.1 | 6 / 31 | |
| 4.38.0 | 5 / 31 | |
| 4.37.1 | 5 / 31 | |
| 4.37.0 | 5 / 31 | |
| 4.36.3 | 5 / 31 | |
| 4.36.2 | 4 / 31 | |
| 4.36.1 | 4 / 31 | |
| 4.36.0 | 4 / 31 | |
| 4.35.0 | 4 / 31 | |
| 4.34.0 | 4 / 31 | |
| 4.33.0 | 4 / 31 | |
| 4.32.1 | 4 / 31 | |
| 4.32.0 | 4 / 31 | |
| 4.31.0 | 4 / 31 | |
| 4.30.1 | 4 / 31 | |
| 4.30.0 | 4 / 31 | |
| 4.29.0 | 4 / 31 | |
| 4.28.1 | 4 / 31 | |
| 4.28.0 | 4 / 31 | |
| 4.27.0 | 4 / 31 | |
| 4.26.0 | 4 / 31 | |
| 4.25.1 | 4 / 31 | |
| 4.25.0 | 4 / 31 | |
| 4.24.0 | 4 / 31 | |
| 4.23.0 | 4 / 31 | |
| 4.22.1 | 4 / 31 | |
| 4.22.0 | 4 / 31 | |
| 4.21.0 | 4 / 31 | |
| 4.20.1 | 4 / 31 | |
| 4.20.0 | 4 / 31 | |
| 4.19.0 | 4 / 31 | |
| 4.18.0 | 4 / 31 | |
| 4.17.2 | 4 / 31 | |
| 4.17.1 | 4 / 31 | |
| 4.17.0 | 4 / 31 | |
| 4.16.0 | 4 / 31 | |
| 4.15.4 | 4 / 31 | |
| 4.15.3 | 4 / 31 | |
| 4.15.2 | 4 / 31 | |
| 4.15.1 | 4 / 31 | |
| 4.15.0 | 4 / 31 | |
| 4.14.1 | 4 / 31 | |
| 4.14.0 | 4 / 31 | |
| 4.13.0 | 4 / 31 | |
| 4.12.0 | 4 / 31 | |
| 4.11.2 | 4 / 31 | |
| 4.11.1 | 4 / 31 | |
| 4.11.0 | 4 / 31 | |
| 4.10.0 | 4 / 31 | |
| 4.9.4 | 4 / 31 | |
| 4.9.3 | 4 / 31 | |
| 4.9.2 | 4 / 31 | |
| 4.9.1 | 4 / 31 | |
| 4.9.0 | 1 / 31 | |
| 4.8.2 | 1 / 31 | |
| 4.8.1 | 1 / 30 | |
| 4.8.0 | 1 / 30 | |
| 4.7.7 | 1 / 30 | |
| 4.7.6 | 1 / 30 | |
| 4.7.5 | 1 / 30 | |
| 4.7.4 | 2 / 31 | |
| 4.7.3 | 3 / 31 | |
| 4.7.2 | 3 / 31 | |
| 4.7.1 | 2 / 31 | |
| 4.7.0 | 2 / 31 | |
| 4.6.1 | 2 / 31 | |
| 4.6.0 | 2 / 31 | |
| 4.5.0 | 2 / 31 | |
| 4.4.0 | 2 / 31 |
v4.57.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.57.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.57.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.57.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.56.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.56.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.56.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.56.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.56.7
2 findingsThis version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.54.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.53.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.52.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.51.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.43.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.36.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.36.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.