Repository Analysis

d12frosted/homebrew-emacs-plus

Emacs Plus formulae for the Homebrew package manager

19.2 Moderate AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of d12frosted/homebrew-emacs-plus, a Ruby project with 2,892 GitHub stars. SynthScan v2.0 examined 12,777 lines of code across 129 source files, recording 95 pattern matches distributed across 6 syntactic categories. The overall adjusted score of 19.2 places this repository in the Moderate 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).

19.2
Adjusted Score
19.2
Raw Score
100%
Time Factor
2026-07-14
Last Push
2.9K
Stars
Ruby
Language
12.8K
Lines of Code
129
Files
95
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 71LOW 24

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 95 distinct pattern matches across 6 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 Separators68 hits · 207 pts
SeverityFileLineSnippetContext
MEDIUMtests/test_applescript_escaping.rb37 # ===========================================COMMENT
MEDIUMtests/test_applescript_escaping.rb39 # ===========================================COMMENT
MEDIUMtests/test_applescript_escaping.rb107 # ===========================================COMMENT
MEDIUMtests/test_applescript_escaping.rb109 # ===========================================COMMENT
MEDIUMtests/test_applescript_escaping.rb140 # ===========================================COMMENT
MEDIUMtests/test_applescript_escaping.rb142 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb42 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb44 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb66 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb68 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb132 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb134 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb288 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb290 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb471 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb473 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb591 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb593 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb621 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb623 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb746 # ===========================================COMMENT
MEDIUMtests/test_cask_env.rb748 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb16 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb18 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb74 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb76 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb123 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb125 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb182 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb184 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb208 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb210 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb232 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb234 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb293 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb295 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb339 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb341 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb399 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb401 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb642 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb644 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb702 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb704 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb755 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb757 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb794 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb796 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb827 # ===========================================COMMENT
MEDIUMtests/test_build_config.rb829 # ===========================================COMMENT
MEDIUMtests/test_format_maintainer.rb31 # ===========================================COMMENT
MEDIUMtests/test_format_maintainer.rb33 # ===========================================COMMENT
MEDIUMtests/test_format_maintainer.rb43 # ===========================================COMMENT
MEDIUMtests/test_format_maintainer.rb45 # ===========================================COMMENT
MEDIUMtests/test_format_maintainer.rb59 # ===========================================COMMENT
MEDIUMtests/test_format_maintainer.rb61 # ===========================================COMMENT
MEDIUMtests/test_format_maintainer.rb77 # ===========================================COMMENT
MEDIUMtests/test_format_maintainer.rb79 # ===========================================COMMENT
MEDIUMtests/test_format_maintainer.rb90 # ===========================================COMMENT
MEDIUMtests/test_format_maintainer.rb92 # ===========================================COMMENT
8 more matches not shown…
Redundant / Tautological Comments8 hits · 13 pts
SeverityFileLineSnippetContext
LOWLibrary/IconApplier.rb163 # Check if we're in Homebrew context where ohai is a methodCOMMENT
LOWLibrary/EmacsBase.rb248 # Check if icon is configured for non-Cocoa buildsCOMMENT
LOWLibrary/EmacsBase.rb459 # Check if user PATH injection is enabled (default: true)COMMENT
LOWLibrary/EmacsBase.rb813 # Set CFBundleIconName to match the icon name in Assets.car (defaults to "Emacs")COMMENT
LOWLibrary/CaskEnv.rb66 # Check if user PATH injection is enabled (default: true)COMMENT
LOWLibrary/CaskEnv.rb210 # Check if already injectedCOMMENT
LOWLibrary/CaskEnv.rb267 # Check if we need to recompile (look for our marker in Info.plist)COMMENT
LOWscripts/create-community-icon.rb54 # Check if it's a valid icns file (magic number)COMMENT
Self-Referential Comments3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMtests/test_applescript_escaping.rb190 # Create a script that sets PATH and echoes it backCOMMENT
MEDIUMtests/test_cask_env.rb635 # Create a fake versioned gcc driver that answers -print-file-name withCOMMENT
MEDIUMLibrary/CaskEnv.rb239 # Create a wrapper script at Emacs.app/Contents/MacOS/bin/emacsCOMMENT
Over-Commented Block9 hits · 8 pts
SeverityFileLineSnippetContext
LOW.rubocop.yml201COMMENT
LOW.rubocop.yml221# Enabled: falseCOMMENT
LOWtests/test_applescript_escaping.rb1#!/usr/bin/env rubyCOMMENT
LOWtests/test_build_config.rb1#!/usr/bin/env rubyCOMMENT
LOWLibrary/EmacsBase.rb681 endCOMMENT
LOWLibrary/CaskEnv.rb1# frozen_string_literal: trueCOMMENT
LOWLibrary/CaskEnv.rb181 # Environment variables injected into LSEnvironment for native compilation.COMMENT
LOWscripts/postinstall-formula.rb1#!/usr/bin/env rubyCOMMENT
LOW.github/workflows/build-app.yml981 doneCOMMENT
Hyper-Verbose Identifiers5 hits · 5 pts
SeverityFileLineSnippetContext
LOWtests/test_applescript_escaping.rb167 def assert_applescript_compiles(path)CODE
LOWLibrary/BuildConfig.rb116 def native_comp_driver_options_el(prefix)CODE
LOWLibrary/EmacsBase.rb543 def inject_emacs_plus_site_lisp(major_version)CODE
LOWLibrary/EmacsBase.rb711 def escape_for_applescript_shell(str)CODE
LOWLibrary/CaskEnv.rb425 def escape_for_applescript_shell(str)CODE
Fake / Example Data2 hits · 3 pts
SeverityFileLineSnippetContext
LOWtests/test_format_maintainer.rb73 maintainer = { "github" => "user", "name" => "Full Name", "email" => "user@example.com" }CODE
LOWtests/test_format_maintainer.rb109 maintainer = { "email" => "user@example.com" }CODE