Repository Analysis

LiveContainer/LiveContainer

Run iOS apps without actually installing them!

2.6 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of LiveContainer/LiveContainer, a Swift project with 10,085 GitHub stars. SynthScan v2.0 examined 37,906 lines of code across 165 source files, recording 78 pattern matches distributed across 3 syntactic categories. The overall adjusted score of 2.6 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).

2.6
Adjusted Score
2.6
Raw Score
100%
Time Factor
2026-07-14
Last Push
10.1K
Stars
Swift
Language
37.9K
Lines of Code
165
Files
78
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 0MEDIUM 21LOW 57

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

Over-Commented Block54 hits · 54 pts
SeverityFileLineSnippetContext
LOWShareExtension/ShareExtension-Bridging-Header.h1#import "LCShareExtensionLauncher.h"COMMENT
LOW…ontainerSwiftUI/LiveContainerSwiftUI-Bridging-Header.h1//COMMENT
LOWLiveContainerSwiftUI/Utilities/archive.h61/* Older code relied on the __LA_INT64_T macro; after 4.0 we'll switch to the typedef exclusively. */COMMENT
LOWLiveContainerSwiftUI/Utilities/archive.h81# if ARCHIVE_VERSION_NUMBER < 4000000COMMENT
LOWLiveContainerSwiftUI/Utilities/archive.h101#include "android_lf.h"COMMENT
LOWLiveContainerSwiftUI/Utilities/archive.h121# endifCOMMENT
LOWLiveContainerSwiftUI/Utilities/archive.h261 */COMMENT
LOWLiveContainerSwiftUI/Utilities/archive.h281#define ARCHIVE_FILTER_LZ4 13COMMENT
LOWLiveContainerSwiftUI/Utilities/archive.h321#define ARCHIVE_FORMAT_CPIO_AFIO_LARGE (ARCHIVE_FORMAT_CPIO | 6)COMMENT
LOWLiveContainerSwiftUI/Utilities/archive_entry.h41 */COMMENT
LOWLiveContainerSwiftUI/Utilities/archive_entry.h61#include <unistd.h>COMMENT
LOWLiveContainerSwiftUI/Utilities/archive_entry.h81typedef __int64 la_ssize_t;COMMENT
LOWLiveContainerSwiftUI/Utilities/archive_entry.h101/* Large file support for Android */COMMENT
LOWLiveContainerSwiftUI/Utilities/archive_entry.h121# elseCOMMENT
LOWLiveContainerSwiftUI/Utilities/archive_entry.h181 * In libarchive 4.0, we can drop the casts here.COMMENT
LOWLiveContainerSwiftUI/Utilities/archive_entry.h421 * complete set of ACL support routines.COMMENT
LOWLiveProcess/main.m1//COMMENT
LOWLiveContainer/LCBootstrap.m1#import "FoundationPrivate.h"COMMENT
LOWLiveContainer/dyld_bypass_validation.m1// Based on: https://blog.xpnsec.com/restoring-dyld-memory-loadingCOMMENT
LOWLiveContainer/Tweaks/NSFileManager+GuestHooks.m1@import Foundation;COMMENT
LOWLiveContainer/Tweaks/NSUserDefaults.m1//COMMENT
LOWLiveContainer/Tweaks/Dead10ccFix.m1//COMMENT
LOWLiveContainer/Tweaks/mach_excServer.c21#if !defined(__MigTypeCheck) && defined(TypeCheck)COMMENT
LOWLiveContainer/Tweaks/mach_excServer.c41#if !defined(_WALIGNSZ_)COMMENT
LOWLiveContainer/Tweaks/mach_excServer.c61#ifndef __AfterRcvRpcCOMMENT
LOWLiveContainer/Tweaks/SecItem.m1//COMMENT
LOWLiveContainer/Tweaks/mach_excServer.h1#ifndef _mach_exc_server_COMMENT
LOWLiveContainer/Tweaks/mach_excServer.h21#ifndef USING_VOUCHERSCOMMENT
LOWLiveContainer/Tweaks/mach_excServer.h41/* END VOUCHER CODE */COMMENT
LOWLiveContainer/Tweaks/mach_excServer.h81COMMENT
LOWLiveContainer/Tweaks/Dyld.m1//COMMENT
LOWMultitaskSupport/ResizeHandleView.h1//COMMENT
LOWMultitaskSupport/AppSceneViewController.m1//COMMENT
LOWLaunchAppExtension/LaunchAppExtension-Bridging-Header.h1//COMMENT
LOWSideStore/SideStore-Bridging-Header.h1#ifndef SideStore_Bridging_Header_h_hCOMMENT
LOWZSign/zsign.hpp1//COMMENT
LOWZSign/zsign.mm1#include "zsign.hpp"COMMENT
LOWZSign/Utils.hpp1//COMMENT
LOWZSign/common/common.h1#pragma onceCOMMENT
LOWZSign/common/common.h21COMMENT
LOWZSign/common/common.h41#include <memory>COMMENT
LOWZSign/common/mach-o.h21#define CPU_TYPE_I386 CPU_TYPE_X86 /* compatibility */COMMENT
LOWZSign/common/mach-o.h61#define CPU_SUBTYPE_BIG_ENDIAN 1COMMENT
LOWZSign/common/mach-o.h81#define CPU_SUBTYPE_PENTIUM_3_M CPU_SUBTYPE_INTEL(8, 1)COMMENT
LOWZSign/common/mach-o.h101#define CPU_SUBTYPE_X86_ALL 3COMMENT
LOWZSign/common/mach-o.h121#define CPU_SUBTYPE_ARM_V7M 15COMMENT
LOWZSign/common/mach-o.h141#define MH_OBJECT 0x1 /* relocatable object file */COMMENT
LOWZSign/common/mach-o.h161#define MH_TWOLEVEL 0x00000080COMMENT
LOWZSign/common/mach-o.h181COMMENT
LOWZSign/common/mach-o.h201#define LC_SUB_UMBRELLA 0x00000013COMMENT
LOWZSign/common/mach-o.h221#define LC_FUNCTION_STARTS 0x00000026COMMENT
LOWZSign/common/mach-o.h241 in it and nothing relocated to it, that isCOMMENT
LOWZSign/common/mach-o.h261#define S_MOD_INIT_FUNC_POINTERS 0x09COMMENT
LOWZSign/common/json.cpp1#include "json.h"COMMENT
Excessive Try-Catch Wrapping22 hits · 44 pts
SeverityFileLineSnippetContext
MEDIUM…veContainerSwiftUI/Views/Settings/LCSettingsView.swift499 print("Error copying embedded.mobileprovision: \(error)")CODE
MEDIUM…veContainerSwiftUI/Views/Settings/LCSettingsView.swift512 print("Error writing certData to cert.p12: \(error)")CODE
MEDIUM…veContainerSwiftUI/Views/Settings/LCSettingsView.swift525 print("Error writing certPassword to pass.txt: \(error)")CODE
MEDIUM…veContainerSwiftUI/Views/Settings/LCSettingsView.swift541 print("Error copying main bundle \(error)")CODE
MEDIUM…veContainerSwiftUI/Views/Settings/LCSettingsView.swift682 print("Error copying dyld \(error)")CODE
MEDIUM.github/update_json.py28 print(f"Error fetching releases: {e}")CODE
MEDIUM.github/update_json.py37 print(f"Error getting file size: {e}")CODE
MEDIUM.github/update_json.py44 print("Error getting latest release")CODE
MEDIUM.github/update_json.py53 print(f"Error reading JSON file: {e}")CODE
MEDIUM.github/update_json.py81 print("Error: IPA file not found in release assets.")CODE
MEDIUM.github/update_json.py132 print(f"Error writing to JSON file: {e}")CODE
MEDIUM.github/update_json.py139 print("Error getting nightly release")CODE
MEDIUM.github/update_json.py146 print(f"Error reading JSON file: {e}")CODE
MEDIUM.github/update_json.py182 print("Error: IPA file not found in release assets.")STRING
MEDIUM.github/update_json.py215 print(f"Error writing to JSON file: {e}")STRING
MEDIUM.github/update_json.py222 print("Error getting latest release")STRING
MEDIUM.github/update_json.py231 print(f"Error reading JSON file: {e}")STRING
MEDIUM.github/update_json.py263 print("Error: IPA file not found in release assets.")STRING
MEDIUM.github/update_json.py326 print(f"Error writing to JSON file: {e}")STRING
LOW.github/update_json.py344 except Exception as e:STRING
MEDIUM.github/update_json.py345 print(f"An error occurred: {e}")STRING
MEDIUM.github/update_json.py31def get_file_size(url):CODE
Hyper-Verbose Identifiers2 hits · 2 pts
SeverityFileLineSnippetContext
LOWLiveContainerSwiftUI/Utilities/Shared.swift109class DataManager {CODE
LOW.github/update_json.py218def update_json_file_release_ss_lc(repo_url, json_file, latest_release, is_nightly: bool):STRING