expo-camera-interface
expo-camera interface package.
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): brentvatne is a well-known Expo core team member; publisher change from sjchmiela is a legitimate internal Expo team transition, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): janicduplessis and wkozyra are recognized Expo contributors; addition reflects normal team growth within the official Expo org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of jakubste is consistent with normal team transitions within the Expo org; no compromise indicators present. | 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.