Repository Analysis

simplifaisoul/osiris

Open Source Global Intelligence Platform - Real-Time OSINT Dashboard - A Palantir Alternative - We Get 0.5% on Volume Traded 2nZNHm3Lr9umG3DVrzYwHgktwkuKuJRXqqRqs3ewpump

3.9 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of simplifaisoul/osiris, a TypeScript project with 6,764 GitHub stars. SynthScan v2.0 examined 35,147 lines of code across 128 source files, recording 57 pattern matches distributed across 5 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
6.8K
Stars
TypeScript
Language
35.1K
Lines of Code
128
Files
57
Pattern Hits
2026-07-14
Scan Date
0.02
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 2MEDIUM 32LOW 23

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 57 distinct pattern matches across 5 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 Separators32 hits · 100 pts
SeverityFileLineSnippetContext
MEDIUMdeploy.sh2# =========================================================COMMENT
MEDIUMdeploy.sh5# =========================================================COMMENT
MEDIUMdeploy.sh11# =========================================================COMMENT
MEDIUMintel/server.js22// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js24// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js35// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js37// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js143// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js145// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js167// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js169// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js206// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js208// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js689// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js691// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js704// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js706// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js759// ════════════════════════════════════════════════════COMMENT
MEDIUMintel/server.js761// ════════════════════════════════════════════════════COMMENT
MEDIUMsrc/app/api/flights/route.ts325 // ── Phase 3: Regional fallback (when OpenSky unavailable) ─────────────────COMMENT
MEDIUMsrc/app/api/flights/route.ts350 // ── Classify ──────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/sdk/PolybolosClient.ts24// ── OSIRIS Feed → Entity Translators ───────────────────────────────COMMENT
MEDIUMsrc/lib/sdk/PolybolosClient.ts158// ── Main Client ────────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/sdk/LatticeAdapter.ts20// ── Lattice Raw Types (Simulated from Lattice SDK docs) ────────────COMMENT
MEDIUMsrc/lib/sdk/LatticeAdapter.ts41// ── Domain Mapping ─────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/sdk/LatticeAdapter.ts67// ── Adapter Class ──────────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/sdk/types.ts10// ── Domain Classification ──────────────────────────────────────────COMMENT
MEDIUMsrc/lib/sdk/types.ts46// ── Core Entity Interface ──────────────────────────────────────────COMMENT
MEDIUMsrc/lib/sdk/types.ts103// ── Lattice Integration Types ──────────────────────────────────────COMMENT
MEDIUMsrc/lib/sdk/types.ts134// ── SDK Client Types ───────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/sdk/types.ts156// ── Stream Event Types ─────────────────────────────────────────────COMMENT
MEDIUMsrc/lib/sdk/types.ts171// ── Ingestion Types (External Push) ────────────────────────────────COMMENT
Verbosity Indicators11 hits · 14 pts
SeverityFileLineSnippetContext
LOWintel/server.js322 // Step 3: Add aircraft model infoCOMMENT
LOWintel/server.js329 // Step 4: Cross-ref sanctions on airline name + callsignCOMMENT
LOWintel/server.js251 // Step 1: Decode ICAO airline prefix from callsign (e.g. TRK → Turkish Airlines)COMMENT
LOWintel/server.js295 // Step 2: Decode registration prefix → country (e.g. TC → Turkey, N → USA, G → UK)COMMENT
LOWintel/server.js478 // Step 1: ip-api.com — geolocation, ISP, ASN, proxy/hosting detectionCOMMENT
LOWintel/server.js536 // Step 2: RIPEstat WHOISCOMMENT
LOWintel/server.js557 // Step 3: RIPEstat Abuse ContactCOMMENT
LOWintel/server.js576 // Step 4: RIPEstat Network InfoCOMMENT
LOWsrc/app/api/region-dossier/route.ts15 // Step 1: Reverse geocode to get country (must complete first — other steps depend on it)COMMENT
LOWsrc/app/api/region-dossier/route.ts45 // Step 2: Fetch Wikipedia summaryCOMMENT
LOWsrc/app/api/region-dossier/route.ts66 // Step 3: Fetch all country info & head of state from Wikidata SPARQLCOMMENT
Structural Annotation Overuse11 hits · 14 pts
SeverityFileLineSnippetContext
LOWintel/server.js322 // Step 3: Add aircraft model infoCOMMENT
LOWintel/server.js329 // Step 4: Cross-ref sanctions on airline name + callsignCOMMENT
LOWintel/server.js251 // Step 1: Decode ICAO airline prefix from callsign (e.g. TRK → Turkish Airlines)COMMENT
LOWintel/server.js295 // Step 2: Decode registration prefix → country (e.g. TC → Turkey, N → USA, G → UK)COMMENT
LOWintel/server.js478 // Step 1: ip-api.com — geolocation, ISP, ASN, proxy/hosting detectionCOMMENT
LOWintel/server.js536 // Step 2: RIPEstat WHOISCOMMENT
LOWintel/server.js557 // Step 3: RIPEstat Abuse ContactCOMMENT
LOWintel/server.js576 // Step 4: RIPEstat Network InfoCOMMENT
LOWsrc/app/api/region-dossier/route.ts15 // Step 1: Reverse geocode to get country (must complete first — other steps depend on it)COMMENT
LOWsrc/app/api/region-dossier/route.ts45 // Step 2: Fetch Wikipedia summaryCOMMENT
LOWsrc/app/api/region-dossier/route.ts66 // Step 3: Fetch all country info & head of state from Wikidata SPARQLCOMMENT
Synthetic Comment Markers2 hits · 10 pts
SeverityFileLineSnippetContext
HIGHsrc/components/OsirisMap.tsx1403 color: '#1976D2', // Darker blue as requested, more transparent in layer paintCODE
HIGHsrc/components/OsirisMap.tsx1403 color: '#1976D2', // Darker blue as requested, more transparent in layer paintCODE
Over-Commented Block1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdeploy.sh1#!/bin/bashCOMMENT