Repository Analysis

ohmybash/oh-my-bash

A delightful community-driven framework for managing your bash configuration, and an auto-update tool so that makes it easy to keep up with the latest updates from the community.

17.7 Moderate AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of ohmybash/oh-my-bash, a Shell project with 7,617 GitHub stars. SynthScan v2.0 examined 35,091 lines of code across 303 source files, recording 302 pattern matches distributed across 10 syntactic categories. The overall adjusted score of 17.7 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).

17.7
Adjusted Score
17.7
Raw Score
100%
Time Factor
2026-08-01
Last Push
7.6K
Stars
Shell
Language
35.1K
Lines of Code
303
Files
302
Pattern Hits
2026-08-02
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

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 0HIGH 1MEDIUM 137LOW 164

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 302 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.

Decorative Section Separators123 hits · 400 pts
SeverityFileLineSnippetContext
MEDIUMtools/autossh.sh2# ------------------------------------------------------------------------------COMMENT
MEDIUMtools/autossh.sh9# ------------------------------------------------------------------------------COMMENT
MEDIUMplugins/bashmarks/bashmarks.plugin.sh12#------------------------------------------------------------------------------COMMENT
MEDIUMplugins/bashmarks/bashmarks.plugin.sh36#------------------------------------------------------------------------------COMMENT
MEDIUMplugins/nvm/nvm.plugin.sh16#------------------------------------------------------------------------------COMMENT
MEDIUMplugins/nvm/nvm.plugin.sh101#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/svn.completion.sh10# ------------------------------------------------------------COMMENT
MEDIUMcompletions/svn.completion.sh27# ------------------------------------------------------------COMMENT
MEDIUMcompletions/sdkman.completion.sh4#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/gradle.completion.sh3#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/salt.completion.sh5#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/vagrant.completion.sh5#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/defaults.completion.sh14#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/gh.completion.sh5#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/go.completion.sh5#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/git_flow.completion.sh4# ===================COMMENT
MEDIUMcompletions/git_flow.completion.sh16# ------------COMMENT
MEDIUMcompletions/git_flow.completion.sh42# --------------COMMENT
MEDIUMcompletions/virtualbox.completion.sh17#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/grunt.completion.sh9#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/maven.completion.sh10#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/vault.completion.sh9# ---------------------------------------------------------------------------COMMENT
MEDIUMcompletions/vault.completion.sh15# ---------------------------------------------------------------------------COMMENT
MEDIUMcompletions/django.completion.sh8# =================================COMMENT
MEDIUMcompletions/django.completion.sh21# ==========COMMENT
MEDIUMcompletions/django.completion.sh32# ============COMMENT
MEDIUMcompletions/hub.completion.sh5#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/git_flow_avh.completion.sh5#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/git_flow_avh.completion.sh7# ===================COMMENT
MEDIUMcompletions/git_flow_avh.completion.sh19# ------------COMMENT
MEDIUMcompletions/git_flow_avh.completion.sh45# --------------COMMENT
MEDIUMcompletions/fallback/docker.bash3#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/fallback/docker.bash10#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/fallback/docker-compose.bash2#------------------------------------------------------------------------------COMMENT
MEDIUMcompletions/fallback/docker-compose.bash10#------------------------------------------------------------------------------COMMENT
MEDIUMlib/base.sh29#------------------------------------------------------------------------------COMMENT
MEDIUMlib/base.sh31# -----------------------------COMMENT
MEDIUMlib/base.sh33# -----------------------------COMMENT
MEDIUMlib/base.sh36# --------------------------------------------------------------------COMMENT
MEDIUMlib/base.sh42# --------------------------------------------------------------------COMMENT
MEDIUMlib/base.sh46# ------------------------------------------------------------COMMENT
MEDIUMlib/base.sh50# ------------------------------------------------------------COMMENT
MEDIUMlib/base.sh56# ------------------------------------------------------------COMMENT
MEDIUMlib/base.sh61# ------------------------------------------------------------COMMENT
MEDIUMlib/base.sh69# ------------------------------------------------------------COMMENT
MEDIUMlib/base.sh80# -------------------------------COMMENT
MEDIUMlib/base.sh82# -------------------------------COMMENT
MEDIUMlib/base.sh87# ---------------------------------------------------------COMMENT
MEDIUMlib/base.sh110# ---------------------------------------------------------COMMENT
MEDIUMlib/base.sh119# ---------------------------------------------------------COMMENT
MEDIUMlib/base.sh125# ---------------------------------------------------------COMMENT
MEDIUMlib/base.sh176# ---------------------------COMMENT
MEDIUMlib/base.sh178# ---------------------------COMMENT
MEDIUMlib/base.sh181# -----------------------------------------------------COMMENT
MEDIUMlib/base.sh185# -----------------------------------------------------COMMENT
MEDIUMlib/base.sh189# ------------------------------------------------------------COMMENT
MEDIUMlib/base.sh193# ---------------------------COMMENT
MEDIUMlib/base.sh195# ---------------------------COMMENT
MEDIUMlib/base.sh198# -------------------------------------------------------------------COMMENT
MEDIUMlib/base.sh212# -------------------------------------------------------------------COMMENT
63 more matches not shown…
Over-Commented Block140 hits · 136 pts
SeverityFileLineSnippetContext
LOWtools/git-prompt.sh1# bash/zsh git prompt supportCOMMENT
LOWtools/git-prompt.sh21# you would put in $PS1 before and after the status stringCOMMENT
LOWtools/git-prompt.sh41# bash.showDirtyState variable, which defaults to true onceCOMMENT
LOWtools/git-prompt.sh61#COMMENT
LOWtools/git-prompt.sh81#COMMENT
LOWtools/git-prompt.sh281__git_eread ()COMMENT
LOWtools/git-prompt.sh321 *) return $exitCOMMENT
LOWtools/git-prompt.sh341 # with the user's environment) and that variable should beCOMMENT
LOWtools/bash-preexec.sh1# bash-preexec.sh -- Bash support for ZSH-like 'preexec' and 'precmd' functions.COMMENT
LOWtools/bash-preexec.sh21# e.g.COMMENT
LOWtools/git-completion.bash1# bash/zsh completion support for core Git.COMMENT
LOWtools/git-completion.bash21# 2) Add the following line to your .bashrc/.zshrc:COMMENT
LOWtools/git-completion.bash41# Compatible with bash 3.2.57.COMMENT
LOWtools/git-completion.bash181# © 2009-2010, Bash Completion MaintainersCOMMENT
LOWtools/git-completion.bash201# RELEASE: 2.xCOMMENT
LOWtools/git-completion.bash401# the completion script.COMMENT
LOWtools/git-completion.bash681 # employ the heuristic used by git checkout and git switchCOMMENT
LOWtools/git-completion.bash801 doneCOMMENT
LOWtools/git-completion.bash1241# $1: short option nameCOMMENT
LOWtools/git-completion.bash1501# git-switch and git-checkout.COMMENT
LOWtools/git-completion.bash3281 add,*) # usage: git worktree add [<options>] <path> [<commit-ish>]COMMENT
LOWtools/update-wiki-themes.sh1#!/usr/bin/env bashCOMMENT
LOWplugins/bashmarks/bashmarks.plugin.sh1#! bash oh-my-bash.moduleCOMMENT
LOWplugins/bashmarks/bashmarks.plugin.sh21# * Neither the name of Huy Nguyen nor the names of contributors may beCOMMENT
LOWplugins/progress/progress.plugin.sh1#! bash oh-my-bash.moduleCOMMENT
LOWplugins/nvm/nvm.plugin.sh1#! bash oh-my-bash.moduleCOMMENT
LOWplugins/nvm/nvm.plugin.sh21#COMMENT
LOWplugins/tmux-autoattach/tmux-autoattach.plugin.sh1#! bash oh-my-bash.moduleCOMMENT
LOWplugins/tmux/tmux.plugin.bash1#! bash oh-my-bash.moduleCOMMENT
LOWplugins/npm/npm.plugin.sh1#! bash oh-my-bash.moduleCOMMENT
LOWplugins/git/git.plugin.sh561alias gke='\gitk --all $(git log --walk-reflogs --pretty=%h)'COMMENT
LOWcompletions/fabric-completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/fabric-completion.sh21# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERCOMMENT
LOWcompletions/svn.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/svn.completion.sh21# Unless required by applicable law or agreed to in writing,COMMENT
LOWcompletions/svn.completion.sh121# 2. svn+ssh:// lists servers from .ssh/known_hostsCOMMENT
LOWcompletions/svn.completion.sh201# - there is a "real" parser to check for what is available and deduce whatCOMMENT
LOWcompletions/svn.completion.sh221# SVN_BASH_USERNAME: usernames suggested for --usernameCOMMENT
LOWcompletions/svn.completion.sh301 # Parse arguments and set various variables about what was found.COMMENT
LOWcompletions/svn.completion.sh621 # property names...COMMENT
LOWcompletions/gulp.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/makefile.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/sdkman.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/salt.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/vagrant.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/defaults.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/defaults.completion.sh161# This file is licensed under the BSD license, as follows:COMMENT
LOWcompletions/defaults.completion.sh181# disclaimed. In no event shall the copyright owner or contributors be liableCOMMENT
LOWcompletions/git_flow.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/git_flow.completion.sh21#COMMENT
LOWcompletions/virtualbox.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/packer.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/packer.completion.sh21# team in general.COMMENT
LOWcompletions/grunt.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/kubectl.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/vault.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/django.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/django.completion.sh21# ==========COMMENT
LOWcompletions/hub.completion.sh1#! bash oh-my-bash.moduleCOMMENT
LOWcompletions/docker-machine.completion.sh1#! bash oh-my-bash.moduleCOMMENT
80 more matches not shown…
Self-Referential Comments12 hits · 36 pts
SeverityFileLineSnippetContext
MEDIUMtools/bash-preexec.sh135# This function is installed as part of the PROMPT_COMMAND;COMMENT
MEDIUMtools/bash-preexec.sh143# This function is installed as part of the PROMPT_COMMAND.COMMENT
MEDIUMtools/bash-preexec.sh203# This function is installed as the DEBUG trap. It is invoked before eachCOMMENT
MEDIUMtools/git-completion.bash176# The following function is based on code from:COMMENT
MEDIUMtools/git-completion.bash408# This function is equivalent toCOMMENT
MEDIUMplugins/dotnet/dotnet.plugin.sh28#Create a new .NET project or file.COMMENT
MEDIUMplugins/dotnet/dotnet.plugin.sh44#Create a NuGet package.COMMENT
MEDIUMcompletions/defaults.completion.sh161# This file is licensed under the BSD license, as follows:COMMENT
MEDIUMcompletions/fallback/docker.bash672# This function is needed for key-specific completions.COMMENT
MEDIUMcompletions/fallback/docker-compose.bash64# This function is needed for key-specific completions.COMMENT
MEDIUMlib/shopt.sh97# Define a variable containing a path and you will be able to cd into it regardless of the directory you're inCOMMENT
MEDIUMlib/readlink.sh3## This module provides the following function which can be used as "readlinkCOMMENT
Redundant / Tautological Comments15 hits · 22 pts
SeverityFileLineSnippetContext
LOWoh-my-bash.sh35# Set OSH_CUSTOM to the path where your custom config filesCOMMENT
LOWoh-my-bash.sh43# Set OSH_CACHE_DIR to the path where cache files should be createdCOMMENT
LOWplugins/starship/starship.plugin.sh3# Check if starship is installedCOMMENT
LOWplugins/cargo/cargo.plugin.sh4# Set CARGO_HOME to default if not already setCOMMENT
LOWplugins/cargo/cargo.plugin.sh7# Check if the directory existsCOMMENT
LOWplugins/zoxide/zoxide.plugin.sh3# Check if zoxide is installedCOMMENT
LOWplugins/jump/jump.plugin.sh3# Check if jump is installedCOMMENT
LOWplugins/virtualenvwrapper/virtualenvwrapper.plugin.sh3# Check if virtualenvwrapper is installedCOMMENT
LOWplugins/fzf/fzf.plugin.sh3# Check if fzf is installedCOMMENT
LOWplugins/git/git.plugin.sh42# Check if main exists and use instead of masterCOMMENT
LOWcompletions/fabric-completion.sh43# Set command to get time of last file modification as seconds since EpochCOMMENT
LOWcompletions/drush.completion.sh27 # Set IFS to newline (locally), since we only use newline separators, andCOMMENT
LOWthemes/binaryanomaly/binaryanomaly.theme.sh3# Set term to 256color mode, if 256color is not supported, colors won't work properlyCOMMENT
LOWthemes/rana/rana.theme.sh118 # Check if the current directory is in a Git repository.COMMENT
LOWthemes/pzq/pzq.theme.sh73 # Check if the current directory is in a Git repository.COMMENT
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHtools/git-completion.bash1510# logic, as requested by the user.COMMENT
Slop Phrases2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMtools/git-completion.bash26# If you use complex aliases of form '!f() { ... }; f', you can use the nullCOMMENT
MEDIUMtools/git-completion.bash33# like completion, you can use __git_complete:COMMENT
Example Usage Blocks4 hits · 6 pts
SeverityFileLineSnippetContext
LOWcompletions/gulp.completion.sh8# Usage:COMMENT
LOWcompletions/grunt.completion.sh17# Usage:COMMENT
LOWlib/utils.sh89# Usage:COMMENT
LOWcustom/aliases/example.aliases.sh4# Usage:COMMENT
AI Slop Vocabulary3 hits · 4 pts
SeverityFileLineSnippetContext
LOWtools/git-prompt.sh315 # simply return early if the prompt should notCOMMENT
LOWcompletions/fallback/docker.bash1179 # if result empty, just use filename completion as fallbackCOMMENT
LOWthemes/hawaii50/hawaii50.theme.sh107 # If no virtual info, just returnCOMMENT
Structural Annotation Overuse1 hit · 2 pts
SeverityFileLineSnippetContext
LOWtools/bash-preexec.sh56# WARNING: This variable is no longer used and should not be relied upon.COMMENT
TODO Padding1 hit · 2 pts
SeverityFileLineSnippetContext
LOWlib/omb-prompt-base.sh177 # TODO: consider adding minimal status information for hg and svnCOMMENT