gentle-fs
Gentle Filesystem operations
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:path-is-inside | AI (phantom-deps): Phantom deps in utility libraries are common; dependencies are declared for downstream use or indirect consumption. | ai | |
| phantom-deps | phantom-dep:graceful-fs | AI (phantom-deps): Phantom deps in utility libraries are common; dependencies are declared for downstream use or indirect consumption. | ai | |
| phantom-deps | phantom-dep:read-cmd-shim | AI (phantom-deps): Phantom deps in utility libraries are common; dependencies are declared for downstream use or indirect consumption. | ai | |
| phantom-deps | phantom-dep:iferr | AI (phantom-deps): Phantom deps in utility libraries are common; dependencies are declared for downstream use or indirect consumption. | ai | |
| phantom-deps | phantom-dep:slide | AI (phantom-deps): Phantom deps in utility libraries are common; dependencies are declared for downstream use or indirect consumption. | ai | |
| phantom-deps | phantom-dep:aproba | AI (phantom-deps): Phantom deps in utility libraries are common; dependencies are declared for downstream use or indirect consumption. | ai | |
| phantom-deps | phantom-dep:mkdirp | AI (phantom-deps): Phantom deps in utility libraries are common; dependencies are declared for downstream use or indirect consumption. | ai | |
| phantom-deps | phantom-dep:fs-vacuum | AI (phantom-deps): Phantom deps in utility libraries are common; dependencies are declared for downstream use or indirect consumption. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance attestation; absence is expected for this era of npm packages. | ai | |
| provenance | publisher-changed | AI (provenance): The mikesherov → zkat transition in 2017 is a well-documented legitimate npm org maintainer handoff; zkat is a trusted long-time npm core contributor. This generalizes across versions. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.3.1 | 11 / 6 | |
| 2.3.0 | 11 / 8 | |
| 2.2.1 | 10 / 8 | |
| 2.2.0 | 10 / 8 | |
| 2.1.0 | 10 / 8 | |
| 2.0.1 | 8 / 8 | |
| 2.0.0 | 8 / 8 | |
| 1.0.2 | 9 / 8 | |
| 1.0.1 | 9 / 8 | |
| 1.0.0 | 9 / 8 |
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findings[Accepted risk] Package 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 2019-08-14. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2017-11-28. 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.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.