Project Scanners
Run customizable scans on your repository and keep your project in good shape.
Automated Scanning Agents for a Healthy Codebase
A project scanners allow Snapr to automatically run analysis jobs on your repositories, keeping your project clean, secure, and compliant with your rules.
How it works?
-
1
The definition
A Project Scanner defines what should be checked in your repository. It can be a built-in scanner (dependency audits, code quality, Dockerfile linting, etc.) or a custom scanner defined by the user via a configuration file or container image.
-
2
The scheduling
Based on configuration, Snapr runs scanners on demand or on a schedule. Each scan is executed as an isolated Kubernetes Job or CronJob, ensuring safe, reproducible checks that scale with your infrastructure.
-
3
The analysis
When triggered, Snapr analyzes the repository according to the selected scanner template, identifying issues relevant to its scope.
-
4
The reporting
Detected issues are automatically turned into GitHub Issues, complete with relevant context and remediation guidance, so problems can be tracked and resolved directly in your existing workflow.
Customization
Define your scanning lifecycle: run a one-off Job or schedule recurring CronJobs.
Built-in Templates
Select from a library of predefined scanning templates such as dependency audits, code quality checks, Dockerfile linting, and more.
Custom Templates
Create scanner configurations through the UI or define them during installation using Helm to match your project’s specific requirements.
Documentation
- Project Scanners command.