Repository Analysis

NVIDIA/stdexec

`std::execution`, the standard C++ framework for asynchronous and parallel programming.

4.5 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of NVIDIA/stdexec, a C++ project with 2,386 GitHub stars. SynthScan v2.0 examined 99,183 lines of code across 426 source files, recording 406 pattern matches distributed across 7 syntactic categories. The overall adjusted score of 4.5 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).

4.5
Adjusted Score
4.5
Raw Score
100%
Time Factor
2026-07-12
Last Push
2.4K
Stars
C++
Language
99.2K
Lines of Code
426
Files
406
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 22LOW 384

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 406 distinct pattern matches across 7 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 Block378 hits · 370 pts
SeverityFileLineSnippetContext
LOWCMakeLists.txt141# - Main library targets -----------------------------------------------------COMMENT
LOWtest/CMakeLists.txt1#=============================================================================COMMENT
LOWtest/test_main.cpp1#define CATCH_CONFIG_MAINCOMMENT
LOWtest/nvexec/CMakeLists.txt1#=============================================================================COMMENT
LOWtest/nvexec/test_main.cpp1#define CATCH_CONFIG_MAINCOMMENT
LOWtest/exec/test_completion_signatures.cpp81 == completion_signatures<set_error_t(float), set_value_t(int)>{});COMMENT
LOWtest/exec/CMakeLists.txt1#=============================================================================COMMENT
LOWtest/exec/test_repeat_until.cpp21#include "stdexec/execution.hpp"COMMENT
LOWtest/exec/test_windows_thread_pool_context.cpp61 [&]() noexceptCOMMENT
LOWtest/exec/test_windows_thread_pool_context.cpp101 REQUIRE(duration > 40ms);COMMENT
LOWtest/exec/test_windows_thread_pool_context.cpp141// exec::windows_thread_pool tp;COMMENT
LOWtest/exec/asio/CMakeLists.txt1# SPDX-FileCopyrightText: Copyright (c) 2025 NVIDIA CORPORATION & AFFILIATES. All rights reserved.COMMENT
LOWtest/exec/asio/test_completion_token.cpp21COMMENT
LOWtest/exec/tbb/CMakeLists.txt1# SPDX-FileCopyrightText: Copyright (c) 2025 NVIDIA CORPORATION & AFFILIATES. All rights reserved.COMMENT
LOWtest/exec/async_scope/test_spawn_future.cpp321 // (void)snd;COMMENT
LOWtest/exec/async_scope/test_spawn_future.cpp481 // catch(int error)COMMENT
LOWtest/exec/sequence/test_merge_each_threaded.cpp21#include "exec/sequence/merge.hpp"COMMENT
LOWtest/exec/sequence/test_merge_each.cpp21#include "exec/sequence/merge.hpp"COMMENT
LOWtest/exec/sequence/test_merge.cpp21#include "exec/sequence.hpp"COMMENT
LOWtest/exec/taskflow/CMakeLists.txt1# SPDX-FileCopyrightText: Copyright (c) 2025 NVIDIA CORPORATION & AFFILIATES. All rights reserved.COMMENT
LOWtest/test_common/tuple.hpp21#include <tuple>COMMENT
LOWtest/stdexec/concepts/test_concepts_receiver.cpp1// /*COMMENT
LOWinclude/._clangd_helper_file.cpp21// provide intellisense for the opened header file.COMMENT
LOWinclude/exec/static_thread_pool.hpp21#include "../stdexec/__detail/__bulk.hpp"COMMENT
LOWinclude/exec/static_thread_pool.hpp41#include "detail/numa.hpp"COMMENT
LOWinclude/exec/start_detached.hpp141 concept __use_submit =COMMENT
LOWinclude/exec/start_detached.hpp161 //! at shutdown), prefer @c stdexec::spawn. For top-level *waiting*, useCOMMENT
LOWinclude/exec/start_detached.hpp181 //! to, and an error completion is therefore considered a contractCOMMENT
LOWinclude/exec/libdispatch_queue.hpp21// TODO: This is needed for libdispatch to compile with GCC. Need to look forCOMMENT
LOWinclude/exec/function.hpp21#include "../stdexec/__detail/__meta.hpp"COMMENT
LOWinclude/exec/function.hpp41// This file defines function<ReturnType(Arguments...)>, which is a type-erased senderCOMMENT
LOWinclude/exec/function.hpp81 struct __receiver_wrapper : public _ReceiverCOMMENT
LOWinclude/exec/function.hpp321 && ((!__has_completion_domain<_Attrs, set_stopped_t>) || _Sigs::__count(set_stopped) > 0);COMMENT
LOWinclude/exec/function.hpp361 __alloc,COMMENT
LOWinclude/exec/function.hpp521 //! default_domain(get_completion_domain_t<Tag>)COMMENT
LOWinclude/exec/function.hpp681 //! baz) that completes in the ways specified by the given specialization ofCOMMENT
LOWinclude/exec/sequence_senders.hpp21#include "../stdexec/__detail/__completion_signatures.hpp"COMMENT
LOWinclude/exec/task.hpp21#include <utility>COMMENT
LOWinclude/exec/__memory_resource_adaptor.hpp21#include <cstring>COMMENT
LOWinclude/exec/__memory_resource_adaptor.hpp41//! - std::pmr::memory_resource*; orCOMMENT
LOWinclude/exec/__memory_resource_adaptor.hpp161 }COMMENT
LOWinclude/exec/completion_signatures.hpp41 template <class... Sigs>COMMENT
LOWinclude/exec/completion_signatures.hpp61 //!COMMENT
LOWinclude/exec/completion_signatures.hpp121 //! custom transformation functions to value, error, and stopped completion cases.COMMENT
LOWinclude/exec/completion_signatures.hpp141 //!COMMENT
LOWinclude/exec/completion_signatures.hpp161 //! // error.COMMENT
LOWinclude/exec/completion_signatures.hpp181 //! return ex::completion_signatures<set_value_t(),COMMENT
LOWinclude/exec/completion_signatures.hpp201 //! template <class Self, class... Env>COMMENT
LOWinclude/exec/just_from.hpp221 //!COMMENT
LOWinclude/exec/just_from.hpp241 //! // A just_from sender can have multiple completion signatures:COMMENT
LOWinclude/exec/repeat_effect_until.hpp21# pragma message( \COMMENT
LOWinclude/exec/timed_thread_scheduler.hpp21#include "timed_scheduler.hpp" // IWYU pragma: keep for schedule_at and schedule_afterCOMMENT
LOWinclude/exec/thread_pool_base.hpp21COMMENT
LOWinclude/exec/__frame_allocator.hpp21#include <memory>COMMENT
LOWinclude/exec/asio/completion_token.hpp21#include <exec/asio/asio_config.hpp>COMMENT
LOWinclude/exec/asio/completion_token.hpp41#include <version>COMMENT
LOWinclude/exec/asio/use_sender.hpp21#include <exec/asio/asio_config.hpp>COMMENT
LOWinclude/exec/detail/shared.hpp21#include "../../stdexec/__detail/__atomic.hpp"COMMENT
LOWinclude/exec/detail/shared.hpp41// shared components of split and ensure_startedCOMMENT
LOWinclude/exec/detail/shared.hpp221 // 3. The underlying operation has already completed.COMMENT
318 more matches not shown…
Decorative Section Separators16 hits · 48 pts
SeverityFileLineSnippetContext
MEDIUMtest/CMakeLists.txt1#=============================================================================COMMENT
MEDIUMtest/CMakeLists.txt15#=============================================================================COMMENT
MEDIUMtest/nvexec/CMakeLists.txt1#=============================================================================COMMENT
MEDIUMtest/nvexec/CMakeLists.txt15#=============================================================================COMMENT
MEDIUMtest/exec/CMakeLists.txt1#=============================================================================COMMENT
MEDIUMtest/exec/CMakeLists.txt15#=============================================================================COMMENT
MEDIUMdocs/eelis_link_filter.pl1#=============================================================================COMMENT
MEDIUMdocs/eelis_link_filter.pl15#=============================================================================COMMENT
MEDIUMdocs/CMakeLists.txt1#=============================================================================COMMENT
MEDIUMdocs/CMakeLists.txt15#=============================================================================COMMENT
MEDIUMdocs/source/conf.py1#=============================================================================COMMENT
MEDIUMdocs/source/conf.py15#=============================================================================COMMENT
MEDIUMexamples/CMakeLists.txt1#=============================================================================COMMENT
MEDIUMexamples/CMakeLists.txt15#=============================================================================COMMENT
MEDIUMexamples/nvexec/CMakeLists.txt1#=============================================================================COMMENT
MEDIUMexamples/nvexec/CMakeLists.txt15#=============================================================================COMMENT
Self-Referential Comments5 hits · 15 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/test-gcc-11.sh11# Create a temporary directory to store results between runsCOMMENT
MEDIUM.github/workflows/test-static-checks.sh13# Create a temporary directory to store results between runsCOMMENT
MEDIUM.github/workflows/test-clang-13.sh11# Create a temporary directory to store results between runsCOMMENT
MEDIUM.github/workflows/test-clang-12.sh11# Create a temporary directory to store results between runsCOMMENT
MEDIUM.github/workflows/test-sanitizer.sh11# Create a temporary directory to store results between runsCOMMENT
Fake / Example Data3 hits · 4 pts
SeverityFileLineSnippetContext
LOWexamples/server_theme/on_transfer.cpp78 char const fake_data[] = "Hello, world!";CODE
LOWexamples/server_theme/on_transfer.cpp79 size_t sz = sizeof(fake_data) - 1;CODE
LOWexamples/server_theme/on_transfer.cpp81 std::memcpy(buffer, fake_data, count);CODE
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMinclude/exec/asio/completion_token.hpp56 // The technique used to achieve this is to utilize an unevaluated call againstCOMMENT
Unused Imports2 hits · 2 pts
SeverityFileLineSnippetContext
LOWconanfile.py4CODE
LOWdocs/source/conf.py25CODE
TODO Padding1 hit · 2 pts
SeverityFileLineSnippetContext
LOWtest/stdexec/algos/adaptors/test_upon_stopped.cpp28 // TODO: implement upon_stoppedCOMMENT