@apify/storage-local
Drop in replacement of Apify API with a local SQLite and filesystem implementation. Not all API features are supported.
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 | slsa-provenance | AI (provenance): Official Apify org package published via CI with Sigstore attestation; stable pattern going forward. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is consistent with Apify org practices and backed by SLSA provenance. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is expected when switching to GitHub Actions CI publish flow; SLSA attestation compensates. | ai | |
| phantom-deps | phantom-dep:@types/integer | AI (phantom-deps): @types/integer is a TypeScript type package intentionally shipped as a runtime dep for better-sqlite3 integer support; not directly imported by convention. | ai | |
| phantom-deps | phantom-dep:@types/better-sqlite3 | AI (phantom-deps): @types/better-sqlite3 is a TypeScript type package intentionally shipped as a runtime dep; not directly imported by convention. | ai |
v3.0.0
3 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.
This version was published by a different npm account than previous versions on 2026-05-05. 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.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.