@aws-sdk/client-ebs
AWS SDK for JavaScript Ebs 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@aws-sdk/client-sts | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS SDK clients. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-sso-oidc | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS SDK clients. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-stack | AI (phantom-deps): Smithy framework-scoped package; loaded by convention in AWS SDK clients. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-stack | AI (phantom-deps): AWS SDK framework-scoped package loaded by convention; stable pattern. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/util-base64-node | AI (phantom-deps): AWS SDK framework-scoped package loaded by convention; stable pattern. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/util-base64-browser | AI (phantom-deps): AWS SDK framework-scoped package loaded by convention; stable pattern. | ai |
Versions (showing 100 of 611)
| Version | Deps | Published |
|---|---|---|
| 3.830.0 | 42 / 6 | |
| 3.828.0 | 42 / 6 | |
| 3.826.0 | 42 / 6 | |
| 3.825.0 | 42 / 6 | |
| 3.823.0 | 42 / 6 | |
| 3.821.0 | 42 / 6 | |
| 3.817.0 | 42 / 6 | |
| 3.816.0 | 42 / 6 | |
| 3.812.0 | 42 / 6 | |
| 3.810.0 | 42 / 6 | |
| 3.808.0 | 42 / 6 | |
| 3.806.0 | 42 / 6 | |
| 3.804.0 | 42 / 6 | |
| 3.803.0 | 42 / 6 | |
| 3.799.0 | 42 / 6 | |
| 3.798.0 | 42 / 6 | |
| 3.797.0 | 42 / 6 | |
| 3.796.0 | 42 / 6 | |
| 3.787.0 | 42 / 6 | |
| 3.782.0 | 42 / 6 | |
| 3.777.0 | 42 / 6 | |
| 3.775.0 | 42 / 6 | |
| 3.774.0 | 42 / 6 | |
| 3.772.0 | 42 / 6 | |
| 3.758.0 | 42 / 6 | |
| 3.750.0 | 42 / 6 | |
| 3.749.0 | 42 / 6 | |
| 3.744.0 | 42 / 6 | |
| 3.743.0 | 42 / 6 | |
| 3.741.0 | 42 / 6 | |
| 3.738.0 | 42 / 6 | |
| 3.734.0 | 42 / 6 | |
| 3.731.1 | 42 / 6 | |
| 3.731.0 | 42 / 6 | |
| 3.730.0 | 42 / 6 | |
| 3.726.1 | 44 / 6 | |
| 3.726.0 | 44 / 6 | |
| 3.723.0 | 44 / 6 | |
| 3.721.0 | 44 / 6 | |
| 3.716.0 | 44 / 6 | |
| 3.714.0 | 44 / 6 | |
| 3.713.0 | 44 / 6 | |
| 3.712.0 | 44 / 6 | |
| 3.709.0 | 44 / 6 | |
| 3.699.0 | 44 / 6 | |
| 3.696.0 | 44 / 6 | |
| 3.693.0 | 44 / 6 | |
| 3.692.0 | 44 / 6 | |
| 3.691.0 | 44 / 6 | |
| 3.687.0 | 44 / 6 | |
| 3.686.0 | 44 / 6 | |
| 3.682.0 | 44 / 6 | |
| 3.679.0 | 44 / 6 | |
| 3.678.0 | 44 / 6 | |
| 3.677.0 | 44 / 6 | |
| 3.675.0 | 44 / 6 | |
| 3.674.0 | 44 / 6 | |
| 3.670.0 | 43 / 7 | |
| 3.669.0 | 43 / 7 | |
| 3.668.0 | 43 / 7 | |
| 3.667.0 | 43 / 7 | |
| 3.666.0 | 43 / 7 | |
| 3.665.0 | 43 / 7 | |
| 3.664.0 | 43 / 7 | |
| 3.662.0 | 43 / 7 | |
| 3.658.1 | 43 / 7 | |
| 3.658.0 | 43 / 7 | |
| 3.654.0 | 43 / 7 | |
| 3.651.1 | 43 / 7 | |
| 3.650.0 | 43 / 7 | |
| 3.649.0 | 43 / 7 | |
| 3.645.0 | 43 / 7 | |
| 3.637.0 | 43 / 7 | |
| 3.635.0 | 43 / 7 | |
| 3.632.0 | 43 / 7 | |
| 3.631.0 | 43 / 7 | |
| 3.629.0 | 43 / 7 | |
| 3.624.0 | 43 / 7 | |
| 3.623.0 | 43 / 7 | |
| 3.622.0 | 43 / 7 | |
| 3.621.0 | 43 / 7 | |
| 3.620.1 | 43 / 7 | |
| 3.620.0 | 43 / 7 | |
| 3.616.0 | 43 / 7 | |
| 3.614.0 | 43 / 7 | |
| 3.613.0 | 43 / 7 | |
| 3.609.0 | 43 / 7 | |
| 3.606.0 | 43 / 7 | |
| 3.600.0 | 43 / 7 | |
| 3.598.0 | 43 / 7 | |
| 3.596.0 | 43 / 7 | |
| 3.592.0 | 43 / 7 | |
| 3.590.0 | 43 / 7 | |
| 3.588.0 | 43 / 7 | |
| 3.587.0 | 43 / 7 | |
| 3.583.0 | 43 / 7 | |
| 3.582.0 | 43 / 7 | |
| 3.577.0 | 43 / 7 | |
| 3.576.0 | 43 / 7 | |
| 3.575.0 | 43 / 7 |
v3.797.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.787.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.758.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.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.726.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.726.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.723.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.721.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.716.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.714.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.713.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.712.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.709.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.699.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.696.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.693.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.692.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.691.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.687.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.686.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.682.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.679.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.678.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.677.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.675.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.674.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.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.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.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.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.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.