Skip to main content

Available images

Crypto Finder has three images. They differ in size and in what they include: The standard image includes OpenGrep 1.30.2 and Semgrep 1.145.0+, so every scanning capability works out of the box. The image unpacks OpenGrep’s matching opengrep-core at build time, so the default core mode runs from the first scan in a fresh container.

Slim image

The slim image contains only the crypto-finder binary, which keeps it small. You must supply an external OpenGrep or Semgrep installation, for example by mounting it into the container or by building a derived image. Use it when your workflow manages scanner versions itself.

Deps image (dependency scanning)

The deps image adds the language toolchains needed to scan third-party dependencies with --scan-dependencies. It detects cryptographic usage in those dependencies and traces the call chains that reach it.
It has everything in the standard image except Semgrep, plus:
  • The Go toolchain, for dependency resolution with go list and go mod graph.
  • Java (JDK 8, 11, 17, and 21, with Maven and Gradle), for JDK-aware Java dependency resolution and deterministic platform signature indexing.
  • Rust (Cargo), for dependency resolution with cargo metadata.
  • Python in an isolated virtualenv, for pip dependency resolution.

Basic usage

Scanning with mounted volumes

Volume mounting patterns

Preserving the cache between runs

CI/CD integration

GitHub Actions

This workflow scans code on every push and pull request:

With custom rules

Dependency scanning

The latest-deps image includes every language toolchain that dependency scanning needs. Use it with the --scan-dependencies flag.

Go projects

Java (Maven or Gradle) projects

Rust projects

Python projects

For Python projects, install the dependencies before scanning, because pip needs them to be resolved:
Note: The deps image keeps project dependencies in an isolated virtualenv, separate from the scanner tooling, so pip install affects only the target project’s environment.

CI/CD with dependency scanning (GitHub Actions)

Advanced Docker usage

Running with a specific scanner

Since 0.48.0, the deps image no longer bundles Semgrep, so scan --scanner semgrep fails there because semgrep is not on PATH. Use the standard image, which still ships Semgrep, or install it into the container. Dependency scanning runs OpenGrep and is not affected.

Custom timeout and language override

Docker Compose

An example docker-compose.yml for local development:
Start it with: