@aws-amplify/ui-react-notifications
The React Notifications package provides components for in-app messaging in Amplify connected applications.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): AWS Amplify packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 2.3.4 | 5 / 1 | |
| 2.3.3 | 5 / 1 | |
| 2.3.2 | 5 / 1 | |
| 2.3.1 | 5 / 1 | |
| 2.3.0 | 5 / 1 | |
| 2.2.15 | 5 / 1 | |
| 2.2.14 | 5 / 1 | |
| 2.2.13 | 5 / 1 | |
| 2.2.12 | 5 / 1 | |
| 2.2.11 | 5 / 1 | |
| 2.2.10 | 5 / 1 | |
| 2.2.9 | 5 / 1 | |
| 2.2.8 | 5 / 1 | |
| 2.2.7 | 5 / 1 | |
| 2.2.6 | 5 / 1 | |
| 2.2.5 | 5 / 1 | |
| 2.2.4 | 5 / 1 | |
| 2.2.3 | 5 / 1 | |
| 2.2.2 | 5 / 1 | |
| 2.2.1 | 5 / 1 | |
| 2.2.0 | 5 / 1 | |
| 2.1.1 | 5 / 1 | |
| 2.1.0 | 5 / 1 | |
| 2.0.38 | 5 / 1 | |
| 2.0.37 | 5 / 1 | |
| 2.0.36 | 5 / 1 | |
| 2.0.35 | 5 / 1 | |
| 2.0.34 | 5 / 1 | |
| 2.0.33 | 5 / 1 | |
| 2.0.32 | 5 / 1 | |
| 2.0.31 | 5 / 1 | |
| 2.0.30 | 5 / 1 | |
| 2.0.29 | 4 / 1 | |
| 2.0.28 | 4 / 1 | |
| 2.0.27 | 4 / 1 | |
| 2.0.26 | 4 / 1 | |
| 2.0.25 | 4 / 1 | |
| 2.0.24 | 4 / 1 | |
| 2.0.23 | 4 / 1 | |
| 2.0.22 | 4 / 1 | |
| 2.0.21 | 4 / 1 | |
| 2.0.20 | 4 / 1 | |
| 2.0.19 | 4 / 1 | |
| 2.0.18 | 4 / 1 | |
| 2.0.17 | 4 / 1 | |
| 2.0.16 | 4 / 1 | |
| 2.0.15 | 4 / 1 | |
| 2.0.14 | 4 / 1 | |
| 2.0.13 | 4 / 1 | |
| 2.0.12 | 4 / 1 | |
| 2.0.11 | 4 / 1 |
v2.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.