Repository Analysis

n0-computer/iroh

IP addresses break, dial keys instead. A library that adds QUIC + NAT Traversal to your apps.

7.7 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of n0-computer/iroh, a Rust project with 11,693 GitHub stars. SynthScan v2.0 examined 66,856 lines of code across 221 source files, recording 400 pattern matches distributed across 3 syntactic categories. The overall adjusted score of 7.7 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).

7.7
Adjusted Score
7.7
Raw Score
100%
Time Factor
2026-07-14
Last Push
11.7K
Stars
Rust
Language
66.9K
Lines of Code
221
Files
400
Pattern Hits
2026-07-14
Scan Date
0.05
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 11HIGH 0MEDIUM 1LOW 388

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 400 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 Block388 hits · 364 pts
SeverityFileLineSnippetContext
LOWiroh-base/src/key.rs301 PublicKey(CompressedEdwardsY(key))COMMENT
LOWiroh-base/src/endpoint_addr.rs1//! Addressing for iroh endpoints.COMMENT
LOWiroh-base/src/endpoint_addr.rs21///COMMENT
LOWiroh-base/src/endpoint_addr.rs161/// A custom transport address consisting of a transport id and opaque address data.COMMENT
LOWiroh-base/src/endpoint_addr.rs301 /// You can freely choose this. There is a table of reserved custom transport ids inCOMMENT
LOWiroh-base/src/relay_url.rs1use std::{fmt, ops::Deref, str::FromStr, sync::Arc};COMMENT
LOWiroh-relay/proptest-regressions/protos/send_recv.txt1# Seeds for failure cases proptest has generated in the past. It isCOMMENT
LOWiroh-relay/proptest-regressions/protos/relay.txt1# Seeds for failure cases proptest has generated in the past. It isCOMMENT
LOWiroh-relay/tests/multiple-hostnames-pebble.sh1#!/usr/bin/env bashCOMMENT
LOWiroh-relay/tests/runtime_auth.rs1//! Runtime revocation of relay access via the [`AccessControl`] trait.COMMENT
LOWiroh-relay/src/client.rs41mod tls;COMMENT
LOWiroh-relay/src/client.rs141/// Build a Client.COMMENT
LOWiroh-relay/src/client.rs181 key_cache: KeyCache::new(128),COMMENT
LOWiroh-relay/src/client.rs201 ///COMMENT
LOWiroh-relay/src/quic.rs81 pub(crate) fn bind_addr(&self) -> SocketAddr {COMMENT
LOWiroh-relay/src/quic.rs281 // enable the receive side of address discoveryCOMMENT
LOWiroh-relay/src/quic.rs321 let connecting = selfCOMMENT
LOWiroh-relay/src/lib.rs1//! Iroh's relay is a feature within [iroh](https://github.com/n0-computer/iroh), a peer-to-peerCOMMENT
LOWiroh-relay/src/lib.rs61pub trait ExportKeyingMaterial {COMMENT
LOWiroh-relay/src/server.rs1//! A fully-fledged iroh-relay server over HTTP or HTTPS.COMMENT
LOWiroh-relay/src/server.rs121/// Configuration for the Relay HTTP and HTTPS server.COMMENT
LOWiroh-relay/src/server.rs241 /// Each item is a `(name, value)` pair. Both names and values are percent-decoded.COMMENT
LOWiroh-relay/src/server.rs281/// Implement this trait to gate access to a relay server.COMMENT
LOWiroh-relay/src/server.rs361///COMMENT
LOWiroh-relay/src/server.rs421 if let Some(access) = self.access.as_ref() {COMMENT
LOWiroh-relay/src/server.rs481 }COMMENT
LOWiroh-relay/src/server.rs521 }COMMENT
LOWiroh-relay/src/server.rs601 ///COMMENT
LOWiroh-relay/src/main.rs41/// Environment variable to override the ACME directory URL.COMMENT
LOWiroh-relay/src/main.rs81 filename: impl AsRef<Path>,COMMENT
LOWiroh-relay/src/main.rs101 ///COMMENT
LOWiroh-relay/src/main.rs121 /// TLS is disabled if not present and the Relay server will serve all services overCOMMENT
LOWiroh-relay/src/main.rs141 /// Defaults to `true`, when the metrics feature is enabled.COMMENT
LOWiroh-relay/src/main.rs161 /// Allows everyoneCOMMENT
LOWiroh-relay/src/main.rs181 /// All other connections are denied.COMMENT
LOWiroh-relay/src/main.rs401 ///COMMENT
LOWiroh-relay/src/main.rs421 ///COMMENT
LOWiroh-relay/src/main.rs441 /// certificates, we must use the LetsEncrypt production server. Read more here:COMMENT
LOWiroh-relay/src/http.rs41 strum::EnumString,COMMENT
LOWiroh-relay/src/defaults.rs1//! Default values used in the relay.COMMENT
LOWiroh-relay/src/defaults.rs21/// memory usage will be (32 + 8 + 8 + 8) * 1_000_000 = 56MB on 64 bit,COMMENT
LOWiroh-relay/src/relay_map.rs221 fmt::Debug::fmt(&self, f)COMMENT
LOWiroh-relay/src/tls.rs1//! TLS verification configuration for iroh and iroh-relay.COMMENT
LOWiroh-relay/src/tls.rs21#[derive(Debug, Clone)]COMMENT
LOWiroh-relay/src/tls.rs121 /// The [`CryptoProvider`] passed to the callback should be used for all cryptographic operations.COMMENT
LOWiroh-relay/src/protos/streams.rs21pub(crate) struct WsBytesFramed<T> {COMMENT
LOWiroh-relay/src/protos/handshake.rs1//! Implements the handshake protocol that authenticates and authorizes clients connecting to the relays.COMMENT
LOWiroh-relay/src/protos/handshake.rs61pub(crate) struct KeyMaterialClientAuth {COMMENT
LOWiroh-relay/src/protos/handshake.rs81 pub(crate) challenge: [u8; 16],COMMENT
LOWiroh-relay/src/protos/handshake.rs141#[allow(missing_docs)]COMMENT
LOWiroh-relay/src/protos/handshake.rs201 /// Generates a new challenge.COMMENT
LOWiroh-relay/src/protos/handshake.rs381///COMMENT
LOWiroh-relay/src/protos/handshake.rs401 SignedChallenge,COMMENT
LOWiroh-relay/src/protos/handshake.rs501 Access::Deny { reason } => Err(self.deny(reason, io).await),COMMENT
LOWiroh-relay/src/protos/relay.rs21/// (This only includes the data bytes visible to the socket, notCOMMENT
LOWiroh-relay/src/protos/relay.rs41COMMENT
LOWiroh-relay/src/protos/relay.rs81 /// Indicates that the client identified by the underlying public key had previously sent you aCOMMENT
LOWiroh-relay/src/protos/relay.rs101 /// with the payload sent previously in the ping.COMMENT
LOWiroh-relay/src/protos/relay.rs201 ecn: None,COMMENT
LOWiroh-relay/src/protos/common.rs21 /// The client frame type for the authentication frameCOMMENT
328 more matches not shown…
Hallucination Indicators11 hits · 145 pts
SeverityFileLineSnippetContext
CRITICALiroh/src/socket.rs1527 self.sock.metrics.socket.actor_tick_other.inc();CODE
CRITICALiroh/src/socket.rs1533 self.sock.metrics.socket.actor_tick_msg.inc();CODE
CRITICALiroh/src/socket.rs1538 self.sock.metrics.socket.actor_tick_re_stun.inc();CODE
CRITICALiroh/src/socket.rs1583 self.sock.metrics.socket.actor_tick_other.inc();CODE
CRITICALiroh/src/socket.rs1590 self.sock.metrics.socket.actor_tick_portmap_changed.inc();CODE
CRITICALiroh/src/socket.rs1593 self.sock.metrics.net_report.portmap_external_address_updated.inc();CODE
CRITICALiroh/src/socket.rs1601 self.sock.metrics.socket.actor_tick_other.inc();CODE
CRITICALiroh/src/socket.rs805 self.sock.metrics.net_report.portmap_attempts.inc();CODE
CRITICALiroh/src/socket.rs1508 self.sock.metrics.socket.actor_tick_main.inc();CODE
CRITICALiroh/src/socket.rs1612 self.sock.metrics.socket.actor_link_change.inc();CODE
CRITICALiroh/src/endpoint.rs1181 self.inner.static_config.tls_config.secret_key.public()CODE
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMiroh/src/lib.rs241//! Please see the examples directory for more nuanced examples.COMMENT