🐢 Node-Secure 🚀
a Node.js CLI to deeply analyze the dependency tree of a given package / directory
Node.js security Command Line Interface. The goal of the project is to a design a CLI/API that will fetch and deeply analyze the dependency tree of a given npm package (Or a local project with a package.json) and output a .json file that will contains all metadata and flags about each packages. All this data will allow to quickly identify different issues across projects and packages (related to security and quality).
The CLI allow to load the JSON into a Webpage with the open command. The page will draw a Network of all dependencies with vis.js (example in the screenshot above). We also wrote a little Google drive document a while ago that summarizes some of these points:
- Run an AST analysis on each .js/.mjs file in the packages tarball and sort out warnings (unsafe-regex, unsafe-import etc) and the complete list of required expr and statements (files, node.js module, etc.).
- Return complete composition for each packages (extensions, files, tarball size, etc).
- Packages metadata from the npm registry API (number of releases, last publish date, maintainers etc).
- Search for licenses files in the tarball and return the SPDX expression conformance of each detected licenses.
- Link vulnerabilities from the Security-WG repository to the package version node.
- Add flags to each packages versions to identify well known patterns and potential security threats easily.
- Analyze npm packages and local Node.js projects.
- Node.js LTS 16.x or higher
💃 Getting Started
$ npm install nsecure -g
$ git clone https://github.com/ES-Community/nsecure.git $ cd nsecure $ npm ci $ npm run build $ npm link
Then the nsecure binary will be available in your terminal. Give a try with the popular express package. This will automatically open the webpage in your default system browser.
$ nsecure auto express
⚠️Setup an npm token to avoid hiting the maximum request limit of the npm registry API.
👀 Usage example
To show the complete list of commands
$ nsecure --help
# Run an analysis on the current working dir (must have a package.json file). $ nsecure cwd # Run an analysis for a given 'npm' package (must be in the npm registry). $ nsecure from @sindresorhus/is
nsecure-result.json will be writted at the current CLI location. To open it on a web page just run
$ nsecure open # If you want to define a specific port use the --port option. $ nsecure open --port 8080
|--port||-p||Define the running port, can also be define through the environment variable
auto command can be used to chain
open commands automatically.
$ nsecure auto jest # if no package is given to the auto command then it will run the cwd command instead of from. $ nsecure auto
👀By default with the auto command the .json file is deleted when the http server is closed. It's possible to disable this behavior by using the CLI option
Some options are available on both
auto commands. The output option is not available for the
|--depth||-d||4||the maximum depth we must walk (when we fetch the whole tree).|
|--output||-o||nsecure-result||the name that the outputted .json file will have|
$ nsecure from express -d 10 -o express-security-report
Private packages / registry
Nsecure allow you to fetch stats on private npm packages by setting up a
NODE_SECURE_TOKEN env variable (which must contains an npm token).
💬If you link the package by yourself with npm you can create a
.envfile at the root of the project too.
Nsecure is capable to work behind a custom private npm registry too by searching the default registry URL in your local npm configuration.
$ npm config get registry $ npm config set "http://your-registry/"
Our back-end scanner package is available here.
Flags and emojis legends are documented here.
Since version 0.6.0 of Node-secure the UI include a brand new searchbar that allow to search anything on the tree (graph) by multiple criteria (filters). The current available filters are:
- package (the default filter if there is none).
- version (take a semver range as an argument).
- flag (list of available flags in the current payload/tree).
- license (list of available licenses in the current payload/tree).
- author (author name/email/url).
- ext (list of available file extensions in the current payload/tree).
- builtin (available Node.js core module name).
Exemple of query:
version: >=1.2 | 2, ext: .js, builtin: fs
Why some nodes are red in the UI ?
Nodes are red when the project/package has been flagged with
Why the node-secure package size is so different from Bundlephobia ?
Node-secure will analyze the complete size of the npm tarball with no filters or particular optimization. Bundlephobia on the other side will bundle and remove most of the useless files from the tarball (Like the documentation, etc.).
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!