@capraconsulting/webapp-deploy-lambda
CDK construct for deploying a webapp release to S3 and CloudFront
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 62 of 162)
| Version | Deps | Published |
|---|---|---|
| 2.5.42 | 0 / 16 | |
| 2.5.41 | 0 / 16 | |
| 2.5.40 | 0 / 16 | |
| 2.5.39 | 0 / 16 | |
| 2.5.38 | 0 / 16 | |
| 2.5.37 | 0 / 16 | |
| 2.5.36 | 0 / 16 | |
| 2.5.35 | 0 / 16 | |
| 2.5.34 | 0 / 16 | |
| 2.5.33 | 0 / 16 | |
| 2.5.32 | 0 / 16 | |
| 2.5.31 | 0 / 16 | |
| 2.5.30 | 0 / 16 | |
| 2.5.29 | 0 / 16 | |
| 2.5.28 | 0 / 16 | |
| 2.5.27 | 0 / 16 | |
| 2.5.26 | 0 / 16 | |
| 2.5.25 | 0 / 16 | |
| 2.5.24 | 0 / 16 | |
| 2.5.23 | 0 / 16 | |
| 2.5.22 | 0 / 16 | |
| 2.5.21 | 0 / 16 | |
| 2.5.20 | 0 / 16 | |
| 2.5.19 | 0 / 16 | |
| 2.5.18 | 0 / 16 | |
| 2.5.17 | 0 / 16 | |
| 2.5.16 | 0 / 16 | |
| 2.5.15 | 0 / 16 | |
| 2.5.14 | 0 / 16 | |
| 2.5.13 | 0 / 16 | |
| 2.5.12 | 0 / 16 | |
| 2.5.11 | 0 / 16 | |
| 2.5.10 | 0 / 16 | |
| 2.5.9 | 0 / 16 | |
| 2.5.8 | 0 / 16 | |
| 2.5.7 | 0 / 16 | |
| 2.5.6 | 0 / 16 | |
| 2.5.5 | 0 / 16 | |
| 2.5.4 | 0 / 16 | |
| 2.5.3 | 0 / 16 | |
| 2.5.2 | 0 / 15 | |
| 2.5.1 | 0 / 15 | |
| 2.5.0 | 0 / 15 | |
| 2.4.1 | 0 / 22 | |
| 2.4.0 | 0 / 22 | |
| 2.3.1 | 0 / 22 | |
| 2.3.0 | 0 / 22 | |
| 2.2.6 | 0 / 21 | |
| 2.2.5 | 0 / 21 | |
| 2.2.4 | 0 / 21 | |
| 2.2.3 | 0 / 21 | |
| 2.2.2 | 0 / 21 | |
| 2.2.1 | 0 / 21 | |
| 2.2.0 | 0 / 21 | |
| 2.1.6 | 0 / 21 | |
| 2.1.5 | 0 / 21 | |
| 2.1.4 | 0 / 21 | |
| 2.1.3 | 0 / 21 | |
| 2.1.2 | 0 / 21 | |
| 2.1.1 | 0 / 21 | |
| 2.1.0 | 0 / 21 | |
| 2.0.0 | 0 / 21 |
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.