Repository Analysis

raineorshine/npm-check-updates

Find newer versions of package dependencies than what your package.json allows

12.6 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of raineorshine/npm-check-updates, a TypeScript project with 10,276 GitHub stars. SynthScan v2.0 examined 42,952 lines of code across 262 source files, recording 102 pattern matches distributed across 5 syntactic categories. The overall adjusted score of 12.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).

12.6
Adjusted Score
12.6
Raw Score
100%
Time Factor
2026-07-14
Last Push
10.3K
Stars
TypeScript
Language
43.0K
Lines of Code
262
Files
102
Pattern Hits
2026-07-14
Scan Date
0.32
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

Longitudinal tracking requires multiple scan runs. Once this repository is re-scanned after new commits land, this chart will visualise how the synthetic code signal evolves over time — enabling you to detect whether AI authorship is growing, stabilising, or being actively corrected by human engineers.

No multi-scan history yet — run the scanner again to build trend data.

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 85MEDIUM 1LOW 16

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 102 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.

Cross-Language Confusion (JS/TS)85 hits · 520 pts
SeverityFileLineSnippetContext
HIGHsrc/index.ts83 print(options, message, 'error')CODE
HIGHsrc/index.ts127 print(options, '')CODE
HIGHsrc/index.ts152 print(options, '')CODE
HIGHsrc/index.ts170 print(options, '')CODE
HIGHsrc/index.ts172 print(options, 'Installing dependencies...')CODE
HIGHsrc/index.ts212 print(options, stdout)CODE
HIGHsrc/index.ts213 print(options, 'Done')CODE
HIGHsrc/index.ts229 print(options, `\n${installHint}.`)CODE
HIGHsrc/index.ts304 print(pkgOptions, '')CODE
HIGHsrc/index.ts306 print(pkgOptions, `${pkgOptions.upgrade ? 'Upgrading' : 'Checking'} ${relPathToPackage} catalog dependencies`)CODE
HIGHsrc/index.ts310 print(pkgOptions, '')CODE
HIGHsrc/index.ts358 print(options, '')CODE
HIGHsrc/index.ts398 print(options, 'Initializing', 'verbose')CODE
HIGHsrc/index.ts433 print(options, `Usage: ncu --doctor\n\n${help}`, 'warn')CODE
HIGHsrc/lib/initOptions.ts103 print(options, `Using config file ${options.rcConfigPath}`)CODE
HIGHsrc/lib/initOptions.ts119 print(options, chalk.yellow(deprecationMessage), 'warn')CODE
HIGHsrc/lib/initOptions.ts121 print(options, '', 'warn')CODE
HIGHsrc/lib/initOptions.ts239 print(CODE
HIGHsrc/lib/initOptions.ts245 print({ ...options, json }, `Using minimumReleaseAge from pnpm-workspace.yaml: ${formatDays(days)}`)CODE
HIGHsrc/lib/initOptions.ts261 print(CODE
HIGHsrc/lib/initOptions.ts267 print({ ...options, json }, `Using npmMinimalAgeGate from .yarnrc.yml: ${formatDays(days)}`)CODE
HIGHsrc/lib/initOptions.ts307 print(CODE
HIGHsrc/lib/initOptions.ts313 print({ ...options, json }, `Using min-release-age from .npmrc: ${formatDays(days)}`)CODE
HIGHsrc/lib/initOptions.ts367 print(resolvedOptionsFiltered, `Using ${packageManager}`)CODE
HIGHsrc/lib/runGlobal.ts13 print(options, '\nOptions:', 'verbose')CODE
HIGHsrc/lib/runGlobal.ts16 print(options, '\nGetting installed packages', 'verbose')CODE
HIGHsrc/lib/runGlobal.ts36 print(options, 'globalPackages:', 'verbose')CODE
HIGHsrc/lib/runGlobal.ts37 print(options, globalPackages, 'verbose')CODE
HIGHsrc/lib/runGlobal.ts38 print(options, '', 'verbose')CODE
HIGHsrc/lib/runGlobal.ts39 print(options, `Fetching ${options.target} versions`, 'verbose')CODE
HIGHsrc/lib/runGlobal.ts42 print(options, latest, 'verbose')CODE
HIGHsrc/lib/runGlobal.ts81 print(CODE
HIGHsrc/lib/programError.ts18 print(options, color ? chalk.red(message) : message, null, 'error')CODE
HIGHsrc/lib/runLocal.ts108 print(options, '')CODE
HIGHsrc/lib/runLocal.ts179 print(options, '\nOptions:', 'verbose')CODE
HIGHsrc/lib/runLocal.ts199 print(options, '\nCurrent versions:', 'verbose')CODE
HIGHsrc/lib/runLocal.ts200 print(options, current, 'verbose')CODE
HIGHsrc/lib/runLocal.ts235 print(options, '\nupgradedPeerDependencies:', 'verbose')CODE
HIGHsrc/lib/runLocal.ts236 print(options, upgradedPeerDependencies, 'verbose')CODE
HIGHsrc/lib/runLocal.ts239 print(CODE
HIGHsrc/lib/runLocal.ts246 print(options, latest, 'verbose')CODE
HIGHsrc/lib/runLocal.ts248 print(options, '\nUpgraded versions:', 'verbose')CODE
HIGHsrc/lib/runLocal.ts249 print(options, upgraded, 'verbose')CODE
HIGHsrc/lib/runLocal.ts337 print(options, upgradeHint)CODE
HIGHsrc/lib/cache.ts122 print(CODE
HIGHsrc/lib/cache.ts127 print(options, cacheHits, 'verbose')CODE
HIGHsrc/lib/findPackage.ts34 print(options, `${options.upgrade ? 'Upgrading' : 'Checking'} ${relPathToPackage}`)CODE
HIGHsrc/lib/findPackage.ts56 print(options, 'Running in local mode', 'verbose')CODE
HIGHsrc/lib/findPackage.ts57 print(options, 'Finding package file data', 'verbose')CODE
HIGHsrc/lib/findPackage.ts67 print(options, 'Waiting for package data on stdin', 'verbose')CODE
HIGHsrc/lib/logging.ts477 print(options, '\n' + chalk.blue(chalk.bold('Updates')))CODE
HIGHsrc/lib/logging.ts479 print(options, '')CODE
HIGHsrc/lib/logging.ts488 print(options, 'No dependencies.')CODE
HIGHsrc/lib/logging.ts497 print(CODE
HIGHsrc/lib/logging.ts506 print(options, `All global packages are up-to-date ${smiley}`)CODE
HIGHsrc/lib/logging.ts508 print(CODE
HIGHsrc/lib/logging.ts514 print(options, `No dependencies upgraded ${smiley}`)CODE
HIGHsrc/lib/logging.ts547 print(options, table)CODE
HIGHsrc/lib/logging.ts555 print(options, `\nIgnored incompatible updates (engines node):\n`)CODE
HIGHsrc/lib/logging.ts565 print(options, table)CODE
25 more matches not shown…
Hyper-Verbose Identifiers14 hits · 14 pts
SeverityFileLineSnippetContext
LOWsrc/lib/getIgnoredUpgradesDueToEnginesNode.ts17export async function getIgnoredUpgradesDueToEnginesNode(CODE
LOWsrc/lib/version-util.ts476export function upgradeDependencyDeclaration(CODE
LOWsrc/lib/upgradePackageDefinitions.ts75export async function upgradePackageDefinitions(CODE
LOWsrc/lib/upgradeJsonCatalogDependencies.ts9export async function upgradeJsonCatalogDependencies(CODE
LOWsrc/lib/getPeerDependenciesFromRegistry.ts56async function getPeerDependenciesFromRegistry(packageMap: Index<Version>, options: Options) {CODE
LOWsrc/lib/queryVersions.ts43 async function getPackageVersionProtected(dep: VersionSpec): Promise<VersionResult> {CODE
LOWsrc/lib/getEnginesNodeFromRegistry.ts15async function getEnginesNodeFromRegistry(packageMap: Index<Version>, options: Options) {CODE
LOWsrc/lib/upgradeYamlCatalogDependencies.ts93export function updateYamlCatalogDependencies({CODE
LOWsrc/lib/getIgnoredUpgradesDueToPeerDeps.ts11export async function getIgnoredUpgradesDueToPeerDeps(CODE
LOWsrc/lib/logging.ts551export function printIgnoredUpdatesDueToEnginesNode(CODE
LOWsrc/lib/logging.ts275async function printSkippedByCooldownTable({CODE
LOWsrc/lib/logging.ts535export function printIgnoredUpdatesDueToPeerDeps(options: Options, ignoredUpdates: Index<IgnoredUpgradeDueToPeerDeps>) {CODE
LOWsrc/package-managers/filters.ts16export function allowDeprecatedOrIsNotDeprecated(versionResult: Partial<Packument>, options: Options): boolean {CODE
LOWsrc/package-managers/filters.ts52export function satisfiesPeerDependencies(versionResult: Partial<Packument>, peerDependencies: Index<Index<Version>>) {CODE
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMtest/e2e.sh113# Create a package.json file with a dependency on npm-check-updates since it is already published to the local registryCOMMENT
Structural Annotation Overuse1 hit · 2 pts
SeverityFileLineSnippetContext
LOWtest/e2e.sh33 # WARNING: The original authToken cannot be restored because it is protected and cannot be read with 'npm config get'.COMMENT
Over-Commented Block1 hit · 1 pts
SeverityFileLineSnippetContext
LOWsrc/bin/cli.ts21 //COMMENT