@aws-sdk/client-securityhub Apache-2.0 51 versions

@aws-sdk/client-securityhub

npm Repository Homepage

AWS SDK for JavaScript Securityhub Client for Node.js, Browser and React Native

51

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

amzn-ossaws-sdk-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist-cjs/schemas/schemas_0.js	AI (source-diff): AWS SDK v3 ships minified schema bundles as part of its standard build; not obfuscation.	ai	2026/05/05
phantom-deps	phantom-dep:@smithy/middleware-serde	AI (phantom-deps): Smithy framework packages are loaded by convention in AWS SDK v3; stable false positive.	ai	2026/05/05
phantom-deps	phantom-dep:@smithy/middleware-stack	AI (phantom-deps): Smithy framework packages are loaded by convention in AWS SDK v3; stable false positive.	ai	2026/05/05

Versions (showing 51 of 187)

View all versions

Version	Deps	Published
3.1063.0	10 / 6	2026-06-05
3.1062.0	10 / 6	2026-06-04
3.1061.0	10 / 6	2026-06-03
3.1060.0	10 / 6	2026-06-03
3.1059.0	10 / 6	2026-06-02
3.1058.0	10 / 6	2026-06-01
3.1057.0	10 / 6	2026-05-29
3.1056.0	10 / 6	2026-05-28
3.1055.0	10 / 6	2026-05-27
3.1054.0	10 / 6	2026-05-26
3.1053.0	10 / 6	2026-05-22
3.1052.0	10 / 6	2026-05-21
3.1051.0	10 / 6	2026-05-20
3.1050.0	10 / 6	2026-05-19
3.1049.0	10 / 6	2026-05-18
3.1048.0	10 / 6	2026-05-15
3.1047.0	18 / 6	2026-05-14
3.1046.0	18 / 6	2026-05-14
3.1045.0	39 / 6	2026-05-07
3.1044.0	39 / 6	2026-05-06
3.1043.0	39 / 6	2026-05-05
3.1042.0	39 / 6	2026-05-04
3.1041.0	39 / 6	2026-05-01
3.1040.0	39 / 6	2026-04-30
3.1039.0	39 / 6	2026-04-29
3.1038.0	39 / 6	2026-04-27
3.1037.0	39 / 6	2026-04-24
3.1036.0	39 / 6	2026-04-23
3.1035.0	39 / 6	2026-04-22
3.1034.0	39 / 6	2026-04-21
3.1033.0	39 / 6	2026-04-20
3.1032.0	39 / 6	2026-04-17
3.1031.0	39 / 6	2026-04-16
3.1030.0	39 / 6	2026-04-13
3.1029.0	39 / 6	2026-04-10
3.1028.0	39 / 6	2026-04-09
3.1027.0	39 / 6	2026-04-08
3.1026.0	39 / 6	2026-04-07
3.1025.0	39 / 6	2026-04-06
3.1024.0	39 / 6	2026-04-03
3.1023.0	39 / 6	2026-04-02
3.1022.0	39 / 6	2026-04-01
3.1021.0	39 / 6	2026-03-31
3.1020.0	39 / 6	2026-03-30
3.1019.0	39 / 6	2026-03-27
3.1018.0	39 / 6	2026-03-26
3.1017.0	39 / 6	2026-03-25
3.1016.0	39 / 6	2026-03-24
3.1015.0	39 / 6	2026-03-23
3.1014.0	39 / 6	2026-03-20
3.1013.0	39 / 6	2026-03-19

v3.1063.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1062.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1061.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1060.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1059.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1058.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1057.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1056.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1055.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1054.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1053.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1052.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1051.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1050.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1049.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1048.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1047.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1046.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1045.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1044.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1043.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1042.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1041.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1040.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1039.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1037.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1036.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1035.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1034.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1033.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1032.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1031.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1030.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1029.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1028.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1027.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1026.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1025.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1024.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1023.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1022.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1021.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1020.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1019.0

2 findings

HIGH New obfuscated file: dist-cjs/schemas/schemas_0.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1018.0

2 findings

HIGH New obfuscated file: dist-cjs/schemas/schemas_0.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1017.0

2 findings

HIGH New obfuscated file: dist-cjs/schemas/schemas_0.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1016.0

2 findings

HIGH New obfuscated file: dist-cjs/schemas/schemas_0.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1015.0

2 findings

HIGH New obfuscated file: dist-cjs/schemas/schemas_0.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1014.0

2 findings

HIGH New obfuscated file: dist-cjs/schemas/schemas_0.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1013.0

2 findings

HIGH New obfuscated file: dist-cjs/schemas/schemas_0.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.