@aws-sdk/client-dynamodb
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@smithy/middleware-serde | AI (phantom-deps): Framework-scoped smithy package loaded by convention in AWS SDK v3; not a real phantom dependency risk for this package. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-stack | AI (phantom-deps): Framework-scoped smithy package loaded by convention in AWS SDK v3; not a real phantom dependency risk for this package. | ai |
Versions (showing 100 of 616)
| Version | Deps | Published |
|---|---|---|
| 3.844.0 | 43 / 6 | |
| 3.840.0 | 43 / 6 | |
| 3.839.0 | 43 / 6 | |
| 3.835.0 | 43 / 6 | |
| 3.830.0 | 43 / 6 | |
| 3.828.0 | 43 / 6 | |
| 3.826.0 | 43 / 6 | |
| 3.825.0 | 43 / 6 | |
| 3.823.0 | 43 / 6 | |
| 3.821.0 | 43 / 6 | |
| 3.817.0 | 43 / 6 | |
| 3.816.0 | 43 / 6 | |
| 3.812.0 | 43 / 6 | |
| 3.810.0 | 43 / 6 | |
| 3.808.0 | 43 / 6 | |
| 3.806.0 | 43 / 6 | |
| 3.804.0 | 43 / 6 | |
| 3.803.0 | 43 / 6 | |
| 3.799.0 | 43 / 6 | |
| 3.798.0 | 43 / 6 | |
| 3.797.0 | 43 / 6 | |
| 3.796.0 | 43 / 6 | |
| 3.788.0 | 43 / 6 | |
| 3.787.0 | 43 / 6 | |
| 3.786.0 | 43 / 6 | |
| 3.782.0 | 43 / 6 | |
| 3.777.0 | 43 / 6 | |
| 3.775.0 | 43 / 6 | |
| 3.774.0 | 43 / 6 | |
| 3.772.0 | 43 / 6 | |
| 3.767.0 | 43 / 6 | |
| 3.758.0 | 43 / 6 | |
| 3.751.0 | 43 / 6 | |
| 3.750.0 | 43 / 6 | |
| 3.749.0 | 43 / 6 | |
| 3.744.0 | 43 / 6 | |
| 3.743.0 | 43 / 6 | |
| 3.741.0 | 43 / 6 | |
| 3.738.0 | 43 / 6 | |
| 3.734.0 | 43 / 6 | |
| 3.733.0 | 43 / 6 | |
| 3.731.1 | 43 / 6 | |
| 3.731.0 | 43 / 6 | |
| 3.730.0 | 43 / 6 | |
| 3.670.0 | 44 / 7 | |
| 3.669.0 | 44 / 7 | |
| 3.668.0 | 44 / 7 | |
| 3.667.0 | 44 / 7 | |
| 3.666.0 | 44 / 7 | |
| 3.665.0 | 44 / 7 | |
| 3.664.0 | 44 / 7 | |
| 3.662.0 | 44 / 7 | |
| 3.658.1 | 44 / 7 | |
| 3.658.0 | 44 / 7 | |
| 3.656.0 | 44 / 7 | |
| 3.654.0 | 44 / 7 | |
| 3.651.1 | 44 / 7 | |
| 3.650.0 | 44 / 7 | |
| 3.649.0 | 44 / 7 | |
| 3.648.0 | 44 / 7 | |
| 3.645.0 | 44 / 7 | |
| 3.637.0 | 44 / 7 | |
| 3.635.0 | 44 / 7 | |
| 3.632.0 | 44 / 7 | |
| 3.631.0 | 44 / 7 | |
| 3.629.0 | 44 / 7 | |
| 3.624.0 | 44 / 7 | |
| 3.623.0 | 44 / 7 | |
| 3.622.0 | 44 / 7 | |
| 3.621.0 | 44 / 7 | |
| 3.620.1 | 44 / 7 | |
| 3.620.0 | 44 / 7 | |
| 3.619.0 | 44 / 7 | |
| 3.616.0 | 44 / 7 | |
| 3.614.0 | 44 / 7 | |
| 3.613.0 | 44 / 7 | |
| 3.609.0 | 44 / 7 | |
| 3.606.0 | 44 / 7 | |
| 3.602.0 | 44 / 7 | |
| 3.600.0 | 44 / 7 | |
| 3.598.0 | 44 / 7 | |
| 3.596.0 | 44 / 7 | |
| 3.592.0 | 44 / 7 | |
| 3.590.0 | 44 / 7 | |
| 3.588.0 | 44 / 7 | |
| 3.587.0 | 44 / 7 | |
| 3.585.0 | 44 / 7 | |
| 3.584.0 | 44 / 7 | |
| 3.583.0 | 44 / 7 | |
| 3.582.0 | 44 / 7 | |
| 3.577.0 | 44 / 7 | |
| 3.576.0 | 44 / 7 | |
| 3.575.0 | 44 / 7 | |
| 3.574.0 | 44 / 7 | |
| 3.572.0 | 44 / 7 | |
| 3.569.0 | 44 / 7 | |
| 3.568.0 | 42 / 7 | |
| 3.567.0 | 42 / 7 | |
| 3.565.0 | 42 / 8 | |
| 3.564.0 | 42 / 8 |
v3.796.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.788.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.787.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.786.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.782.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.777.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.775.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.774.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.772.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.767.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.758.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.751.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.750.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.749.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.744.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.743.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.741.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.738.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.734.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.733.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.731.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.731.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.730.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.670.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.669.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.668.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.667.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.666.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.665.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.664.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.662.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.658.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.658.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.656.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.654.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.651.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.650.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.649.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.648.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.645.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.637.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.635.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.632.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.631.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.629.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.624.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.623.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.622.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.621.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.620.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.620.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.619.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.616.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.614.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.613.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.609.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.606.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.602.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.600.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.598.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.596.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.592.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.590.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.588.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.587.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.585.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.584.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.583.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.582.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.577.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.576.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.575.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.574.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.572.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.569.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.568.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.567.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.565.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.564.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.