Repository Analysis

nicholas-fedor/watchtower

Automate Docker container image updates

4.4 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of nicholas-fedor/watchtower, a Go project with 4,016 GitHub stars. SynthScan v2.0 examined 114,077 lines of code across 370 source files, recording 363 pattern matches distributed across 8 syntactic categories. The overall adjusted score of 4.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).

4.4
Adjusted Score
4.4
Raw Score
100%
Time Factor
2026-07-14
Last Push
4.0K
Stars
Go
Language
114.1K
Lines of Code
370
Files
363
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 52LOW 311

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 363 distinct pattern matches across 8 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 Block286 hits · 285 pts
SeverityFileLineSnippetContext
LOWmain.go1// @title Watchtower HTTP APICOMMENT
LOWmain.go21// @tag.name healthCOMMENT
LOWcmd/notify-upgrade.go61// - _: A slice of strings representing positional arguments, unused here as the command accepts no arguments (enforceCOMMENT
LOWcmd/doc.go1// Package cmd contains the command-line interface (CLI) definitions and execution logic for Watchtower.COMMENT
LOWcmd/root.go41 client container.ClientCOMMENT
LOWcmd/root.go61COMMENT
LOWcmd/root.go81 //COMMENT
LOWcmd/root.go101 // When set, only containers whose image matches one of these patterns are monitored.COMMENT
LOWcmd/root.go121 // timeout specifies the maximum duration allowed for container stop operations during updates.COMMENT
LOWcmd/root.go141 // It is configured in preRun via the --rolling-restart flag or the WATCHTOWER_ROLLING_RESTART environment variable,COMMENT
LOWcmd/root.go161 scope stringCOMMENT
LOWcmd/root.go181 // notificationSplitByContainer is a boolean flag enabling separate notifications for each updated container.COMMENT
LOWcmd/root.go201 // When true, Watchtower uses a short-lived orchestrator container to perform the self-updateCOMMENT
LOWcmd/root.go221 // It is initialized to time.Sleep by default, providing a way to mock sleep behavior during testingCOMMENT
LOWcmd/root.go521 // Set up the notification system with types specified via flags (e.g., email, Slack).COMMENT
LOWcmd/root.go721// It validates the environment, performs one-time updates if specified,COMMENT
LOWcmd/root.go741COMMENT
LOWinternal/metrics/doc.go1// Package metrics provides tracking and exposure of Watchtower scan metrics.COMMENT
LOWinternal/flags/flags.go681// markFlagDeprecated marks a pflag as deprecated with a migration hint.COMMENT
LOWinternal/flags/flags.go721COMMENT
LOWinternal/flags/flags.go1041 }).Debug("Configured Docker environment variables")COMMENT
LOWinternal/flags/flags.go1481//COMMENT
LOWinternal/flags/doc.go1// Package flags manages command-line flags and environment variables for Watchtower configuration.COMMENT
LOWinternal/util/util.go81//COMMENT
LOWinternal/util/util.go201COMMENT
LOWinternal/util/util.go261// Returns:COMMENT
LOWinternal/util/util.go321}COMMENT
LOWinternal/util/doc.go1// Package util provides utility functions for Watchtower operations.COMMENT
LOWinternal/scheduling/scheduling.go61// Parameters:COMMENT
LOWinternal/scheduling/scheduling.go281 }COMMENT
LOWinternal/actions/ephemeral.go41 // errOrchestratorCreateFailed indicates a failure to create the new container.COMMENT
LOWinternal/actions/ephemeral.go61// This function returns immediately after starting the orchestrator. TheCOMMENT
LOWinternal/actions/ephemeral.go161 //COMMENT
LOWinternal/actions/ephemeral.go181// 2. INSPECT: Get the old container's full configurationCOMMENT
LOWinternal/actions/ephemeral.go281COMMENT
LOWinternal/actions/ephemeral.go361 // after the source Watchtower process is stopped by the orchestrator.COMMENT
LOWinternal/actions/ephemeral.go441// name for the new one. If StopContainer returns NotFound, removal is skippedCOMMENT
LOWinternal/actions/ephemeral.go561 clog.WithError(err).Error("Failed to create and start new container")COMMENT
LOWinternal/actions/update.go581 "container",COMMENT
LOWinternal/actions/update.go701 logrus.WithField(COMMENT
LOWinternal/actions/update.go761}COMMENT
LOWinternal/actions/update.go1061COMMENT
LOWinternal/actions/update.go1181// Uses the container name with ":latest" as the fallback image.COMMENT
LOWinternal/actions/update.go1341// It stops each container, tracking stopped images and errors, to prepare for restarts whileCOMMENT
LOWinternal/actions/update.go1421//COMMENT
LOWinternal/actions/update.go1521}COMMENT
LOWinternal/actions/update.go1681COMMENT
LOWinternal/actions/cleanup.go21COMMENT
LOWinternal/actions/cleanup.go101 return removed, errCOMMENT
LOWinternal/actions/cleanup.go381 "excess_containers_found": len(excessContainers),COMMENT
LOWinternal/actions/cleanup.go521 for _, c := range containersToRemoveMap {COMMENT
LOWinternal/actions/cleanup.go681//COMMENT
LOWinternal/actions/actions.go61 SkipSelfUpdate bool // Skip Watchtower self-updateCOMMENT
LOWinternal/actions/actions.go241func (emptyReport) All() []types.ContainerReport { return nil }COMMENT
LOWinternal/actions/actions.go281 Failed: 0,COMMENT
LOWinternal/actions/actions.go381//COMMENT
LOWinternal/actions/actions.go481//COMMENT
LOWinternal/actions/actions.go521}COMMENT
LOWinternal/actions/actions.go621 "failed": len(result.Failed()),COMMENT
LOWinternal/actions/actions.go661COMMENT
226 more matches not shown…
Decorative Section Separators40 hits · 139 pts
SeverityFileLineSnippetContext
MEDIUMcliff.toml9# ──────────────────────────────────────────────────────────────COMMENT
MEDIUMcliff.toml12# ──────────────────────────────────────────────────────────────COMMENT
MEDIUMcliff.toml23# ──────────────────────────────────────────────────────────────STRING
MEDIUMcliff.toml26# ──────────────────────────────────────────────────────────────STRING
MEDIUMcliff.toml61# ──────────────────────────────────────────────────────────────STRING
MEDIUMcliff.toml64# ──────────────────────────────────────────────────────────────STRING
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh6# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh8# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh15# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh17# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh23# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh25# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh30# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh32# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh38# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh40# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh70# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh72# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh76# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh78# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh95# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh97# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh115# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh117# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh123# ------------------------------------------------------------------COMMENT
MEDIUMexamples/lifecycle-hooks/synology-stop/synology-stop.sh125# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh7# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh9# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh44# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh46# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh70# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh72# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh116# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh118# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh148# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh150# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh180# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh182# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh221# ------------------------------------------------------------------COMMENT
MEDIUM…lifecycle-hooks/synology-stop/test_synology_parsing.sh223# ------------------------------------------------------------------COMMENT
AI Slop Vocabulary10 hits · 30 pts
SeverityFileLineSnippetContext
MEDIUMpkg/registry/auth/auth_test.go1358 // required fields (e.g., service). Ensures robust error handling for malformed inputs.COMMENT
MEDIUMpkg/registry/auth/auth_fuzz_test.go18// with malformed authentication challenge strings. It ensures robust parsing of WWW-Authenticate headersCOMMENT
MEDIUMpkg/registry/auth/auth_fuzz_test.go100// FuzzGetBearerHeader fuzzes the JSON unmarshaling in GetBearerHeader to ensure robust parsingCOMMENT
MEDIUMpkg/registry/auth/auth_fuzz_test.go156// with various base64-encoded inputs. It ensures robust decoding and unmarshaling of JSON credentials,COMMENT
MEDIUMpkg/registry/auth/auth_fuzz_test.go188// with malformed authentication challenge strings. It ensures robust URL construction fromCOMMENT
MEDIUMpkg/registry/digest/digest_integration_fuzz_test.go84// FuzzDigestsMatch fuzzes the digestsMatch function to ensure robust handling of malformed inputs.COMMENT
MEDIUMpkg/registry/digest/digest_integration_fuzz_test.go119// FuzzBuildManifestURL fuzzes the buildManifestURL function to ensure robust URL construction.COMMENT
MEDIUMpkg/registry/manifest/manifest_fuzz_test.go16// to ensure robust parsing. It tests valid references, malformed strings, and edge cases to preventCOMMENT
MEDIUMpkg/notifications/shoutrrr_fuzz_test.go8// FuzzGetShoutrrrTemplate fuzzes the getShoutrrrTemplate function to ensure robust parsing of template strings.COMMENT
MEDIUMpkg/notifications/shoutrrr_fuzz_test.go26// FuzzSanitizeURLForLogging fuzzes the sanitizeURLForLogging function to ensure robust URL parsing.COMMENT
Example Usage Blocks13 hits · 20 pts
SeverityFileLineSnippetContext
LOWinternal/metrics/doc.go8// Usage example:COMMENT
LOWinternal/flags/doc.go10// Usage example:COMMENT
LOWinternal/util/doc.go13// Usage example:COMMENT
LOWinternal/actions/doc.go12// Usage example:COMMENT
LOWpkg/filters/doc.go8// Usage example:COMMENT
LOWpkg/types/doc.go13// Usage example:COMMENT
LOWpkg/sorter/doc.go9// Usage example:COMMENT
LOWpkg/compose/doc.go11// Usage example:COMMENT
LOWpkg/lifecycle/doc.go8// Usage example:COMMENT
LOWpkg/container/doc.go12// Usage example:COMMENT
LOWpkg/registry/doc.go12// Usage example:COMMENT
LOWpkg/notifications/doc.go15// Usage example:COMMENT
LOWpkg/session/doc.go11// Usage example:COMMENT
Structural Annotation Overuse7 hits · 12 pts
SeverityFileLineSnippetContext
LOWdocs/http-api/configuration/tls/index.md27### Step 1: Obtain a Certificate and Private KeyCOMMENT
LOWdocs/http-api/configuration/tls/index.md59### Step 2: Prepare Files for the ContainerCOMMENT
LOWdocs/http-api/configuration/tls/index.md70### Step 3: Mount and Configure WatchtowerCOMMENT
LOWdocs/http-api/configuration/tls/index.md110### Step 4: Connect Using HTTPSCOMMENT
LOWpkg/container/cycles.go70 // Step 1: Mark node as visiting (gray) and add to current exploration pathCOMMENT
LOWpkg/container/cycles.go76 // Step 2: Explore all dependencies (neighbors) of this nodeCOMMENT
LOWpkg/container/cycles.go109 // Step 3: Backtrack - remove node from current path and mark as fully visited (black)COMMENT
Self-Referential Comments2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMscripts/docker-util.sh2# This file is meant to be sourced into other scripts and contain some utility functions for docker e2e testingCOMMENT
MEDIUM.circleci/continue-config.yml14# Define a job to be invoked later in a workflow.COMMENT
Verbosity Indicators3 hits · 6 pts
SeverityFileLineSnippetContext
LOWpkg/container/cycles.go70 // Step 1: Mark node as visiting (gray) and add to current exploration pathCOMMENT
LOWpkg/container/cycles.go76 // Step 2: Explore all dependencies (neighbors) of this nodeCOMMENT
LOWpkg/container/cycles.go109 // Step 3: Backtrack - remove node from current path and mark as fully visited (black)COMMENT
Redundant / Tautological Comments2 hits · 3 pts
SeverityFileLineSnippetContext
LOWtest/scripts/test_tls_integration.sh52# Check if certs existCOMMENT
LOW.github/workflows/release-nightly.yaml69 # Check if there are any changes in the watched paths since last successful nightly runCOMMENT