Repository Analysis

doocs/source-code-hunter

😱 从源码层面,剖析挖掘互联网行业主流技术的底层实现原理,为广大开发者 “提升技术深度” 提供便利。目前开放 Spring 全家桶,Mybatis、Netty、Dubbo 框架,及 Redis、Tomcat 中间件等

5.6 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of doocs/source-code-hunter, a Java project with 23,131 GitHub stars. SynthScan v2.0 examined 65,928 lines of code across 218 source files, recording 28 pattern matches distributed across 1 syntactic category. The overall adjusted score of 5.6 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).

5.6
Adjusted Score
5.6
Raw Score
100%
Time Factor
2026-06-25
Last Push
23.1K
Stars
Java
Language
65.9K
Lines of Code
218
Files
28
Pattern Hits
2026-07-14
Scan Date
0.13
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 28HIGH 0MEDIUM 0LOW 0

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 28 distinct pattern matches across 1 syntactic category. 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.

Hallucination Indicators28 hits · 370 pts
SeverityFileLineSnippetContext
CRITICALdocs/Mybatis/核心处理层/Mybatis-DataSource.md310 //org.apache.ibatis.session.Configuration.Configuration()COMMENT
CRITICALdocs/Mybatis/核心处理层/Mybatis-Alias.md7- 与 Alias 相关的一个方法`org.apache.ibatis.type.TypeAliasRegistry.registerAlias(java.lang.String, java.lang.Class<?>)`(别名注册)CODE
CRITICALdocs/Mybatis/核心处理层/Mybatis-Alias.md80最后回到了`org.apache.ibatis.type.TypeAliasRegistry.registerAlias(java.lang.String, java.lang.Class<?>)`方法CODE
CRITICALdocs/Spring/AOP/Spring-Aop如何生效.md59- `org.springframework.aop.config.AopConfigUtils.registerAspectJAnnotationAutoProxyCreatorIfNecessary(org.springframeworCODE
CRITICALdocs/Spring/TX/Spring-transaction.md139 dataSource.setDriverClassName(com.mysql.jdbc.Driver.class.getName());CODE
CRITICALdocs/Spring/clazz/Spring-AnnotationUtils.md26- `org.springframework.core.annotation.AnnotationUtils.getAnnotation(java.lang.reflect.Method, java.lang.Class<A>)`CODE
CRITICALdocs/Spring/clazz/Spring-AnnotationUtils.md87- `org.springframework.core.annotation.AnnotationUtils.synthesizeAnnotation(A, java.lang.reflect.AnnotatedElement)`CODE
CRITICALdocs/Spring/clazz/Spring-BeanDefinitionReaderUtils.md34- `org.springframework.beans.factory.support.BeanDefinitionReaderUtils.generateBeanName(org.springframework.beans.factorCODE
CRITICAL…cs/Spring/clazz/Spring-DefaultSingletonBeanRegistry.md159- `org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(java.lang.String)`CODE
CRITICALdocs/Spring/clazz/Spring-Custom-label-resolution.md175- `org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(org.w3c.dom.Element)`CODE
CRITICALdocs/Spring/clazz/Spring-Custom-label-resolution.md176 - `org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(org.w3c.dom.Element, org.spriCODE
CRITICALdocs/Spring/RMI/Spring-RMI.md89 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBCODE
CRITICALdocs/Spring/RMI/Spring-RMI.md90 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeaCODE
CRITICALdocs/Spring/RMI/Spring-RMI.md91 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFCODE
CRITICALdocs/Spring/RMI/Spring-RMI.md93 at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.javCODE
CRITICALdocs/Spring/RMI/Spring-RMI.md94 at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:306)CODE
CRITICALdocs/Spring/RMI/Spring-RMI.md95 at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:176)CODE
CRITICALdocs/Spring/RMI/Spring-RMI.md96 at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFacCODE
CRITICALdocs/Spring/RMI/Spring-RMI.md97 at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationCoCODE
CRITICALdocs/Spring/RMI/Spring-RMI.md98 at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:579)CODE
CRITICALdocs/Spring/RMI/Spring-RMI.md101 at com.huifer.source.spring.rmi.RMIClientSourceCode.main(RMIClientSourceCode.java:7)CODE
CRITICALdocs/Spring/RMI/Spring-RMI.md103 at org.springframework.remoting.rmi.RmiClientInterceptor.lookupStub(RmiClientInterceptor.java:209)CODE
CRITICALdocs/Spring/RMI/Spring-RMI.md104 at org.springframework.remoting.rmi.RmiClientInterceptor.prepare(RmiClientInterceptor.java:147)CODE
CRITICALdocs/Spring/RMI/Spring-RMI.md105 at org.springframework.remoting.rmi.RmiClientInterceptor.afterPropertiesSet(RmiClientInterceptor.java:134)CODE
CRITICALdocs/Spring/RMI/Spring-RMI.md106 at org.springframework.remoting.rmi.RmiProxyFactoryBean.afterPropertiesSet(RmiProxyFactoryBean.java:68)CODE
CRITICALdocs/Spring/RMI/Spring-RMI.md107 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapabCODE
CRITICALdocs/Spring/RMI/Spring-RMI.md108 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBCODE
CRITICALdocs/Spring/RMI/Spring-RMI.md114 at org.springframework.remoting.rmi.RmiClientInterceptor.lookupStub(RmiClientInterceptor.java:201)CODE