Repository Analysis

shakacode/react-webpack-rails-tutorial

Legacy full-app React on Rails tutorial repo and live demo. See reactonrails.com/examples for current maintained demos.

8.2 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of shakacode/react-webpack-rails-tutorial, a JavaScript project with 1,719 GitHub stars. SynthScan v2.0 examined 14,269 lines of code across 232 source files, recording 81 pattern matches distributed across 8 syntactic categories. The overall adjusted score of 8.2 places this repository in the Low AI signal 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).

8.2
Adjusted Score
8.2
Raw Score
100%
Time Factor
2026-07-14
Last Push
1.7K
Stars
JavaScript
Language
14.3K
Lines of Code
232
Files
81
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 9LOW 72

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 81 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 Block41 hits · 41 pts
SeverityFileLineSnippetContext
LOW.overcommit.yml1# Use this file to configure the Overcommit hooks you wish to use. This willCOMMENT
LOW.overcommit.yml21# on_warn: fail # Treat all warnings as failuresCOMMENT
LOWrenderer/node-renderer.js41 workersCount: parseIntegerEnv('RENDERER_WORKERS_COUNT', process.env.CI ? 2 : 3, { min: 0 }),COMMENT
LOWapp/controllers/pages_controller.rb1# frozen_string_literal: trueCOMMENT
LOWconfig/storage.yml1test:COMMENT
LOWconfig/storage.yml21# credentials: <%= Rails.root.join("path/to/gcs.keyfile") %>COMMENT
LOWconfig/application.rb21 # Configuration for the application, engines, and railties goes here.COMMENT
LOWconfig/puma.rb1# frozen_string_literal: trueCOMMENT
LOWconfig/puma.rb21# Global VM Lock (GVL) it has diminishing returns and will degrade theCOMMENT
LOWconfig/puma.rb41# Run the Solid Queue supervisor inside of Puma for single-server deployments.COMMENT
LOWconfig/database.yml1# SQLite version 3.xCOMMENT
LOWconfig/environments/production.rb61 # Set this to true and configure the email server for immediate delivery to raise delivery errors.COMMENT
LOWconfig/environments/test.rb1# frozen_string_literal: trueCOMMENT
LOWconfig/webpack/commonWebpackConfig.js1// The source code including full typescript support is available at:COMMENT
LOWconfig/initializers/backtrace_silencers.rb1# frozen_string_literal: trueCOMMENT
LOWconfig/initializers/mime_types.rb1# frozen_string_literal: trueCOMMENT
LOWconfig/initializers/wrap_parameters.rb1# frozen_string_literal: trueCOMMENT
LOWconfig/initializers/react_on_rails.rb21 # If you are using the same file for client and server rendering, having this set probably doesCOMMENT
LOWconfig/initializers/react_on_rails.rb41 # CLIENT RENDERING OPTIONSCOMMENT
LOWconfig/initializers/react_on_rails.rb61COMMENT
LOWconfig/initializers/permissions_policy.rb1# frozen_string_literal: trueCOMMENT
LOWconfig/initializers/content_security_policy.rb1# frozen_string_literal: trueCOMMENT
LOWconfig/initializers/content_security_policy.rb21# # Generate session nonces for permitted importmap, inline scripts, and inline styles.COMMENT
LOWconfig/initializers/inflections.rb1# frozen_string_literal: trueCOMMENT
LOWconfig/initializers/cors.rb1# frozen_string_literal: trueCOMMENT
LOWspec/spec_helper.rb1# frozen_string_literal: trueCOMMENT
LOWspec/spec_helper.rb21COMMENT
LOWspec/spec_helper.rb41 # library (such as bogus or mocha) by changing the `mock_with` option here.COMMENT
LOWspec/spec_helper.rb61 # - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntaxCOMMENT
LOWspec/spec_helper.rb81 # config.profile_examples = 10COMMENT
LOWspec/rails_helper.rb21# run twice. It is recommended that you do not name files matching this glob toCOMMENT
LOWspec/rails_helper.rb41 config.include FactoryBot::Syntax::MethodsCOMMENT
LOWspec/rails_helper.rb61 # explicitly tag your specs with their type, e.g.:COMMENT
LOW.controlplane/templates/postgres.yml41#COMMENT
LOW.controlplane/templates/postgres.yml61#}COMMENT
LOW.controlplane/templates/postgres.yml81#COMMENT
LOW.controlplane/templates/org.yml1# App secret dictionaries store sensitive information for apps in theCOMMENT
LOW…hub/workflows/cpflow-promote-staging-to-production.yml21 # Space-separated list of HTTP statuses considered healthy. The default accepts 301/302COMMENT
LOW.github/workflows/claude.yml141 # Optional: Give a custom prompt to Claude. If this is not specified, Claude will perform the instructions speCOMMENT
LOWdb/schema.rb1# This file is auto-generated from the current state of the database. InsteadCOMMENT
LOWdb/seeds.rb1# This file should contain all the record creation needed to seed the database with its default values.COMMENT
Structural Annotation Overuse20 hits · 34 pts
SeverityFileLineSnippetContext
LOWapp/controllers/pages_controller.rb9 # NOTE: The below notes apply if you want to set the value of the props in the controller, asCOMMENT
LOW.claude/commands/address-review.md9## Step 1: Determine the RepositoryCOMMENT
LOW.claude/commands/address-review.md17## Step 2: Parse User InputCOMMENT
LOW.claude/commands/address-review.md34## Step 3: Fetch Review CommentsCOMMENT
LOW.claude/commands/address-review.md69## Step 4: Triage CommentsCOMMENT
LOW.claude/commands/address-review.md84## Step 5: Create Todo ListCOMMENT
LOW.claude/commands/address-review.md94## Step 6: Present Triage to UserCOMMENT
LOW.claude/commands/address-review.md104## Step 7: Address Items, Reply, and ResolveCOMMENT
LOW.controlplane/docs/debugging-deployment-failures.md73### Step 1: Set ContextCOMMENT
LOW.controlplane/docs/debugging-deployment-failures.md82### Step 2: Check Workload StatusCOMMENT
LOW.controlplane/docs/debugging-deployment-failures.md101### Step 3: Check EventsCOMMENT
LOW.controlplane/docs/debugging-deployment-failures.md112### Step 4: Check Container LogsCOMMENT
LOW.controlplane/docs/debugging-deployment-failures.md122### Step 5: Check GVC EnvironmentCOMMENT
LOW.controlplane/docs/debugging-deployment-failures.md134### Step 6: Check DependenciesCOMMENT
LOW.controlplane/docs/debugging-deployment-failures.md343# Step 1: Create a policy in the PRODUCTION org that grants access to the staging service accountCOMMENT
LOW.controlplane/docs/debugging-deployment-failures.md351# Step 2: Also grant access to workloads within the GVCCOMMENT
LOW.controlplane/docs/debugging-deployment-failures.md360# Step 3: Grant access to view/manage secrets if neededCOMMENT
LOWdocs/verify-early-hints-manual.md15### Step 1: Open the PR Review AppCOMMENT
LOWdocs/verify-early-hints-manual.md23### Step 2: Look for Early Hints EvidenceCOMMENT
LOWdocs/verify-early-hints-manual.md65### Step 3: Take ScreenshotsCOMMENT
Self-Referential Comments6 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUMconfig/initializers/wrap_parameters.rb5# This file contains settings for ActionController::ParamsWrapper whichCOMMENT
MEDIUMconfig/initializers/permissions_policy.rb5# Define an application-wide HTTP permissions policy. For furtherCOMMENT
MEDIUMconfig/initializers/content_security_policy.rb5# Define an application-wide content security policy.COMMENT
MEDIUMspec/rails_helper.rb3# This file is copied to spec/ when you run "rails generate rspec:install"COMMENT
MEDIUMdb/schema.rb1# This file is auto-generated from the current state of the database. InsteadCOMMENT
MEDIUMdb/schema.rb5# This file is the source Rails uses to define your schema when running `bin/railsCOMMENT
Slop Phrases5 hits · 10 pts
SeverityFileLineSnippetContext
MEDIUM.overcommit.yml13# For a complete list of options that you can use to customize hooks, see:COMMENT
MEDIUMspec/spec_helper.rb50 # with RSpec, but feel free to customize to your heart's content.COMMENT
LOW…les/comments/containers/NonRouterCommentsContainer.jsx42// Don't forget to actually use connect!COMMENT
LOW…undles/comments/containers/RouterCommentsContainer.jsx41// Don't forget to actually use connect!COMMENT
LOW…bundles/comments/containers/NavigationBarContainer.jsx33// Don't forget to actually use connect!COMMENT
Redundant / Tautological Comments4 hits · 6 pts
SeverityFileLineSnippetContext
LOWconfig/environments/production.rb61 # Set this to true and configure the email server for immediate delivery to raise delivery errors.COMMENT
LOWconfig/environments/production.rb64 # Set host to be used by links generated in mailer templates.COMMENT
LOWconfig/environments/development.rb41 # Set localhost to be used by links generated in mailer templates.COMMENT
LOWconfig/environments/test.rb41 # Set host to be used by links generated in mailer templates.COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMconfig/initializers/react_on_rails.rb32 # BREAKING CHANGE in v16: React on Rails 14.2.1 had robust error handling that wouldCOMMENT
Hyper-Verbose Identifiers3 hits · 3 pts
SeverityFileLineSnippetContext
LOWspec/requests/server_components_spec.rb28 def discard_blank_frame_lines(body)CODE
LOWspec/requests/server_components_spec.rb33 def parse_length_prefixed_chunk(body)CODE
LOW…server-components/components/LiveActivityRefresher.jsx43function toServerComponentFetchError(error, componentProps) {CODE
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOWcheck_early_hints.py81 except Exception as e:CODE