Repository Analysis

Tencent/MMKV

An efficient, small mobile key-value storage framework developed by WeChat. Works on Android, iOS, macOS, Windows, POSIX, and OHOS.

2.8 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of Tencent/MMKV, a C++ project with 18,665 GitHub stars. SynthScan v2.0 examined 55,393 lines of code across 368 source files, recording 139 pattern matches distributed across 5 syntactic categories. The overall adjusted score of 2.8 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).

2.8
Adjusted Score
2.8
Raw Score
100%
Time Factor
2026-06-26
Last Push
18.7K
Stars
C++
Language
55.4K
Lines of Code
368
Files
139
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 9LOW 130

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 139 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 Block128 hits · 128 pts
SeverityFileLineSnippetContext
LOWPOSIX/CMakeLists.txt1#COMMENT
LOWPOSIX/demo/CMakeLists.txt1#COMMENT
LOWPOSIX/demo/TestInterProcessLock.cpp21#include <MMKV/MMKV.h>COMMENT
LOWPOSIX/demo/demo.cpp21#include <MMKV/MMKV.h>COMMENT
LOWPOSIX/demo/demo.cpp1121// string key = "keyyy";COMMENT
LOWPOSIX/golang/CMakeLists.txt1#COMMENT
LOWPOSIX/src/CMakeLists.txt1#COMMENT
LOWCore/MMKVLog.h21#ifndef MMKV_MMKVLOG_HCOMMENT
LOWCore/MMKVLog.h41COMMENT
LOWCore/MMKVLog.h61# endifCOMMENT
LOWCore/MMBuffer.cpp21#define NOMINMAX // undefine max/minCOMMENT
LOWCore/MMKV.h21#ifndef MMKV_MMKV_HCOMMENT
LOWCore/MMKV.h601 // MMKV's size won't reduce after deleting key-valuesCOMMENT
LOWCore/MMKV_Android.cpp21#include "MMKV.h"COMMENT
LOWCore/CMakeLists.txt1#COMMENT
LOWCore/MMKV.cpp21#include "CodedInputData.h"COMMENT
LOWCore/MMKV.cpp41#include <cstring>COMMENT
LOWCore/MMKVMetaInfo.hpp101#endifCOMMENT
LOWCore/PBEncodeItem.hpp101#endifCOMMENT
LOWCore/ThreadLock.h21#ifndef MMKV_THREADLOCK_HCOMMENT
LOWCore/MiniPBCoder.cpp21#include "MiniPBCoder.h"COMMENT
LOWCore/MiniPBCoder_OSX.cpp21#include "MiniPBCoder.h"COMMENT
LOWCore/MMKVPredef.h21#ifndef MMKV_SRC_MMKVPREDEF_HCOMMENT
LOWCore/MMKVPredef.h41#endifCOMMENT
LOWCore/MMKVPredef.h61# define MMKV_ANDROIDCOMMENT
LOWCore/MMKVPredef.h81# endifCOMMENT
LOWCore/MMKVPredef.h121#endif // MMKV_WIN32COMMENT
LOWCore/MMKVPredef.h261constexpr size_t AES_IV_LEN = 16;COMMENT
LOWCore/MMKVPredef.h281#elseCOMMENT
LOWCore/CodedInputDataCrypt.cpp21#include "CodedInputDataCrypt.h"COMMENT
LOWCore/KeyValueHolder.h121#endifCOMMENT
LOWCore/MMKV_OSX.cpp21#include "MMKVPredef.h"COMMENT
LOWCore/MemoryFile_Linux.cpp21#include "MemoryFile.h"COMMENT
LOWCore/ScopedLock.hpp61#include <type_traits>COMMENT
LOWCore/MMKV_IO.cpp21#include "MMKV_IO.h"COMMENT
LOWCore/MMKV_IO.cpp41#include <filesystem>COMMENT
LOWCore/MiniPBCoder.h21#ifndef MMKV_MINIPBCODER_HCOMMENT
LOWCore/MemoryFile.cpp21#include "MemoryFile.h"COMMENT
LOWCore/fakeinclude/MMKVCore/ThreadLock.h21#include "../../ThreadLock.h"COMMENT
LOWCore/fakeinclude/MMKVCore/ScopedLock.hpp21#include "../../ScopedLock.hpp"COMMENT
LOWCore/crc32/CMakeLists.txt1#COMMENT
LOWCore/crc32/crc32_armv8.cpp41COMMENT
LOWCore/crc32/Checksum.h61// getauxval(AT_HWCAP) in OHOS returns wrong value, we just assume all OHOS device have crc32 instrCOMMENT
LOWCore/crc32/zlib/zconf.h1/* zconf.h -- configuration of the zlib compression libraryCOMMENT
LOWCore/crc32/zlib/zconf.h21#define WINDOWSCOMMENT
LOWCore/crc32/zlib/zconf.h41#define MAXSEG_64KCOMMENT
LOWCore/crc32/zlib/zconf.h61#define STDCCOMMENT
LOWCore/crc32/zlib/zconf.h81#define z_const constCOMMENT
LOWCore/crc32/zlib/zconf.h141COMMENT
LOWCore/crc32/zlib/zconf.h161#define FAR _farCOMMENT
LOWCore/crc32/zlib/zconf.h181#ifdef ZLIB_DLLCOMMENT
LOWCore/crc32/zlib/zconf.h201#define ZEXPORT WINAPICOMMENT
LOWCore/crc32/zlib/zconf.h221COMMENT
LOWCore/crc32/zlib/zconf.h261#endifCOMMENT
LOWCore/crc32/zlib/zconf.h281#define Z_HAVE_UNISTD_HCOMMENT
LOWCore/crc32/zlib/zconf.h301#ifndef Z_SOLOCOMMENT
LOWCore/crc32/zlib/zconf.h321#include <unistd.h> /* for SEEK_*, off_t, and _LFS64_LARGEFILE */COMMENT
LOWCore/crc32/zlib/zconf.h341#endifCOMMENT
LOWCore/crc32/zlib/zconf.h361#endifCOMMENT
LOWCore/aes/openssl/openssl_md5_locl.h21#define HASH_LONG MD5_LONGCOMMENT
68 more matches not shown…
Self-Referential Comments7 hits · 21 pts
SeverityFileLineSnippetContext
MEDIUMflutter/mmkv_ios/pubspec.yaml28# The following section is specific to Flutter.COMMENT
MEDIUMflutter/mmkv_android/pubspec.yaml28# The following section is specific to Flutter.COMMENT
MEDIUMflutter/mmkv/pubspec.yaml43# The following section is specific to Flutter.COMMENT
MEDIUMflutter/mmkv/example/pubspec.yaml38# The following section is specific to Flutter.COMMENT
MEDIUMflutter/mmkv_ohos/pubspec.yaml32# The following section is specific to Flutter packages.COMMENT
MEDIUMflutter/mmkv_win32/pubspec.yaml27# The following section is specific to Flutter packages.COMMENT
MEDIUMflutter/mmkv_linux/pubspec.yaml27# The following section is specific to Flutter packages.COMMENT
Excessive Try-Catch Wrapping2 hits · 3 pts
SeverityFileLineSnippetContext
LOWScript/dumpJavaSignature.py129 except Exception as e:CODE
MEDIUMScript/dumpJavaSignature.py144 print(f"Error: {e}")CODE
Slop Phrases1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMflutter/mmkv/example/pubspec.yaml42 # included with your application, so that you can use the icons inCOMMENT
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOW…y/src/ohosTest/ets/testrunner/OpenHarmonyTestRunner.ts27async function addAbilityMonitorCallback(err: any) {CODE