The npm package @aws-sdk/credential-provider-env was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. No risks were detected, therefore, this version of the package is currently considered as safe to use.

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

The npm package @aws-sdk/credential-provider-env ranks among the top 10000 projects in this community. It has 2B 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-env 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-env 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-env version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.