@callstack/async-storage
Cross platform storage for React Native and Web, built on top of React Native
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): New maintainers (grabbou, lukewalczak) are Callstack-affiliated; grabbou is the named package author. This is a legitimate internal org transition, not a hijack. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to lukewalczak, a Callstack employee; grabbou (package author) is also a new maintainer. Consistent with legitimate org restructuring in 2017. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Added maintainers are known Callstack members; no malicious indicators. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of 'callstack' org account in favor of individual maintainers is consistent with legitimate org restructuring. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.0.3 | 1 / 12 | |
| 1.1.0 | 1 / 12 | |
| 1.0.1 | 1 / 12 | |
| 1.0.0 | 1 / 13 |
v1.1.0
3 findingsAll previous maintainers (callstack) were replaced by new maintainers (lukewalczak, grabbou). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2017-10-05. 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.
v1.0.1
3 findingsAll previous maintainers (callstack) were replaced by new maintainers (lukewalczak, grabbou). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2017-10-02. 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.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.