Top issues
Detected presence of licenses that place restrictions on software distribution.
Causes risk: software distribution restrictions
licenses
Problem
Software license is a legal instrument that governs the use and distribution of software source code and its binary representation. Software publishers have the freedom to choose any commonly used or purposefully written license to publish their work under. While some licenses are liberal and allow almost any kind of distribution, with or without code modification, other licenses are more restrictive and impose rules for their inclusion in other software projects. Some software licenses place restrictions on software distribution of the code they apply to. These restrictions may extend to the services built upon the code licensed under such restrictive licenses. Some restrictive licenses explicitly state that the licensee may not provide the software to third parties as a hosted or managed service, where the service provides users with access to any substantial set of the features or functionality of the licensed software. When building commercial applications, this is typically undesirable. Therefore, the inclusion of any code that may impose limits on software distribution is commonly avoided or even prohibited by the organization policy.Prevalence in PyPI community
7 packages
found in
Top 100
82 packages
found in
Top 1k
1208 packages
found in
Top 10k
109.57k packages
in community
Next steps
Confirm that the software package references a component or a dependency with a restrictive license.
Consider replacing the software component with an alternative that offers a license compatible with organization policy.
Detected presence of software components that are rarely included by other public software packages.
hunting
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 PyPI community
1 packages
found in
Top 100
11 packages
found in
Top 1k
910 packages
found in
Top 10k
717.09k 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.
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. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.Prevalence in PyPI community
70 packages
found in
Top 100
472 packages
found in
Top 1k
4207 packages
found in
Top 10k
413.79k 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.
Detected presence of low severity vulnerabilities.
Causes risk: low severity vulnerabilities
vulnerabilities
Problem
Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as low severity.Prevalence in PyPI community
19 packages
found in
Top 100
59 packages
found in
Top 1k
395 packages
found in
Top 10k
11.9k packages
in community
Next steps
Perform impact analysis for the reported CVEs.
Update the component to the latest version.
Lower severity vulnerabilities can be resolved with less urgency, but you should still make a plan to do so.
Top behaviors
Contains URLs that link to interesting file formats.
network
Prevalence in PyPI community
Behavior often found in this community (Common)
76 packages
found in
Top 100
459 packages
found in
Top 1k
3531 packages
found in
Top 10k
105.97k packages
in community
The software package does not declare any source code repository.
anomaly
Prevalence in PyPI community
Behavior often found in this community (Common)
70 packages
found in
Top 100
472 packages
found in
Top 1k
4207 packages
found in
Top 10k
413.79k packages
in community
Top vulnerabilities
Vulnerability Exploitation Lifecycle
(2 Active Vulnerabilities)
1 (0 Fixable)
CVE-2020-1738l
1 (0 Fixable)
CVE-2020-1736l
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated