Keyshade Alpha is launching April 30th 5:00 PM IST
Join our Launch Party
keyshade docs
GithubDiscordReddit
  • 👋What is keyshade?
  • Getting Started
    • Introduction
    • Adding your first secret and variable
    • Installing the CLI
    • Setting up your profile
    • Add keyshade to your project
    • Running your app
  • CLI
    • Introduction
    • Profile
    • Init
    • Workspace
    • Project
    • Environment
    • Run
    • Scan
  • 🥰CONTRIBUTING TO KEYSHADE
    • Summary
    • Design of our code
      • Organization of code
      • API
      • CLI
      • Web
      • Integrations
    • Prerequisites
    • Environment Variables
    • Setting things up
    • Running things locally
      • Running the API
      • Running the Web
      • Running the Platform
      • Running the CLI
      • API Testing
      • Docker Support
  • Internals
    • Architecture of keyshade
    • How the CLI works
Powered by GitBook
On this page
  • Usage
  • Options
  • -f, --file <string>
  • -c, --current-changes

Was this helpful?

Edit on GitHub
  1. CLI

Scan

The `scan` command

The scan command is used to detect any hardcoded secrets in your project files. It can scan specific files, only changed files, or all files in the project.

Usage

keyshade scan [options]

Options

These are the options supported by the scan command:

-f, --file <string>

Scan a specific file.

Example:

keyshade scan -f path/to/your/file.js

-c, --current-changes

Scan only the current changed files that are not committed.

Example:

keyshade scan -c
PreviousRunNextSummary

Last updated 7 months ago

Was this helpful?