mem-fs-editor
File edition helpers working on top of mem-fs
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/ejs | AI (phantom-deps): @types/ejs is a runtime dep for TypeScript type exports; not a phantom dep for this package. | ai | |
| phantom-deps | phantom-dep:@types/picomatch | AI (phantom-deps): @types/picomatch is a runtime dep for TypeScript type exports; not a phantom dep for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 12.0.3 | 14 / 21 | |
| 12.0.2 | 14 / 21 | |
| 12.0.1 | 13 / 22 | |
| 12.0.0 | 13 / 21 | |
| 7.1.0 | 11 / 7 |
v12.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.