⚡️ Run a static analysis of your module's dependencies.
Scanner builds on JS-X-Ray (SAST) and Vulnera (CVE detection), and adds additional detections such as:
- Detects:
- Manifest confusion
- Dependency confusion
- Typosquatting of popular package names
- Install scripts (e.g.
install,preinstall,postinstall,preuninstall,postuninstall)
- Highlights packages by name, version(s), or maintainer
- Highlights infrastructure components such as ip, hostname, email, url
- Supports NPM and Yarn lockfiles
$ npm i @nodesecure/scanner
# or
$ yarn add @nodesecure/scannerFor full API documentation, options, and usage examples, see the @nodesecure/scanner package README.
- @nodesecure/scanner
- @nodesecure/tarball
- @nodesecure/tree-walker
- @nodesecure/flags
- @nodesecure/mama
- @nodesecure/contact
- @nodesecure/conformance
- @nodesecure/npm-types
- @nodesecure/i18n
- @nodesecure/rc
- @nodesecure/utils
- @nodesecure/fs-walk
- @nodesecure/github
- @nodesecure/gitlab
If you are a developer looking to contribute to the project, you must first read the CONTRIBUTING guide.
Once you have finished your development, check that the tests (and linter) are still good by running the following script:
$ npm run checkCaution
In case you introduce a new feature or fix a bug, make sure to include tests for it as well.
Thanks goes to these wonderful people (emoji key):
MIT
