@aws-sdk/client-rds
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/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 | |
| dependencies | unvetted-dep:@aws-sdk/middleware-sdk-rds | AI (dependencies): First-party AWS SDK middleware package in the same @aws-sdk namespace; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-serde | AI (phantom-deps): Framework-scoped Smithy package loaded by convention in AWS SDK clients; stable false positive. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-stack | AI (phantom-deps): Framework-scoped Smithy package loaded by convention in AWS SDK clients; stable false positive. | ai |
Versions (showing 100 of 211)
| Version | Deps | Published |
|---|---|---|
| 3.996.0 | 41 / 6 | |
| 3.995.0 | 41 / 6 | |
| 3.994.0 | 41 / 6 | |
| 3.993.0 | 41 / 6 | |
| 3.992.0 | 41 / 6 | |
| 3.991.0 | 41 / 6 | |
| 3.990.0 | 41 / 6 | |
| 3.989.0 | 41 / 6 | |
| 3.988.0 | 41 / 6 | |
| 3.987.0 | 41 / 6 | |
| 3.986.0 | 41 / 6 | |
| 3.985.0 | 41 / 6 | |
| 3.984.0 | 41 / 6 | |
| 3.983.0 | 41 / 6 | |
| 3.982.0 | 41 / 6 | |
| 3.981.0 | 41 / 6 | |
| 3.980.0 | 41 / 6 | |
| 3.978.0 | 41 / 6 | |
| 3.975.0 | 41 / 6 | |
| 3.974.0 | 41 / 6 | |
| 3.972.0 | 41 / 6 | |
| 3.971.0 | 41 / 6 | |
| 3.970.0 | 41 / 6 | |
| 3.969.0 | 41 / 6 | |
| 3.968.0 | 41 / 6 | |
| 3.967.0 | 41 / 6 | |
| 3.966.0 | 41 / 6 | |
| 3.965.0 | 41 / 6 | |
| 3.964.0 | 41 / 6 | |
| 3.963.0 | 41 / 6 | |
| 3.962.0 | 41 / 6 | |
| 3.958.0 | 41 / 6 | |
| 3.957.0 | 41 / 6 | |
| 3.956.0 | 41 / 6 | |
| 3.955.0 | 41 / 6 | |
| 3.954.0 | 41 / 6 | |
| 3.953.0 | 41 / 6 | |
| 3.952.0 | 41 / 6 | |
| 3.948.0 | 41 / 6 | |
| 3.947.0 | 41 / 6 | |
| 3.946.0 | 41 / 6 | |
| 3.943.0 | 41 / 6 | |
| 3.940.0 | 41 / 6 | |
| 3.939.0 | 41 / 6 | |
| 3.938.0 | 41 / 6 | |
| 3.937.0 | 41 / 6 | |
| 3.936.0 | 41 / 6 | |
| 3.935.0 | 41 / 6 | |
| 3.934.0 | 41 / 6 | |
| 3.933.0 | 41 / 6 | |
| 3.932.0 | 41 / 6 | |
| 3.931.0 | 41 / 6 | |
| 3.930.0 | 41 / 6 | |
| 3.929.0 | 41 / 6 | |
| 3.928.0 | 41 / 6 | |
| 3.927.0 | 41 / 6 | |
| 3.926.0 | 41 / 6 | |
| 3.925.0 | 41 / 6 | |
| 3.922.0 | 41 / 6 | |
| 3.921.0 | 41 / 6 | |
| 3.552.0 | 42 / 7 | |
| 3.549.0 | 42 / 7 | |
| 3.540.0 | 42 / 7 | |
| 3.537.0 | 42 / 7 | |
| 3.536.0 | 42 / 7 | |
| 3.535.0 | 42 / 7 | |
| 3.534.0 | 42 / 7 | |
| 3.533.0 | 42 / 7 | |
| 3.529.1 | 42 / 7 | |
| 3.529.0 | 42 / 7 | |
| 3.528.0 | 43 / 7 | |
| 3.525.0 | 43 / 7 | |
| 3.523.0 | 43 / 7 | |
| 3.522.0 | 43 / 7 | |
| 3.521.0 | 43 / 7 | |
| 3.516.0 | 43 / 7 | |
| 3.515.0 | 43 / 7 | |
| 3.514.0 | 43 / 7 | |
| 3.513.0 | 43 / 7 | |
| 3.511.0 | 43 / 7 | |
| 3.509.0 | 43 / 7 | |
| 3.507.0 | 43 / 7 | |
| 3.325.0 | 38 / 8 | |
| 3.321.1 | 38 / 8 | |
| 3.321.0 | 38 / 8 | |
| 3.319.0 | 38 / 8 | |
| 3.317.0 | 38 / 8 | |
| 3.316.0 | 38 / 8 | |
| 3.216.0 | 38 / 8 | |
| 3.215.0 | 38 / 8 | |
| 3.213.0 | 38 / 8 | |
| 3.212.0 | 38 / 8 | |
| 3.211.0 | 38 / 8 | |
| 3.210.0 | 38 / 8 | |
| 3.209.0 | 38 / 8 | |
| 3.208.0 | 40 / 8 | |
| 3.204.0 | 40 / 8 | |
| 3.202.0 | 39 / 8 | |
| 3.201.0 | 39 / 8 | |
| 3.200.0 | 39 / 8 |
v3.929.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.928.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.927.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.926.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.925.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.922.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.921.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.552.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.549.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.540.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.537.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.536.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.535.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.534.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.533.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.529.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.529.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.528.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.525.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.523.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.522.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.521.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.516.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.515.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.514.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.513.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.511.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.509.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.507.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.325.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.321.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.321.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.319.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.317.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.316.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.216.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.215.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.213.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.212.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.211.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.210.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.209.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.208.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.204.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.202.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.201.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.200.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.