Repository Analysis

agentclientprotocol/agent-client-protocol

A protocol for connecting any editor to any agent

7.1 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of agentclientprotocol/agent-client-protocol, a Rust project with 4,099 GitHub stars. SynthScan v2.0 examined 94,260 lines of code across 76 source files, recording 969 pattern matches distributed across 5 syntactic categories. The overall adjusted score of 7.1 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.1
Adjusted Score
7.1
Raw Score
100%
Time Factor
2026-08-28
Last Push
4.1K
Stars
Rust
Language
94.3K
Lines of Code
76
Files
969
Pattern Hits
2026-08-29
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 4LOW 965

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 969 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.

Over-Commented Block961 hits · 654 pts
SeverityFileLineSnippetContext
LOWdeny.toml1# This template contains all of the possible sections and their default valuesCOMMENT
LOWdeny.toml21# `target_family = "unix"` configuration, that only having windows targets inCOMMENT
LOWdeny.toml41#exclude = []COMMENT
LOWdeny.toml61COMMENT
LOWdeny.toml81# See Git Authentication for more information about setting up git authentication.COMMENT
LOWdeny.toml101confidence-threshold = 0.8COMMENT
LOWdeny.toml121# and the crate will be checked normally, which may produce warnings or errorsCOMMENT
LOWdeny.toml141# This section is considered when running `cargo deny check bans`.COMMENT
LOWdeny.toml161# on a crate-by-crate basis if desired.COMMENT
LOWdeny.toml181# List of features to allow/denyCOMMENT
LOWdeny.toml201# this is set there is no point setting `deny`COMMENT
LOWagent-client-protocol-schema/src/version.rs1use derive_more::{Display, From};COMMENT
LOWagent-client-protocol-schema/src/version.rs21 ///COMMENT
LOWagent-client-protocol-schema/src/serde_util.rs1//! Custom option-like field wrappers and builder helpers for serde.COMMENT
LOWagent-client-protocol-schema/src/serde_util.rs21};COMMENT
LOWagent-client-protocol-schema/src/serde_util.rs301/// use serde::{Serialize, Deserialize};COMMENT
LOWagent-client-protocol-schema/src/serde_util.rs441 /// # ExampleCOMMENT
LOWagent-client-protocol-schema/src/serde_util.rs461 MaybeUndefined::Undefined => {}COMMENT
LOWagent-client-protocol-schema/src/lib.rs1#![cfg_attr(docsrs, feature(doc_cfg))]COMMENT
LOWagent-client-protocol-schema/src/lib.rs21//!COMMENT
LOWagent-client-protocol-schema/src/rpc.rs1//! JSON-RPC envelope types shared by ACP clients and agents.COMMENT
LOWagent-client-protocol-schema/src/rpc.rs41/// A JSON-RPC request object.COMMENT
LOWagent-client-protocol-schema/src/rpc.rs101COMMENT
LOWagent-client-protocol-schema/src/rpc.rs161COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs41/// See protocol docs: [Agent Reports Output](https://agentclientprotocol.com/protocol/prompt-turn#3-agent-reports-outpuCOMMENT
LOWagent-client-protocol-schema/src/v1/client.rs81 /// See protocol docs: [Extensibility](https://agentclientprotocol.com/protocol/extensibility)COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs101 UserMessageChunk(ContentChunk),COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs121 ///COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs141 /// This capability is not part of the spec yet, and may be removed or changed at any point.COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs161 /// This capability is not part of the spec yet, and may be removed or changed at any point.COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs181pub enum NoticeSeverity {COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs201///COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs221 ///COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs261 }COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs281 pub fn new(id: impl Into<Arc<str>>) -> Self {COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs301 /// Compaction finished unsuccessfully.COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs321///COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs401/// the terminal update for the same ID. Agents MUST only send this update whenCOMMENT
LOWagent-client-protocol-schema/src/v1/client.rs441COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs481 #[must_use]COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs521COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs541#[derive(Default, Debug, Clone, Serialize, Deserialize, PartialEq, Eq)]COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs601#[serde_as]COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs661#[serde_as]COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs701 pub fn meta(mut self, meta: impl IntoOption<Meta>) -> Self {COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs721 #[serde_as(deserialize_as = "DefaultOnError")]COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs761 ///COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs801 #[serde_as(deserialize_as = "DefaultOnError<VecSkipError<_, SkipListener>>")]COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs841#[cfg_attr(feature = "schemars", derive(schemars::JsonSchema))]COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs901#[serde(untagged, rename_all = "camelCase")]COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs941 /// metadata to their interactions. Implementations MUST NOT make assumptions about values atCOMMENT
LOWagent-client-protocol-schema/src/v1/client.rs961#[cfg_attr(feature = "schemars", derive(schemars::JsonSchema))]COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs1001 /// The _meta property is reserved by ACP to allow clients and agents to attach additionalCOMMENT
LOWagent-client-protocol-schema/src/v1/client.rs1021 /// Unique identifier for this permission option.COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs1081}COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs1101/// Response to a permission request.COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs1141 pub fn meta(mut self, meta: impl IntoOption<Meta>) -> Self {COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs1161 Cancelled,COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs1201 /// these keys.COMMENT
LOWagent-client-protocol-schema/src/v1/client.rs1221#[serde(rename_all = "camelCase")]COMMENT
901 more matches not shown…
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMagent-client-protocol-schema/src/v1/content.rs8//! allowing seamless integration between ACP and MCP-based tools.COMMENT
MEDIUMagent-client-protocol-schema/src/v2/content.rs8//! allowing seamless integration between ACP and MCP-based tools.COMMENT
Excessive Try-Catch Wrapping3 hits · 5 pts
SeverityFileLineSnippetContext
LOWscripts/generate_registry_docs.py128 except Exception as e:CODE
MEDIUMscripts/generate_registry_docs.py153 print(f"Error: Failed to fetch icons for {len(failed)} agent(s): {', '.join(failed)}")CODE
MEDIUMscripts/generate_registry_docs.py210 print(f"Error: Template file not found at {TEMPLATE_PATH}")CODE
Redundant / Tautological Comments2 hits · 3 pts
SeverityFileLineSnippetContext
LOWscripts/generate_registry_docs.py208 # Check if template existsCOMMENT
LOWscripts/spellcheck.sh3# Check if typos is installedCOMMENT
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWscripts/generate_registry_docs.py15CODE