Top issues
Detected presence of software components that were recently published to the public package repository.
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 being the first to try out a new project 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 npm community
0 packages
found in
Top 100
0 packages
found in
Top 1k
4 packages
found in
Top 10k
128.62k 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 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 npm community
1 packages
found in
Top 100
2 packages
found in
Top 1k
66 packages
found in
Top 10k
2.88M 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 npm community
18 packages
found in
Top 100
133 packages
found in
Top 1k
1817 packages
found in
Top 10k
2.98M 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.
Top behaviors
Encodes data using the Base64 algorithm.
packer
Prevalence in npm community
Behavior often found in this community (Common)
7 packages
found in
Top 100
62 packages
found in
Top 1k
984 packages
found in
Top 10k
344.78k packages
in community
Decodes data using the Base64 algorithm.
packer
Prevalence in npm community
Behavior often found in this community (Common)
6 packages
found in
Top 100
45 packages
found in
Top 1k
684 packages
found in
Top 10k
195.24k packages
in community
Executes files during installation or upon launch.
execution
Prevalence in npm community
Behavior often found in this community (Common)
95 packages
found in
Top 100
726 packages
found in
Top 1k
7488 packages
found in
Top 10k
4.56M packages
in community
Creates a process.
execution
Prevalence in npm community
Behavior often found in this community (Common)
15 packages
found in
Top 100
52 packages
found in
Top 1k
615 packages
found in
Top 10k
153.81k packages
in community
Renames a file or directory.
file
Prevalence in npm community
Behavior often found in this community (Common)
0 packages
found in
Top 100
4 packages
found in
Top 1k
54 packages
found in
Top 10k
25.07k packages
in community
Top vulnerabilities
No vulnerabilities found.