file-stat
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:through2 | AI (phantom-deps): through2 is a core dependency for stream handling in this vinyl-fs abstraction utility; phantom-dep is a false positive for this package's design. | ai | |
| phantom-deps | phantom-dep:lazy-cache | AI (phantom-deps): lazy-cache is used for performance optimization; phantom-dep is expected for this caching pattern. | ai | |
| phantom-deps | phantom-dep:graceful-fs | AI (phantom-deps): graceful-fs is a standard dependency for robust file operations; phantom-dep is a false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 4 / 6 | |
| 0.2.3 | 4 / 6 | |
| 0.2.2 | 3 / 6 | |
| 0.2.1 | 3 / 6 | |
| 0.2.0 | 3 / 6 | |
| 0.1.3 | 3 / 6 | |
| 0.1.2 | 3 / 6 | |
| 0.1.1 | 2 / 1 | |
| 0.1.0 | 2 / 1 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.