Repository Analysis

FuelLabs/sway

🌴 Empowering everyone to build reliable and efficient smart contracts.

4.2 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of FuelLabs/sway, a Rust project with 61,576 GitHub stars. SynthScan v2.0 examined 326,525 lines of code across 4438 source files, recording 994 pattern matches distributed across 11 syntactic categories. The overall adjusted score of 4.2 places this repository in the Likely human-written band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

4.2
Adjusted Score
4.2
Raw Score
100%
Time Factor
2026-07-13
Last Push
61.6K
Stars
Rust
Language
326.5K
Lines of Code
4.4K
Files
994
Pattern Hits
2026-07-14
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 21HIGH 1MEDIUM 37LOW 935

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 994 distinct pattern matches across 11 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Over-Commented Block898 hits · 888 pts
SeverityFileLineSnippetContext
LOWci_checks.sh1#!/usr/bin/env bashCOMMENT
LOWforc/src/cli/shared.rs101 /// Create a binary file at the provided path representing the final bytecode.COMMENT
LOWforc/src/cli/shared.rs121 /// Use the release build profile.COMMENT
LOWforc/src/cli/shared.rs141pub struct Print {COMMENT
LOWforc/src/cli/shared.rs161 /// - virtual: initial ASM with virtual registers and abstract control flow.COMMENT
LOWforc/src/cli/shared.rs221 /// Prevents Forc from using the network when managing dependencies.COMMENT
LOWforc/src/cli/shared.rs241 ///COMMENT
LOWforc/src/cli/commands/test.rs21 [ Run test without any output => "forc test --silent" ]COMMENT
LOWforc/src/cli/commands/test.rs41#[clap(bin_name = "forc test", version, after_help = help())]COMMENT
LOWforc/src/cli/commands/test.rs61 /// These are the gas costs values of the Fuel mainnet as of time ofCOMMENT
LOWforc/src/cli/commands/check.rs21pub struct Command {COMMENT
LOWforc/src/cli/commands/build.rs21///COMMENT
LOWforc/src/cli/commands/update.rs21COMMENT
LOWforc/src/cli/commands/init.rs21 /// The default program type, excluding all flags or adding this flag creates a basic contract program.COMMENT
LOWforc/src/cli/commands/new.rs21 /// program.COMMENT
LOWforc/src/ops/forc_update.rs1use crate::cli::UpdateCommand;COMMENT
LOWsway-parse/src/token.rs101 start: usize,COMMENT
LOWsway-parse/src/parser.rs81 /// Tries to peek a `P` in its canonical way.COMMENT
LOWsway-parse/src/parser.rs141COMMENT
LOWtest/src/main.rs81 /// Print out the specified IR (separate options with comma), if the verbose option is onCOMMENT
LOWtest/src/main.rs101COMMENT
LOWtest/src/main.rs121 /// This option is ignored if tests are run in parallel.COMMENT
LOWtest/src/in_language_tests/run_in_language_tests.sh1#!/usr/bin/env bashCOMMENT
LOWtest/src/in_language_tests/run_in_language_tests.sh21# (compilation and tests output) is printed as it runs.COMMENT
LOWtest/src/snapshot/mod.rs601 let logs = receipts.into_iter().collect();COMMENT
LOWtest/src/sdk-harness/test_projects/storage_init/mod.rs21 .unwrap()COMMENT
LOW…ess/test_projects/storage_vec_of_storage_string/mod.rs61// let _ = instanceCOMMENT
LOW…ess/test_projects/storage_vec_of_storage_string/mod.rs81// .methods()COMMENT
LOWtest/src/ir_generation/mod.rs41 /// // ::check-ir-optimized::COMMENT
LOWtest/src/e2e_vm_tests/mod.rs1241 // However, "run_on_node" tests deploy contracts to a local node, and if multiple such testsCOMMENT
LOW…fail/match_expressions_struct_missing_fields/test.toml1category = "fail"COMMENT
LOW…ould_fail/storage_in_library/test.dynamic_storage.toml1category = "fail"COMMENT
LOW…test_programs/should_fail/storage_in_library/test.toml1category = "fail"COMMENT
LOW…test_programs/should_fail/where_clause_impls/test.toml1category = "fail"COMMENT
LOW…hould_fail/struct_field_privacy_field_access/test.toml1category = "fail"COMMENT
LOW…hould_fail/struct_field_privacy_field_access/test.toml21#check: $()Private struct field is inaccessibleCOMMENT
LOW…s/test_programs/should_fail/nested_functions/test.toml1category = "fail"COMMENT
LOW…rams/should_fail/superabi_duplicate_methods6/test.toml1category = "fail"COMMENT
LOW…programs/should_fail/variable_does_not_exist/test.toml1category = "fail"COMMENT
LOW…programs/should_fail/variable_does_not_exist/test.toml21# check: $()let _ = x + y + z;COMMENT
LOW…rams/should_fail/superabi_duplicate_methods8/test.toml1category = "fail"COMMENT
LOW…s/should_fail/trait_method_generic_ambiguous/test.toml1category = "fail"COMMENT
LOW…programs/should_fail/superabi_contract_call2/test.toml1category = "fail"COMMENT
LOW…ould_fail/struct_field_privacy_instantiation/test.toml1category = "fail"COMMENT
LOW…ould_fail/struct_field_privacy_instantiation/test.toml21#check: $()Struct "LibTwoPrivateFields" is declared here, and has private fields "y" and "z".COMMENT
LOW…ould_fail/struct_field_privacy_instantiation/test.toml41#check: $()Inaccessible fields are "y" and "z".COMMENT
LOW…ould_fail/struct_field_privacy_instantiation/test.toml61#check: $()z: u64,COMMENT
LOW…ould_fail/struct_field_privacy_instantiation/test.toml81#check: $()let _ = LibStruct { nn: 0, x: 0 };COMMENT
LOW…ould_fail/struct_field_privacy_instantiation/test.toml101#check: $()let _ = LibStruct { nn: 0, x: 0, y: 0, z: 0 };COMMENT
LOW…ould_fail/struct_field_privacy_instantiation/test.toml121COMMENT
LOW…ould_fail/struct_field_privacy_instantiation/test.toml141#check: $()Struct cannot be instantiated due to inaccessible private fieldsCOMMENT
LOW…ould_fail/struct_field_privacy_instantiation/test.toml161#check: $()Struct cannot be instantiated due to inaccessible private fieldsCOMMENT
LOW…ould_fail/struct_field_privacy_instantiation/test.toml181#nextln: $()Field "z" of the struct "LibStruct" is declared here as private.COMMENT
LOW…ould_fail/struct_field_privacy_instantiation/test.toml201#nextln: $()Field "nn" does not exist in the struct "MainStruct".COMMENT
LOW…e_field_access_on_non_struct/test.dynamic_storage.toml1category = "fail"COMMENT
LOW…e_field_access_on_non_struct/test.dynamic_storage.toml21#check: $()Struct field does not existCOMMENT
LOW…e_field_access_on_non_struct/test.dynamic_storage.toml41#check: $()Fields can only be accessed on storage variables that are structs.COMMENT
LOW…ould_fail/storage_field_access_on_non_struct/test.toml1category = "fail"COMMENT
LOW…ould_fail/storage_field_access_on_non_struct/test.toml21#check: $()let _ = storage.s_01.non_existing_field.read();COMMENT
LOW…ould_fail/storage_field_access_on_non_struct/test.toml41COMMENT
838 more matches not shown…
Hallucination Indicators21 hits · 275 pts
SeverityFileLineSnippetContext
CRITICALtest/src/e2e_vm_tests/mod.rs938 pkg.built.descriptor.pinned.name.as_str(),CODE
CRITICALtest/src/e2e_vm_tests/mod.rs962 pkg.built.descriptor.pinned.name.as_str(),CODE
CRITICAL…e_field_access_on_non_struct/test.dynamic_storage.toml27#check: $()let _ = storage.s_01.second.x.prev_not_a_struct.read();COMMENT
CRITICAL…e_field_access_on_non_struct/test.dynamic_storage.toml38#check: $()let _ = storage.s_01.second.third.x.prev_not_a_struct.read();COMMENT
CRITICAL…e_field_access_on_non_struct/test.dynamic_storage.toml44#check: $()let _ = storage.s_01.second.third.non_existing_field.read();COMMENT
CRITICAL…ould_fail/storage_field_access_on_non_struct/test.toml26#check: $()let _ = storage.s_01.second.x.prev_not_a_struct.read();COMMENT
CRITICAL…ould_fail/storage_field_access_on_non_struct/test.toml37#check: $()let _ = storage.s_01.second.third.x.prev_not_a_struct.read();COMMENT
CRITICAL…ould_fail/storage_field_access_on_non_struct/test.toml43#check: $()let _ = storage.s_01.second.third.non_existing_field.read();COMMENT
CRITICALsway-core/src/semantic_analysis/namespace/trait_map.rs693 prefixes: self_entry.inner.key.name.prefixes.clone(),CODE
CRITICALsway-core/src/semantic_analysis/namespace/trait_map.rs694 suffix: self_entry.inner.key.name.suffix.name.clone(),CODE
CRITICALsway-core/src/semantic_analysis/namespace/trait_map.rs1197 prefixes: entry.inner.key.name.prefixes.clone(),CODE
CRITICALsway-core/src/semantic_analysis/namespace/trait_map.rs1198 suffix: entry.inner.key.name.suffix.name.clone(),CODE
CRITICALsway-core/src/semantic_analysis/namespace/trait_map.rs1251 prefixes: e.inner.key.name.prefixes.clone(),CODE
CRITICALsway-core/src/semantic_analysis/namespace/trait_map.rs1252 suffix: e.inner.key.name.suffix.name.clone(),CODE
CRITICALsway-core/src/semantic_analysis/namespace/trait_map.rs1257 && trait_type_args.len() == e.inner.key.name.suffix.args.len()CODE
CRITICALsway-core/src/semantic_analysis/namespace/trait_map.rs1260 .zip(e.inner.key.name.suffix.args.iter())CODE
CRITICALsway-core/src/semantic_analysis/namespace/trait_map.rs1348 prefixes: entry.inner.key.name.prefixes.clone(),CODE
CRITICALsway-core/src/semantic_analysis/namespace/trait_map.rs1349 suffix: entry.inner.key.name.suffix.name.clone(),CODE
CRITICALsway-core/src/semantic_analysis/namespace/trait_map.rs1353 .push((trait_call_path, entry.inner.key.name.suffix.args.clone()));CODE
CRITICAL…ore/src/semantic_analysis/namespace/trait_coherence.rs68 let package_name = trait_entry.inner.key.name.prefixes.first().unwrap();CODE
CRITICAL…ore/src/semantic_analysis/namespace/trait_coherence.rs179 let trait_name = trait_entry.inner.key.name.suffix.name.to_string();CODE
Decorative Section Separators31 hits · 98 pts
SeverityFileLineSnippetContext
MEDIUM…ould_fail/struct_field_privacy_instantiation/test.toml106# ---------------------------------------------------COMMENT
MEDIUM…ould_fail/struct_field_privacy_instantiation/test.toml183# ---------------------------------------------------COMMENT
MEDIUM…ould_fail/struct_instantiation_type_mismatch/test.toml67# ----------------------------------------------------COMMENT
MEDIUM…rograms/should_fail/array_invalid_index_type/test.toml61#---------------------------------------------------COMMENT
MEDIUM…/test_programs/should_pass/storage_benchmarks/bench.sh31# ── Output file ─────────────────────────────────────────────────────COMMENT
MEDIUM…/test_programs/should_pass/storage_benchmarks/bench.sh40# ── Main ────────────────────────────────────────────────────────────COMMENT
MEDIUM…t_programs/should_pass/storage_benchmarks/perf_diff.sh31# ── Argument validation ─────────────────────────────────────────────COMMENT
MEDIUM…t_programs/should_pass/storage_benchmarks/perf_diff.sh90# ── Parse benchmark data from a perf output file ────────────────────COMMENT
MEDIUM…t_programs/should_pass/storage_benchmarks/perf_diff.sh126# ── Collect data ────────────────────────────────────────────────────COMMENT
MEDIUM…t_programs/should_pass/storage_benchmarks/perf_diff.sh156# ── Compute diffs and generate output ───────────────────────────────COMMENT
MEDIUM…ms/should_pass/storage_benchmarks/bench_storage_vec.sh69# ── Helpers ─────────────────────────────────────────────────────────COMMENT
MEDIUM…ms/should_pass/storage_benchmarks/bench_storage_vec.sh138 # ── CSV output ──────────────────────────────────────────────────COMMENT
MEDIUM…ms/should_pass/storage_benchmarks/bench_storage_vec.sh184# ── Main ────────────────────────────────────────────────────────────COMMENT
MEDIUM…_pass/storage_benchmarks/generate_storage_vec_bench.sh22# ── Size → type mapping ────────────────────────────────────────────COMMENT
MEDIUM…_pass/storage_benchmarks/generate_storage_vec_bench.sh42# ── Helpers ─────────────────────────────────────────────────────────COMMENT
MEDIUM…_pass/storage_benchmarks/generate_storage_vec_bench.sh143# ── Generate one project ───────────────────────────────────────────COMMENT
MEDIUM…_pass/storage_benchmarks/generate_storage_vec_bench.sh156 # ── Forc.toml ───────────────────────────────────────────────────COMMENT
MEDIUM…_pass/storage_benchmarks/generate_storage_vec_bench.sh173 # ── test.toml ───────────────────────────────────────────────────COMMENT
MEDIUM…_pass/storage_benchmarks/generate_storage_vec_bench.sh176 # ── test.dynamic_storage.toml ────────────────────────────────────COMMENT
MEDIUM…_pass/storage_benchmarks/generate_storage_vec_bench.sh182 # ── src/main.sw ─────────────────────────────────────────────────COMMENT
MEDIUM…_pass/storage_benchmarks/generate_storage_vec_bench.sh199 # ── Empty-call baseline ──────────────────────────────────────COMMENT
MEDIUM…_pass/storage_benchmarks/generate_storage_vec_bench.sh205 # ── Populate baselines ──────────────────────────────────────COMMENT
MEDIUM…_pass/storage_benchmarks/generate_storage_vec_bench.sh216 # ── store_vec baselines ─────────────────────────────────────COMMENT
MEDIUM…_pass/storage_benchmarks/generate_storage_vec_bench.sh226 # ── Operation methods ───────────────────────────────────────COMMENT
MEDIUM…_pass/storage_benchmarks/generate_storage_vec_bench.sh254 # ── Test functions ──────────────────────────────────────────COMMENT
MEDIUM…_pass/storage_benchmarks/generate_storage_vec_bench.sh304# ── Main ────────────────────────────────────────────────────────────COMMENT
MEDIUM…should_pass/storage_benchmarks/bench_storage_fields.sh58# ── Helpers ─────────────────────────────────────────────────────────COMMENT
MEDIUM…should_pass/storage_benchmarks/bench_storage_fields.sh110 # ── CSV output ──────────────────────────────────────────────────COMMENT
MEDIUM…should_pass/storage_benchmarks/bench_storage_fields.sh120# ── Main ────────────────────────────────────────────────────────────COMMENT
MEDIUM…rams/should_pass/storage_benchmarks/perf_diff_stats.sh16# ── Argument validation ─────────────────────────────────────────────COMMENT
MEDIUM…rams/should_pass/storage_benchmarks/perf_diff_stats.sh38# ── Parse CSV and compute stats ─────────────────────────────────────COMMENT
Verbosity Indicators16 hits · 32 pts
SeverityFileLineSnippetContext
LOWforc-pkg/src/manifest/mod.rs664 // While creating a `ManifestFile` we need to check if the given path corresponds to aCOMMENT
LOWforc-pkg/src/manifest/mod.rs682 // While creating a `ManifestFile` we need to check if the given path corresponds to aCOMMENT
LOWforc-pkg/src/manifest/mod.rs1092 // While creating a `ManifestFile` we need to check if the given path corresponds to aCOMMENT
LOWsway-core/src/asm_generation/fuel/register_allocator.rs584 // Step 1: Liveness Analysis.COMMENT
LOWsway-core/src/asm_generation/fuel/register_allocator.rs587 // Step 2: Construct the interference graph.COMMENT
LOWsway-core/src/asm_generation/fuel/register_allocator.rs591 // Step 3: Remove redundant MOVE instructions using the interference graph.COMMENT
LOWsway-core/src/asm_generation/fuel/register_allocator.rs595 // Step 4: Simplify - i.e. color the interference graph and return a stack that containsCOMMENT
LOWsway-core/src/asm_generation/fuel/register_allocator.rs659 // Step 5: Use the stack to assign a register for each virtual register.COMMENT
LOWsway-core/src/asm_generation/fuel/register_allocator.rs661 // Step 6: Update all instructions to use the resulting register pool.COMMENT
LOWsway-core/src/ir_generation/function.rs1823 // Step 1: compile the user data and get its typeCOMMENT
LOWsway-core/src/ir_generation/function.rs1837 // Step 2: build a struct with two fields:COMMENT
LOWsway-core/src/ir_generation/function.rs1844 // Step 3: construct a local pointer for the message aggregate structCOMMENT
LOWsway-core/src/ir_generation/function.rs1859 // Step 4: Convert the local variable into a value via `get_local`.COMMENT
LOWsway-core/src/ir_generation/function.rs1866 // Step 5: Grab the message ID from `messages_types_map` and insert it as theCOMMENT
LOWsway-core/src/ir_generation/function.rs1888 // Step 6: Insert the user message data as the second field of the structCOMMENT
LOWsway-core/src/type_system/info.rs1558 // TODO we need to check if this type has a custom AbiEncode impl or notCOMMENT
Structural Annotation Overuse13 hits · 27 pts
SeverityFileLineSnippetContext
LOWforc-pkg/src/source/git/mod.rs515/// NOTE: This function assumes that the caller has acquired an advisory lock to co-ordinate accessCOMMENT
LOWsway-core/src/asm_generation/fuel/register_allocator.rs584 // Step 1: Liveness Analysis.COMMENT
LOWsway-core/src/asm_generation/fuel/register_allocator.rs587 // Step 2: Construct the interference graph.COMMENT
LOWsway-core/src/asm_generation/fuel/register_allocator.rs591 // Step 3: Remove redundant MOVE instructions using the interference graph.COMMENT
LOWsway-core/src/asm_generation/fuel/register_allocator.rs595 // Step 4: Simplify - i.e. color the interference graph and return a stack that containsCOMMENT
LOWsway-core/src/asm_generation/fuel/register_allocator.rs659 // Step 5: Use the stack to assign a register for each virtual register.COMMENT
LOWsway-core/src/asm_generation/fuel/register_allocator.rs661 // Step 6: Update all instructions to use the resulting register pool.COMMENT
LOWsway-core/src/ir_generation/function.rs1823 // Step 1: compile the user data and get its typeCOMMENT
LOWsway-core/src/ir_generation/function.rs1837 // Step 2: build a struct with two fields:COMMENT
LOWsway-core/src/ir_generation/function.rs1844 // Step 3: construct a local pointer for the message aggregate structCOMMENT
LOWsway-core/src/ir_generation/function.rs1859 // Step 4: Convert the local variable into a value via `get_local`.COMMENT
LOWsway-core/src/ir_generation/function.rs1866 // Step 5: Grab the message ID from `messages_types_map` and insert it as theCOMMENT
LOWsway-core/src/ir_generation/function.rs1888 // Step 6: Insert the user message data as the second field of the structCOMMENT
AI Slop Vocabulary5 hits · 14 pts
SeverityFileLineSnippetContext
MEDIUMforc/src/cli/commands/test.rs53 /// Number of threads to utilize when running the tests. By default, this is the number ofCOMMENT
MEDIUMsway-core/src/asm_generation/from_ir.rs104 Stack(u64), // Storage in the runtime stack starting at an absolute word offset. Essentially a global.CODE
MEDIUMsway-core/src/language/purity.rs6/// or could potentially access contract storage, it is [Purity::Impure]. If a function does not utilize anyCOMMENT
MEDIUM…ysis/ast_node/expression/match_expression/typed/mod.rs162//! Essentially, we have to extract the variables exactly from the variant that has matched.COMMENT
MEDIUMsway-ir/src/optimize/init_aggr_lowering.rs169 // Essentially, we are treating the nested `init_aggr` as a root for the rest of the lowerinCOMMENT
Example Usage Blocks6 hits · 9 pts
SeverityFileLineSnippetContext
LOW…/test_programs/should_pass/storage_benchmarks/bench.sh17# Usage:COMMENT
LOW…t_programs/should_pass/storage_benchmarks/perf_diff.sh6# Usage:COMMENT
LOW…ms/should_pass/storage_benchmarks/bench_storage_vec.sh23# Usage:COMMENT
LOW…_pass/storage_benchmarks/generate_storage_vec_bench.sh5# Usage:COMMENT
LOW…should_pass/storage_benchmarks/bench_storage_fields.sh15# Usage:COMMENT
LOW…rams/should_pass/storage_benchmarks/perf_diff_stats.sh5# Usage:COMMENT
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGH…emantic_analysis/ast_node/declaration/auto_impl/mod.rs1//! This module contains common infrastructure for generating and parsing auto-generated code.COMMENT
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMupdate_fuel_dependencies.sh11# Define the list of fuel maintained cratesCOMMENT
TODO Padding1 hit · 2 pts
SeverityFileLineSnippetContext
LOWforc-pkg/src/source/ipfs.rs57 // TODO: implement local cache search for ipfs sources.COMMENT
Fake / Example Data1 hit · 2 pts
SeverityFileLineSnippetContext
LOW…src/semantic_analysis/ast_node/declaration/trait_fn.rs95 /// This function is used in trait declarations to insert "placeholder"COMMENT