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. 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 RubyGems community
No prevalence information at this timeNext 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
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. A port number is associated with a network address of a host, such as an IP address, and the type of network protocol used for communication. Within URLs, the ports are optional. Ports can be specified in a URL immediately following the domain name. Each network protocol, or schema, has a set of standard ports on which the service operates. This issue is raised when a mismatch between a network protocol and its expected port number is detected. While the presence of non-standard ports does not imply malicious intent, all of their uses in a software package should be documented and approved.Prevalence in RubyGems community
27 packages
found in
Top 100
375 packages
found in
Top 1k
1571 packages
found in
Top 10k
15785 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 port to one that is standard for the networking protocol.
Top behaviors
Encodes data using the Base64 algorithm.
packer
Prevalence in RubyGems community
Behavior often found in this community (Common)
15 packages
found in
Top 100
98 packages
found in
Top 1k
644 packages
found in
Top 10k
5994 packages
in community
Contains URLs that link to interesting file formats.
network
Prevalence in RubyGems community
Behavior often found in this community (Common)
53 packages
found in
Top 100
247 packages
found in
Top 1k
2209 packages
found in
Top 10k
16324 packages
in community
Contains URLs that use non-standard ports.
network
Prevalence in RubyGems community
Behavior often found in this community (Common)
27 packages
found in
Top 100
376 packages
found in
Top 1k
1574 packages
found in
Top 10k
15826 packages
in community
Contains IP addresses.
network
Prevalence in RubyGems community
Behavior often found in this community (Common)
68 packages
found in
Top 100
566 packages
found in
Top 1k
3736 packages
found in
Top 10k
43562 packages
in community
Contains URLs with unusual hostname lengths.
network
Prevalence in RubyGems community
Behavior often found in this community (Common)
24 packages
found in
Top 100
102 packages
found in
Top 1k
760 packages
found in
Top 10k
6608 packages
in community
Top vulnerabilities
No vulnerabilities found.