Top issues
Detected presence of software components distributed with copyleft licenses.
Causes risk: copyleft licensed components
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. Copyleft licenses in particular impose substantial restrictions on the licensee. They typically require that any derived works, and even software code that merely interacts with copyleft code, be licensed under the same license. Since copyleft licenses are commonly applied to open source code, their inclusion requires that the entire software package becomes open sourced. For commercial applications, this is typically undesirable. Therefore, the inclusion of copyleft code is commonly avoided or even prohibited by the organization policy.Prevalence in PyPI community
4 packages
found in
Top 100
42 packages
found in
Top 1k
659 packages
found in
Top 10k
89.98k packages
in community
Next steps
Confirm that the software package includes a copyleft component.
Investigate if the software publisher provides this component under a non-copyleft license.
Consider replacing the software component with an alternative that offers a license compatible with commercial use.
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.
Problem
Private keys and certificates are considered sensitive information that should not be included in released software packages. However, developers frequently release sensitive information alongside their applications to facilitate automated software testing. Testing keys and certificates often proliferate through the software supply chain. When such information gets shared publicly, it is catalogued by file reputation databases. Any private key and certificate files seen by a file reputation database prior to configured time threshold can be automatically suppressed. Commonly shared sensitive information is not considered to be secret.Prevalence in PyPI community
37 packages
found in
Top 100
169 packages
found in
Top 1k
753 packages
found in
Top 10k
16.54k packages
in community
Next steps
Review the commonly shared sensitive information for evidence of inadvertently exposed secrets.
If the keys were published unintentionally and the software has been made public, you should revoke the keys and file a security incident.
Top behaviors
Creates a process.
execution
Prevalence in PyPI community
Behavior often found in this community (Common)
69 packages
found in
Top 100
506 packages
found in
Top 1k
3612 packages
found in
Top 10k
163.85k packages
in community
Contains URLs that contain basic authentication credentials.
network
Prevalence in PyPI community
Behavior often found in this community (Common)
26 packages
found in
Top 100
118 packages
found in
Top 1k
563 packages
found in
Top 10k
12.66k packages
in community
Renames a file or directory.
file
Prevalence in PyPI community
Behavior often found in this community (Common)
68 packages
found in
Top 100
540 packages
found in
Top 1k
3680 packages
found in
Top 10k
150.76k packages
in community
Deletes a file/directory.
file
Prevalence in PyPI community
Behavior often found in this community (Common)
68 packages
found in
Top 100
533 packages
found in
Top 1k
3858 packages
found in
Top 10k
146.15k packages
in community
Contains URLs.
network
Prevalence in PyPI community
Behavior often found in this community (Common)
33 packages
found in
Top 100
225 packages
found in
Top 1k
1322 packages
found in
Top 10k
35.04k packages
in community
Top vulnerabilities
No vulnerabilities found.