priority-nav - Package Alerts

This package is not very popular.

Found 1 instance in 1 package

This package is not very popular.

Found 1 instance in 1 package

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 19 instances in 19 packages

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 31 instances in 31 packages

This module accesses the network.

Found 38 instances in 19 packages

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 5 instances in 5 packages

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

Found 9 instances in 9 packages

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

Found 30 instances in 24 packages

(Experimental) A package's licensing information has fine-grained problems.

Found 4 instances in 4 packages

Package has a dependency with a floating version range. This can cause issues if the dependency publishes a new major version.

Found 1 instance in 1 package

Contains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior.

Found 1 instance in 1 package

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

Found 2 instances in 1 package