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

Az.Tools.Predictor

latest
Top 1k
Microsoft Azure PowerShell - Module providing recommendations for cmdlets comprised in the Az module - This module requires PowerShell 7.2 and PSReadLine 2.2.2. Suggestions must be activated: - Enable-AzPredictor: Activate the suggestions - Disable-AzPredictor: Disable the suggestions For more information on Az Predictor, please visit the following: https://aka.ms/azpredictordocs
License: unknown
Published: about 2 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

Popularity

236.67k
Total Downloads
Contributors
Declared Dependencies
1
Dependents

Top issues

Problem

Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. Top-level domains (TLD) are a part of the Domain Name System (DNS), and are used to lookup an Internet Protocol (IP) address of a requested website. There are a few different types of top-level domains. Generic, sponsored and country-code TLDs are generally accessible to the public. Registrars that govern the assignment of domain names within the TLD may choose to sell specific domain names to an interested party. However, some registrars are known to have less strict rules for assigning domain names. Attackers often abuse gaps in governance and actively seek to register their malicious domains in such TLDs. This issue is raised for all domains registered within TLDs that harbor an excessive number of malicious sites. While the presence of suspicious TLDs does not imply malicious intent, all of its uses in a software package should be documented and approved.

Prevalence in PowerShell Gallery community

2 packages
found in
Top 100
35 packages
found in
Top 1k
181 packages
found in
Top 10k
325 packages
in community

Next steps

Investigate reported detections.
If the software should not include these network references, investigate your build and release environment for software supply chain compromise.
You should delay the software release until the investigation is completed, or until the issue is risk accepted.
Consider changing the top-level domain to avoid being flagged by security solutions.

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)
17 packages
found in
Top 100
283 packages
found in
Top 1k
1860 packages
found in
Top 10k
3073 packages
in community

Prevalence in PowerShell Gallery community

Behavior uncommon for this community (Uncommon)
2 packages
found in
Top 100
35 packages
found in
Top 1k
183 packages
found in
Top 10k
328 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)
25 packages
found in
Top 100
257 packages
found in
Top 1k
1227 packages
found in
Top 10k
2010 packages
in community

Top vulnerabilities

No vulnerabilities found.