@expo/dom-webview
A WebView specifically designed for Expo DOM components
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 | missing-githead | AI (provenance): Canary releases in the Expo ecosystem frequently lack gitHead due to CI pipeline differences; publisher has strong track record with 2055 approved packages. | ai | |
| publish-pattern | suspicious-version-number | AI (publish-pattern): Canary date-stamped versioning is standard practice for Expo packages; not indicative of malicious intent. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher rotation within the Expo org (brentvatne → alanhughes) is consistent with normal team operations for this well-established package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Expo is a large org with multiple maintainers; team membership changes are routine and not a risk signal for this package. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 56.0.5 | 0 / 3 | |
| 56.0.4 | 0 / 3 | |
| 56.0.3 | 0 / 3 | |
| 56.0.2 | 0 / 3 | |
| 56.0.1 | 0 / 2 | |
| 56.0.0 | 0 / 2 | |
| 55.0.6 | 0 / 1 | |
| 55.0.5 | 0 / 1 | |
| 55.0.4 | 0 / 1 | |
| 55.0.3 | 0 / 1 | |
| 55.0.2 | 0 / 1 | |
| 55.0.1 | 0 / 1 | |
| 55.0.0 | 0 / 1 | |
| 0.2.8 | 0 / 1 | |
| 0.2.7 | 0 / 1 | |
| 0.2.6 | 0 / 1 | |
| 0.2.5 | 0 / 1 | |
| 0.2.4 | 0 / 1 | |
| 0.2.3 | 0 / 1 | |
| 0.2.2 | 0 / 1 | |
| 0.2.1 | 0 / 1 | |
| 0.2.0 | 0 / 1 | |
| 0.1.5 | 0 / 1 | |
| 0.1.4 | 0 / 1 | |
| 0.1.3 | 0 / 1 | |
| 0.1.2 | 0 / 1 | |
| 0.1.1 | 0 / 1 | |
| 0.1.0 | 0 / 1 | |
| 0.0.2 | 0 / 1 | |
| 0.0.1 | 0 / 1 |
v56.0.5
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 2026-05-14. This could indicate a legitimate maintainer transition or an account compromise.
v56.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.