Repository Analysis

gruntwork-io/terragrunt

Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu/Terraform to scale.

2.4 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of gruntwork-io/terragrunt, a Go project with 9,711 GitHub stars. SynthScan v2.0 examined 259,609 lines of code across 1127 source files, recording 329 pattern matches distributed across 10 syntactic categories. The overall adjusted score of 2.4 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).

2.4
Adjusted Score
2.4
Raw Score
100%
Time Factor
2026-07-14
Last Push
9.7K
Stars
Go
Language
259.6K
Lines of Code
1.1K
Files
329
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 0HIGH 0MEDIUM 114LOW 215

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 329 distinct pattern matches across 10 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.

Modern AI Meta-Vocabulary76 hits · 244 pts
SeverityFileLineSnippetContext
MEDIUMtest/integration_scaffold_test.go24// scaffoldModuleURL returns the canonical scaffold-module source on theCOMMENT
MEDIUMtest/integration_scaffold_test.go222 templatePath := workingDir + "//fixtures/scaffold/with-shell-commands"CODE
MEDIUMtest/integration_scaffold_test.go250 templatePath := workingDir + "//fixtures/scaffold/with-shell-commands"CODE
MEDIUMtest/integration_scaffold_test.go277 templatePath := workingDir + "//fixtures/scaffold/with-hooks"CODE
MEDIUMtest/integration_scaffold_test.go302 templatePath := workingDir + "//fixtures/scaffold/with-hooks"CODE
MEDIUMtest/integration_scaffold_test.go327 templatePath := workingDir + "//fixtures/scaffold/with-shell-and-hooks"CODE
MEDIUMtest/integration_scaffold_test.go377 // Verify the pre-existing file was not modified by scaffold's formatting step.COMMENT
MEDIUMtest/integration_scaffold_test.go390 templatePath := workingDir + "//fixtures/scaffold/with-shell-and-hooks"CODE
MEDIUMtest/integration_scaffold_ssh_test.go21// sshScaffoldModuleURL is the SSH-form source for scaffold-moduleCOMMENT
MEDIUMtest/integration_scaffold_ssh_test.go26 return "git::" + m.SSHURL + "//test/fixtures/scaffold/scaffold-module"CODE
MEDIUMtest/integration_scaffold_ssh_test.go29// sshScaffoldTemplateModule is the SSH-form source for the scaffoldCOMMENT
MEDIUMtest/integration_scaffold_ssh_test.go34 return "git::" + m.SSHURL + "//test/fixtures/scaffold/module-with-template"CODE
MEDIUMtest/integration_scaffold_ssh_test.go38// scaffold external-template/template fixture, which it asks the serverCOMMENT
MEDIUMtest/integration_scaffold_ssh_test.go43 return "git::" + m.SSHURL + "//test/fixtures/scaffold/external-template/template"CODE
MEDIUMtest/integration_scaffold_ssh_test.go95// internal/cli/commands/scaffold/source_url_test.go, so thisCOMMENT
MEDIUMtest/integration_scaffold_ssh_test.go96// integration test now just verifies that scaffold runs end-to-endCOMMENT
MEDIUMtest/integration_scaffold_ssh_test.go147// scaffold's source_url_test; this test now just verifies theCOMMENT
MEDIUMtest/integration_scaffold_ssh_test.go148// var-file plumbing reaches scaffold and EnableRootInclude=falseCOMMENT
MEDIUMtest/helpers/git_server.go232// subpaths (e.g. "test/fixtures/scaffold/scaffold-module") andCOMMENT
MEDIUMtest/helpers/git_server.go245// branches at the new HEAD (so a `scaffold` source resolved to theCOMMENT
MEDIUMinternal/cli/flags/shared/scaffold.go18// NewScaffoldingFlags creates the flags shared between catalog and scaffold commands.COMMENT
MEDIUMinternal/cli/commands/commands.go88 scaffold.NewCommand(l, opts, v), // scaffoldCODE
MEDIUMinternal/cli/commands/catalog/tui/model_test.go184// the interactive scaffold key (`s`) on a copyable component transitionsCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/model_test.go221 // Lowercase s = interactive scaffold flow.COMMENT
MEDIUMinternal/cli/commands/catalog/tui/model_test.go518// TestModelScaffoldFailureQuitsWithError verifies that a failed scaffoldCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/update.go311 // Discard further input while the scaffold subprocess is running;COMMENT
MEDIUMinternal/cli/commands/catalog/tui/update.go366// ScaffoldFinishedMsg is delivered when a scaffold subprocess completes.COMMENT
MEDIUMinternal/cli/commands/catalog/tui/update.go390// scaffold or copy action. action is a verb phrase ("scaffolding component",COMMENT
MEDIUMinternal/cli/commands/catalog/tui/update.go524// scaffold run, pointing the user at the generated terragrunt.hcl. WhenCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/update.go601// and (for module/template) the prepared scaffold.Plan, or (for unit/stack)COMMENT
MEDIUMinternal/cli/commands/catalog/tui/update.go611// like a scaffold or copy failure: stash a styled message and quit.COMMENT
MEDIUMinternal/cli/commands/catalog/tui/update.go617// scaffold from.COMMENT
MEDIUMinternal/cli/commands/catalog/tui/update.go631// parsing variables via scaffold.Prepare; for unit/stack it means readingCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/update.go645// discoverModuleFields prepares the scaffold for a module/template andCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/update.go727// abandonForm releases any prepared scaffold.Plan and clears the formCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/keys.go77// interactive scaffold form; the placeholder-only flow is reachable fromCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/keys.go134 // Run the interactive scaffold flow (s).COMMENT
MEDIUMinternal/cli/commands/catalog/tui/copy.go46// directory tree into the user's working directory. Unlike scaffold, it doesCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/copy.go173// action mirrors how scaffold emits its output.COMMENT
MEDIUMinternal/cli/commands/catalog/tui/keys_test.go43 // The previous design split scaffold across `s` (validated) and `S`COMMENT
MEDIUMinternal/cli/commands/catalog/tui/keys_test.go108 // Pager mirrors the list: only the lowercase scaffold entry point;COMMENT
MEDIUMinternal/cli/commands/catalog/tui/scaffold.go15// via the scaffold package. When plan is non-nil the command takes theCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/scaffold.go32// WithPlan attaches a prepared scaffold.Plan and the user-supplied HCLCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/form.go187// scaffold.Plan.Generate or WriteValuesFile.COMMENT
MEDIUMinternal/cli/commands/catalog/tui/form.go243// pager state without performing the scaffold or copy.COMMENT
MEDIUMinternal/cli/commands/catalog/tui/form.go403// FieldsFromParsedVariables maps scaffold's variable representation ontoCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/model.go69 // work (e.g. scaffold.Prepare downloading sources) propagates theCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/model.go78 // and is handed down to the scaffold/copy/form-discovery leaves.COMMENT
MEDIUMinternal/cli/commands/catalog/tui/model.go84 // the pager and form so scaffold and "view source" know their targetCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/model.go88 // scaffold) matched while in the list view.COMMENT
MEDIUMinternal/cli/commands/catalog/tui/model.go105 // from scaffold-variable discovery.COMMENT
MEDIUMinternal/cli/commands/catalog/tui/model.go109 // or the scaffold is consumed.COMMENT
MEDIUMinternal/cli/commands/catalog/tui/model.go114 // terminalErr is the failure that ended the session (a scaffold, copy,COMMENT
MEDIUMinternal/cli/commands/catalog/tui/model.go123 // entrypoint, so scaffold and form-discovery leaves run against theCOMMENT
MEDIUMinternal/cli/commands/catalog/tui/model.go142 // State is the current view (list, pager, form, or scaffold).COMMENT
MEDIUMinternal/cli/commands/hcl/format/format.go148// This is used by scaffold to format only the files that were generated by boilerplate.COMMENT
MEDIUMinternal/cli/commands/scaffold/scaffold_test.go457 // Apply catalog config settings to options (simulating scaffold.Run behavior)COMMENT
MEDIUMinternal/cli/commands/scaffold/scaffold.go142// Plan captures the state of a scaffold preparation: the source module hasCOMMENT
MEDIUMinternal/cli/commands/scaffold/scaffold.go195 // scaffold only in empty directoriesCOMMENT
MEDIUMinternal/cli/commands/scaffold/scaffold.go290// Generate renders the prepared scaffold into the output directory. WhenCOMMENT
16 more matches not shown…
Over-Commented Block168 hits · 168 pts
SeverityFileLineSnippetContext
LOWtest/integration_aws_oidc_test.go181 )COMMENT
LOWtest/integration_run_test.go201// executes for each unit when both tofu and terraform are on PATH:COMMENT
LOWtest/integration_include_test.go301COMMENT
LOWtest/integration_regressions_test.go601 t.Logf("Output length: before cancel=%d, after cancel=%d, final=%d", len(outputBeforeCancel), len(outputAfterCancel), lCOMMENT
LOWtest/integration_regressions_test.go621// ├── module1/ <- Has dependency on bastionCOMMENT
LOWtest/integration_test.go1021// TestTerragruntFullLockfile asserts that a single `terragrunt init` (noCOMMENT
LOWtest/integration_runner_pool_test.go281 // Verify that source map values are usedCOMMENT
LOWtest/helpers/git_server.go61}COMMENT
LOWtest/helpers/git_server.go301COMMENT
LOWtest/helpers/git_server_ssh.go41COMMENT
LOWtest/helpers/git_server_ssh.go201COMMENT
LOWinternal/cas/gitstore.go21 // gitStoreLockTimeout bounds how long EnsureRef waits for the per-URLCOMMENT
LOWinternal/cas/gitstore.go121 }COMMENT
LOWinternal/cas/gitstore.go221 Err: git.ErrNoMatchingReference,COMMENT
LOWinternal/cas/telemetry.go21COMMENT
LOWinternal/cas/venv.go21// panic surfaces a test misconfiguration rather than a runtimeCOMMENT
LOWinternal/cas/local.go61// hashes in the synthetic tree, so blob lookups and tree lookups stay consistent.COMMENT
LOWinternal/cas/clone_e2e_test.go121COMMENT
LOWinternal/cas/cas.go41COMMENT
LOWinternal/cas/cas.go181COMMENT
LOWinternal/cas/cas.go661 if err := c.ensureBlob(ctx, v, runner, entry.Hash, gitFilePerm(entry.Mode)); err != nil {COMMENT
LOWinternal/cas/stacks.go61 ContentDir stringCOMMENT
LOWinternal/cas/stacks.go321 // avoid mutating the stored blob.COMMENT
LOWinternal/cas/stacks.go401COMMENT
LOWinternal/cas/source.go21// version identifier for a source. Callers fall back to downloading,COMMENT
LOWinternal/cas/source.go41COMMENT
LOWinternal/cas/source.go61 // Scheme is the URL scheme of URL ("s3", "gcs", "http"). Used inCOMMENT
LOWinternal/cas/source.go261 return LinkTree(ctx, v, c.blobStore, c.treeStore, tree, opts.Dir, linkOpts...)COMMENT
LOWinternal/cas/errors.go21 // ErrReadFile is returned when failing to read a fileCOMMENT
LOWinternal/cas/errors.go81 ErrFetchClosureRequired = errors.New("fetch closure is required")COMMENT
LOWinternal/getter/git.go21// wired with the default detector chain. GitGetter wraps an instance of thisCOMMENT
LOWinternal/getter/options.go41COMMENT
LOWinternal/getter/oci.go21// OCIRepositoryStore is the narrow seam between the OCI getter and theCOMMENT
LOWinternal/getter/tfr.go21const versionQueryKey = "version"COMMENT
LOWinternal/getter/tfr.go41// Authentication uses environment variables: TG_TF_REGISTRY_TOKEN supplies aCOMMENT
LOWinternal/getter/defaults.go181// and an optional set of extra headers. Pass nil for `extra` to get theCOMMENT
LOWinternal/getter/resolver.go1package getterCOMMENT
LOWinternal/getter/doc.go1// Package getter is Terragrunt's single integration point with theCOMMENT
LOWinternal/getter/resolver_tfr.go21// TFRResolver is a [cas.SourceResolver] for tfr:// URLs.COMMENT
LOWinternal/getter/resolver_s3.go41 // s3URLPathSegments is the count produced by splitting `/bucket/key`COMMENT
LOWinternal/getter/resolver_s3.go61// https://<bucket>.s3.amazonaws.com/<key> (global virtual-host)COMMENT
LOWinternal/getter/resolver_s3.go81COMMENT
LOWinternal/getter/casgetter.go41 //COMMENT
LOWinternal/getter/casgetter.go81COMMENT
LOWinternal/getter/casgetter.go221COMMENT
LOWinternal/getter/casgetter.go261//COMMENT
LOWinternal/getter/casgetter.go441 Fetch: g.buildInnerFetch(bare, scheme, innerURL),COMMENT
LOWinternal/vfs/vfs.go281}COMMENT
LOWinternal/vfs/vfs.go321 err := fastwalk.Walk(fwCfg, root, fn)COMMENT
LOWinternal/hclparse/autoinclude.go21// the first parsing pass extracts all unit/stack names and paths.COMMENT
LOWinternal/hclparse/autoinclude.go41// - dependency.config_path is resolved (references unit.*.path / values.*)COMMENT
LOWinternal/hclparse/autoinclude.go61COMMENT
LOWinternal/providercache/providercache.go61 //COMMENT
LOWinternal/providercache/providercache.go421// createLocalCLIConfig creates a local CLI config that merges the default/user configuration with our Provider Cache coCOMMENT
LOWinternal/providercache/providercache.go661COMMENT
LOWinternal/stacks/output/output.go41}COMMENT
LOWinternal/stacks/output/output.go61// parts of the infrastructure while maintaining awareness of the overall architecture.COMMENT
LOWinternal/stacks/output/output.go241// nestUnitOutputs transforms a flat map of unit outputs into a nested hierarchical structure.COMMENT
LOWinternal/util/jsons.go41// escapeInterpolationPatternsInValue recursively walks a value tree and escapesCOMMENT
LOWinternal/util/file.go601 return nilCOMMENT
108 more matches not shown…
Decorative Section Separators34 hits · 111 pts
SeverityFileLineSnippetContext
MEDIUMinternal/cli/commands/scaffold/scaffold.go74 # --------------------------------------------------------------------------------------------------------------------COMMENT
MEDIUMinternal/cli/commands/scaffold/scaffold.go76 # --------------------------------------------------------------------------------------------------------------------COMMENT
MEDIUMinternal/cli/commands/scaffold/scaffold.go94 # --------------------------------------------------------------------------------------------------------------------COMMENT
MEDIUMinternal/cli/commands/scaffold/scaffold.go97 # --------------------------------------------------------------------------------------------------------------------COMMENT
MEDIUMdocs/public/robots.txt5# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt7# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt11# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt13# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt56# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt62# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt76# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt86# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt128# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt132# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt140# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt143# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt148# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt150# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt193# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt196# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt201# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt203# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt36# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt42# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt112# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt117# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt226# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt228# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt266# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt268# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt324# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt327# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt344# ==============================================================COMMENT
MEDIUMdocs/public/robots.txt346# ==============================================================COMMENT
Verbosity Indicators15 hits · 30 pts
SeverityFileLineSnippetContext
LOWtest/integration_docs_test.go176 // Step 1: Generate the stackCOMMENT
LOWtest/integration_docs_test.go191 // Step 2: Apply the stack to create state filesCOMMENT
LOWtest/integration_docs_test.go216 // Step 3: Clean and regenerate the stackCOMMENT
LOWtest/integration_docs_test.go236 // Step 4: Verify that existing state is recognized after regenerationCOMMENT
LOWtest/integration_docs_test.go244 // Step 5: Destroy resources to clean upCOMMENT
LOWtest/integration_test.go4180 // Step 1: Create plan with custom name (no .tfplan extension)COMMENT
LOWtest/integration_test.go4187 // Step 2: Apply using the custom plan file nameCOMMENT
LOWinternal/queue/queue.go99 // If the entry is a "down" command, we need to check if all of its dependents are ready.COMMENT
LOWinternal/queue/queue_test.go922 // Step 1: Only C should be ready (it has no dependents)COMMENT
LOWinternal/queue/queue_test.go931 // Step 2: After C is destroyed, B should be ready (but NOT A yet, as A is a dependency of B)COMMENT
LOWinternal/queue/queue_test.go940 // Step 3: After B is destroyed, A should be readyCOMMENT
LOWinternal/queue/queue_test.go949 // Step 4: All entries should be finishedCOMMENT
LOWinternal/queue/queue_test.go982 // Step 1: Only C should be readyCOMMENT
LOWinternal/queue/queue_test.go997 // Step 2: B should now be ready even though C failedCOMMENT
LOWinternal/queue/queue_test.go1006 // Step 3: After B succeeds, A should be readyCOMMENT
Structural Annotation Overuse15 hits · 30 pts
SeverityFileLineSnippetContext
LOWtest/integration_docs_test.go176 // Step 1: Generate the stackCOMMENT
LOWtest/integration_docs_test.go191 // Step 2: Apply the stack to create state filesCOMMENT
LOWtest/integration_docs_test.go216 // Step 3: Clean and regenerate the stackCOMMENT
LOWtest/integration_docs_test.go236 // Step 4: Verify that existing state is recognized after regenerationCOMMENT
LOWtest/integration_docs_test.go244 // Step 5: Destroy resources to clean upCOMMENT
LOWtest/integration_test.go4180 // Step 1: Create plan with custom name (no .tfplan extension)COMMENT
LOWtest/integration_test.go4187 // Step 2: Apply using the custom plan file nameCOMMENT
LOWinternal/cli/flags/flag_opts.go44// NOTE: This function is currently unused but retained for future flag deprecation needs.COMMENT
LOWinternal/queue/queue_test.go922 // Step 1: Only C should be ready (it has no dependents)COMMENT
LOWinternal/queue/queue_test.go931 // Step 2: After C is destroyed, B should be ready (but NOT A yet, as A is a dependency of B)COMMENT
LOWinternal/queue/queue_test.go940 // Step 3: After B is destroyed, A should be readyCOMMENT
LOWinternal/queue/queue_test.go949 // Step 4: All entries should be finishedCOMMENT
LOWinternal/queue/queue_test.go982 // Step 1: Only C should be readyCOMMENT
LOWinternal/queue/queue_test.go997 // Step 2: B should now be ready even though C failedCOMMENT
LOWinternal/queue/queue_test.go1006 // Step 3: After B succeeds, A should be readyCOMMENT
AI Slop Vocabulary4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUMtest/integration_test.go918 // This makes the test more robust.COMMENT
MEDIUMinternal/util/datetime.go60 // be robust here.COMMENT
MEDIUMinternal/glob/glob_test.go251 // ElementsMatch ignores order, so the assertion is robust to walkerCOMMENT
MEDIUMpkg/config/dependency.go976 // To make parsing robust to either, isolate the first JSON object in the buffer.COMMENT
Hyper-Verbose Identifiers9 hits · 9 pts
SeverityFileLineSnippetContext
LOW…/src/components/vendored/starlight/rehype-file-tree.ts187function getFileIconTypeFromExtension(fileName: string) {CODE
LOW…/src/components/vendored/starlight/rehype-file-tree.ts240function throwFileTreeValidationError(message: string): never {CODE
LOWdocs/src/lib/changelog.ts277function transformAsidesToGitHubAlerts(input: string): string {CODE
LOWdocs/src/lib/page-to-markdown.ts93 .use(function improveExpressiveCodeHandling() {CODE
LOWdocs/src/lib/page-to-markdown.ts327export async function componentToSimpleMarkdown(CODE
LOWdocs/src/lib/commands/sidebar/index.ts28function organizeCommandsIntoGroups(flatCommandItems: (SidebarItem & { originalPath: string })[]): SidebarItem[] {CODE
LOWdocs/src/lib/commands/sidebar/index.ts59function insertCommandsIntoSidebar(CODE
LOWdocs/src/lib/commands/sidebar/index.ts95function expandAutogenerateDirectory(directory: string): SidebarItem[] {CODE
LOWdocs/src/lib/commands/sidebar/index.ts115function populateAutogeneratedSections(items: SidebarItem[]): SidebarItem[] {CODE
Redundant / Tautological Comments3 hits · 4 pts
SeverityFileLineSnippetContext
LOW.github/scripts/release/check-release-exists.sh20 # Check if release exists using gh CLI (only care about exit code)COMMENT
LOW.github/scripts/release/lib-release-config.sh79# Check if config file existsCOMMENT
LOW.github/scripts/release/verify-assets-uploaded.sh52 # Check if file exists in releaseCOMMENT
Fake / Example Data3 hits · 3 pts
SeverityFileLineSnippetContext
LOWtest/helpers/git_server_ssh.go226 {"config", "user.email", "test@test.com"},CODE
LOWtest/helpers/test_helpers.go98 cmd = exec.CommandContext(ctx, "git", "config", "user.email", "test@test.com")CODE
LOWinternal/cli/commands/hcl/validate/validate_test.go120 return vexec.Result{Stdout: []byte(`{"envs":{"AWS_ACCESS_KEY_ID":"fake-key"}}`)}CODE
Example Usage Blocks2 hits · 3 pts
SeverityFileLineSnippetContext
LOWinternal/cli/commands/info/strict/command.go2// Example usage:COMMENT
LOWdocs/tests/install_test.sh4# Usage:COMMENT