@aws-sdk/client-elastic-load-balancing
AWS SDK for JavaScript Elastic Load Balancing 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist-types/commands/CreateLoadBalancerPolicyCommand.d.ts | AI (source-diff): Base64 string is a sample RSA public key in JSDoc documentation; stable pattern across AWS SDK versions. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-serde | AI (phantom-deps): Smithy framework package loaded by convention; stable false positive for all AWS SDK clients. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-stack | AI (phantom-deps): Smithy framework package loaded by convention; stable false positive for all AWS SDK clients. | ai |
Versions (showing 51 of 184)
| Version | Deps | Published |
|---|---|---|
| 3.1063.0 | 10 / 6 | |
| 3.1062.0 | 10 / 6 | |
| 3.1061.0 | 10 / 6 | |
| 3.1060.0 | 10 / 6 | |
| 3.1059.0 | 10 / 6 | |
| 3.1058.0 | 10 / 6 | |
| 3.1057.0 | 10 / 6 | |
| 3.1056.0 | 10 / 6 | |
| 3.1055.0 | 10 / 6 | |
| 3.1054.0 | 10 / 6 | |
| 3.1053.0 | 10 / 6 | |
| 3.1052.0 | 10 / 6 | |
| 3.1051.0 | 10 / 6 | |
| 3.1050.0 | 10 / 6 | |
| 3.1049.0 | 10 / 6 | |
| 3.1048.0 | 10 / 6 | |
| 3.1047.0 | 18 / 6 | |
| 3.1046.0 | 18 / 6 | |
| 3.1045.0 | 40 / 6 | |
| 3.1044.0 | 40 / 6 | |
| 3.1043.0 | 40 / 6 | |
| 3.1042.0 | 40 / 6 | |
| 3.1041.0 | 40 / 6 | |
| 3.1040.0 | 40 / 6 | |
| 3.1039.0 | 40 / 6 | |
| 3.1038.0 | 40 / 6 | |
| 3.1037.0 | 40 / 6 | |
| 3.1036.0 | 40 / 6 | |
| 3.1035.0 | 40 / 6 | |
| 3.1034.0 | 40 / 6 | |
| 3.1033.0 | 40 / 6 | |
| 3.1032.0 | 40 / 6 | |
| 3.1031.0 | 40 / 6 | |
| 3.1030.0 | 40 / 6 | |
| 3.1029.0 | 40 / 6 | |
| 3.1028.0 | 40 / 6 | |
| 3.1027.0 | 40 / 6 | |
| 3.1026.0 | 40 / 6 | |
| 3.1025.0 | 40 / 6 | |
| 3.1024.0 | 40 / 6 | |
| 3.1023.0 | 40 / 6 | |
| 3.1022.0 | 40 / 6 | |
| 3.1021.0 | 40 / 6 | |
| 3.1020.0 | 40 / 6 | |
| 3.1019.0 | 40 / 6 | |
| 3.1018.0 | 40 / 6 | |
| 3.1017.0 | 40 / 6 | |
| 3.1016.0 | 40 / 6 | |
| 3.1015.0 | 40 / 6 | |
| 3.1014.0 | 40 / 6 | |
| 3.1013.0 | 40 / 6 |
v3.1063.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1062.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1061.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1060.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1059.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1058.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1057.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1056.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1055.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1054.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1053.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1052.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1051.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1050.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1049.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1048.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1047.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1046.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1045.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1044.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1043.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1042.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1041.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1040.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1039.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1037.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1036.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1035.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1034.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1033.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1032.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1031.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1030.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1029.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1028.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1027.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1026.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1025.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1024.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1023.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1022.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1021.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1020.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1019.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1018.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1017.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1016.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1015.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1014.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1013.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.