Repository Analysis

lobsters/lobsters

Computing-focused community centered around link aggregation and discussion

3.9 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of lobsters/lobsters, a Ruby project with 4,759 GitHub stars. SynthScan v2.0 examined 31,395 lines of code across 512 source files, recording 85 pattern matches distributed across 7 syntactic categories. The overall adjusted score of 3.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).

3.9
Adjusted Score
3.9
Raw Score
100%
Time Factor
2026-07-14
Last Push
4.8K
Stars
Ruby
Language
31.4K
Lines of Code
512
Files
85
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

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 0MEDIUM 16LOW 69

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

Self-Referential Comments13 hits · 39 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
MEDIUMspec/requests/search_spec.rb6 # Create a comment we can search for. Rspec wraps tests in individual transactions, andCOMMENT
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
MEDIUMdb/queue_schema.rb1# This file is auto-generated from the current state of the database. InsteadCOMMENT
MEDIUMdb/queue_schema.rb5# This file is the source Rails uses to define your schema when running `bin/railsCOMMENT
MEDIUMdb/rack_attack_schema.rb1# This file is auto-generated from the current state of the database. InsteadCOMMENT
MEDIUMdb/rack_attack_schema.rb5# This file is the source Rails uses to define your schema when running `bin/railsCOMMENT
MEDIUMdb/cache_schema.rb1# This file is auto-generated from the current state of the database. InsteadCOMMENT
MEDIUMdb/cache_schema.rb5# This file is the source Rails uses to define your schema when running `bin/railsCOMMENT
Over-Commented Block29 hits · 29 pts
SeverityFileLineSnippetContext
LOW.database_consistency.ignore.yml1# This file lists exceptions for database_consistency checks at build time.COMMENT
LOW.database_consistency.ignore.yml21# a `has_many` with `dependent: :nullify` (Story#merged_stories), and a caseCOMMENT
LOWapp/models/comment.rb341 last_byte = [id & 0xff].pack("C")COMMENT
LOWconfig/locales/en.yml1# Files in the config/locales directory are used for internationalizationCOMMENT
LOWconfig/environments/production.rb41 # Enable serving of images, stylesheets, and JavaScripts from an asset server.COMMENT
LOWconfig/environments/test.rb1# typed: falseCOMMENT
LOWconfig/initializers/application_controller_renderer.rb1# typed: falseCOMMENT
LOWconfig/initializers/backtrace_silencers.rb1# typed: falseCOMMENT
LOWconfig/initializers/mime_types.rb1# typed: falseCOMMENT
LOWconfig/initializers/session_store.rb1# typed: falseCOMMENT
LOWconfig/initializers/wrap_parameters.rb1# typed: falseCOMMENT
LOWconfig/initializers/assets.rb1# typed: falseCOMMENT
LOWconfig/initializers/page_caching_monkeypatch.rb1# https://github.com/lobsters/lobsters/issues/1825COMMENT
LOWconfig/initializers/permissions_policy.rb1# typed: falseCOMMENT
LOWconfig/initializers/rack_attack.rb1# typed: falseCOMMENT
LOWconfig/initializers/inflections.rb1# typed: falseCOMMENT
LOWspec/spec_helper.rb1# typed: falseCOMMENT
LOWspec/spec_helper.rb21RSpec.configure do |config|COMMENT
LOWspec/spec_helper.rb41 # `true` in RSpec 4.COMMENT
LOWspec/spec_helper.rb61 # # metadata: `fit`, `fdescribe` and `fcontext`, respectively.COMMENT
LOWspec/spec_helper.rb81 # # unless a formatter has already been configuredCOMMENT
LOWspec/css_widely_available_spec.rb61# baseline "high" == "widely available"COMMENT
LOWspec/models/search_parser_spec.rb1# typed: falseCOMMENT
LOW.github/workflows/stale.yml21 close-pr-message: "This PR was closed because it was open for 40 days with no activity. Please reopen when you'dCOMMENT
LOWdb/schema.rb1# This file is auto-generated from the current state of the database. InsteadCOMMENT
LOWdb/queue_schema.rb1# This file is auto-generated from the current state of the database. InsteadCOMMENT
LOWdb/rack_attack_schema.rb1# This file is auto-generated from the current state of the database. InsteadCOMMENT
LOWdb/cache_schema.rb1# This file is auto-generated from the current state of the database. InsteadCOMMENT
LOWdb/migrate/20250818182728_add_fts_tables.rb1# If you are reading this file because Rails complains that there isn't aCOMMENT
Fake / Example Data19 hits · 21 pts
SeverityFileLineSnippetContext
LOWCONTRIBUTING.md87 lobsters$ rails fake_dataCODE
LOWCONTRIBUTING.md90 The default password for users generated by `fake_data` is `"fake"`.CODE
LOWspec/rails_helper.rb39 # 'placeholder' is so factory_bot can instantiate valid Story objects, but tests must replaceCOMMENT
LOWspec/rails_helper.rb41 c.tags.create!([{tag: "placeholder"}, {tag: "tag1"}, {tag: "tag2"}])CODE
LOWspec/slow/fake_data_spec.rb7describe "fake_data" doCODE
LOWspec/features/edit_hat_spec.rb6 let!(:hat) { create(:hat, link: "foo@bar.com") }CODE
LOWspec/features/hats_spec.rb8 hat = create(:hat, link: "foo@bar.com")CODE
LOWspec/features/hats_spec.rb20 hat = create(:hat, link: "foo@bar.com")CODE
LOWspec/models/mastodon_app_spec.rb18 expect(MastodonApp.sanitized_instance_name("user@example.com")).to eq("example.com")CODE
LOWspec/models/hat_spec.rb22 hat = build(:hat, link: "foo@bar.com")CODE
LOWspec/models/search_parser_spec.rb136 it("doesn't parse emails") { expect(sp.user).to_not parse("user@example.com") }CODE
LOWspec/models/user_spec.rb72 create(:user, email: "user@example.com")CODE
LOWspec/models/user_spec.rb75 expect { create(:user, email: "user@example.com") }.to raise_errorCODE
LOWspec/factories/story.rb8 tags { Tag.where(tag: "placeholder") }CODE
LOWdocs/SETUP_DEVCONTAINER.md22* Create the fake data by running `rails fake_data`COMMENT
LOWdocs/setup_with_docker.md23* Create the fake data by running `docker compose run app rails fake_data`COMMENT
LOW.devcontainer/devcontainer.json32 "postStartCommand": "bin/rails fake_data"CODE
LOWdb/seeds.rb41Rails.logger.debug "If this is a dev environment, you probably want to run `rails fake_data`"CODE
LOWextras/mastodon.rb96 # returns { "user@example.com" => 123 } for remove_list_accounts callCOMMENT
Hyper-Verbose Identifiers12 hits · 12 pts
SeverityFileLineSnippetContext
LOWapp/models/user.rb496 def initiate_password_reset_for_ip(ip)CODE
LOWapp/models/story.rb662 def description_or_story_text(chars = 0)CODE
LOWapp/jobs/notify_mod_mail_message_job.rb12 def deliver_mod_mail_message_notifications(mod_mail_message, recipient)CODE
LOWapp/jobs/notify_message_job.rb10 def deliver_message_notifications(message)CODE
LOWapp/jobs/notify_comment_job.rb10 def deliver_comment_notifications(comment)CODE
LOWapp/jobs/notify_comment_job.rb15 def deliver_mention_notifications(comment, notified)CODE
LOWapp/jobs/notify_comment_job.rb68 def deliver_reply_notifications(comment)CODE
LOWapp/controllers/home_controller.rb384 def tags_with_description_for_rss(tags)CODE
LOWapp/helpers/users_helper.rb8 def stories_submitted_content(user, showing_user)CODE
LOWapp/helpers/application_helper.rb47 def excerpt_fragment_around_link(html, url)CODE
LOWapp/helpers/application_helper.rb130 def page_numbers_for_pagination(max, cur)CODE
LOWlib/time_series.rb55 def data_with_extrapolated_month(data)CODE
Slop Phrases6 hits · 10 pts
SeverityFileLineSnippetContext
LOWapp/models/vote.rb26 # don't forget to edit the explanations on /aboutCOMMENT
LOWapp/models/vote.rb26 # don't forget to edit the explanations on /aboutCOMMENT
LOWapp/models/vote.rb39 # don't forget to edit the explanations on /aboutCOMMENT
LOWapp/models/vote.rb39 # don't forget to edit the explanations on /aboutCOMMENT
MEDIUMspec/spec_helper.rb56 # with RSpec, but feel free to customize to your heart's content.COMMENT
LOW.github/workflows/check.yml1# If any steps below are added or changed, make sure to keep build.rake in sync.COMMENT
AI Slop Vocabulary3 hits · 8 pts
SeverityFileLineSnippetContext
MEDIUMbin/stackprof-flamegraph.pl8# this file is here to facilitate running it.COMMENT
MEDIUMbin/stackprof-gprof2dot.py8# this file is here to facilitate running it.COMMENT
LOWspec/models/story_spec.rb152 # we can't seemingly just set body, so...COMMENT
Redundant / Tautological Comments3 hits · 4 pts
SeverityFileLineSnippetContext
LOWapp/models/notification.rb47 # Check if this is a mention notificationCOMMENT
LOWapp/jobs/restic_job.rb6 # Check if the shared directory existsCOMMENT
LOWconfig/environments/production.rb96 # Set this to true and configure the email server for immediate delivery to raise delivery errors.COMMENT