file-system-cache
A super-fast, promise-based cache that reads and writes to the file-system.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; absence is expected and not a security signal for this established package. | ai | |
| dependencies | unvetted-dep:bluebird | AI (dependencies): bluebird is a well-known, widely-used Promise library; its use is appropriate and expected for a promise-based cache package from this era. | ai | |
| phantom-deps | phantom-dep:@types/ramda | AI (phantom-deps): @types/ramda is a TypeScript type package mistakenly placed in dependencies; not imported at runtime and poses no security risk. | ai | |
| phantom-deps | phantom-dep:@types/fs-extra | AI (phantom-deps): @types/fs-extra is a TypeScript type package mistakenly placed in dependencies; not imported at runtime and poses no security risk. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is part of a standard AES decryption routine (createDecipheriv) in a cache library that supports encryption. No obfuscation or exfiltration concern. | ai | |
| dependencies | unvetted-dep:ramda | AI (dependencies): Ramda is a well-known, widely-used functional programming library. Its use in file-system-cache is legitimate and expected; this finding is a stable false positive for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 0 / 12 | |
| 2.4.7 | 4 / 8 | |
| 2.4.6 | 0 / 12 | |
| 2.4.5 | 0 / 14 | |
| 2.4.4 | 4 / 8 | |
| 2.4.3 | 4 / 8 | |
| 2.4.2 | 3 / 9 | |
| 2.4.1 | 2 / 10 | |
| 2.4.0 | 2 / 10 | |
| 2.3.0 | 2 / 9 | |
| 2.1.1 | 2 / 9 | |
| 2.1.0 | 2 / 9 | |
| 2.0.2 | 2 / 9 | |
| 2.0.1 | 2 / 9 | |
| 2.0.0 | 2 / 9 | |
| 1.1.0 | 2 / 9 | |
| 1.0.5 | 3 / 4 | |
| 1.0.4 | 3 / 4 | |
| 1.0.3 | 3 / 4 | |
| 1.0.2 | 3 / 9 | |
| 1.0.1 | 3 / 9 | |
| 1.0.0 | 3 / 9 |
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.