snyk/cli

This is the command-line tool for Snyk, a service that checks software projects for security vulnerabilities. The idea is that code you write, or more often the open-source libraries your project depends on, may contain known security flaws. Snyk scans your project, identifies those flaws, and tells you how severe they are and how to fix them. The CLI can check four different things. It can scan the open-source packages your project uses and flag ones with known vulnerabilities. It can scan your own application code for security issues. It can check Docker container images for problems. It can also inspect infrastructure configuration files, like Terraform or Kubernetes YAML files, for insecure settings. To get started, you install the CLI tool, connect it to your Snyk account with an authentication step, and then run a scan command in your project folder. For an open-source check, you run snyk test in the directory that contains your project's dependency file such as package.json or pom.xml. The tool reports what it finds: each vulnerability, its severity level, how the vulnerable package got pulled into your project, and what fix is available. Fixes are typically either upgrading a dependency to a patched version or applying a code patch. Beyond one-time scans, Snyk can set up ongoing monitoring of a project. The snyk monitor command takes a snapshot of your current dependencies and registers them with the Snyk service, which then alerts you by email when new vulnerabilities are disclosed that affect packages you rely on. The CLI integrates into development editors and CI/CD pipelines so that security checks can happen automatically as part of existing workflows. Public repositories scan without counting against usage limits. Private repositories are subject to the plan's test quota. The full documentation for commands and supported languages lives on the Snyk docs website rather than in the repository itself.