expo-notifications
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ide/backoff | AI (dependencies): @ide/backoff is authored by an Expo core contributor; its use here is expected and benign. | ai | |
| phantom-deps | phantom-dep:assert | AI (phantom-deps): assert is a declared runtime dep used in build output; phantom-dep false positive for this package. | ai | |
| dependencies | unvetted-dep:badgin | AI (dependencies): badgin is a legitimate browser badge library; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:expo-application | AI (dependencies): expo-application is an official Expo SDK package; stable sibling dependency. | ai | |
| provenance | no-provenance | AI (provenance): Official Expo monorepo package; lack of Sigstore provenance is consistent across all Expo SDK releases. | ai |
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 57.0.6 | 5 / 5 | |
| 57.0.5 | 5 / 5 | |
| 57.0.4 | 5 / 5 | |
| 57.0.3 | 5 / 5 | |
| 57.0.2 | 5 / 5 | |
| 57.0.1 | 5 / 5 | |
| 57.0.0 | 5 / 5 | |
| 56.0.21 | 5 / 5 | |
| 56.0.20 | 5 / 5 | |
| 56.0.19 | 5 / 5 | |
| 56.0.18 | 5 / 5 | |
| 56.0.17 | 5 / 5 | |
| 56.0.16 | 5 / 5 | |
| 56.0.15 | 5 / 5 | |
| 56.0.14 | 5 / 5 | |
| 56.0.13 | 5 / 5 | |
| 56.0.12 | 5 / 5 | |
| 56.0.11 | 5 / 5 | |
| 56.0.10 | 5 / 5 | |
| 56.0.9 | 5 / 5 | |
| 56.0.7 | 5 / 5 | |
| 56.0.6 | 5 / 5 | |
| 56.0.5 | 5 / 5 | |
| 56.0.4 | 5 / 5 | |
| 56.0.3 | 5 / 5 | |
| 56.0.2 | 5 / 5 | |
| 56.0.1 | 5 / 5 | |
| 56.0.0 | 5 / 4 | |
| 55.0.25 | 5 / 2 | |
| 55.0.24 | 5 / 2 | |
| 55.0.23 | 5 / 2 | |
| 55.0.22 | 5 / 2 | |
| 55.0.21 | 5 / 2 | |
| 55.0.20 | 5 / 2 | |
| 55.0.19 | 5 / 2 | |
| 55.0.18 | 5 / 2 | |
| 55.0.17 | 5 / 2 | |
| 55.0.16 | 5 / 2 | |
| 55.0.15 | 5 / 2 | |
| 55.0.14 | 5 / 2 | |
| 55.0.13 | 5 / 2 | |
| 55.0.12 | 5 / 2 | |
| 55.0.11 | 5 / 2 | |
| 55.0.9 | 5 / 2 | |
| 55.0.8 | 5 / 2 | |
| 55.0.7 | 5 / 2 | |
| 55.0.6 | 7 / 2 | |
| 55.0.5 | 7 / 2 | |
| 55.0.4 | 7 / 2 | |
| 55.0.3 | 7 / 2 | |
| 55.0.2 | 7 / 2 |
v57.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (brentvatne) than the most recent previously approved version (alanhughes) on 2026-06-27, but brentvatne is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v56.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.19
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alanhughes) than the most recent previously approved version (brentvatne) on 2026-07-01, but alanhughes is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v55.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.