cli icon indicating copy to clipboard operation
cli copied to clipboard

JavaScript security CLI that allow you to deeply analyze the dependency tree of a given package or local Node.js project.

Results 30 cli issues
Sort by recently updated
recently updated
newest added

This project began as a small interface built with Vanilla JavaScript, with limited features and interactions. Over the past five years, the project has grown significantly, and attempts to completely...

help wanted
Interface

**GOAL** use scanner extractors to get manifest info to show in UI instead of computing scanner results again. **Relates to** https://github.com/NodeSecure/scanner/issues/307 **To do / Propositions** - improve scanner warnings extractor:...

The latest version of the NodeSecure scanner can highlight a given list of packages (see the highlight.packages option in the cwd / from commands and highlighted.packages in the result payload)....

The goal is to create a new cache implementation to replace the old one and allow the cache to live in the local system or in the browser (using LocalStorage...

V4

### Today: Today, the project consists of a set of pseudo-components fully managed in Vanilla JavaScript without any external libraries. ### Goal: Implement [Lit.js](https://lit.dev/) to maintain a primarily Vanilla approach...

help wanted
V4

The goal is to create an online version of the tool by running NodeSecure directly in the navigator using [WebContainer](https://webcontainers.io/) API. My plan right now is the following: - Implement...

enhancement
help wanted
V4

When running commands such as auto, cwd and from we always scan even if the package has been registered in the local system cache. The idea would be to improve...