Repository Analysis

permissionlesstech/bitchat

bluetooth mesh chat, IRC vibes

2.8 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of permissionlesstech/bitchat, a Swift project with 26,109 GitHub stars. SynthScan v2.0 examined 124,164 lines of code across 511 source files, recording 281 pattern matches distributed across 4 syntactic categories. The overall adjusted score of 2.8 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.8
Adjusted Score
2.8
Raw Score
100%
Time Factor
2026-07-12
Last Push
26.1K
Stars
Swift
Language
124.2K
Lines of Code
511
Files
281
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 23LOW 258

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 281 distinct pattern matches across 4 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 Block253 hits · 253 pts
SeverityFileLineSnippetContext
LOW.periphery.yml1# Periphery dead-code scan configuration (https://github.com/peripheryapp/periphery)COMMENT
LOWbitchat/ViewModels/ChatLiveVoiceCoordinator.swift61/// Where a live voice burst lives: a Noise DM or the public mesh timeline.COMMENT
LOWbitchat/ViewModels/ChatLiveVoiceCoordinator.swift141 private var fileManager: FileManager { fileStore.fileManager }COMMENT
LOWbitchat/ViewModels/ChatOutgoingCoordinator.swift41 /// coordinator never reads it.)COMMENT
LOW…at/ViewModels/ChatPrivateConversationCoordinator.swift1import BitFoundationCOMMENT
LOWbitchat/ViewModels/ChatViewModel.swift1//COMMENT
LOWbitchat/ViewModels/ChatViewModel.swift21/// - Command processingCOMMENT
LOWbitchat/ViewModels/ChatViewModel.swift41/// - Supports verified fingerprints for secure communicationCOMMENT
LOWbitchat/ViewModels/ChatViewModel.swift61/// - SwiftUI automatically optimizes UI updatesCOMMENT
LOWbitchat/ViewModels/ChatViewModel.swift121 // MARK: - Published PropertiesCOMMENT
LOWbitchat/ViewModels/ChatViewModel.swift181 lazy var verificationCoordinator = ChatVerificationCoordinator(context: self)COMMENT
LOWbitchat/ViewModels/PublicMessagePipeline.swift1//COMMENT
LOWbitchat/ViewModels/GeoChannelCoordinator.swift1//COMMENT
LOWbitchat/ViewModels/ChatPeerIdentityCoordinator.swift1import BitFoundationCOMMENT
LOWbitchat/ViewModels/ChatPeerIdentityCoordinator.swift101 func sendFavoriteNotificationViaNostr(noisePublicKey: Data, isFavorite: Bool)COMMENT
LOWbitchat/ViewModels/ChatNostrCoordinator.swift21 func sendGeohashDeliveryAck(for messageID: String, toRecipientHex recipientHex: String, from identity: NostrIdentityCOMMENT
LOW…hat/ViewModels/ChatPublicConversationCoordinator.swift1import BitFoundationCOMMENT
LOW…hat/ViewModels/ChatPublicConversationCoordinator.swift101COMMENT
LOWbitchat/ViewModels/ChatVerificationCoordinator.swift61 func sendVerifyChallenge(to peerID: PeerID, noiseKeyHex: String, nonceA: Data)COMMENT
LOWbitchat/ViewModels/ChatViewModelBootstrapper.swift201 }COMMENT
LOWbitchat/ViewModels/ChatDeliveryCoordinator.swift1import BitFoundationCOMMENT
LOWbitchat/ViewModels/ChatPeerListCoordinator.swift1import BitFoundationCOMMENT
LOWbitchat/App/NearbyNotesCounter.swift1//COMMENT
LOWbitchat/App/ConversationStore.swift1//COMMENT
LOWbitchat/App/ConversationStore.swift221COMMENT
LOWbitchat/App/ConversationStore.swift321COMMENT
LOWbitchat/App/ConversationStore.swift341 /// in TWO direct conversations: step 2's raw per-peer keying mirrors aCOMMENT
LOWbitchat/App/ConversationStore.swift641 // MARK: DiagnosticsCOMMENT
LOWbitchat/Identity/SecureIdentityStateManager.swift1//COMMENT
LOWbitchat/Identity/SecureIdentityStateManager.swift21/// - Thread-safe access patternsCOMMENT
LOWbitchat/Identity/SecureIdentityStateManager.swift41/// - No cloud sync or backupCOMMENT
LOWbitchat/Identity/SecureIdentityStateManager.swift61///COMMENT
LOWbitchat/Identity/SecureIdentityStateManager.swift81/// - Users can disable all persistenceCOMMENT
LOWbitchat/Identity/SecureIdentityStateManager.swift161 // Pending-save coalescing flag. Reads/writes are serialized on `queue`.COMMENT
LOWbitchat/Identity/IdentityModels.swift1//COMMENT
LOWbitchat/Identity/IdentityModels.swift21/// This separation allows users to maintain stable cryptographic identitiesCOMMENT
LOWbitchat/Identity/IdentityModels.swift41/// - Favorite/blocked statusCOMMENT
LOWbitchat/Identity/IdentityModels.swift61/// 2. System looks up social identity by fingerprintCOMMENT
LOWbitchat/Identity/IdentityModels.swift121 var isBlocked: BoolCOMMENT
LOWbitchat/Features/voice/PTTBurstPlayer.swift1//COMMENT
LOWbitchat/Features/voice/PTTBurstPlayer.swift141 }COMMENT
LOWbitchat/Features/voice/VoiceCaptureSession.swift1//COMMENT
LOWbitchat/Features/voice/PTTAudioFormat.swift1//COMMENT
LOWbitchat/Features/voice/AudioSessionCoordinator.swift1//COMMENT
LOWbitchat/Features/voice/AudioSessionCoordinator.swift21/// main thread.COMMENT
LOWbitchat/Features/voice/AudioSessionCoordinator.swift41/// not yank the route out from under live playback);COMMENT
LOWbitchat/Features/voice/AudioSessionCoordinator.swift241 /// finalize any artifacts, and release — resuming means acquiring again.COMMENT
LOWbitchat/Features/voice/PTTCaptureEngine.swift1//COMMENT
LOWbitchat/Features/voice/PTTCaptureEngine.swift81/// Captures microphone audio for a live push-to-talk burst, producing both:COMMENT
LOWbitchat/Features/voice/PTTSettings.swift1//COMMENT
LOWbitchat/Utils/SystemSettings.swift1//COMMENT
LOWbitchat/Models/RequestSyncPacket.swift1import BitFoundationCOMMENT
LOWbitchat/Models/CommandInfo.swift1//COMMENT
LOWbitchat/Noise/NoiseProtocol.swift1//COMMENT
LOWbitchat/Noise/NoiseProtocol.swift21/// - Protection against replay attacksCOMMENT
LOWbitchat/Noise/NoiseProtocol.swift41/// --------- ---------COMMENT
LOWbitchat/Noise/NoiseProtocol.swift61/// pattern: .XX,COMMENT
LOWbitchat/Sync/GossipMessageArchive.swift1//COMMENT
LOWbitchat/Sync/RequestSyncManager.swift1//COMMENT
LOWbitchat/Sync/SyncTypeFlags.swift41 // the bitfield little-endian with trailing zero bytes trimmed (bit 10COMMENT
193 more matches not shown…
AI Slop Vocabulary22 hits · 84 pts
SeverityFileLineSnippetContext
MEDIUMbitchat/Services/BLE/BLEAnnounceHandler.swift204 // Persist cryptographic identity and signing key for robust offlineCOMMENT
MEDIUM…tFoundation/Sources/BitFoundation/BinaryProtocol.swift257 // Try decode as-is first (robust when padding wasn't applied)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift81 #expect(harness.lines.isEmpty)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift94 #expect(harness.lines.isEmpty)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift103 #expect(harness.lines.isEmpty)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift106 #expect(harness.lines.count == 1)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift107 #expect(harness.lines[0].geohash == "9q8yy")COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift108 #expect(harness.lines[0].content.contains("road closed"))COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift109 #expect(harness.lines[0].content.contains("@alice"))COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift122 #expect(harness.lines.isEmpty)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift135 #expect(harness.lines.count == 1)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift136 #expect(harness.lines[0].content.contains("3"))COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift137 #expect(harness.pendingFlushes.isEmpty)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift149 #expect(harness.lines.count == 2)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift150 #expect(Set(harness.lines.map(\.geohash)) == ["9q8yy", ""])COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift164 #expect(harness.lines.count == 1)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift165 #expect(!harness.lines[0].content.contains("2"))COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift192 #expect(harness.pendingFlushes.count == 1)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift198 #expect(harness.lines.isEmpty)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift211 #expect(harness.lines.count == 1)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift212 #expect(harness.lines[0].content.count < 200)COMMENT
MEDIUMbitchatTests/Services/BoardAlertsModelTests.swift213 #expect(harness.lines[0].content.contains("…"))COMMENT
Fake / Example Data5 hits · 6 pts
SeverityFileLineSnippetContext
LOWbitchat/_PreviewHelpers/BitchatMessage+Preview.swift16 sender: "John Doe",CODE
LOWbitchat/_PreviewHelpers/BitchatMessage+Preview.swift22 recipientNickname: "Jane Doe",CODE
LOWbitchat/Views/Components/DeliveryStatusView.swift131 .delivered(to: "John Doe", at: Date()),CODE
LOWbitchat/Views/Components/DeliveryStatusView.swift132 .read(by: "Jane Doe", at: Date()),CODE
LOWbitchatTests/ProtocolContractTests.swift115 #expect(preview.sender == "John Doe")COMMENT
Modern AI Meta-Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMbitchat/Services/VerificationService.swift118 // MARK: - Noise payloads (scaffold only)COMMENT