A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Unstable ownership

Supply chain risk

A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.

Found 10 instances in 10 packages

Socket optimized override available

Maintenance

Package can be replaced with a Socket optimized override.

Found 12 instances in 12 packages

High CVE

Vulnerability

Contains a high severity Common Vulnerability and Exposure (CVE).

Found 1 instance in 1 package

Deprecated

Maintenance

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Found 12 instances in 12 packages

Uses eval

Supply chain risk

Package uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Found 8 instances in 7 packages

Trivial Package

Supply chain risk

Packages less than 10 lines of code are easily copied into your own project and may not warrant the additional supply chain risk of an external dependency.

Found 5 instances in 5 packages

Shell access

Supply chain risk

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Found 11 instances in 10 packages

Network access

Supply chain risk

This module accesses the network.

Found 23 instances in 16 packages

Medium CVE

Vulnerability

Contains a medium severity Common Vulnerability and Exposure (CVE).

Found 1 instance in 1 package

Install scripts

Supply chain risk

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Found 1 instance in 1 package

New author

Supply chain risk

Found 28 instances in 28 packages

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 175 instances in 54 packages

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 75 instances in 65 packages

Unmaintained

Maintenance

Package has not been updated in more than 5 years and may be unmaintained. Problems with the package may go unaddressed.

Found 85 instances in 85 packages

Debug access

Supply chain risk

Uses debug, reflection and dynamic code execution features.

Found 10 instances in 8 packages

Dynamic require

Supply chain risk

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Found 56 instances in 21 packages

Non-permissive License

License

(Experimental) A license not known to be considered permissive was found.

Found 2 instances in 2 packages

Copyleft License

License

(Experimental) Copyleft license information was found.

Found 2 instances in 2 packages

Minified code

Quality

This package contains minified code. This may be harmless in some cases where minified code is included in packaged libraries, however packages on npm should not minify code.

Found 1 instance in 1 package

AI-detected potential code anomaly

Supply chain risk

AI has identified unusual behaviors that may pose a security risk.

Found 2 instances in 2 packages

Unidentified License

License

(Experimental) Something that seems like a license was found, but its contents could not be matched with a known license.

Found 3 instances in 3 packages