AI Slop Code RIsk Monitor

model-checking/kani

A model checker for Rust programs.

6.7 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for model-checking/kani, a Rust project with 3,533 GitHub stars. SynthScan examined 170,916 lines of code across 2569 source files, recording 912 pattern matches distributed across 17 syntactic categories. The legacy adjusted pattern signal is 6.7 (Moderate pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

6.7
Adjusted Signal
6.7
Raw Pattern Score
100%
Time Factor
2026-10-08
Last Push
3.5K
Stars
Rust
Language
170.9K
Lines of Code
2.6K
Files
912
Pattern Hits
2026-10-12
Scan Date
0.01
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 26.2/100 · MEDIUM

Can maintainers explain intent, assumptions, and trade-offs? 890 finding(s).

Hallucinated Dependency & Supply Chain Risk 2.3/100 · LOW

Are imports declared and package/API names verified? 13 finding(s).

Agent Over-Engineering Ratio 1.8/100 · LOW

Are wrappers, guards, and repeated structures necessary? 36 finding(s).

PR Review Velocity Impact 28.2/100 · MEDIUM

Which changes need focused human review? 912 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 1HIGH 14MEDIUM 72LOW 825

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 912 distinct pattern matches across 17 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block769 hits · 757 pts
SeverityFileLineSnippetContext
LOWtools/build-kani/src/main.rs121/// Copy CBMC files into `dir`COMMENT
LOWtools/build-kani/src/sysroot.rs1// Copyright Kani ContributorsCOMMENT
LOWtools/build-kani/src/parser.rs1// Copyright Kani ContributorsCOMMENT
LOWtools/benchcomp/benchcomp/entry/__init__.py1# Copyright Kani ContributorsCOMMENT
LOWtools/benchcomp/test/unit/__init__.py1# Copyright Kani ContributorsCOMMENT
LOWtools/benchcomp/configs/perf-regression.yaml101 variant_pairs: [[kani_old, kani_new]]COMMENT
LOWtools/benchcomp/configs/perf-regression.yaml121 # applies. Both compare the *total* solver time, so a change that adds solver calls isCOMMENT
LOWtools/compiletest/src/raise_fd_limit.rs1// SPDX-License-Identifier: Apache-2.0 OR MITCOMMENT
LOWtools/compiletest/src/runtest.rs281 }COMMENT
LOWtools/compiletest/src/runtest.rs341 let proc_res = self.compose_and_run(cargo);COMMENT
LOWtools/compiletest/src/main.rs381 relative_dir_path: &Path,COMMENT
LOWtools/kani-cov/src/report.rs81COMMENT
LOWtools/kani-cov/src/report.rs101/// ``` println!("Hello, world!");'''COMMENT
LOWtools/kani-cov/src/args.rs1// Copyright Kani ContributorsCOMMENT
LOWtools/kani-cov/src/args.rs21/// As an example, let's assume we execute Kani with coverage enabledCOMMENT
LOWtools/kani-cov/src/args.rs41///COMMENT
LOWtools/kani-cov/src/args.rs81#[derive(Debug, clap::Args)]COMMENT
LOWtools/kani-cov/src/args.rs101 // Csv,COMMENT
LOWtools/kani-cov/src/summary.rs101 total_regions: usize,COMMENT
LOWtools/scanner/src/analysis.rs661struct Recursion {COMMENT
LOWtools/scanner/src/bin/scan.rs1// SPDX-License-Identifier: Apache-2.0 OR MITCOMMENT
LOWkani-compiler/src/kani_compiler.rs1// Copyright Kani ContributorsCOMMENT
LOWkani-compiler/src/kani_compiler.rs41/// rustc flags kani-compiler requires for correct verification semantics, setCOMMENT
LOWkani-compiler/src/kani_compiler.rs61/// change this list, not just kani-driver — compare `--prove-safety-only`,COMMENT
LOWkani-compiler/src/kani_compiler.rs81/// are parsed and applied in this exact form.COMMENT
LOWkani-compiler/src/kani_compiler.rs201COMMENT
LOWkani-compiler/src/kani_compiler.rs221 /// Instead we bring the overrides into scope crate-wide by injecting aCOMMENT
LOWkani-compiler/src/kani_compiler.rs241 // Only inject when an external `std` is available to import. TheCOMMENT
LOWkani-compiler/src/kani_compiler.rs281/// Inject `#[macro_use] extern crate std as _kani_std_macros;` at the crate root soCOMMENT
LOWkani-compiler/src/main.rs1// Copyright Kani ContributorsCOMMENT
LOWkani-compiler/src/main.rs81/// Return whether we should run our flavour of the compiler, and which arguments to pass to rustc.COMMENT
LOWkani-compiler/src/args.rs21#[derive(Debug, Default, Clone, Copy, AsRefStr, EnumString, VariantNames, PartialEq, Eq)]COMMENT
LOWkani-compiler/src/args.rs41 #[clap(long)]COMMENT
LOWkani-compiler/src/args.rs61 /// If used with --exact, the harness filter will only match the exact fully qualified name of a harness.COMMENT
LOWkani-compiler/src/args.rs81 #[clap(long = "enable-stubbing")]COMMENT
LOWkani-compiler/src/args.rs101 #[clap(long)]COMMENT
LOWkani-compiler/src/args.rs121 /// functions whose arguments require bounded nondeterministic values (e.g. sliceCOMMENT
LOWkani-compiler/src/intrinsics.rs181 /// The operand that must be a SIMD vector for this intrinsic to have a meaning, given theCOMMENT
LOWkani-compiler/src/kani_middle/kani_functions.rs1// Copyright Kani ContributorsCOMMENT
LOWkani-compiler/src/kani_middle/kani_functions.rs61/// Kani models are Rust functions that model some runtime behavior used by Kani instrumentation.COMMENT
LOWkani-compiler/src/kani_middle/kani_functions.rs181 SizeOfSliceObject,COMMENT
LOWkani-compiler/src/kani_middle/codegen_order.rs1// Copyright Kani ContributorsCOMMENT
LOWkani-compiler/src/kani_middle/mined_invariants.rs1// Copyright Kani ContributorsCOMMENT
LOWkani-compiler/src/kani_middle/analysis.rs1// Copyright Kani ContributorsCOMMENT
LOWkani-compiler/src/kani_middle/resolve.rs1181 // parens can only fail to match, never match the wrong candidate.COMMENT
LOWkani-compiler/src/kani_middle/metadata.rs101 // FIXME: This is a bit hacky. We can't resolve the target_fn to a DefId because we need somewhere to start COMMENT
LOWkani-compiler/src/kani_middle/codegen_units.rs481COMMENT
LOWkani-compiler/src/kani_middle/codegen_units.rs621///COMMENT
LOWkani-compiler/src/kani_middle/codegen_units.rs721COMMENT
LOWkani-compiler/src/kani_middle/codegen_units.rs901COMMENT
LOWkani-compiler/src/kani_middle/codegen_units.rs1261 // Each argument of `instance` must be supported by automatic harness generation, i.e.,COMMENT
LOWkani-compiler/src/kani_middle/attributes.rs41 Stub,COMMENT
LOWkani-compiler/src/kani_middle/attributes.rs61 CheckedWith,COMMENT
LOWkani-compiler/src/kani_middle/attributes.rs141/// Bundles together common data used when evaluating the attributes of a givenCOMMENT
LOWkani-compiler/src/kani_middle/attributes.rs441 ///COMMENT
LOWkani-compiler/src/kani_middle/mod.rs781/// complete model of the element's values *without any validity assumption*, i.e. every bitCOMMENT
LOWkani-compiler/src/kani_middle/mod.rs861}COMMENT
LOWkani-compiler/src/kani_middle/mod.rs1321 /// The type is not supported.COMMENT
LOWkani-compiler/src/kani_middle/coercion.rs1// Copyright Kani ContributorsCOMMENT
LOWkani-compiler/src/kani_middle/coercion.rs21use rustc_public::CrateDefType;COMMENT
709 more matches not shown…
AI Slop Vocabulary59 hits · 178 pts
SeverityFileLineSnippetContext
MEDIUMtools/build-kani/src/main.rs5//! We use Rust here just to aid in making the "script" more robust.COMMENT
MEDIUMtools/benchcomp/benchcomp/parsers/kani_perf.py33 # CBMC solves a harness in several calls, and the number of calls is not stable acrossSTRING
MEDIUMtools/benchcomp/benchcomp/parsers/kani_perf.py42 # harness solve that instance incrementally, one clause and variable at a time, so onlySTRING
MEDIUMtools/benchcomp/configs/perf-regression.yaml124 # harness that newly needs 10s or more of solver time also counts.COMMENT
MEDIUMtools/benchcomp/configs/perf-regression.yaml130 # tripped harness on both sides (https://github.com/model-checking/kani/issues/4918),COMMENT
MEDIUMtools/compiletest/src/runtest.rs569 // output. This is a temporary mechanism until we have more robustCOMMENT
MEDIUMkani-compiler/src/args.rs63 #[arg(long = "harness", num_args(1), value_name = "HARNESS_FILTER")]COMMENT
MEDIUMkani-compiler/src/kani_middle/attributes.rs1116 format!("only one '#[kani::{}]' attribute is allowed per harness", kind.as_ref()),CODE
MEDIUMkani-compiler/src/kani_middle/mod.rs120 "stub verified target `{}` does not have a corresponding `#[proof_for_contract]` harness",CODE
MEDIUM…mpiler/src/kani_middle/points_to/points_to_analysis.rs7//! The analysis uses Rust's dataflow framework by implementing appropriate traits to leverage theCOMMENT
MEDIUM…mpiler/src/kani_middle/points_to/points_to_analysis.rs192 // if a function pointer call is used), but we could leverage the call graph to resolveCOMMENT
MEDIUM…compiler/src/kani_middle/transform/rustc_intrinsics.rs168 /// Our models are usually augmented by some trait bounds, or they leverage Kani intrinsics toCOMMENT
MEDIUMtests/ui/arbitrary-ptr-doc/doc_examples.rs8//! We may be able to leverage `--runtool` from rustdoc once its stabilized. SeeCOMMENT
MEDIUM…-verified-without-contract/stub_verified_no_harness.rs18// This should fail because target_function has no `#[proof_for_contract]` harnessCOMMENT
MEDIUM⚡tests/cargo-ui/ws-integ-tests/Cargo.toml5# The `in_src_harness` has a proof harness co-located with the code.COMMENT
MEDIUM⚡tests/cargo-ui/ws-integ-tests/Cargo.toml6# The `integ_harness` has a proof harness co-located with an integration test.COMMENT
MEDIUMtests/expected/loop-contract/function_call_with_loop.rs6//! Calling a function that contains loops and test that using a #[kani::proof] harness fails because the function's preCOMMENT
MEDIUMtests/json-handler/fail-fast/test.sh5# Test JSON export under --fail-fast: a harness that completed before the abort mustCOMMENT
MEDIUMtests/json-handler/fail-fast/test.sh26# design (a harness fails), so only this invocation is exempted from `set -e`.COMMENT
MEDIUMtests/json-handler/multiple-harnesses/test.sh35# lists them, but that the summary counters, the per-harness results, and theCOMMENT
MEDIUMtests/json-handler/multiple-harnesses/test.sh36# per-harness detail arrays all agree with each other and with the harnesses that ran.COMMENT
MEDIUMtests/json-handler/multiple-harnesses/test.sh76# Each per-harness array must cover every harness exactly once. These arrays are builtCOMMENT
MEDIUMtests/json-handler/failed-verification/test.sh79# error_details is an array with one entry per harness, each identified by harness_idCOMMENT
MEDIUMtests/script-based-pre/verify_std_cmd/verify_std.sh23# Insert a small harness in one of the standard library modules.COMMENT
MEDIUM…ts/script-based-pre/cargo_autoharness_bounds/bounds.sh16# on slower CI runners it exceeds the autoharness default 60s harness timeout, so raise it here.COMMENT
MEDIUM…ts/script-based-pre/cargo_autoharness_slices/slices.sh15# reason about; on slower CI runners it can exceed the autoharness default 60s harness timeout,COMMENT
MEDIUM…ts/script-based-pre/cargo_autoharness_slices/slices.sh16# so raise it here to keep this (genuinely passing) harness from spuriously timing out.COMMENT
MEDIUM…/script-based-pre/cargo_autoharness_bounded/bounded.sh16# 60s harness timeout, so raise it here to keep these harnesses from spuriously timing out.COMMENT
MEDIUMtests/script-based-pre/log_file/log_file.sh18# The per-harness detail belongs in the file, not on the terminal. `kani` aboveCOMMENT
MEDIUMtests/script-based-pre/log_file/log_file.sh19# is unredirected so the harness output would show up in `.expected` if itCOMMENT
MEDIUM…based-pre/fail_fast_keeps_completed/keeps_completed.sh6# under `--fail-fast`, a harness that already completed must not be dropped fromCOMMENT
MEDIUM…based-pre/fail_fast_keeps_completed/keeps_completed.sh7# the final summary when a later harness fails and aborts the run.COMMENT
MEDIUM…based-pre/fail_fast_keeps_completed/keeps_completed.sh22# The run must still fail overall (a harness failed).COMMENT
MEDIUM…based-pre/fail_fast_keeps_completed/keeps_completed.sh29# The already-completed passing harness must be retained in the summary.COMMENT
MEDIUM…s/script-based-pre/harness_filter_no_match/no_match.sh6# a `--harness` filter that matches no harness must fail (non-zero exit + anCOMMENT
MEDIUM…ipt-based-pre/cargo_autoharness_fmt_impls/fmt-impls.sh5# Raise the harness timeout above autoharness's 60s default, like the other autoharness tests: onCOMMENT
MEDIUM…d-pre/cargo_no_assert_overrides/no-assert-overrides.sh30# intentionally failing harness still fails verification, producing theCOMMENT
MEDIUM…cript-based-pre/compiler_defaults/compiler_defaults.sh9# the defaults, --cfg=kani would be unset, the harness module would beCOMMENT
MEDIUM…cript-based-pre/compiler_defaults/compiler_defaults.sh142# the required values resolved. The #[cfg(panic = "abort")]-gated harnessCOMMENT
MEDIUM⚡…sts/script-based-pre/fail_fast_parallel/early_abort.sh36# Every harness fails, so every counted harness must be a failure.COMMENT
MEDIUM⚡…sts/script-based-pre/fail_fast_parallel/early_abort.sh42# At least the failing harness itself is counted.COMMENT
MEDIUM⚡…sts/script-based-pre/fail_fast_parallel/early_abort.sh48# Smoke check, not the regression assertion: some harness was skipped, so theCOMMENT
MEDIUMlibrary/kani_core/src/arbitrary/pointer.rs38 /// # fn harness() {COMMENT
MEDIUMlibrary/kani_core/src/arbitrary/pointer.rs55 /// # fn harness() {COMMENT
MEDIUMlibrary/kani_core/src/arbitrary/pointer.rs81 /// # fn harness() {COMMENT
MEDIUMlibrary/kani_core/src/arbitrary/pointer.rs133 /// # fn harness() {COMMENT
MEDIUMlibrary/kani_core/src/arbitrary/pointer.rs151 /// # fn harness() {COMMENT
MEDIUMlibrary/kani_core/src/arbitrary/pointer.rs177 /// # fn harness() {COMMENT
MEDIUMlibrary/kani/src/contracts.rs178//! Contract are used both to verify function behavior and to leverage theCOMMENT
MEDIUMlibrary/kani_macros/src/lib.rs673 /// Add #[allow(dead_code)] to a proof harness to avoid dead code warnings.COMMENT
MEDIUMkani_metadata/src/harness.rs37 /// The `#[kani::<>]` attributes added to a harness.COMMENT
MEDIUMkani_metadata/src/harness.rs129/// but this function is written to be robust against that changing in the future.COMMENT
MEDIUMscripts/kani-slow-tests.sh18# TODO: We should add a more robust mechanism to detect python unexpected behavior.COMMENT
MEDIUMscripts/validate_json_export.py101 # element let malformed data in every later harness pass validation, whichCOMMENT
MEDIUMscripts/validate_json_export.py102 # defeats the purpose on exactly the multi-harness runs this validates.COMMENT
MEDIUMscripts/kani-perf.sh29# Bound each test's wall time so a runaway case (e.g. an OOM-prone harness)COMMENT
MEDIUMscripts/kani-regression.sh18# TODO: We should add a more robust mechanism to detect python unexpected behavior.COMMENT
MEDIUMscripts/kani-regression.sh112# It should just successfully find the project and specified proof harness. (Then clean up.)COMMENT
MEDIUMkani-driver/src/args/mod.rs287 #[arg(long = "harness", num_args(1), value_name = "HARNESS_FILTER")]COMMENT
Cross-Language Confusion10 hits · 68 pts
SeverityFileLineSnippetContext
HIGH⚡tools/benchcomp/test/test_regression.py302 "command_line": "mkdir bench_1 && echo true > bench_1/success"CODE
HIGH⚡tools/benchcomp/test/test_regression.py308 "command_line": "mkdir bench_1 && echo false > bench_1/success"CODE
HIGH⚡tools/benchcomp/test/test_regression.py344 "command_line": "mkdir bench_1 && echo true > bench_1/success"CODE
HIGH⚡tools/benchcomp/test/test_regression.py350 "command_line": "mkdir bench_1 && echo true > bench_1/success"CODE
HIGH⚡tools/benchcomp/test/test_regression.py386 "command_line": "mkdir bench_1 && echo 10 > bench_1/n_bugs"CODE
HIGH⚡tools/benchcomp/test/test_regression.py392 "command_line": "mkdir bench_1 && echo 5 > bench_1/n_bugs"CODE
HIGH⚡tools/benchcomp/test/test_regression.py427 "command_line": "mkdir bench_1 && echo 10 > bench_1/n_bugs"CODE
HIGH⚡tools/benchcomp/test/test_regression.py433 "command_line": "mkdir bench_1 && echo 5 > bench_1/n_bugs"CODE
HIGHtools/benchcomp/test/test_regression.py850 grep bin out && grep '^foo:' out && echo '{CODE
HIGHscripts/validate_json_export.py45 nullable: Whether the parent declared this value may be null, via itsSTRING
Hyper-Verbose Identifiers27 hits · 30 pts
SeverityFileLineSnippetContext
LOWtools/benchcomp/benchcomp/visualizers/__init__.py246 def _parse_scatterplot_config(scatterplot_config_string):CODE
LOWtools/benchcomp/benchcomp/visualizers/__init__.py357 def _organize_results_into_metrics(results, log_scaling):STRING
LOWtools/benchcomp/test/test_unit.py16 def test_environment_construction(self):CODE
LOWtools/benchcomp/test/test_unit.py24 def test_placeholder_construction(self):CODE
LOWtools/benchcomp/test/test_unit.py50 def test_environment_update_variable(self):CODE
LOWtools/benchcomp/test/test_regression.py135 def test_error_on_regression_two_benchmarks_previously_failed(self):CODE
LOWtools/benchcomp/test/test_regression.py183 def test_error_on_regression_two_benchmarks_one_failed(self):CODE
LOWtools/benchcomp/test/test_regression.py231 def test_error_on_regression_all_metrics(self):CODE
LOW⚡tools/benchcomp/test/test_regression.py293 def test_error_on_regression_visualization_success_regressed(self):CODE
LOW⚡tools/benchcomp/test/test_regression.py335 def test_error_on_regression_visualization_success_no_regressed(self):CODE
LOW⚡tools/benchcomp/test/test_regression.py377 def test_error_on_regression_visualization_ratio_no_regressed(self):CODE
LOW⚡tools/benchcomp/test/test_regression.py418 def test_error_on_regression_visualization_ratio_regressed(self):CODE
LOWtools/benchcomp/test/test_regression.py459 def test_markdown_results_table(self):CODE
LOWtools/benchcomp/test/test_regression.py961 def test_run_command_visualization(self):STRING
LOWtools/benchcomp/test/test_regression.py1012 def test_run_failing_command_visualization(self):STRING
LOWtools/benchcomp/test/test_regression.py1057 def test_unknown_metric_in_benchmark(self):STRING
LOW⚡…ols/benchcomp/test/unit/test_perf_regression_config.py49 def test_same_instance_noise_is_tolerated(self):CODE
LOW⚡…ols/benchcomp/test/unit/test_perf_regression_config.py54 def test_same_instance_large_slowdown_is_caught(self):CODE
LOW⚡…ols/benchcomp/test/unit/test_perf_regression_config.py59 def test_more_calls_at_the_same_per_call_time_is_caught(self):CODE
LOW⚡…ols/benchcomp/test/unit/test_perf_regression_config.py65 def test_changed_instance_uses_the_strict_threshold(self):CODE
LOW⚡…ols/benchcomp/test/unit/test_perf_regression_config.py74 def test_short_runs_are_ignored(self):CODE
LOW⚡…ols/benchcomp/test/unit/test_perf_regression_config.py78 def test_harness_without_solver_output(self):CODE
LOW⚡…ols/benchcomp/test/unit/test_perf_regression_config.py86 def test_newly_needing_the_solver_is_caught(self):CODE
LOW⚡…ols/benchcomp/test/unit/test_perf_regression_config.py96 def test_missing_label_metric_is_not_a_key_error(self):CODE
LOWtools/benchcomp/test/unit/test_kani_perf_parser.py23 def test_solver_calls_are_counted(self):CODE
LOWtools/benchcomp/test/unit/test_kani_perf_parser.py61 def test_harness_without_solver_output(self):STRING
LOWscripts/validate_json_export.py37def validate_structure_recursive(data, schema, path="", nullable=False):CODE
Redundant / Tautological Comments12 hits · 20 pts
SeverityFileLineSnippetContext
LOWtools/benchcomp/benchcomp/cmd_args.py252 # Set entrypoint to benchcomp.entry.visualize.main()COMMENT
LOW…d-pre/playback_with_cfg_kani/playback_with_cfg_kani.sh14# Check if cargo is installedCOMMENT
LOW⚡…d-pre/individual_file_output/individual_file_output.sh21# Check if the output directory existsCOMMENT
LOW⚡…d-pre/individual_file_output/individual_file_output.sh27# Check if there are any files in the output directoryCOMMENT
LOW⚡…d-pre/individual_file_output/individual_file_output.sh35# Check if each file contains textCOMMENT
LOW…-pre/kani_autoharness_exclude_precedence/precedence.sh21# Check if a function appears in the "Selected Function" tableCOMMENT
LOW…-pre/kani_autoharness_exclude_precedence/precedence.sh32# Check if a function appears in the "Skipped Function" tableCOMMENT
LOWscripts/check_kissat_version.sh5# Check if kissat has the minimum required version specified in theCOMMENT
LOWscripts/validate_json_export.py80 # Check if field exists in dataCOMMENT
LOWscripts/validate_json_export.py221 # Check if specific field validation requestedCOMMENT
LOWscripts/kani-regression.sh26# Check if installed versions are correct.COMMENT
LOWscripts/setup/install_kissat.sh15# Check if the correct Kissat version is already installedCOMMENT
Empty Error Handlers3 hits · 15 pts
SeverityFileLineSnippetContext
HIGHtools/benchcomp/benchcomp/__init__.py106except ImportError:CODE
HIGHtools/benchcomp/benchcomp/parsers/kani_perf.py138except KeyError:CODE
HIGHtools/benchcomp/benchcomp/parsers/kani_perf.py145except (KeyError, ZeroDivisionError):CODE
Decorative Section Separators5 hits · 15 pts
SeverityFileLineSnippetContext
MEDIUMtests/kani/Static/anon_static.rs11 // ╾───────alloc2────────╼ │ ╾──────╼COMMENT
MEDIUMtests/kani/Static/anon_static.rs31 // ╾───────alloc2────────╼ │ ╾──────╼COMMENT
MEDIUMtests/kani/Static/anon_static.rs39 // ╾───────alloc2────────╼ │ ╾──────╼COMMENT
MEDIUMtests/kani/Static/pointer_to_const_alloc.rs9// ╾─────alloc3<imm>─────╼ 01 00 00 00 00 00 00 00 │ ╾──────╼........COMMENT
MEDIUMtests/kani/Static/pointer_to_const_alloc.rs17// ╾─────alloc3<imm>─────╼ 01 00 00 00 00 00 00 00 │ ╾──────╼........COMMENT
Slop Phrases5 hits · 14 pts
SeverityFileLineSnippetContext
MEDIUM…orm/check_uninit/delayed_ub/instrumentation_visitor.rs137 // Here is a simple example:COMMENT
MEDIUM…compiler/src/codegen_cprover_gotoc/codegen/function.rs210 // As discussed above, fields are named like `0: t1`.COMMENT
LOWtests/firecracker/virtio-balloon-compact/ignore-main.rs42 // Don't forget to push the last range to the result.COMMENT
MEDIUMlibrary/kani_macros/src/lib.rs180/// As mentioned earlier, the `#[safety_constraint(...)]` attribute can be addedCOMMENT
MEDIUMlibrary/kani_macros/src/lib.rs307/// As mentioned earlier, the `#[safety_constraint(...)]` attribute can be addedCOMMENT
Self-Referential Comments4 hits · 14 pts
SeverityFileLineSnippetContext
MEDIUM⚡tests/cargo-ui/ws-integ-tests/Cargo.toml4# Create a workspace with three independent libraries that have integration tests.COMMENT
MEDIUMtests/cargo-kani/stubbing-ws-packages/Cargo.toml4# Create a workspace with multiple packages with stubsCOMMENT
MEDIUMtests/script-based-pre/verify_std_cmd/verify_std.sh17# Create a custom standard library.COMMENT
MEDIUMtests/script-based-pre/std_codegen/codegen_std.sh21# Create a custom standard library.COMMENT
Hallucination Indicators1 hit · 10 pts
SeverityFileLineSnippetContext
CRITICAL…i-compiler/src/codegen_aeneas_llbc/mir_to_ullbc/mod.rs1288 trait_refs: trait_ref.trait_decl_ref.skip_binder.generics.trait_refs.clone(),CODE
Deep Nesting8 hits · 8 pts
SeverityFileLineSnippetContext
LOWtools/benchcomp/benchcomp/__init__.py78CODE
LOWtools/benchcomp/benchcomp/parsers/kani_perf.py96CODE
LOWtools/benchcomp/benchcomp/visualizers/__init__.py316CODE
LOWtools/benchcomp/benchcomp/visualizers/__init__.py357CODE
LOWtools/benchcomp/benchcomp/visualizers/__init__.py384CODE
LOWtools/benchcomp/benchcomp/visualizers/utils.py71CODE
LOWtools/benchcomp/benchcomp/visualizers/utils.py117CODE
LOWscripts/validate_json_export.py37CODE
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGH…ni-compiler/src/codegen_cprover_gotoc/codegen/place.rs368 /// For example, the auto-generated code for Fn::call_once uses a local FnDef to call theCOMMENT
Verbosity Indicators2 hits · 4 pts
SeverityFileLineSnippetContext
LOW⚡…kani/FunctionContracts/stub_verified_safe_arbitrary.rs33// Step 1: Verify the contractCOMMENT
LOW⚡…kani/FunctionContracts/stub_verified_safe_arbitrary.rs39// Step 2: Use stub_verified in a caller — works becauseCOMMENT
Structural Annotation Overuse2 hits · 4 pts
SeverityFileLineSnippetContext
LOW⚡…kani/FunctionContracts/stub_verified_safe_arbitrary.rs33// Step 1: Verify the contractCOMMENT
LOW⚡…kani/FunctionContracts/stub_verified_safe_arbitrary.rs39// Step 2: Use stub_verified in a caller — works becauseCOMMENT
Unused Imports2 hits · 2 pts
SeverityFileLineSnippetContext
LOWscripts/validate_json_export.py13CODE
LOWscripts/gen_benchcomp_schemas.py12CODE
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWscripts/run-autopep8.sh6# Usage:COMMENT
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOWscripts/validate_json_export.py161 except Exception as e:CODE