Spectra Assure
Community
Docs
passEverything is awesome!
Scanned: 10 days ago

AzureRM.Scheduler

latest
Top 1k
Microsoft Azure PowerShell - Scheduler cmdlets for Azure Resource Manager
License: unknown
Published: over 7 years 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

10.42M
Total Downloads
Contributors
Declared Dependencies
5
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. Some open source repositories allow the developers to take down software component versions that they have published. For open source projects, version unpublishing is uncommon. Versions are typically removed due to a security incident, such as malicious code tampering or accidental development secrets exposure. Software developers often prioritize taking down such packages before informing the community that they have experienced a security incident. Therefore, it is prudent to review the reasons behind software version removals as these events might be a signal of an ongoing software supply chain attack.

Prevalence in PowerShell Gallery community

0 packages
found in
Top 100
1 packages
found in
Top 1k
0 packages
found in
Top 10k
1 packages
in community

Next steps

Review software component documentation for the reasons behind the recent version removal.
If the software version was removed due to a security incident, investigate the build and release environment for software supply chain compromise.
Revise the use of components that raise these alarms. If you can't deprecate those components, make sure that their versions are pinned.
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)
90 packages
found in
Top 100
509 packages
found in
Top 1k
3113 packages
found in
Top 10k
5185 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
74 packages
found in
Top 100
404 packages
found in
Top 1k
2154 packages
found in
Top 10k
3540 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)
74 packages
found in
Top 100
296 packages
found in
Top 1k
1795 packages
found in
Top 10k
2826 packages
in community

Top vulnerabilities

No vulnerabilities found.