Prerequisites
Before you begin, ensure you have:- Crypto Finder installed (see Installation)
- At least one scanner installed (OpenGrep or Semgrep)
- SCANOSS API key (optional but recommended for remote rulesets)
- Source code to scan
First Scan
Basic Scanning
Scan with remote rulesets (recommended):Common Use Cases
CI/CD Integration:Configuration
The application can be configured via command-line flags, environment variables, or configuration files.scanoss.json:
Command Line Arguments
--rules <file>- Custom rule file (repeatable)--rules-dir <dir>- Rule directory (repeatable)--no-remote-rules- Disable remote ruleset fetching--no-cache- Force fresh download, bypass cache--scanner <name>- Scanner to use:opengrep(default),semgrep--format <format>- Output format:json(default),cyclonedx--output <file>- Output file path (default: stdout)--languages <langs>- Override language detection (comma-separated)--fail-on-findings- Exit with error if findings detected--timeout <duration>- Scan timeout (default: 10m)--verbose,-v- Enable verbose logging--help- Display help information
crypto-finder --help.
Advanced Topics
Features
- Multi-Scanner Support - OpenGrep (default) and Semgrep with advanced taint analysis
- Remote Rulesets - Automatically fetch curated rules from SCANOSS API with local caching
- Flexible Configuration - Combine remote and local rules, configure via CLI, env vars, or config files
- Multiple Output Formats - JSON and CycloneDX 1.6 CBOM formats
- CI/CD Ready - Docker images for GitHub Actions, GitLab CI, Jenkins, and more
- Smart Caching - TTL-based cache with automatic stale cache fallback (opt-out with
--strict)