Repository Analysis

firezone/firezone

Enterprise-ready zero-trust access platform built on WireGuard®.

2.4 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of firezone/firezone, a Elixir project with 8,727 GitHub stars. SynthScan v2.0 examined 148,784 lines of code across 865 source files, recording 271 pattern matches distributed across 11 syntactic categories. The overall adjusted score of 2.4 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.4
Adjusted Score
2.4
Raw Score
100%
Time Factor
2026-07-14
Last Push
8.7K
Stars
Elixir
Language
148.8K
Lines of Code
865
Files
271
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 2MEDIUM 26LOW 243

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 271 distinct pattern matches across 11 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 Block222 hits · 222 pts
SeverityFileLineSnippetContext
LOWdocker-compose.yml421 set -eCOMMENT
LOWelixir/priv/static/robots.txt1# See http://www.robotstxt.org/robotstxt.html for documentation on how to use the robots.txt fileCOMMENT
LOWelixir/assets/js/popover.js1// A standalone popover/tooltip controller.COMMENT
LOWrust/deny.toml1# This template contains all of the possible sections and their default valuesCOMMENT
LOWrust/deny.toml41COMMENT
LOWrust/deny.toml61# If true, metadata will be collected with `--all-features`. Note that this can'tCOMMENT
LOWrust/deny.toml121 #"RUSTSEC-0000-0000",COMMENT
LOWrust/deny.toml181COMMENT
LOWrust/deny.toml201# More documentation about the 'bans' section can be found here:COMMENT
LOWrust/deny.toml221external-default-features = "allow"COMMENT
LOWrust/deny.toml241# Features to not allowCOMMENT
LOWrust/deny.toml301 "windows-targets",COMMENT
LOWrust/gui-client/src-tauri/build.rs21/// Must match `<Application Id="…"/>` in `win_files/AppxManifest.xml`.COMMENT
LOWrust/gui-client/src-tauri/src/ipc.rs41pub struct WrongUser;COMMENT
LOWrust/gui-client/src-tauri/src/ipc.rs61/// UDS support, so in a year or two we might be better off making it UDSCOMMENT
LOWrust/gui-client/src-tauri/src/launch_lock.rs1//! Advisory file lock used to coordinate first-instance detection.COMMENT
LOWrust/gui-client/src-tauri/src/launch_lock.rs41 /// We acquired the exclusive lock and are the running firstCOMMENT
LOWrust/gui-client/src-tauri/src/lib.rs21pub mod launch_lock;COMMENT
LOWrust/gui-client/src-tauri/src/lib.rs41COMMENT
LOWrust/gui-client/src-tauri/src/service.rs861#[cfg(debug_assertions)]COMMENT
LOWrust/gui-client/src-tauri/src/gui.rs581 server: ipc::Server,COMMENT
LOWrust/gui-client/src-tauri/src/package_identity.rs1//! Ensures the GUI process carries the Firezone sparse-MSIX packageCOMMENT
LOWrust/gui-client/src-tauri/src/package_identity.rs21#[error("Registered package identity for the current user; a restart is required")]COMMENT
LOWrust/gui-client/src-tauri/src/package_identity.rs41/// package for the current user (no admin needed once provisioned).COMMENT
LOWrust/gui-client/src-tauri/src/package_identity.rs81/// [`InstallationCorrupt`].COMMENT
LOWrust/gui-client/src-tauri/src/settings.rs21#[cfg(target_os = "macos")]COMMENT
LOWrust/gui-client/src-tauri/src/mdm_migration.rs1//! One-shot migration of MDM policy values from the per-userCOMMENT
LOW…gui-client/src-tauri/src/bin/firezone-client-tunnel.rs61 /// Maximum length of time to retry connecting to the portal if we're having internet issues orCOMMENT
LOW…st/gui-client/src-tauri/src/bin/firezone-gui-client.rs261 /// Crash the `Controller` task to test error handlingCOMMENT
LOW…st/gui-client/src-tauri/src/bin/firezone-gui-client.rs281 test_update_notification: bool,COMMENT
LOW…st/gui-client/src-tauri/src/bin/firezone-gui-client.rs361 SmokeTest,COMMENT
LOWrust/gui-client/src-tauri/src/bin/register-sparse.rs1//! WiX deferred custom actions that register / deregister theCOMMENT
LOWrust/gui-client/src-tauri/src/bin/register-sparse.rs101 "register-sparse failed"COMMENT
LOWrust/gui-client/src-tauri/src/bin/register-sparse.rs201 /// for all users, so every account (including `LocalSystem` andCOMMENT
LOWrust/gui-client/src-tauri/src/bin/register-sparse.rs281 tracing::info!(pfn = %pfn.to_string_lossy(), "calling DeprovisionPackageForAllUsersAsync");COMMENT
LOWrust/gui-client/src-tauri/src/gui/os_windows.rs41}COMMENT
LOWrust/gui-client/src-tauri/src/gui/system_tray.rs21mod builder;COMMENT
LOW…gui-client/src-tauri/src/gui/system_tray/compositor.rs21COMMENT
LOW…st/gui-client/src-tauri/src/gui/system_tray/builder.rs21 Separator,COMMENT
LOW…st/gui-client/src-tauri/src/gui/system_tray/builder.rs61 AddFavorite(ResourceId),COMMENT
LOWrust/gui-client/src-tauri/src/ipc/windows.rs21 },COMMENT
LOWrust/gui-client/src-tauri/src/ipc/windows.rs41/// because the GUI is a *full-trust* packaged app: it runs as theCOMMENT
LOWrust/gui-client/src-tauri/src/ipc/windows.rs61///COMMENT
LOWrust/gui-client/src-tauri/src/ipc/windows.rs281 };COMMENT
LOWrust/gui-client/src-tauri/src/ipc/windows.rs301/// of our pipe *while the legit server is bound*, but during the brief windowCOMMENT
LOWrust/gui-client/src-tauri/src/ipc/unix/peer_check.rs1//! Verify that the peer of a connected Unix Domain Socket is a FirezoneCOMMENT
LOW…/gui-client/src-tauri/src/ipc/unix/peer_check/linux.rs41 /// `anyhow::Error` describing why on reject.COMMENT
LOWrust/tests/gui-smoke-test/src/main.rs21/// to this hardcoded path. The deb/rpm package installs the GUI there;COMMENT
LOWrust/tests/loadtest/loadtest.example.toml1# Loadtest ConfigurationCOMMENT
LOWrust/tests/loadtest/loadtest.example.toml61# [turn]COMMENT
LOWrust/tests/loadtest/tests/echo_integration.rs1// #![allow(clippy::unwrap_used)]COMMENT
LOWrust/tests/loadtest/tests/echo_integration.rs21// self.0.kill().ok();COMMENT
LOWrust/tests/loadtest/tests/echo_integration.rs41// .port()COMMENT
LOWrust/tests/loadtest/tests/echo_integration.rs61// .env("RUST_LOG", "warn")COMMENT
LOWrust/tests/loadtest/tests/echo_integration.rs81// .spawn()COMMENT
LOWrust/tests/loadtest/tests/echo_integration.rs101// panic!(COMMENT
LOWrust/tests/loadtest/tests/echo_integration.rs121// });COMMENT
LOWrust/tests/loadtest/tests/echo_integration.rs141COMMENT
LOWrust/tests/loadtest/tests/echo_integration.rs161// }COMMENT
LOWrust/tests/loadtest/tests/echo_integration.rs181// &target,COMMENT
162 more matches not shown…
Decorative Section Separators22 hits · 68 pts
SeverityFileLineSnippetContext
MEDIUMelixir/README.md26# --------------------COMMENT
MEDIUMelixir/README.md30# ---------------------------------------------------------COMMENT
MEDIUMelixir/README.md35# ---------------------COMMENT
MEDIUMelixir/README.md39# ------------------COMMENT
MEDIUMrust/mise.toml18# =============================================================================COMMENT
MEDIUMrust/mise.toml20# =============================================================================COMMENT
MEDIUMrust/mise.toml75# =============================================================================COMMENT
MEDIUMrust/mise.toml77# =============================================================================COMMENT
MEDIUMrust/mise.toml155# =============================================================================STRING
MEDIUMrust/mise.toml157# =============================================================================STRING
MEDIUMrust/relay/server/src/main.rs593 // ┌──┼──┼──────────────────────────┐COMMENT
MEDIUMrust/relay/server/src/main.rs595 // └──┴──┴──────────────────────────┘COMMENT
MEDIUMswift/apple/.swiftlint.yml9# ============================================================================COMMENT
MEDIUMswift/apple/.swiftlint.yml11# ============================================================================COMMENT
MEDIUMswift/apple/.swiftlint.yml35# ============================================================================COMMENT
MEDIUMswift/apple/.swiftlint.yml37# ============================================================================COMMENT
MEDIUMswift/apple/.swiftlint.yml87# ============================================================================COMMENT
MEDIUMswift/apple/.swiftlint.yml89# ============================================================================COMMENT
MEDIUMswift/apple/.swiftlint.yml142# ============================================================================COMMENT
MEDIUMswift/apple/.swiftlint.yml144# ============================================================================COMMENT
MEDIUMswift/apple/mise.toml21# =============================================================================COMMENT
MEDIUMswift/apple/mise.toml23# =============================================================================COMMENT
Synthetic Comment Markers2 hits · 15 pts
SeverityFileLineSnippetContext
HIGH…firezone/android/features/splash/ui/SplashViewModel.kt111 // If already granted, mark as requested and don't show the screenCOMMENT
HIGH…sion/notification/ui/NotificationPermissionActivity.kt41 // Mark as requested even if user skipsCOMMENT
Verbosity Indicators4 hits · 9 pts
SeverityFileLineSnippetContext
LOWswift/apple/FirezoneNetworkExtension/Adapter.swift469 // Step 1: Get system default resolversCOMMENT
LOWswift/apple/FirezoneNetworkExtension/Adapter.swift475 // Step 2: Validate addresses and filter out sentinel ranges and non-routable addressesCOMMENT
LOWswift/apple/FirezoneNetworkExtension/Adapter.swift516 // Step 3: Fall back to Cloudflare DNS if no usable resolvers remainCOMMENT
LOWswift/apple/FirezoneNetworkExtension/Adapter.swift524 // Step 4: Send to connlibCOMMENT
Structural Annotation Overuse4 hits · 9 pts
SeverityFileLineSnippetContext
LOWswift/apple/FirezoneNetworkExtension/Adapter.swift469 // Step 1: Get system default resolversCOMMENT
LOWswift/apple/FirezoneNetworkExtension/Adapter.swift475 // Step 2: Validate addresses and filter out sentinel ranges and non-routable addressesCOMMENT
LOWswift/apple/FirezoneNetworkExtension/Adapter.swift516 // Step 3: Fall back to Cloudflare DNS if no usable resolvers remainCOMMENT
LOWswift/apple/FirezoneNetworkExtension/Adapter.swift524 // Step 4: Send to connlibCOMMENT
Self-Referential Comments3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMscripts/gateway-systemd-install.sh186# Define the target directory and binary pathCOMMENT
MEDIUMscripts/gateway-systemd-install.sh217# Create the directory if it doesn’t existCOMMENT
MEDIUM.github/workflows/publish-release.yml238 # Create the PRCOMMENT
Fake / Example Data7 hits · 7 pts
SeverityFileLineSnippetContext
LOWrust/gui-client/src-tauri/src/auth.rs420 actor_name: "Jane Doe".to_string(),CODE
LOWrust/gui-client/src-tauri/src/auth.rs511 let actor_name = "Jane Doe";CODE
LOWrust/gui-client/src-tauri/src/auth.rs585 actor_name: "Jane Doe".into(),CODE
LOWrust/gui-client/src-tauri/src/auth.rs619 actor_name: "Jane Doe".into(),CODE
LOWrust/gui-client/src-tauri/src/gui/system_tray.rs474 actor_name: "Jane Doe".into(),CODE
LOW…d/features/session/ui/compose/SampleSessionActivity.kt28 actorName = "Jane Doe",CODE
LOW…/android/features/session/ui/compose/SessionSamples.kt23 actorName = "Jane Doe",CODE
Redundant / Tautological Comments3 hits · 4 pts
SeverityFileLineSnippetContext
LOWscripts/firezone-client-gui-install.sh20# Check if the user is already in the groupCOMMENT
LOW.github/actions/setup-rust-nightly/action.yml16 # Check if nightly toolchain is already installedCOMMENT
LOW.github/actions/setup-rust-nightly/action.yml27 # Check if nightly toolchain is already installedCOMMENT
Example Usage Blocks2 hits · 3 pts
SeverityFileLineSnippetContext
LOWrust/tests/loadtest/loadtest.example.toml6# Usage:COMMENT
LOWswift/apple/FirezoneNetworkExtension/Channel.swift53/// Example usage:COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMrust/libs/connlib/ip-packet/src/lib.rs922 /// Essentially, the only time we need to update the ECN flags is:COMMENT
Slop Phrases1 hit · 2 pts
SeverityFileLineSnippetContext
LOWrust/libs/telemetry/src/feature_flags.rs79 // Exhaustive destruction so we don't forget to update this when we add a flag.COMMENT