expo-file-system-interface
Interface for expo-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 | publisher-changed | AI (provenance): Publisher change from sjchmiela to brentvatne reflects a legitimate Expo team transition; both are known 650 Industries contributors within the official expo/expo monorepo. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): janicduplessis and wkozyra are known Expo/650 Industries contributors; additions reflect normal team roster changes for this official Expo package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of jakubste is consistent with normal team transitions within 650 Industries for this official Expo monorepo package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 0 / 1 | |
| 2.0.0 | 1 / 0 | |
| 1.1.0 | 1 / 0 | |
| 1.0.2 | 1 / 0 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 | |
| 0.0.1 | 0 / 0 |
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2019-02-27. 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
2 findingsPackage 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-01-04. This could indicate a legitimate maintainer transition or an account compromise.