Repository Analysis

silvertakana/worldwideview

4.5 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of silvertakana/worldwideview, a HTML project with 1,710 GitHub stars. SynthScan v2.0 examined 103,648 lines of code across 859 source files, recording 187 pattern matches distributed across 9 syntactic categories. The overall adjusted score of 4.5 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.5
Adjusted Score
4.5
Raw Score
100%
Time Factor
2026-07-14
Last Push
1.7K
Stars
HTML
Language
103.6K
Lines of Code
859
Files
187
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 1MEDIUM 110LOW 76

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 187 distinct pattern matches across 9 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 Separators108 hits · 346 pts
SeverityFileLineSnippetContext
MEDIUMdocker-entrypoint.sh2# ─── Docker Entrypoint ───────────────────────────────────────COMMENT
MEDIUMtests/marketplace-from-instance.spec.ts21// ─── Marketplace capture side (no worldwideview auth needed) ────────────────COMMENT
MEDIUMtests/marketplace-from-instance.spec.ts83// ─── Linked-instance API surface (anonymous, marketplace-only) ──────────────COMMENT
MEDIUMtests/marketplace-from-instance.spec.ts134// ─── InstanceCapture → server-link fire-and-forget ──────────────────────────COMMENT
MEDIUMtests/marketplace-from-instance.spec.ts154// ─── Full flow (worldwideview → marketplace, requires Docker + auth) ─────────COMMENT
MEDIUMtests/web-auth.spec.ts6// ─── /auth/reset-password ────────────────────────────────────────────────────COMMENT
MEDIUMtests/web-auth.spec.ts32// ─── /accounts unauthenticated redirect ──────────────────────────────────────COMMENT
MEDIUMtests/web-auth.spec.ts47// ─── /auth/verify without a code ─────────────────────────────────────────────COMMENT
MEDIUMtests/web-auth.spec.ts60// ─── /auth/reset-password/confirm without a hash ─────────────────────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts38 // ── 1. Sign up at worldwideview-web ────────────────────────────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts51 // ── 2. Navigate to globe app ──────────────────────────────────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts55 // ── 3. Click "Connect to Marketplace" ──────────────────────────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts60 // ── 4. Verify redirect to marketplace /oauth/authorize ─────────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts67 // ── 5. Verify consent page shows user email and scope ──────────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts72 // ── 6. Click "Approve" ────────────────────────────────────────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts77 // ── 7. Wait for redirect back to globe app ─────────────────────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts80 // ── 8. Verify "Connected as <email>" is visible ────────────────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts84 // ── 9. Navigate to a page with a plugin that requires auth ─────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts90 // ── 10. Verify ticketClient fetches from /api/auth/ticket ──────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts114 // ── 11. Verify WebSocket auth: auth message sent, welcome received ─────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts122 // ── 12. Verify data streams ───────────────────────────────────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts135 // ── 1. Sign up (fresh user, no marketplace connection) ─────────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts146 // ── 2. Navigate to globe app ──────────────────────────────────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts150 // ── 3. Navigate to plugins tab ────────────────────────────────────────COMMENT
MEDIUMtests/account-connect-e2e.spec.ts155 // ── 4. Listen for /api/auth/ticket — expect noCredential ──────────────COMMENT
MEDIUMtests/marketplace-sign-out.spec.ts27 // ── Establish authenticated session ──────────────────────────────────COMMENT
MEDIUMtests/marketplace-sign-out.spec.ts39 // ── Open avatar dropdown and click Sign Out ──────────────────────────COMMENT
MEDIUMtests/marketplace-sign-out.spec.ts43 // ── Assert redirect to marketplace home ──────────────────────────────COMMENT
MEDIUMtests/marketplace-sign-out.spec.ts49 // ── Assert session is cleared on the server ──────────────────────────COMMENT
MEDIUMpackages/wwv-lib-incidents/src/index.test.ts26// ─── Minimal GeoEntity factory ────────────────────────────────────────────────COMMENT
MEDIUMpackages/wwv-lib-incidents/src/index.test.ts40// ─── Minimal concrete subclass ────────────────────────────────────────────────COMMENT
MEDIUMpackages/wwv-lib-incidents/src/index.test.ts86// ─── Subclass that DOES override mapWebsocketPayload ─────────────────────────COMMENT
MEDIUMpackages/wwv-lib-incidents/src/index.test.ts98// ─── Helpers that mimic WsClient.handleDataMessage branching logic ────────────COMMENT
MEDIUMpackages/wwv-lib-incidents/src/index.test.ts120// ─── Test suite ───────────────────────────────────────────────────────────────COMMENT
MEDIUMpackages/wwv-plugin-sdk/src/index.ts68// ─── Re-export manifest types ─────────────────────────────────COMMENT
MEDIUMpackages/wwv-plugin-sdk/src/index.ts71// ─── Categories ──────────────────────────────────────────────COMMENT
MEDIUMpackages/wwv-plugin-sdk/src/index.ts85// ─── Time ────────────────────────────────────────────────────COMMENT
MEDIUMpackages/wwv-plugin-sdk/src/index.ts127// ─── Layer Config ────────────────────────────────────────────COMMENT
MEDIUMpackages/wwv-plugin-sdk/src/index.ts139// ─── Cesium Entity Options ───────────────────────────────────COMMENT
MEDIUMpackages/wwv-plugin-sdk/src/index.ts172// ─── Selection Behavior ──────────────────────────────────────COMMENT
MEDIUMpackages/wwv-plugin-sdk/src/index.ts182// ─── Server Plugin Config ────────────────────────────────────COMMENT
MEDIUMpackages/wwv-plugin-sdk/src/index.ts193// ─── Plugin Context ──────────────────────────────────────────COMMENT
MEDIUMpackages/wwv-plugin-sdk/src/index.ts227// ─── Filter Definitions ──────────────────────────────────────COMMENT
MEDIUMpackages/wwv-plugin-sdk/src/index.ts302// ─── Aliases for backwards compatibility ─────────────────────COMMENT
MEDIUMpackages/wwv-plugin-sdk/src/index.ts305// ─── Data Bus Event Types ────────────────────────────────────COMMENT
MEDIUMpackages/wwv-plugin-sdk/src/index.ts326// ─── Auth Contracts ──────────────────────────────────────────COMMENT
MEDIUMpackages/wwv-plugin-sdk/src/index.ts329// ─── Tagged Property Helpers ─────────────────────────────────COMMENT
MEDIUM.github/workflows/docker-publish.yml12 # --------------------------------------------------COMMENT
MEDIUM.github/workflows/docker-publish.yml14 # --------------------------------------------------COMMENT
MEDIUM.github/workflows/docker-publish.yml104 # --------------------------------------------------COMMENT
MEDIUM.github/workflows/docker-publish.yml106 # --------------------------------------------------COMMENT
MEDIUM.github/workflows/docker-publish.yml196 # --------------------------------------------------COMMENT
MEDIUM.github/workflows/docker-publish.yml198 # --------------------------------------------------COMMENT
MEDIUM.github/workflows/docker-publish.yml289 # --------------------------------------------------COMMENT
MEDIUM.github/workflows/docker-publish.yml291 # --------------------------------------------------COMMENT
MEDIUM.github/workflows/docker-publish.yml319 # --------------------------------------------------COMMENT
MEDIUM.github/workflows/docker-publish.yml321 # --------------------------------------------------COMMENT
MEDIUM.github/workflows/docker-publish.yml360 # --------------------------------------------------COMMENT
MEDIUM.github/workflows/docker-publish.yml362 # --------------------------------------------------COMMENT
MEDIUM.github/workflows/docker-publish.yml440 # --------------------------------------------------COMMENT
48 more matches not shown…
Structural Annotation Overuse34 hits · 58 pts
SeverityFileLineSnippetContext
LOW.agents/workflows/researching-plugins/SKILL.md19### Step 1: Take Inspiration from WorldMonitorCOMMENT
LOW.agents/workflows/researching-plugins/SKILL.md25### Step 2: Validate Data SourcesCOMMENT
LOW.agents/skills/migrate-legacy-plugin/SKILL.md54## Step 1: Move the Plugin DirectoryCOMMENT
LOW.agents/skills/migrate-legacy-plugin/SKILL.md70## Step 2: Fix Frontend Routing (getEngineUrl)COMMENT
LOW.agents/skills/migrate-legacy-plugin/SKILL.md111## Step 3: Update package.jsonCOMMENT
LOW.agents/skills/migrate-legacy-plugin/SKILL.md146## Step 4: Ensure Vite Build ConfigCOMMENT
LOW.agents/skills/migrate-legacy-plugin/SKILL.md170## Step 5: Fix Backend Seeder (if applicable)COMMENT
LOW.agents/skills/migrate-legacy-plugin/SKILL.md218## Step 6: Clean Up packages/ ReferencesCOMMENT
LOW.agents/skills/migrate-legacy-plugin/SKILL.md228## Step 7: VerifyCOMMENT
LOWdocs/demo-service-account.md18### Step 1: Create the Demo UserCOMMENT
LOWdocs/demo-service-account.md30### Step 2: Generate an API KeyCOMMENT
LOWdocs/demo-service-account.md37### Step 3: Set the Env Var on CoolifyCOMMENT
LOWdocs/demo-service-account.md44### Step 4: VerifyCOMMENT
LOWdocs/iss-plugin-tutorial.md12## Step 1: Setting up your WorkspaceCOMMENT
LOWdocs/iss-plugin-tutorial.md56## Step 2: Scaffold the Plugin and Backend SeederCOMMENT
LOWdocs/iss-plugin-tutorial.md89## Step 3: Write the Polling Logic (Backend Seeder)COMMENT
LOWdocs/iss-plugin-tutorial.md142## Step 4: Testing the Data EngineCOMMENT
LOWdocs/iss-plugin-tutorial.md156## Step 5: Write the Plugin Logic (Frontend)COMMENT
LOWdocs/iss-plugin-tutorial.md216## Step 6: Connecting and Testing EverythingCOMMENT
LOWdocs/iss-plugin-tutorial.md242## Step 7: Publishing Your PluginCOMMENT
LOWdocs/mcp-quickstart.md22## Step 1: Install and configureCOMMENT
LOWdocs/mcp-quickstart.md37## Step 2: Run the appCOMMENT
LOWdocs/mcp-quickstart.md60## Step 3: Sign in and generate an API keyCOMMENT
LOWdocs/mcp-quickstart.md73## Step 4: Add the MCP server to your clientCOMMENT
LOWdocs/mcp-quickstart.md96## Step 5: Restart your client and verifyCOMMENT
LOWdocs/plans/2026-05-22-adr-001-two-track-rollout.md88# Step 1: JWKS ✅ Step 2: Exchange ✅ Step 3: WS welcome ✅COMMENT
LOWsrc/core/data/SmartFetcher.ts20 // Step 1: Try Direct Fetch (Fastest)COMMENT
LOWsrc/core/data/SmartFetcher.ts30 // Step 2: Local Server ProxyCOMMENT
LOWsrc/app/api/mcp/discoveryTools.ts145 // Step 1: Geocode the place name (limit 1 result).COMMENT
LOWsrc/app/api/mcp/discoveryTools.ts155 // Step 2: Find matching streaming plugins by case-insensitive substring.COMMENT
LOWsrc/app/api/mcp/discoveryTools.ts177 // Step 3: Compute bbox and query region for each matched plugin.COMMENT
LOWsrc/app/api/mcp/discoveryTools.ts189 // Step 4: Pan camera when a session is active.COMMENT
LOWsrc/app/api/mcp/discoveryTools.ts202 // Step 5: Apply overall cap and record truncation metadata.COMMENT
LOWsrc/app/api/mcp/discoveryTools.ts210 // Step 6: Build prose summary using first matched plugin as representative.COMMENT
Verbosity Indicators8 hits · 16 pts
SeverityFileLineSnippetContext
LOWsrc/core/data/SmartFetcher.ts20 // Step 1: Try Direct Fetch (Fastest)COMMENT
LOWsrc/core/data/SmartFetcher.ts30 // Step 2: Local Server ProxyCOMMENT
LOWsrc/app/api/mcp/discoveryTools.ts145 // Step 1: Geocode the place name (limit 1 result).COMMENT
LOWsrc/app/api/mcp/discoveryTools.ts155 // Step 2: Find matching streaming plugins by case-insensitive substring.COMMENT
LOWsrc/app/api/mcp/discoveryTools.ts177 // Step 3: Compute bbox and query region for each matched plugin.COMMENT
LOWsrc/app/api/mcp/discoveryTools.ts189 // Step 4: Pan camera when a session is active.COMMENT
LOWsrc/app/api/mcp/discoveryTools.ts202 // Step 5: Apply overall cap and record truncation metadata.COMMENT
LOWsrc/app/api/mcp/discoveryTools.ts210 // Step 6: Build prose summary using first matched plugin as representative.COMMENT
Over-Commented Block15 hits · 15 pts
SeverityFileLineSnippetContext
LOWdocker/ci/docker-compose.plugin-ci.yml1# Reusable compose for plugin smoke CI (consumed by wwv-plugins repo).COMMENT
LOWdocker/ci/docker-compose.plugin-ci.yml21# ─── Stub seeder source ───COMMENT
LOWdocker/ci/docker-compose.seeder-ci.yml1# Reusable compose for seeder smoke CI (consumed by wwv-seeders-* repos).COMMENT
LOW.agents/hooks/planning-sync.sh1#!/usr/bin/env bashCOMMENT
LOWscripts/web-setup.sh1#!/usr/bin/env bashCOMMENT
LOW.github/workflows/publish-packages.yml1# Trigger model: merge to main with a version bump in the relevant package.json is theCOMMENT
LOWsrc/core/globe/hooks/useSatelliteFrustum.ts61 // Wait, Cesium cylinder geometry aligns its local Z axis with the global Z (North Pole)COMMENT
LOWsrc/app/api/health/route.ts1import { NextResponse } from "next/server";COMMENT
LOWsrc/app/api/mcp/pluginToolDispatch.test.ts261});COMMENT
LOWsrc/app/api/mcp/route.test.ts161});COMMENT
LOWsrc/app/api/mcp/route.ts121 // ------------------------------------------------------------------COMMENT
LOWsrc/app/api/mcp/route.ts161 // STATELESS INVARIANT: never hoist these to module scope.COMMENT
LOWsrc/app/api/mcp/route.ts181 // Phase 26: orientation prompts (INST-03, INST-04)COMMENT
LOWsrc/test/setup.ts1// Vitest setup file — intentionally empty after auth clean-up.COMMENT
LOWsrc/lib/apiKeyAuth.ts1import { randomBytes, createHmac, timingSafeEqual } from "crypto";COMMENT
Hyper-Verbose Identifiers12 hits · 12 pts
SeverityFileLineSnippetContext
LOWpackages/wwv-plugin-sdk/src/vite/wwvStaticCompiler.ts74function generateStaticPluginSource(manifest: any): string {CODE
LOWsrc/core/edition.ts136export function ticketAuthEnabledForPlugin(pluginId: string): boolean {CODE
LOWsrc/core/globe/types/GlobeCommand.ts46function isOptionalPluginOrLayerId(v: unknown): boolean {CODE
LOWsrc/app/setup/actions.ts153export async function activateProvisionedAccount(CODE
LOWsrc/app/api/mcp/globeCommandTools.ts62export function registerGlobeCommandTools(CODE
LOWsrc/app/api/mcp/pluginToolDispatch.ts58export async function registerPluginToolDispatch(CODE
LOW…components/marketplace/UnverifiedPluginBatchDialog.tsx13export default function UnverifiedPluginBatchDialog({CODE
LOWsrc/lib/mcpRateLimitConfig.ts74export async function checkMcpInvocationsRateLimit(CODE
LOWsrc/lib/cross-service/verify.ts7export function verifyCrossServiceSignature(CODE
LOWsrc/lib/auth/migrate-legacy-user.ts9export async function migrateLegacyUserIfNeeded(CODE
LOWsrc/lib/mcp/tools.ts47function resolveDataQueryEmptyReason(serviceReason: EmptyReason | undefined): EmptyReason {CODE
LOWsrc/lib/mcp/server.ts119export async function registerOrientationPrompts(CODE
Fake / Example Data6 hits · 6 pts
SeverityFileLineSnippetContext
LOWtests/tier-sync.spec.ts101 const body = { email: 'test@test.com' };CODE
LOWtests/ci/org-scoping.test.ts199 where: { email: "test@test.com" },CODE
LOWsrc/app/setup/actions.test.ts31 fd.set("email", overrides.email ?? "admin@example.com");CODE
LOWsrc/app/setup/page.tsx205 <input id="email" name="email" type="email" required className={styles.input} placeholder="adminCODE
LOWsrc/app/api/ba/[...all]/route.spec.ts54 body: JSON.stringify({ email: "test@test.com", password: "password" }),CODE
LOWsrc/app/login/LoginForm.tsx84 placeholder={isDemo ? "admin@worldwideview.local" : "admin@example.com"}CODE
Magic Placeholder Names1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHREADME.md170 "Authorization": "Bearer <your-api-key>"CODE
Modern AI Meta-Vocabulary2 hits · 5 pts
SeverityFileLineSnippetContext
MEDIUM.agents/rules/deployment-and-testing.md25pnpm run scaffold-osm-plugin <name> # Generate a new plugin from scaffoldCODE
MEDIUM.agents/skills/plugin-new/SKILL.md35## Stage 1: Isolated worktree + scaffoldCOMMENT
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOWself-host/setup.sh6# Check if docker is actually available and runningCOMMENT