Repository Analysis

microsoft/Ontology-Playground

Free, open-source web app for learning about ontologies and Microsoft Fabric IQ. Explore a catalogue of pre-built ontologies, design your own visually, export as RDF/XML, and share interactive diagrams. Zero backend, fully static.

5.3 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of microsoft/Ontology-Playground, a TypeScript project with 2,308 GitHub stars. SynthScan v2.0 examined 41,456 lines of code across 304 source files, recording 86 pattern matches distributed across 6 syntactic categories. The overall adjusted score of 5.3 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).

5.3
Adjusted Score
5.3
Raw Score
100%
Time Factor
2026-08-01
Last Push
2.3K
Stars
TypeScript
Language
41.5K
Lines of Code
304
Files
86
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 0MEDIUM 61LOW 25

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 86 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 Separators59 hits · 177 pts
SeverityFileLineSnippetContext
MEDIUMscripts/generate-lab-catalogue.ts20// ── Entity Type Definitions ──────────────────────────────────────COMMENT
MEDIUMscripts/generate-lab-catalogue.ts177// ── Relationship Definitions ────────────────────────────────────COMMENT
MEDIUMscripts/generate-lab-catalogue.ts281// ── Step definitions ────────────────────────────────────────────COMMENT
MEDIUMscripts/generate-lab-catalogue.ts370// ── Generate files ──────────────────────────────────────────────COMMENT
MEDIUMsrc/App.tsx142 // ── Global keyboard shortcuts ──────────────────────────COMMENT
MEDIUMsrc/App.tsx169 // ── Command palette items ──────────────────────────────COMMENT
MEDIUMsrc/components/GalleryModal.tsx556// ─── Highlighted RDF source (gallery cards) ──────────────────────────────────COMMENT
MEDIUMsrc/components/LearnPage.tsx933 // ── Title bar ──────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/LearnPage.tsx1037 // ── Graph area (both views stacked absolutely) ─────────────────COMMENT
MEDIUMsrc/components/EmbedWidget.tsx33// ─── Theme tokens ────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/EmbedWidget.tsx57// ─── Component ───────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/EmbedWidget.tsx77 // ─ Load ontology ────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/EmbedWidget.tsx133 // ─ Render ───────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/EmbedWidget.tsx201// ─── Header ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/EmbedWidget.tsx256// ─── Graph ───────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/EmbedWidget.tsx352// ─── RDF Source ──────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/EmbedWidget.tsx372// ─── Inspector overlay ───────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/designer/DesignerPreview.tsx49// ─── Graph tab ───────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/designer/DesignerPreview.tsx224// ─── RDF tab ─────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/shareCodec.ts20// ── helpers ──────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/shareCodec.ts37// ── public API ───────────────────────────────────────────COMMENT
MEDIUMsrc/lib/github.ts29// ─── Types ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/github.ts59// ─── Token storage ──────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/github.ts87// ─── Device Flow ────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/github.ts166// ─── GitHub API helpers ─────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/github.ts303// ─── High-level submit flow ─────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/github.test.ts12// ─── Token storage ──────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/github.test.ts33// ─── Device flow ────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/github.test.ts73// ─── pollForToken ───────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/github.test.ts122// ─── getUser ────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/github.test.ts145// ─── submitToCatalogue ──────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/fabric.ts12// ─── Fabric API types ──────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/fabric.ts73// ─── ID generation ─────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/fabric.ts89// ─── Type mapping ──────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/fabric.ts106// ─── Conversion ────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/fabric.ts245// ─── Fabric REST API client ────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/fabric.ts351// ─── Public API ────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/shareCodec.test.ts101// ── Security tests ───────────────────────────────────────COMMENT
MEDIUMsrc/lib/fabric.test.ts284// ─── Network layer (issue #68) ──────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/fabric.test.ts284// ─── Network layer (issue #68) ──────────────────────────────────────────────COMMENT
MEDIUMsrc/a11y/themeContrast.test.ts64// ── Stat-card metric tiles (OntologyStatsPanel) ──────────────────────────────COMMENT
MEDIUMsrc/a11y/themeContrast.test.ts116// ── Amber foreground token (--ms-yellow-fg) ──────────────────────────────────COMMENT
MEDIUMsrc/a11y/themeContrast.test.ts154// ── Progress-bar fill vs track (SC 1.4.11) ───────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.ts11// ─── Validation ──────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.ts19// ─── Fabric IQ naming rules ─────────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.ts135// ─── ID helpers ──────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.ts156// ─── Default palette ─────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.ts168// ─── History helpers ─────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.ts183// ─── Store ───────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.ts248 // ─ Metadata ─────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.ts255 // ─ Entities ─────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.ts303 // ─ Properties ───────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.ts363 // ─ Relationships ────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.ts449 // ─ Bulk ─────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.ts462 // ─ Undo / Redo ─────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.test.ts10// ─── validateOntology (pure function) ────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.test.ts224// ─── isValidFabricIQName helper ──────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.test.ts261// ─── Store actions ───────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/store/designerStore.test.ts419// ─── Undo / Redo ─────────────────────────────────────────────────────────────COMMENT
Structural Annotation Overuse19 hits · 34 pts
SeverityFileLineSnippetContext
LOW…tology-fundamentals/04-building-your-first-ontology.md13## Step 1: Open the designerCOMMENT
LOW…tology-fundamentals/04-building-your-first-ontology.md17## Step 2: Create entity typesCOMMENT
LOW…tology-fundamentals/04-building-your-first-ontology.md50## Step 3: Add relationshipsCOMMENT
LOW…tology-fundamentals/04-building-your-first-ontology.md61## Step 4: ValidateCOMMENT
LOW…tology-fundamentals/04-building-your-first-ontology.md69## Step 5: Preview the RDFCOMMENT
LOW…tology-fundamentals/04-building-your-first-ontology.md77## Step 6: ExportCOMMENT
LOWdocs/contributing-ontology-from-design-to-github.md33## Step 1: Design in Ontology PlaygroundCOMMENT
LOWdocs/contributing-ontology-from-design-to-github.md48## Step 2: Export RDFCOMMENT
LOWdocs/contributing-ontology-from-design-to-github.md62## Step 3: Choose the Contribution TypeCOMMENT
LOWdocs/contributing-ontology-from-design-to-github.md89## Step 4: Create metadata.jsonCOMMENT
LOWdocs/contributing-ontology-from-design-to-github.md114## Step 5: Validate LocallyCOMMENT
LOWdocs/contributing-ontology-from-design-to-github.md139## Step 6: Commit and Open a Pull RequestCOMMENT
LOWdocs/authoring-guide.md267### Step 1: Identify your entitiesCOMMENT
LOWdocs/authoring-guide.md276### Step 2: Define propertiesCOMMENT
LOWdocs/authoring-guide.md288### Step 3: Define relationshipsCOMMENT
LOWdocs/authoring-guide.md300### Step 4: Pick icons and colorsCOMMENT
LOWdocs/authoring-guide.md310### Step 5: Create in the designer or write RDFCOMMENT
LOWdocs/authoring-guide.md318### Step 6: Test the experienceCOMMENT
LOWdocs/authoring-guide.md327### Step 7: SubmitCOMMENT
AI Slop Vocabulary2 hits · 4 pts
SeverityFileLineSnippetContext
MEDIUMpublic/learn.json186 "html": "<h2>Closing the loop</h2>\n<p>The first three steps built reference data: industry, geography, and loCODE
MEDIUMpublic/learn.json449 "html": "<h2>What we'll build</h2>\n<p>In this tutorial, you'll create a simple <strong>Library</strong> ontolCODE
Hyper-Verbose Identifiers4 hits · 4 pts
SeverityFileLineSnippetContext
LOWscripts/list-changed-catalogue-entries.ts79function changedCataloguePreviewPaths(diffOutput: string): string[] {CODE
LOWsrc/components/InspectorPanel.test.tsx6function setupDataBindingQuestStep() {CODE
LOWsrc/data/questQueryValidator.ts16export function extractQueryFromInstruction(instruction: string): string | null {CODE
LOWsrc/data/questGenerator.ts10export function generateQuestsForOntology(ontology: Ontology): Quest[] {CODE
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWsrc/lib/fabric.test.ts313 const token = 'fake-token';CODE
Over-Commented Block1 hit · 1 pts
SeverityFileLineSnippetContext
LOWsrc/a11y/themeTokens.ts1/// <reference types="node" />COMMENT