@aws-amplify/interactions
Interactions category of aws-amplify
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
Versions (showing 100 of 386)
| Version | Deps | Published |
|---|---|---|
| 5.2.19 | 7 / 0 | |
| 5.2.18 | 7 / 0 | |
| 5.2.17 | 7 / 0 | |
| 5.2.16 | 7 / 0 | |
| 5.2.15 | 7 / 0 | |
| 5.2.14 | 7 / 0 | |
| 5.2.13 | 7 / 0 | |
| 5.2.12 | 7 / 0 | |
| 5.2.11 | 7 / 0 | |
| 5.2.10 | 7 / 0 | |
| 5.2.9 | 7 / 0 | |
| 5.2.8 | 7 / 0 | |
| 5.2.7 | 7 / 0 | |
| 5.2.6 | 7 / 0 | |
| 5.2.5 | 7 / 0 | |
| 5.2.4 | 7 / 0 | |
| 5.2.3 | 7 / 0 | |
| 5.2.2 | 7 / 0 | |
| 5.2.1 | 7 / 0 | |
| 5.2.0 | 7 / 0 | |
| 5.1.1 | 7 / 0 | |
| 5.1.0 | 7 / 0 | |
| 5.0.33 | 7 / 0 | |
| 5.0.32 | 7 / 0 | |
| 5.0.31 | 7 / 0 | |
| 5.0.30 | 7 / 0 | |
| 5.0.29 | 7 / 0 | |
| 5.0.28 | 7 / 0 | |
| 5.0.27 | 7 / 0 | |
| 5.0.26 | 7 / 0 | |
| 5.0.25 | 7 / 0 | |
| 5.0.24 | 7 / 0 | |
| 5.0.23 | 7 / 0 | |
| 5.0.22 | 7 / 0 | |
| 5.0.21 | 7 / 0 | |
| 5.0.20 | 7 / 0 | |
| 5.0.19 | 7 / 0 | |
| 5.0.18 | 7 / 0 | |
| 5.0.17 | 7 / 0 | |
| 5.0.16 | 7 / 0 | |
| 5.0.15 | 7 / 0 | |
| 5.0.14 | 7 / 0 | |
| 5.0.13 | 7 / 0 | |
| 5.0.12 | 7 / 0 | |
| 5.0.11 | 7 / 0 | |
| 5.0.10 | 7 / 0 | |
| 5.0.9 | 7 / 0 | |
| 5.0.8 | 7 / 0 | |
| 5.0.7 | 7 / 0 | |
| 5.0.6 | 7 / 0 | |
| 5.0.5 | 7 / 0 | |
| 5.0.4 | 7 / 0 | |
| 5.0.3 | 7 / 0 | |
| 5.0.2 | 7 / 0 | |
| 5.0.1 | 7 / 0 | |
| 5.0.0 | 7 / 0 | |
| 4.1.12 | 6 / 0 | |
| 4.1.11 | 6 / 0 | |
| 4.1.10 | 6 / 0 | |
| 4.1.9 | 6 / 0 | |
| 4.1.8 | 6 / 0 | |
| 4.1.7 | 6 / 0 | |
| 4.1.6 | 6 / 0 | |
| 4.1.5 | 6 / 0 | |
| 4.1.4 | 6 / 0 | |
| 4.1.3 | 6 / 0 | |
| 4.1.2 | 6 / 0 | |
| 4.1.1 | 6 / 0 | |
| 4.1.0 | 6 / 0 | |
| 4.0.51 | 2 / 0 | |
| 4.0.50 | 2 / 0 | |
| 4.0.49 | 2 / 0 | |
| 4.0.48 | 2 / 0 | |
| 4.0.47 | 2 / 0 | |
| 4.0.46 | 2 / 0 | |
| 4.0.45 | 2 / 0 | |
| 4.0.44 | 2 / 0 | |
| 4.0.43 | 2 / 0 | |
| 4.0.42 | 2 / 0 | |
| 4.0.41 | 2 / 0 | |
| 4.0.40 | 2 / 0 | |
| 4.0.39 | 2 / 0 | |
| 4.0.38 | 2 / 0 | |
| 4.0.37 | 2 / 0 | |
| 4.0.36 | 2 / 0 | |
| 4.0.35 | 2 / 0 | |
| 4.0.34 | 2 / 0 | |
| 4.0.33 | 2 / 0 | |
| 4.0.32 | 2 / 0 | |
| 4.0.31 | 2 / 0 | |
| 4.0.30 | 2 / 0 | |
| 4.0.29 | 2 / 0 | |
| 4.0.28 | 2 / 0 | |
| 4.0.27 | 2 / 0 | |
| 4.0.26 | 2 / 0 | |
| 4.0.25 | 2 / 0 | |
| 4.0.24 | 2 / 0 | |
| 4.0.23 | 2 / 0 | |
| 4.0.22 | 2 / 0 | |
| 4.0.21 | 2 / 0 |
v5.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.