/

Secret Scanner Installation

Before you begin

You'll need:

  • A ByteHide account and project token
  • Go 1.19 or higher installed
  • Node.js 16+ installed (required by the scanner engine)

Installation Options

Choose your preferred installation method:

Install from Source

Bash
git clone https://github.com/bytehide/bytehide-secrets-scanner-wrappers.git
cd bytehide-secrets-scanner-wrappers/wrappers/go
go build -o bytehide-secrets .

Install Globally

Bash
go install github.com/bytehide/bytehide-secrets-scanner-wrappers/wrappers/go@latest

Basic Setup

After installation, initialize the scanner configuration:

Bash
./bytehide-secrets init

This interactive command will create a bytehide.secrets.json file in your project root directory:

JSON
{
  "token": "<your-project-token>",
  "appName": "My Go Project",
  "environment": "development",
  "sync": true,
  "fix": false,
  "anonymize": false
}

Security Warning

Never commit your bytehide.secrets.json file to source control. Add it to your .gitignore file.

Verify Installation

After installation, run a scan to verify everything is working:

Bash
./bytehide-secrets scan

The scanner will automatically:

  1. Check if scanning is enabled for your configuration
  2. Scan source code for secrets
  3. Report any findings to your ByteHide dashboard
  4. Export detected secrets to your ByteHide Secrets Manager (if configured)

Makefile Integration

You can integrate the scanner into your build process using a Makefile:

MAKEFILE
.PHONY: scan-secrets
scan-secrets:
	bytehide-secrets scan .

.PHONY: build
build: scan-secrets
	go build -o myapp .

Then run:

Bash
make build

go:generate Integration

Add to your Go file for scanning during code generation:

Go
//go:generate bytehide-secrets scan .

Then run:

Bash
go generate

Scanner Workflow

The Secret Scanner integrates into your development workflow:

  1. Installation: Build from source or install globally
  2. Configuration: Set up the scanner via the JSON file or init command
  3. Scanning: Run manually or automatically during builds
  4. Reporting: Detected secrets appear in your ByteHide dashboard
  5. Action: Export, fix, or receive alerts about found secrets

What's Next?

Previous
Create a project