lstn in

This command scans all of your project's dependencies, using the list of modules specified in your package.json file.

Running the standalone command lstn uses the package.json file in current directory.

Use this command if you are in your project's root directory.

Running the command lstn in allows you to specify a relative or absolute path for the package.json you want to be analyzed.

This is useful if you want to use multiple package.json files in your workflow, or want to run the command from outside the root directory

Query listen.dev for the verdicts of all the dependencies in your project.

Using this command, you can audit all the dependencies configured for a project and obtain their verdicts.
This requires a package.json file to fetch the package name and version of the project dependencies.

The verdicts it returns are listed by the name of each package and its specified version.

Usage:
  lstn in <path>

Examples:
  lstn in
  lstn in .
  lstn in /we/snitch
  lstn in sub/dir

Flags:
  -h, --help        help for in
  -q, --jq string   filter the output using a jq expression
      --json        output the verdicts (if any) in JSON form

Global Flags:
      --config string     config file (default is $HOME/.lstn.yaml)
      --endpoint string   the listen.dev endpoint emitting the verdicts (default "http://127.0.0.1:3000")
      --loglevel string   log level (default "info")
      --timeout int       timeout in seconds (default 60)

CLI Commands lstn to