@aws-sdk/client-docdb
AWS SDK for JavaScript Docdb Client for Node.js, Browser and React Native
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): AWS SDK packages are published via automated pipeline without Sigstore provenance; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@aws-sdk/middleware-sdk-rds | AI (dependencies): First-party AWS SDK middleware for RDS/DocDB signing; expected dependency for this client. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-serde | AI (phantom-deps): Smithy framework package loaded by convention in AWS SDK clients; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-stack | AI (phantom-deps): Smithy framework package loaded by convention in AWS SDK clients; not a real phantom dep. | ai |
Versions (showing 100 of 620)
| Version | Deps | Published |
|---|---|---|
| 3.839.0 | 41 / 6 | |
| 3.835.0 | 41 / 6 | |
| 3.830.0 | 41 / 6 | |
| 3.828.0 | 41 / 6 | |
| 3.826.0 | 41 / 6 | |
| 3.825.0 | 41 / 6 | |
| 3.823.0 | 41 / 6 | |
| 3.821.0 | 41 / 6 | |
| 3.817.0 | 41 / 6 | |
| 3.816.0 | 41 / 6 | |
| 3.812.0 | 41 / 6 | |
| 3.810.0 | 41 / 6 | |
| 3.808.0 | 41 / 6 | |
| 3.806.0 | 41 / 6 | |
| 3.804.0 | 41 / 6 | |
| 3.803.0 | 41 / 6 | |
| 3.799.0 | 41 / 6 | |
| 3.798.0 | 41 / 6 | |
| 3.797.0 | 41 / 6 | |
| 3.796.0 | 41 / 6 | |
| 3.787.0 | 41 / 6 | |
| 3.782.0 | 41 / 6 | |
| 3.777.0 | 41 / 6 | |
| 3.775.0 | 41 / 6 | |
| 3.774.0 | 41 / 6 | |
| 3.772.0 | 41 / 6 | |
| 3.758.0 | 41 / 6 | |
| 3.750.0 | 41 / 6 | |
| 3.749.0 | 41 / 6 | |
| 3.744.0 | 41 / 6 | |
| 3.743.0 | 41 / 6 | |
| 3.741.0 | 41 / 6 | |
| 3.738.0 | 41 / 6 | |
| 3.734.0 | 41 / 6 | |
| 3.731.1 | 41 / 6 | |
| 3.731.0 | 41 / 6 | |
| 3.730.0 | 41 / 6 | |
| 3.726.1 | 43 / 6 | |
| 3.726.0 | 43 / 6 | |
| 3.723.0 | 43 / 6 | |
| 3.721.0 | 43 / 6 | |
| 3.717.0 | 43 / 6 | |
| 3.716.0 | 43 / 6 | |
| 3.714.0 | 43 / 6 | |
| 3.713.0 | 43 / 6 | |
| 3.712.0 | 43 / 6 | |
| 3.709.0 | 43 / 6 | |
| 3.699.0 | 43 / 6 | |
| 3.696.0 | 43 / 6 | |
| 3.693.0 | 43 / 6 | |
| 3.692.0 | 43 / 6 | |
| 3.691.0 | 43 / 6 | |
| 3.687.0 | 43 / 6 | |
| 3.686.0 | 43 / 6 | |
| 3.682.0 | 43 / 6 | |
| 3.679.0 | 43 / 6 | |
| 3.678.0 | 43 / 6 | |
| 3.677.0 | 43 / 6 | |
| 3.675.0 | 43 / 6 | |
| 3.670.0 | 43 / 6 | |
| 3.669.0 | 43 / 6 | |
| 3.668.0 | 43 / 6 | |
| 3.667.0 | 43 / 6 | |
| 3.666.0 | 43 / 6 | |
| 3.665.0 | 43 / 6 | |
| 3.664.0 | 43 / 6 | |
| 3.662.0 | 43 / 6 | |
| 3.658.1 | 43 / 6 | |
| 3.658.0 | 43 / 6 | |
| 3.654.0 | 43 / 6 | |
| 3.651.1 | 43 / 6 | |
| 3.650.0 | 43 / 6 | |
| 3.649.0 | 43 / 6 | |
| 3.645.0 | 43 / 6 | |
| 3.637.0 | 43 / 6 | |
| 3.635.0 | 43 / 6 | |
| 3.632.0 | 43 / 6 | |
| 3.631.0 | 43 / 6 | |
| 3.629.0 | 43 / 6 | |
| 3.624.0 | 43 / 6 | |
| 3.623.0 | 43 / 6 | |
| 3.622.0 | 43 / 6 | |
| 3.621.0 | 43 / 6 | |
| 3.620.1 | 43 / 6 | |
| 3.620.0 | 43 / 6 | |
| 3.616.0 | 43 / 6 | |
| 3.614.0 | 43 / 6 | |
| 3.613.0 | 43 / 6 | |
| 3.609.0 | 43 / 6 | |
| 3.606.0 | 43 / 6 | |
| 3.600.0 | 43 / 6 | |
| 3.598.0 | 43 / 6 | |
| 3.596.0 | 43 / 6 | |
| 3.592.0 | 43 / 6 | |
| 3.590.0 | 43 / 6 | |
| 3.588.0 | 43 / 6 | |
| 3.587.0 | 43 / 6 | |
| 3.583.0 | 43 / 6 | |
| 3.582.0 | 43 / 6 | |
| 3.577.0 | 43 / 6 |
v3.797.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.796.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.787.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.782.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.777.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.775.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.774.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.772.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.758.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.750.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.749.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.744.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.743.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.741.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.738.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.734.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.731.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.731.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.730.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.726.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.726.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.723.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.721.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.717.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.716.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.714.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.713.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.712.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.709.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.699.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.696.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.693.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.692.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.691.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.687.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.686.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.682.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.679.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.678.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.677.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.675.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.670.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.669.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.668.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.667.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.666.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.665.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.664.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.662.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.658.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.658.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.654.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.651.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.650.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.649.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.645.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.637.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.635.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.632.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.631.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.629.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.624.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.623.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.622.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.621.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.620.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.620.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.616.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.614.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.613.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.609.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.606.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.600.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.598.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.596.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.592.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.590.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.588.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.587.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.583.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.582.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.577.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.