@aws-amplify/cache
Cache 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 230)
| Version | Deps | Published |
|---|---|---|
| 4.0.23 | 1 / 0 | |
| 4.0.22 | 1 / 0 | |
| 4.0.21 | 1 / 0 | |
| 4.0.20 | 1 / 0 | |
| 4.0.19 | 1 / 0 | |
| 4.0.18 | 1 / 0 | |
| 4.0.17 | 1 / 0 | |
| 4.0.16 | 1 / 0 | |
| 4.0.15 | 1 / 0 | |
| 4.0.14 | 1 / 0 | |
| 4.0.13 | 1 / 0 | |
| 4.0.12 | 1 / 0 | |
| 4.0.11 | 1 / 0 | |
| 4.0.10 | 1 / 0 | |
| 4.0.9 | 1 / 0 | |
| 4.0.8 | 1 / 0 | |
| 4.0.7 | 1 / 0 | |
| 4.0.6 | 1 / 0 | |
| 4.0.5 | 1 / 0 | |
| 4.0.4 | 1 / 0 | |
| 4.0.3 | 1 / 0 | |
| 4.0.2 | 1 / 0 | |
| 4.0.1 | 1 / 0 | |
| 4.0.0 | 1 / 0 | |
| 3.1.57 | 1 / 0 | |
| 3.1.56 | 1 / 0 | |
| 3.1.55 | 1 / 0 | |
| 3.1.54 | 1 / 0 | |
| 3.1.53 | 1 / 0 | |
| 3.1.52 | 1 / 0 | |
| 3.1.51 | 1 / 0 | |
| 3.1.50 | 1 / 0 | |
| 3.1.49 | 1 / 0 | |
| 3.1.48 | 1 / 0 | |
| 3.1.47 | 1 / 0 | |
| 3.1.46 | 1 / 0 | |
| 3.1.45 | 1 / 0 | |
| 3.1.44 | 1 / 0 | |
| 3.1.43 | 1 / 0 | |
| 3.1.42 | 1 / 0 | |
| 3.1.41 | 1 / 0 | |
| 3.1.40 | 1 / 0 | |
| 3.1.39 | 1 / 0 | |
| 3.1.38 | 1 / 0 | |
| 3.1.37 | 1 / 0 | |
| 3.1.36 | 1 / 0 | |
| 3.1.35 | 1 / 0 | |
| 3.1.34 | 1 / 0 | |
| 3.1.33 | 1 / 0 | |
| 3.1.32 | 1 / 0 | |
| 3.1.31 | 1 / 0 | |
| 3.1.30 | 1 / 0 | |
| 3.1.29 | 1 / 0 | |
| 3.1.28 | 1 / 0 | |
| 3.1.27 | 1 / 0 | |
| 3.1.26 | 1 / 0 | |
| 3.1.25 | 1 / 0 | |
| 3.1.24 | 1 / 0 | |
| 3.1.23 | 1 / 0 | |
| 3.1.22 | 1 / 0 | |
| 3.1.21 | 1 / 0 | |
| 3.1.20 | 1 / 0 | |
| 3.1.19 | 1 / 0 | |
| 3.1.18 | 1 / 0 | |
| 3.1.17 | 1 / 0 | |
| 3.1.16 | 1 / 0 | |
| 3.1.15 | 1 / 0 | |
| 3.1.14 | 1 / 0 | |
| 3.1.13 | 1 / 0 | |
| 3.1.12 | 1 / 0 | |
| 3.1.11 | 1 / 0 | |
| 3.1.10 | 1 / 0 | |
| 3.1.9 | 1 / 0 | |
| 3.1.8 | 1 / 0 | |
| 3.1.7 | 1 / 0 | |
| 3.1.6 | 1 / 0 | |
| 3.1.5 | 1 / 0 | |
| 3.1.4 | 1 / 0 | |
| 3.1.3 | 1 / 0 | |
| 3.1.2 | 1 / 0 | |
| 3.1.0 | 1 / 0 | |
| 2.1.8 | 1 / 0 | |
| 2.1.7 | 1 / 0 | |
| 2.1.6 | 1 / 0 | |
| 2.1.5 | 1 / 0 | |
| 2.1.3 | 1 / 0 | |
| 2.1.2 | 1 / 0 | |
| 2.1.1 | 1 / 0 | |
| 2.1.0 | 1 / 0 | |
| 1.2.3 | 1 / 0 | |
| 1.2.0 | 1 / 0 | |
| 1.1.4 | 1 / 0 | |
| 1.1.3 | 1 / 0 | |
| 1.1.2 | 1 / 19 | |
| 1.0.34 | 1 / 19 | |
| 1.0.32 | 1 / 19 | |
| 1.0.31 | 1 / 19 | |
| 1.0.30 | 1 / 19 | |
| 1.0.29 | 1 / 19 | |
| 1.0.28 | 1 / 21 |
v4.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.