certora/Certora Run Action
Certora Run Action submits prover jobs to Certora Cloud for verification and returns a report with aggregated results.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jul 8, 2026
- License
- BSD
Pinned Snippet
uses: certora/certora-run-action@b37dc99cef13413f8996b2a137b95e8a25749285 # v2.10.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| certora-key | The Certora key to use for the `certoraRun` command. | yes | — |
| cli-version | The version of the `certora-cli` to use. If not specified, the latest version will be used. Example: ```yaml cli-version: 7.0.0 ``` | no | — |
| cli-release | The release type of the `certora-cli` to use. Default is `stable`. Options: `stable`, `alpha`, `beta`, or a custom branch name. Everything other than `stable` should only be used for testing purposes! Example: ```yaml cli-release: beta ``` | no | stable |
| configurations | List of paths to configuration files to use for the `certoraRun` command. Example: ```yaml configurations: |- certConfigs/config1.conf certConfigs/config2.conf certConfigs/config3.conf ``` | yes | — |
| ecosystem | The ecosystem to use for the `certoraRun` command. Default is `evm`. Options: `evm`, `solana`, `sui`, `soroban`. | yes | evm |
| solc-versions | List of Solidity versions to use for the `certoraRun` command. The first version in the list will be used as the default version (solc binary). Each version will be available as both `solc<version>` and `solc-<version>` in the environment. Example: ```yaml solc-versions: |- 0.5.16 0.6.12 0.7.6 ``` | no | — |
| solc-remove-version-prefix | The prefix to remove from the Solidity version when saving binaries. | no | — |
| server | The server to run the tests on. Default is `production`. Options: `production`, `staging`, or `vaas-dev`. | — | production |
| job-name | The name of the job. Default is the name of the job that called this workflow. | — | ${{ github.job }} |
| install-java | Whether to install Java for type checking. Default is `true`. | — | true |
| compilation-steps-only | Whether to only run the compilation steps. Default is `false`. | — | false |
| comment-fail-only | Add a comment to the PR only if the run fails. | — | true |
| replace-comments | Whether to replace previous review comments made by this action. Default is `true`. | — | true |
| debug-level | The debug level to use for the action command. Default is `0`. Options: `0`, `1`, `2`, or `3`. | — | 0 |
| working-directory | The working directory to run the action in. Default is the current working directory. | — | ${{ github.workspace }} |
| rust-setup | Whether to set up Rust for Solana. Default is `true`. | — | true |
| rust-version | The version of Rust to install. If not specified, the latest stable version will be used. The minimum supported version is `1.82.0`. | no | stable |
| rust-additional-versions | Additional versions of Rust to install, separated by spaces. Example: `1.75 1.79`. | no | "" |
| certora-sbf-version | The version of `cargo-certora-sbf` to install. If not specified, the latest version will be used. | no | "" |
| certora-sbf-options | Additional options to pass to the `cargo certora-sbf` command. This can be used to specify additional flags or configurations for the Certora SBF tool. See https://github.com/Certora/cargo-certora-sbf for more details on available options. | no | "" |
| use-hard-links | Whether to use hard links when copying files. Default is `true`. | no | true |
| use-workspace-dir | Whether to run all configurations directly in the working directory instead of copying it to an isolated temporary directory per configuration. Default is `false`. | no | false |
| run-serially | Whether to run configurations one at a time instead of concurrently. Default is `false`. | no | false |
| vyper-version | The version of Vyper to install. Can be latest, or a specific version like 0.3.3. If not specified, Vyper will not be installed. | no | — |
| gh-review | When to add a review comment to the PR. Options are `always`, `failure`, and `never`. Default is `always`. | no | always |
| gh-review-jobs | Which jobs to include in the GitHub review comment. Options are `all`, `failed`. Default is `all`. | no | all |
| auto-rerun-timeouts | Opt in to automatically re-run jobs that time out, using a per-ecosystem portfolio of variant prover configurations. The PR check stays pending while reruns are in flight; if any rerun succeeds, sibling reruns are cancelled and the group is marked successful. Default is `false`. | no | false |
Outputs
no outputs