Spectra Assure
Community
Docs
passEverything is awesome!
Scanned: about 18 hours ago

AWS.Tools.SSO

latest
Top 1k
The SSO module of AWS Tools for PowerShell lets developers and administrators manage AWS Single Sign-On from the PowerShell scripting environment. In order to manage each AWS service, install the corresponding module (e.g. AWS.Tools.EC2, AWS.Tools.S3...). The module AWS.Tools.Installer (https://www.powershellgallery.com/packages/AWS.Tools.Installer/) makes it easier to install, update and uninstall the AWS.Tools modules. This version of AWS Tools for PowerShell is compatible with Windows PowerShell 5.1+ and PowerShell Core 6+ on Windows, Linux and macOS. When running on Windows PowerShell, .NET Framework 4.7.2 or newer is required. Alternative modules AWSPowerShell.NetCore and AWSPowerShell, provide support for all AWS services from a single module and also support older versions of Windows PowerShell and .NET Framework.
License: unknown
New!
Published: about 20 hours ago




SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
No application hardening issues

Threats

Tampering
No evidence of software tampering
Malware
No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

Popularity

366.67k
Total Downloads
Contributors
Declared Dependencies
1
Dependents

Top issues

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. While a new software project is a welcome addition to the open source community. it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of using components that are rarely used to build applications lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in PowerShell Gallery community

8 packages
found in
Top 100
25 packages
found in
Top 1k
130 packages
found in
Top 10k
259 packages
in community

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

Top behaviors

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
100 packages
found in
Top 100
804 packages
found in
Top 1k
6518 packages
found in
Top 10k
11726 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
53 packages
found in
Top 100
452 packages
found in
Top 1k
2940 packages
found in
Top 10k
4594 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
97 packages
found in
Top 100
693 packages
found in
Top 1k
4437 packages
found in
Top 10k
7330 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
90 packages
found in
Top 100
516 packages
found in
Top 1k
2293 packages
found in
Top 10k
3528 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
92 packages
found in
Top 100
485 packages
found in
Top 1k
1972 packages
found in
Top 10k
3050 packages
in community

Top vulnerabilities

No vulnerabilities found.