The npm package @aws-sdk/credential-provider-http was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Caution is advised as this package is still in review by ReversingLabs threat researchers for inclusion of novel supply chain threats.

Is @aws-sdk/credential-provider-http popular?

The npm package @aws-sdk/credential-provider-http is not widely used. It has 323M recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure @aws-sdk/credential-provider-http once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how @aws-sdk/credential-provider-http behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a @aws-sdk/credential-provider-http version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.