@aws-sdk/client-lambda-microvms
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
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.1095.0 | 8 / 6 | |
| 3.1094.0 | 8 / 6 | |
| 3.1093.0 | 8 / 6 | |
| 3.1092.0 | 8 / 6 | |
| 3.1091.0 | 8 / 6 | |
| 3.1090.0 | 8 / 6 | |
| 3.1089.0 | 8 / 6 | |
| 3.1088.0 | 8 / 6 | |
| 3.1087.0 | 8 / 6 | |
| 3.1086.0 | 8 / 6 | |
| 3.1085.0 | 8 / 6 | |
| 3.1084.0 | 8 / 6 | |
| 3.1083.0 | 8 / 6 | |
| 3.1082.0 | 8 / 6 | |
| 3.1081.0 | 8 / 6 | |
| 3.1080.0 | 8 / 6 | |
| 3.1079.0 | 8 / 6 | |
| 3.1078.0 | 8 / 6 | |
| 3.1077.0 | 8 / 6 | |
| 3.1076.0 | 10 / 6 | |
| 3.1075.0 | 10 / 6 | |
| 3.1074.0 | 10 / 6 |
v3.1095.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1094.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1093.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1092.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1091.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1090.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1089.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1088.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1087.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1086.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1085.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1084.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1083.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1082.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1081.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1080.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1079.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1078.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1077.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1076.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1075.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1074.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.