zenoh unifies data in motion, data in-use, data at rest and computations. It carefully blends traditional pub/sub with geo-distributed storages, queries and computations, while retaining a level of time and space efficiency that is well beyond any of the mainstream stacks.
This report presents the forensic synthetic code analysis of eclipse-zenoh/zenoh, a Rust project with 2,981 GitHub stars. SynthScan v2.0 examined 215,002 lines of code across 766 source files, recording 1222 pattern matches distributed across 9 syntactic categories. The overall adjusted score of 6.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).
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.
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.
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.
The scanner identified 1222 distinct pattern matches across 9 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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | Cargo.toml | 1 | # | COMMENT |
| LOW | rustfmt.toml | 1 | edition = "2021" | COMMENT |
| LOW | .pre-commit-config.yaml | 1 | # | COMMENT |
| LOW | zenoh-ext/Cargo.toml | 1 | # | COMMENT |
| LOW | zenoh-ext/tests/advanced.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/tests/liveliness.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/examples/Cargo.toml | 1 | # | COMMENT |
| LOW | zenoh-ext/examples/examples/z_advanced_sub.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/examples/examples/z_view_size.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/examples/examples/z_advanced_pub.rs | 1 | use std::time::Duration; | COMMENT |
| LOW | zenoh-ext/examples/examples/z_member.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/examples/src/lib.rs | 1 | //! Examples on using Zenoh. | COMMENT |
| LOW | zenoh-ext/src/advanced_cache.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/src/publisher_ext.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/src/publisher_ext.rs | 21 | /// Allow matching [`AdvancedSubscribers`](crate::AdvancedSubscriber) to recover history and/or missed samples. | COMMENT |
| LOW | zenoh-ext/src/lib.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/src/lib.rs | 21 | //! | COMMENT |
| LOW | zenoh-ext/src/session_ext.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/src/session_ext.rs | 21 | #[zenoh_macros::unstable] | COMMENT |
| LOW | zenoh-ext/src/serialization.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/src/serialization.rs | 121 | /// and could be implemented for user-defined types. | COMMENT |
| LOW | zenoh-ext/src/serialization.rs | 141 | /// deserialized into the given type, an error is returned. | COMMENT |
| LOW | zenoh-ext/src/serialization.rs | 161 | /// Serializer implementing the [Zenoh serialization format][1]. | COMMENT |
| LOW | zenoh-ext/src/serialization.rs | 221 | COMMENT | |
| LOW | zenoh-ext/src/serialization.rs | 561 | T13 / 13, | COMMENT |
| LOW | zenoh-ext/src/publication_cache.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/src/querying_subscriber.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/src/querying_subscriber.rs | 121 | self, | COMMENT |
| LOW | zenoh-ext/src/querying_subscriber.rs | 821 | /// Later on, new fetches can be performed again, calling [`FetchingSubscriber::fetch()`](super::FetchingSubscriber::fet | COMMENT |
| LOW | zenoh-ext/src/querying_subscriber.rs | 841 | /// .await | COMMENT |
| LOW | zenoh-ext/src/querying_subscriber.rs | 981 | COMMENT | |
| LOW | zenoh-ext/src/querying_subscriber.rs | 1001 | /// | COMMENT |
| LOW | zenoh-ext/src/querying_subscriber.rs | 1021 | /// // perform an additional fetch | COMMENT |
| LOW | zenoh-ext/src/querying_subscriber.rs | 1081 | /// | COMMENT |
| LOW | zenoh-ext/src/querying_subscriber.rs | 1101 | /// fetching_subscriber | COMMENT |
| LOW | zenoh-ext/src/advanced_subscriber.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/src/advanced_subscriber.rs | 101 | pub struct RecoveryConfig<const CONFIGURED: bool = true> { | COMMENT |
| LOW | zenoh-ext/src/advanced_subscriber.rs | 301 | /// [`sample_miss_detection`](crate::AdvancedPublisherBuilder::sample_miss_detection). | COMMENT |
| LOW | zenoh-ext/src/advanced_subscriber.rs | 521 | } | COMMENT |
| LOW | zenoh-ext/src/advanced_subscriber.rs | 541 | /// use zenoh_ext::{AdvancedSubscriberBuilderExt, HistoryConfig, RecoveryConfig}; | COMMENT |
| LOW | zenoh-ext/src/group.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/src/subscriber_ext.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/src/subscriber_ext.rs | 61 | /// will run the given `fetch` function. The user defined `fetch` function should fetch some samples and return them | COMMENT |
| LOW | zenoh-ext/src/subscriber_ext.rs | 81 | /// .wait() | COMMENT |
| LOW | zenoh-ext/src/subscriber_ext.rs | 101 | COMMENT | |
| LOW | zenoh-ext/src/subscriber_ext.rs | 121 | /// .querying() | COMMENT |
| LOW | zenoh-ext/src/subscriber_ext.rs | 141 | fn history(self, config: HistoryConfig) -> AdvancedSubscriberBuilder<'a, 'b, 'c, Handler>; | COMMENT |
| LOW | zenoh-ext/src/subscriber_ext.rs | 161 | #[allow(deprecated)] | COMMENT |
| LOW | zenoh-ext/src/subscriber_ext.rs | 181 | /// | COMMENT |
| LOW | zenoh-ext/src/subscriber_ext.rs | 221 | /// | COMMENT |
| LOW | zenoh-ext/src/subscriber_ext.rs | 301 | COMMENT | |
| LOW | zenoh-ext/src/subscriber_ext.rs | 321 | /// ```no_run | COMMENT |
| LOW | zenoh-ext/src/subscriber_ext.rs | 361 | fetch, | COMMENT |
| LOW | zenoh-ext/src/subscriber_ext.rs | 381 | /// # async fn main() { | COMMENT |
| LOW | zenoh-ext/src/advanced_publisher.rs | 1 | // | COMMENT |
| LOW | zenoh-ext/src/advanced_publisher.rs | 61 | /// | COMMENT |
| LOW | zenoh-ext/src/advanced_publisher.rs | 81 | /// [`AdvancedSubscribers`](crate::AdvancedSubscriber) can recover last sample with the | COMMENT |
| LOW | zenoh-ext/src/advanced_publisher.rs | 301 | std::future::ready(self.wait()) | COMMENT |
| LOW | zenoh-ext/src/advanced_publisher.rs | 321 | /// # #[tokio::main] | COMMENT |
| LOW | zenoh-ext/src/advanced_publisher.rs | 521 | /// Get the [`Encoding`] used when publishing data. | COMMENT |
| 1133 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| CRITICAL | zenoh/src/net/runtime/adminspace.rs | 249 | let cfg_rx = admin.context.runtime.state.config.subscribe(); | CODE |
| CRITICAL | zenoh/src/net/runtime/adminspace.rs | 263 | let cfg_guard = admin.context.runtime.state.config.lock(); | CODE |
| CRITICAL | zenoh/src/net/runtime/adminspace.rs | 390 | let conf = &self.context.runtime.state.config.lock(); | CODE |
| CRITICAL | zenoh/src/net/runtime/adminspace.rs | 487 | let conf = &self.context.runtime.state.config.lock(); | CODE |
| CRITICAL | zenoh/src/net/tests/regions/mod.rs | 1003 | #[tracing::instrument(level = "info", skip(self), fields(from = %self.b2a.face, to = %self.a2b.face.state.zid.short( | COMMENT |
| CRITICAL | zenoh/src/net/tests/regions/mod.rs | 1015 | #[tracing::instrument(level = "info", skip(self), fields(from = %self.a2b.face, to = %self.b2a.face.state.zid.short( | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM⚡ | zenoh/src/net/routing/dispatcher/tables.rs | 401 | /// ┌───────────────────┐ ┌───────────────────┐ | COMMENT |
| MEDIUM⚡ | zenoh/src/net/routing/dispatcher/tables.rs | 404 | /// └─────/─────────\───┘ └─────/─────────\───┘ | COMMENT |
| MEDIUM⚡ | zenoh/src/net/routing/dispatcher/tables.rs | 405 | /// ┌────/───────────\──┐ ┌────/───────────\──┐ | COMMENT |
| MEDIUM⚡ | zenoh/src/net/routing/dispatcher/tables.rs | 411 | /// └───────────────────┘ └───────────────────┘ | COMMENT |
| MEDIUM⚡ | zenoh/src/net/routing/dispatcher/tables.rs | 420 | /// ┌───────────────────┐ ┌───────────────────┐ | COMMENT |
| MEDIUM⚡ | zenoh/src/net/routing/dispatcher/tables.rs | 424 | /// └─────/─────────\───┘ └─────/─────────\───┘ | COMMENT |
| MEDIUM⚡ | zenoh/src/net/routing/dispatcher/tables.rs | 425 | /// ┌────/───────────\──┐ ┌────/───────────\──┐ | COMMENT |
| MEDIUM⚡ | zenoh/src/net/routing/dispatcher/tables.rs | 429 | /// └───────────────────┘ └───────────────────┘ | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | …plementations/posix/posix_shm_provider_backend_talc.rs | 99 | // because of platform specific, our shm segment is >= requested size, so in order to utilize | COMMENT |
| MEDIUM | …lementations/posix/posix_shm_provider_backend_buddy.rs | 100 | // because of platform specific, our shm segment is >= requested size, so in order to utilize | COMMENT |
| MEDIUM | …ations/posix/posix_shm_provider_backend_binary_heap.rs | 132 | // because of platform specific, our shm segment is >= requested size, so in order to utilize | COMMENT |
| MEDIUM | commons/zenoh-shm/src/metadata/subscription.rs | 58 | // fastest path: try to utilize already existing segment | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …ns/zenoh-plugin-storage-manager/src/replication/log.rs | 508 | // we need to check if it is older or not than the one we are processing. | COMMENT |
| LOW | …-storage-manager/src/replication/core/aligner_reply.rs | 238 | /// it is a `Put` we need to check if a Wildcard Update overwrites it in which case we don't | COMMENT |
| LOW | …-storage-manager/src/replication/core/aligner_reply.rs | 428 | // We received an EventMetadata, we need to check if we don't have: | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | commons/zenoh-crypto/src/cipher.rs | 108 | let t4 = "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labor | CODE |
| LOW | commons/zenoh-crypto/src/cipher.rs | 108 | let t4 = "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labor | CODE |
| LOW | examples/examples/z_bytes.rs | 45 | "name": "John Doe", | CODE |
| LOW | examples/examples/z_bytes.rs | 65 | name: String::from("John Doe"), | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | commons/zenoh-shm/src/api/provider/shm_provider.rs | 435 | // TODO: implement provider's async signalling instead of this! | COMMENT |
| LOW | commons/zenoh-shm/src/api/provider/shm_provider.rs | 455 | // TODO: implement provider's async signalling instead of this! | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …s/zenoh-plugin-storage-manager/src/replication/core.rs | 588 | /// NOTE: This function is used to process both the `latest_updates` structure and the Replication | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | zenoh/src/net/routing/dispatcher/resource.rs | 654 | // don't forget to add 1 to the index because of `[1..]` slice above | COMMENT |