Repository Analysis

s3fs-fuse/s3fs-fuse

FUSE-based file system backed by Amazon S3

6.4 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of s3fs-fuse/s3fs-fuse, a C++ project with 9,924 GitHub stars. SynthScan v2.0 examined 39,937 lines of code across 91 source files, recording 189 pattern matches distributed across 6 syntactic categories. The overall adjusted score of 6.4 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).

6.4
Adjusted Score
6.4
Raw Score
100%
Time Factor
2026-07-05
Last Push
9.9K
Stars
C++
Language
39.9K
Lines of Code
91
Files
189
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 26LOW 163

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 189 distinct pattern matches across 6 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 Block161 hits · 158 pts
SeverityFileLineSnippetContext
LOWautogen.sh1#!/bin/shCOMMENT
LOWtest/integration-test-main.sh1#!/bin/bashCOMMENT
LOWtest/integration-test-main.sh401 # If mtime(ctime/atime) when updating from the external programCOMMENT
LOWtest/integration-test-main.sh521 #COMMENT
LOWtest/integration-test-main.sh601 return 1COMMENT
LOWtest/integration-test-main.sh941}COMMENT
LOWtest/integration-test-main.sh2321COMMENT
LOWtest/integration-test-main.sh2461 # So this test just calls the following program.COMMENT
LOWtest/integration-test-main.sh2481# <SOF>....<write data>....<write data>....<write data>...<EOF>COMMENT
LOWtest/integration-test-main.sh2501 rm_test_file "${_TMP_SKIPWRITE_FILE}"COMMENT
LOWtest/integration-test-main.sh2521 # part 5) 0x2800000..0x31FFFFF : <write area>COMMENT
LOWtest/integration-test-main.sh2541 cmp "${_SKIPWRITE_FILE}" "${_TMP_SKIPWRITE_FILE}"COMMENT
LOWtest/integration-test-main.sh2561 # As a result, areas that are not written to the file are mixed.COMMENT
LOWtest/integration-test-main.sh2601}COMMENT
LOWtest/integration-test-main.sh2621COMMENT
LOWtest/integration-test-main.sh2941COMMENT
LOWtest/integration-test-main.sh3081COMMENT
LOWtest/run_tests_using_sanitizers.sh1#!/bin/bashCOMMENT
LOWtest/run_tests_using_sanitizers.sh61make cleanCOMMENT
LOWtest/integration-test-common.sh1#!/bin/bashCOMMENT
LOWtest/integration-test-common.sh21COMMENT
LOWtest/integration-test-common.sh41#COMMENT
LOWtest/integration-test-common.sh301 elseCOMMENT
LOWtest/integration-test-common.sh401# trap handlers do not stack. If a test sets its own, the new handler should call common_exit_handlerCOMMENT
LOWtest/test-utils.sh1#!/bin/bashCOMMENT
LOWtest/test-utils.sh41COMMENT
LOWtest/test-utils.sh281 TEST_DIR="testdir-${RANDOM_STR}"COMMENT
LOWtest/test-utils.sh441# macos fuse-t mounts over NFS, and the mtime/ctime/atime attributeCOMMENT
LOWtest/mergedir.sh1#!/bin/shCOMMENT
LOWtest/filter-suite-log.sh1#!/bin/bashCOMMENT
LOWtest/filter-suite-log.sh141# vim600: expandtab sw=4 ts=4 fdm=markerCOMMENT
LOWtest/compile_all_targets.sh1#!/bin/bashCOMMENT
LOWtest/compile_all_targets.sh61# vim600: expandtab sw=4 ts=4 fdm=markerCOMMENT
LOWtest/sample_delcache.sh1#!/bin/shCOMMENT
LOWtest/sample_delcache.sh121exit 0COMMENT
LOWtest/small-integration-test.sh1#!/bin/bashCOMMENT
LOW.github/workflows/linux-ci-helper.sh1#!/bin/bashCOMMENT
LOW.github/workflows/linux-ci-helper.sh21COMMENT
LOW.github/workflows/linux-ci-helper.sh41#-----------------------------------------------------------COMMENT
LOW.github/workflows/linux-ci-helper.sh441# vim<600: expandtab sw=4 ts=4COMMENT
LOW.github/workflows/ci.yml1#COMMENT
LOWsrc/test_curl_util.cpp21#include <string>COMMENT
LOWsrc/addhead.h21#ifndef S3FS_ADDHEAD_H_COMMENT
LOWsrc/string_util.cpp21#include <algorithm>COMMENT
LOWsrc/string_util.cpp141 return s;COMMENT
LOWsrc/string_util.cpp581 s3fs_wtf8_decode(s.c_str(), &result);COMMENT
LOWsrc/cache_node.h21#ifndef S3FS_CACHE_NODE_H_COMMENT
LOWsrc/cache_node.h61 // As an exception, declare friends to call some protected methods fromCOMMENT
LOWsrc/filetimes.cpp21#include "filetimes.h"COMMENT
LOWsrc/fdcache_auto.h21#ifndef S3FS_FDCACHE_AUTO_H_COMMENT
LOWsrc/s3objlist.cpp21#include <cstring>COMMENT
LOWsrc/s3fs.cpp21#include <algorithm>COMMENT
LOWsrc/s3fs.cpp41#include "s3fs_logger.h"COMMENT
LOWsrc/s3fs.cpp181// A flag indicating whether the mount point has a statCOMMENT
LOWsrc/s3fs.cpp261// [NOTICE]COMMENT
LOWsrc/s3fs.cpp341 // Check Stat CacheCOMMENT
LOWsrc/s3fs.cpp361 if(objtype_t::NEGATIVE == *pObjType){COMMENT
LOWsrc/s3fs.cpp381 // here.COMMENT
LOWsrc/s3fs.cpp401 // cache, the file permission will be 0644(umask dependent)COMMENT
LOWsrc/s3fs.cpp481 // check to send a head request for "dir/"COMMENT
101 more matches not shown…
Decorative Section Separators22 hits · 81 pts
SeverityFileLineSnippetContext
MEDIUMtest/integration-test-main.sh1748 #------------------------------------------------------COMMENT
MEDIUMtest/integration-test-main.sh1750 #------------------------------------------------------COMMENT
MEDIUMtest/integration-test-main.sh1859 #------------------------------------------------------COMMENT
MEDIUMtest/integration-test-main.sh1861 #------------------------------------------------------COMMENT
MEDIUMtest/integration-test-main.sh2494 #------------------------------------------------------COMMENT
MEDIUMtest/integration-test-main.sh2496 #------------------------------------------------------COMMENT
MEDIUMtest/integration-test-main.sh2543 #------------------------------------------------------COMMENT
MEDIUMtest/integration-test-main.sh2545 #------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh34#-----------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh36#-----------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh41#-----------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh43#-----------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh51#-----------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh53#-----------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh65#-----------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh67#-----------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh73#-----------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh75#-----------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh378#-----------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh380#-----------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh419#-----------------------------------------------------------COMMENT
MEDIUM.github/workflows/linux-ci-helper.sh421#-----------------------------------------------------------COMMENT
Self-Referential Comments3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMautogen.sh3# This file is part of S3FS.COMMENT
MEDIUMtest/integration-test-main.sh1730 # Create a dir with some files and directoriesCOMMENT
MEDIUMtest/test-utils.sh445# This function is called primarily for this purpose.COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMsrc/s3fs_extcred.h29// External projects that utilize this header file substitute emptyCOMMENT
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOW.github/workflows/ci.yml247 # Set this to avoid following error when running configure.COMMENT
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWtest/map-subscript-read.py24CODE