Repository Analysis

encoredev/encore

The infrastructure platform for the intelligence era

2.9 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of encoredev/encore, a Go project with 12,155 GitHub stars. SynthScan v2.0 examined 344,715 lines of code across 1859 source files, recording 522 pattern matches distributed across 13 syntactic categories. The overall adjusted score of 2.9 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.9
Adjusted Score
2.9
Raw Score
100%
Time Factor
2026-07-14
Last Push
12.2K
Stars
Go
Language
344.7K
Lines of Code
1.9K
Files
522
Pattern Hits
2026-07-14
Scan Date
0.01
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

Longitudinal tracking requires multiple scan runs. Once this repository is re-scanned after new commits land, this chart will visualise how the synthetic code signal evolves over time — enabling you to detect whether AI authorship is growing, stabilising, or being actively corrected by human engineers.

No multi-scan history yet — run the scanner again to build trend data.

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 10HIGH 2MEDIUM 171LOW 339

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 522 distinct pattern matches across 13 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.

Decorative Section Separators162 hits · 489 pts
SeverityFileLineSnippetContext
MEDIUMminiredis/tests/cmd_resp3.rs6// ── Helper: raw TCP connection for RESP3 wire format tests ──────────COMMENT
MEDIUMminiredis/tests/cmd_resp3.rs30// ── HELLO command tests ─────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_resp3.rs97// ── HGETALL RESP3 map ───────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_resp3.rs147// ── SMEMBERS RESP3 set ──────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_resp3.rs186// ── Commands still work after HELLO 3 ───────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_resp3.rs228// ── HELLO with AUTH ─────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_resp3.rs251// ── Via redis-rs client ─────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_misc.rs4// ── QUIT ────────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_misc.rs14// ── COMMAND ─────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_misc.rs30// ── INFO ────────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_misc.rs100// ── CLIENT SETNAME/GETNAME ──────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_misc.rs143// ── CLUSTER ─────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_misc.rs224// ── OBJECT IDLETIME ─────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_auth.rs4// ── AUTH ──────────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_auth.rs68// ── HELLO ────────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_tls.rs53// ── Tests ───────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs3// ── String operations ────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs28// ── Key management ───────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs75// ── List operations ──────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs106// ── Set operations ───────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs134// ── Hash operations ──────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs158// ── Sorted set operations ────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs177// ── Stream operations ────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs187// ── HyperLogLog operations ──────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs197// ── TTL operations ───────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs209// ── Select DB ────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs222// ── Connection counting ──────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs247// ── Fast forward ─────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs265// ── Auth ─────────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs280// ── DB() access ─────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs305// ── Restart ─────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/direct_api.rs336// ── Dump ────────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_pubsub.rs4// ── PUBLISH (through regular dispatch) ──────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_pubsub.rs23// ── PUBSUB CHANNELS/NUMSUB/NUMPAT (through regular dispatch) ───────COMMENT
MEDIUMminiredis/tests/cmd_pubsub.rs64// ── SUBSCRIBE + PUBLISH via redis-rs PubSub API ────────────────────COMMENT
MEDIUMminiredis/tests/cmd_pubsub.rs268// ── Direct API ──────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_hll.rs4// ── PFADD ────────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_hll.rs32// ── PFCOUNT ──────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_hll.rs94// ── PFMERGE ──────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_hll.rs173// ── DEL interaction ──────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_transactions.rs4// ── Error cases ──────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_transactions.rs32// ── Basic MULTI / EXEC ──────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_transactions.rs115// ── DISCARD ──────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_transactions.rs141// ── WATCH ────────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_transactions.rs215// ── UNWATCH ──────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_transactions.rs250// ── Transaction with pipe().atomic() ─────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_transactions.rs275// ── MULTI with unknown command → EXECABORT ───────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_transactions.rs311// ── EVAL/EVALSHA inside MULTI/EXEC ───────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_scripting.rs4// ── EVAL basic ───────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_scripting.rs54// ── KEYS and ARGV ────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_scripting.rs72// ── redis.call() ─────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_scripting.rs117// ── redis.pcall() ────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_scripting.rs162// ── redis.error_reply() / redis.status_reply() ──────────────────────COMMENT
MEDIUMminiredis/tests/cmd_scripting.rs178// ── redis.sha1hex() ──────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_scripting.rs188// ── EVALSHA ──────────────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_scripting.rs215// ── SCRIPT LOAD / EXISTS / FLUSH ─────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_scripting.rs288// ── Error handling ───────────────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_scripting.rs324// ── Script using various data types ──────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_scripting.rs349// ── SCRIPT subcommand errors ─────────────────────────────────────────COMMENT
MEDIUMminiredis/tests/cmd_scripting.rs361// ── EVAL_RO / EVALSHA_RO ─────────────────────────────────────────────COMMENT
102 more matches not shown…
Over-Commented Block270 hits · 270 pts
SeverityFileLineSnippetContext
LOW.reviewdog.yml1# Encore's reviewdog configuration file.COMMENT
LOWcheck.bash1#!/usr/bin/env bashCOMMENT
LOWtsparser/txtar/src/lib.rs1//! `txtar` is a rust implementation of the `txtar` Go package.COMMENT
LOWtsparser/txtar/src/lib.rs21//! The format spec as written in the `txtar` Go package source code:COMMENT
LOWtsparser/txtar/src/lib.rs41//! ```rust no_runCOMMENT
LOWruntimes/go/package.go1// Package encore provides the runtime API contract, which Encore applications are build against.COMMENT
LOWruntimes/go/package.go21// # Package encoreCOMMENT
LOWruntimes/go/pkgfn.go21//COMMENT
LOWruntimes/go/request.go61 // and callee are both running within the same process.COMMENT
LOWruntimes/go/meta.go121 // EnvEphemeral represents short-lived cloud-hosted, non-production environments, such as preview environmentsCOMMENT
LOWruntimes/go/beta/errs/error.go21 ValidateJsonRawMessage: true,COMMENT
LOWruntimes/go/beta/errs/codes.go1package errsCOMMENT
LOWruntimes/go/beta/errs/codes.go21 // Encore will generate this error code in the above two mentioned cases.COMMENT
LOWruntimes/go/beta/errs/codes.go41 // NotFound means some requested entity (e.g., file or directory) wasCOMMENT
LOWruntimes/go/beta/errs/codes.go61 PermissionDenied ErrCode = 7COMMENT
LOWruntimes/go/beta/errs/codes.go81 // the system state has been explicitly fixed. E.g., if an "rmdir"COMMENT
LOWruntimes/go/beta/errs/codes.go101 // OutOfRange means operation was attempted past the valid range.COMMENT
LOWruntimes/go/beta/errs/codes.go121 // supported/enabled in this service.COMMENT
LOWruntimes/go/beta/errs/codes.go141 // Encore will generate this error code in aubrupt shutdown of a server processCOMMENT
LOWruntimes/go/middleware/middleware.go1// Package middleware provides middleware functionality for definingCOMMENT
LOWruntimes/go/middleware/middleware.go21// function is used to invoke the next middleware in theCOMMENT
LOWruntimes/go/middleware/middleware.go61// Response represents the API handler's response.COMMENT
LOWruntimes/go/middleware/middleware.go81 // Err is the error returned from the API handler or another middleware.COMMENT
LOWruntimes/go/types/uuid/uuid_test.go1// Copyright (C) 2013-2018 by Maxim Bublis <b@codemonkey.ru>COMMENT
LOWruntimes/go/types/uuid/sql_test.go1// Copyright (C) 2013-2018 by Maxim Bublis <b@codemonkey.ru>COMMENT
LOWruntimes/go/types/uuid/codec_test.go1// Copyright (C) 2013-2018 by Maxim Bublis <b@codemonkey.ru>COMMENT
LOWruntimes/go/types/uuid/generator.go1// Copyright (C) 2013-2018 by Maxim Bublis <b@codemonkey.ru>COMMENT
LOWruntimes/go/types/uuid/generator.go61COMMENT
LOWruntimes/go/types/uuid/uuid.go1// Copyright (C) 2013-2018 by Maxim Bublis <b@codemonkey.ru>COMMENT
LOWruntimes/go/types/uuid/fuzz.go1// Copyright (c) 2018 Andrei Tudor Călin <mail@acln.ro>COMMENT
LOWruntimes/go/types/uuid/fuzz.go21COMMENT
LOWruntimes/go/types/uuid/codec.go1// Copyright (C) 2013-2018 by Maxim Bublis <b@codemonkey.ru>COMMENT
LOWruntimes/go/types/uuid/codec.go61 return NilCOMMENT
LOWruntimes/go/types/uuid/codec.go81//COMMENT
LOWruntimes/go/types/uuid/generator_test.go1// Copyright (C) 2013-2018 by Maxim Bublis <b@codemonkey.ru>COMMENT
LOWruntimes/go/types/uuid/sql.go1// Copyright (C) 2013-2018 by Maxim Bublis <b@codemonkey.ru>COMMENT
LOWruntimes/go/shutdown/shutdown.go1package shutdownCOMMENT
LOWruntimes/go/shutdown/shutdown.go21// is reached, whichever happens first. The OutstandingRequests, OutstandingPubSubMessages, andCOMMENT
LOWruntimes/go/shutdown/shutdown.go41COMMENT
LOWruntimes/go/shutdown/shutdown.go61 //COMMENT
LOWruntimes/go/shutdown/shutdown.go81 // <-p.OutstandingRequests.Done()COMMENT
LOWruntimes/go/config/pkgfn.go21// Load returns the fully loaded configuration for this service.COMMENT
LOWruntimes/go/storage/cache/list.go41// The primary use case is for overriding the expiration time for certain cache operations.COMMENT
LOWruntimes/go/storage/cache/list.go61// PushLeft pushes one or more values at the head of the list stored at key.COMMENT
LOWruntimes/go/storage/cache/list.go81COMMENT
LOWruntimes/go/storage/cache/list.go261// If the key does not exist it returns an empty list.COMMENT
LOWruntimes/go/storage/cache/cache.go21 // If not specified the cache defaults to AllKeysLRU.COMMENT
LOWruntimes/go/storage/cache/cache.go81 // cache key pattern for this keyspace.COMMENT
LOWruntimes/go/storage/cache/basic.go41// For each key, the result contains an Err field indicating success or failure.COMMENT
LOWruntimes/go/storage/cache/basic.go81// GetAndDelete deletes the key and returns the previously stored value.COMMENT
LOWruntimes/go/storage/cache/basic.go101// The primary use case is for overriding the expiration time for certain cache operations.COMMENT
LOWruntimes/go/storage/cache/basic.go261// If the key already exists, it reports an error matching KeyExists.COMMENT
LOWruntimes/go/storage/cache/basic.go281 return s.basicKeyspace.GetAndSet(ctx, key, val)COMMENT
LOWruntimes/go/storage/cache/basic.go381// myKeyspace.With(cache.ExpireIn(3 * time.Second)).Set(...)COMMENT
LOWruntimes/go/storage/cache/basic.go441}COMMENT
LOWruntimes/go/storage/cache/struct.go61COMMENT
LOWruntimes/go/storage/cache/struct.go101// Delete deletes the specified keys.COMMENT
LOWruntimes/go/storage/cache/set.go41COMMENT
LOWruntimes/go/storage/cache/set.go241//COMMENT
LOWruntimes/go/storage/objects/path_escape.go81// Return true if the specified character should be escaped whenCOMMENT
210 more matches not shown…
Hallucination Indicators10 hits · 100 pts
SeverityFileLineSnippetContext
CRITICALv2/parser/apis/middleware/middleware.go40 return mw.Decl.File.Pkg.ImportPath.String() + "." + mw.Decl.NameCODE
CRITICALv2/parser/apis/middleware/middleware.go48 return mw.Decl.File.Pkg.ImportPath.String() + "." + mw.Decl.NameCODE
CRITICALv2/parser/apis/authhandler/authhandler.go40func (ah *AuthHandler) SortKey() string { return ah.Decl.File.Pkg.ImportPath.String() + "." + ah.Name }CODE
CRITICALv2/parser/apis/servicestruct/servicestruct.go34 return ss.Decl.File.Pkg.ImportPath.String() + "." + ss.Decl.NameCODE
CRITICALv2/codegen/apigen/authhandlergen/authhandlergen.go140 fnExpr = Qual(ah.Decl.File.Pkg.ImportPath.String(), ah.Name)CODE
CRITICALv2/codegen/apigen/maingen/maingen.go76 f.Anon(ah.Decl.File.Pkg.ImportPath.String())CODE
CRITICALv2/codegen/apigen/maingen/maingen.go80 f.Anon(mw.Decl.File.Pkg.ImportPath.String())CODE
CRITICALv2/codegen/apigen/maingen/maingen.go117 f.Anon(ah.Decl.File.Pkg.ImportPath.String())CODE
CRITICALv2/codegen/apigen/maingen/maingen.go120 f.Anon(mw.Decl.File.Pkg.ImportPath.String())CODE
CRITICALv2/internals/schema/schemautil/schemautil.go387 buf.WriteString(t.DeclInfo.File.Pkg.ImportPath.String())CODE
Structural Annotation Overuse36 hits · 58 pts
SeverityFileLineSnippetContext
LOWcheck.bash30# Step 0: Setup the script with basic error handling COMMENT
LOWcheck.bash46# Step 1: Configure the script with the parameters the use wants COMMENT
LOWcheck.bash83# Step 2: Check for required tools and error out if anything is missing which we can't install for the user COMMENT
LOWcheck.bash100# Step 3: Create a diff of the changes in the working directory against the common ancestor of the current branch and maCOMMENT
LOWcheck.bash182# Step 4: Run review dog using the diff we just created, allowing reviewdog to only show errors from changes we've made COMMENT
LOWdocs/go/self-host/deploy-to-digital-ocean-wip.md16### Step 1: Create an Encore AppCOMMENT
LOWdocs/go/self-host/deploy-to-digital-ocean-wip.md31### Step 2: Push the Docker Image to a Container RegistryCOMMENT
LOWdocs/go/self-host/deploy-to-digital-ocean-wip.md57### Step 3: Deploy the Docker Image to DigitalOcean App PlatformCOMMENT
LOWdocs/go/self-host/deploy-to-digital-ocean-wip.md77### Step 4: Monitor and Manage the AppCOMMENT
LOWdocs/go/self-host/deploy-to-digital-ocean-wip.md92### Step 5: Add a Database to Your AppCOMMENT
LOWdocs/go/tutorials/incident-management-tool.md780# Step 1: Create a User and copy the User ID to your clipboardCOMMENT
LOWdocs/go/tutorials/incident-management-tool.md787# Step 2: Create a schedule for the user we just createdCOMMENT
LOWdocs/go/tutorials/incident-management-tool.md793# Step 3: Trigger an incidentCOMMENT
LOWdocs/go/tutorials/incident-management-tool.md798# Step 4: Acknowledge the IncidentCOMMENT
LOWdocs/platform/deploy/deploying.md13### Step 1: Create account & applicationCOMMENT
LOWdocs/platform/deploy/deploying.md53### Step 2: Integrate with GitHub (Optional)COMMENT
LOWdocs/platform/deploy/deploying.md68### Step 3: Connect your AWS / GCP account (Optional)COMMENT
LOWdocs/platform/deploy/deploying.md80### Step 4: Push to deployCOMMENT
LOWdocs/platform/integrations/auth-keys.md32### Step 1: Generate an auth keyCOMMENT
LOWdocs/platform/integrations/auth-keys.md46### Step 2: Authenticate with the auth keyCOMMENT
LOWdocs/ts/self-host/deploy-to-digital-ocean.md19### Step 1: Create an Encore AppCOMMENT
LOWdocs/ts/self-host/deploy-to-digital-ocean.md34### Step 2: Push the Docker Image to a Container RegistryCOMMENT
LOWdocs/ts/self-host/deploy-to-digital-ocean.md60### Step 3: Deploy the Docker Image to DigitalOcean App PlatformCOMMENT
LOWdocs/ts/self-host/deploy-to-digital-ocean.md80### Step 4: Monitor and Manage the AppCOMMENT
LOWdocs/ts/self-host/deploy-to-digital-ocean.md95### Step 5: Add a Database to Your AppCOMMENT
LOWdocs/ts/self-host/deploy-to-railway.md15### Step 1: Create an Encore App and a GitHub repositoryCOMMENT
LOWdocs/ts/self-host/deploy-to-railway.md27### Step 2: Push the Docker Image to GitHub's Container RegistryCOMMENT
LOWdocs/ts/self-host/deploy-to-railway.md83### Step 3: Deploy the Docker Image to RailwayCOMMENT
LOWdocs/ts/self-host/deploy-to-railway.md110### Step 4: Automate the Deployment ProcessCOMMENT
LOWdocs/ts/self-host/deploy-to-railway.md177### Step 5: Add a Database to Your AppCOMMENT
LOWdocs/ts/develop/auth.md103#### Step 1: Determining if the request is authenticatedCOMMENT
LOWdocs/ts/develop/auth.md122#### Step 2: Calling the endpoint, if permissibleCOMMENT
LOWpkg/make-release/dist_builder.go195 // Step 1: Find out the latest release version for Encore's Go distributionCOMMENT
LOWpkg/encorebuild/dist_builder.go139 // Step 1: Find out the latest release version for Encore's Go distributionCOMMENT
LOWpkg/idents/identifiers.go23 // Step 1: convert caseCOMMENT
LOWpkg/idents/identifiers.go44 // Step 2: Join PartsCOMMENT
Fake / Example Data19 hits · 30 pts
SeverityFileLineSnippetContext
LOWruntimes/js/encore.dev/pubsub/mod.ts27 * name: "John Doe",COMMENT
LOWdocs/ts/develop/integrations/resend.md157 to: "user@example.com",CODE
LOWcli/internal/dedent/dedent_test.go151 Lorem ipsum dolor sit amet,CODE
LOWcli/internal/dedent/dedent_test.go151 Lorem ipsum dolor sit amet,CODE
LOWcli/internal/dedent/dedent_test.go159 // Lorem ipsum dolor sit amet,COMMENT
LOWcli/internal/dedent/dedent_test.go159 // Lorem ipsum dolor sit amet,COMMENT
LOWcli/internal/dedent/dedent_test.go165 // Lorem ipsum dolor sit amet,COMMENT
LOWcli/internal/dedent/dedent_test.go165 // Lorem ipsum dolor sit amet,COMMENT
LOWcli/internal/dedent/dedent_test.go173 Dedent(`Lorem ipsum dolor sit amet, consectetur adipiscing elit.CODE
LOWcli/internal/dedent/dedent_test.go173 Dedent(`Lorem ipsum dolor sit amet, consectetur adipiscing elit.CODE
LOWcli/daemon/dash/ai/types_test.go14 {1, "Lorem ipsum dolor sit amet"},CODE
LOWcli/daemon/dash/ai/types_test.go14 {1, "Lorem ipsum dolor sit amet"},CODE
LOWcli/daemon/dash/ai/types_test.go15 {80, "Lorem ipsum dolor sit amet"},CODE
LOWcli/daemon/dash/ai/types_test.go15 {80, "Lorem ipsum dolor sit amet"},CODE
LOWcli/daemon/dash/ai/types_test.go16 {80, "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore maCODE
LOWcli/daemon/dash/ai/types_test.go16 {80, "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore maCODE
LOW…ests/testdata/testscript/et_override_user_authdata.txt90 return "hello", &AuthData{Email: "hello@example.org"}, nilCODE
LOWpkg/errinsrc/srcrender_test.go25 {testName: "multiline message", line: 1, column: 9, level: LocError, message: "Lorem ipsum dolor sit amet, consecteturCODE
LOWpkg/errinsrc/srcrender_test.go25 {testName: "multiline message", line: 1, column: 9, level: LocError, message: "Lorem ipsum dolor sit amet, consecteturCODE
Self-Referential Comments5 hits · 20 pts
SeverityFileLineSnippetContext
MEDIUMcheck.bash108 # Create a temp directory to store the common ancestor commitCOMMENT
MEDIUMcheck.bash115 # Create a temp file to store the diff we needCOMMENT
MEDIUMcheck.bash122 # Create a blank file to use as a comparison when a file is missing because either it's new or been deletedCOMMENT
MEDIUMcheck.bash147 # Create a list of files that we care aboutCOMMENT
MEDIUMcheck.bash152 # Create a diff of the changes in the working directory against the common ancestor of the current branch and mainCOMMENT
Verbosity Indicators12 hits · 18 pts
SeverityFileLineSnippetContext
LOWcheck.bash30# Step 0: Setup the script with basic error handling COMMENT
LOWcheck.bash46# Step 1: Configure the script with the parameters the use wants COMMENT
LOWcheck.bash83# Step 2: Check for required tools and error out if anything is missing which we can't install for the user COMMENT
LOWcheck.bash100# Step 3: Create a diff of the changes in the working directory against the common ancestor of the current branch and maCOMMENT
LOWcheck.bash182# Step 4: Run review dog using the diff we just created, allowing reviewdog to only show errors from changes we've made COMMENT
LOWtsparser/src/parser/parser.rs530 // For this case we need to check if the path is a subdirectory of the service root.COMMENT
LOWruntimes/go/appruntime/apisdk/api/handler.go476 // If we're inside a test, we need to check if the target service has been mockedCOMMENT
LOWv2/codegen/apigen/apigenutil/apigenutil.go180 g.Comment(fmt.Sprintf("%s is set to omitempty, so we need to check if it's empty before writing it", p.SrcName))CODE
LOWpkg/make-release/dist_builder.go195 // Step 1: Find out the latest release version for Encore's Go distributionCOMMENT
LOWpkg/encorebuild/dist_builder.go139 // Step 1: Find out the latest release version for Encore's Go distributionCOMMENT
LOWpkg/idents/identifiers.go23 // Step 1: convert caseCOMMENT
LOWpkg/idents/identifiers.go44 // Step 2: Join PartsCOMMENT
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMtsparser/src/parser/resources/infra/cron.rs120 // TODO introduce more robust validation and error reporting here.COMMENT
MEDIUMv2/internals/schema/schemautil/schemautil.go183// To be more robust in the presence of typing errors it supports partial application,COMMENT
Modern AI Meta-Vocabulary2 hits · 5 pts
SeverityFileLineSnippetContext
MEDIUMREADME.md118encore app create # scaffold a projectCODE
MEDIUMdocs/platform/other/vs-supabase.md75## Encore makes it simple to build type-safe event-driven systemsCOMMENT
Magic Placeholder Names1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHdocs/platform/cloud-mcp.md58 --header "Authorization: Bearer <your-api-key>"CODE
Synthetic Comment Markers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHdocs/platform/ai-integration.md11When you connect your cloud account to [Encore Cloud](https://encore.dev), AI-generated code that declares databases, puCODE
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWcheck.bash7# Usage:COMMENT
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOW.github/dockerimg/rename-binary-if-needed.bash4# Check if `encore-nightly`, `encore-beta` or `encore-develop` are present, and if one of them are, rename it to `encoreCOMMENT