Repository Analysis

ipfs/kubo

An IPFS implementation in Go

2.4 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of ipfs/kubo, a Go project with 17,081 GitHub stars. SynthScan v2.0 examined 156,750 lines of code across 793 source files, recording 181 pattern matches distributed across 11 syntactic categories. The overall adjusted score of 2.4 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.4
Adjusted Score
2.4
Raw Score
100%
Time Factor
2026-07-13
Last Push
17.1K
Stars
Go
Language
156.8K
Lines of Code
793
Files
181
Pattern Hits
2026-07-14
Scan Date
0.01
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 7HIGH 1MEDIUM 47LOW 126

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 181 distinct pattern matches across 11 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.

Decorative Section Separators43 hits · 111 pts
SeverityFileLineSnippetContext
MEDIUMtest/sharness/t0114-gateway-subdomains.sh10## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh12## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh83## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh85## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh128## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh131## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh206## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh209## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh292## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh294## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh324## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh327## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh342# =============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh466# ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh497# ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh521## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh573# =============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh599## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh601## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh616# =============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh646## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh649## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh740## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh742## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh773## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh775## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh807## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh809## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh890## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh892## ============================================================================COMMENT
MEDIUMtest/sharness/t0114-gateway-subdomains.sh908# =============================================================================COMMENT
MEDIUMtest/sharness/t0109-gateway-web-_redirects.sh10## ============================================================================COMMENT
MEDIUMtest/sharness/t0109-gateway-web-_redirects.sh12## ============================================================================COMMENT
MEDIUMtest/sharness/t0115-gateway-dir-listing.sh10## ============================================================================COMMENT
MEDIUMtest/sharness/t0115-gateway-dir-listing.sh12## ============================================================================COMMENT
MEDIUMtest/sharness/t0115-gateway-dir-listing.sh30## ============================================================================COMMENT
MEDIUMtest/sharness/t0115-gateway-dir-listing.sh32## ============================================================================COMMENT
MEDIUMtest/sharness/t0115-gateway-dir-listing.sh68## ============================================================================COMMENT
MEDIUMtest/sharness/t0115-gateway-dir-listing.sh70## ============================================================================COMMENT
MEDIUMtest/sharness/t0115-gateway-dir-listing.sh109## ============================================================================COMMENT
MEDIUMtest/sharness/t0115-gateway-dir-listing.sh111## ============================================================================COMMENT
MEDIUMtest/sharness/t0115-gateway-dir-listing.sh160## ============================================================================COMMENT
MEDIUMtest/sharness/t0115-gateway-dir-listing.sh162## ============================================================================COMMENT
Over-Commented Block103 hits · 103 pts
SeverityFileLineSnippetContext
LOWtracing/doc.go1// Package tracing contains the tracing logic for go-ipfs, including configuring the tracer andCOMMENT
LOWtracing/doc.go21// - OTEL_EXPORTER_OTLP_PROTOCOLCOMMENT
LOWtracing/doc.go41// a full Jaeger stack and configure Kubo to publish traces to it:COMMENT
LOWtracing/doc.go61//COMMENT
LOWcore/builder.go21type FXNodeInfo struct {COMMENT
LOWcore/builder.go141 // TODO: How soon will bootstrap move to libp2p?COMMENT
LOWcore/corehttp/gateway.go281 })COMMENT
LOWcore/corehttp/corehttp.go81// Serve accepts incoming HTTP connections on the listener and passes themCOMMENT
LOWcore/coreiface/unixfs.go81 Get(context.Context, path.Path) (files.Node, error)COMMENT
LOWcore/coreiface/unixfs.go101 Ls(context.Context, path.Path, chan<- DirEntry, ...options.UnixfsLsOption) errorCOMMENT
LOWcore/coreiface/name.go21// IPNS is a PKI namespace, where names are the hashes of public keys, and theCOMMENT
LOWcore/commands/provide.go201COMMENT
LOWcore/commands/provide.go781COMMENT
LOWcore/commands/refs.go221 var count intCOMMENT
LOWcore/commands/dag/import.go121COMMENT
LOWcore/commands/dag/export.go141 }COMMENT
LOWcore/commands/cmdenv/cidbase.go61}COMMENT
LOWcore/commands/cmdenv/env.go101// - If Provide.DHT.SweepEnabled=true or OptimisticProvide=true, we make anCOMMENT
LOWcore/commands/cmdenv/env.go121// - wait: whether to block until provide completes (sync mode)COMMENT
LOWcore/commands/cmdenv/env.go201// Context handling:COMMENT
LOWcore/node/provider.go101const consecutiveAlertsThreshold = 3COMMENT
LOWcore/node/provider.go121 // can happen if the provider is closed or if the node is currently OfflineCOMMENT
LOWcore/node/provider.go141 // The keys are not deleted from the keystore, so they will continue to beCOMMENT
LOWcore/node/provider.go661 // In no-schedule mode the on-disk keystore is never used. If aCOMMENT
LOWcore/node/provider.go721 }COMMENT
LOWcore/node/provider.go1321COMMENT
LOWcore/node/p2pforge_resolver.go21// falls back to network DNS. This ensures future <peerID>.libp2p.direct recordsCOMMENT
LOWcore/node/libp2p/routingopt.go321)COMMENT
LOWcore/node/libp2p/addrs.go61// listenAddrs must be already-resolved interface addresses (output ofCOMMENT
LOWcore/node/libp2p/addrs.go141 return "", falseCOMMENT
LOWcore/node/libp2p/addrs.go201// MonitorDeadListeners runs findDeadListeners at startup and on everyCOMMENT
LOWtest/ipfs-test-lib.sh81}COMMENT
LOWtest/sharness/t0051-object.sh41 # only manipulates ProtoNode links without updating UnixFS metadata.COMMENT
LOWtest/sharness/t0095-refs.sh1#!/usr/bin/env bashCOMMENT
LOWtest/sharness/t0095-refs.sh21# L2- D 1.txt B 2.txtCOMMENT
LOWtest/sharness/t0095-refs.sh41# added QmU6xujRsYzcrkocuR3fhfnkZBB8eyUFFq4WKRGw2aS15h ACOMMENT
LOWtest/sharness/t0116-gateway-cache.sh1#!/usr/bin/env bashCOMMENT
LOWtest/sharness/t0114-gateway-subdomains/README.md101# RSA_IPNS_IDv0=QmVujd5Vb7moysJj8itnGufN7MEtPRCNHkKpNuA4onsRa3COMMENT
LOWtest/cli/add_test.go601// createDirectoryForHAMTLinksEstimation creates a directory with the specified numberCOMMENT
LOWtest/cli/provider_test.go1421 // dagwalker: bloom creation logCOMMENT
LOWtest/cli/provider_test.go1501 require.Contains(t, daemonLog, "bloom tracker created")COMMENT
LOWtest/cli/provider_test.go1681 assert.NotContains(t, statRes.Stderr.String(), "stats not available",COMMENT
LOWtest/cli/provider_test.go1801func dirExists(path string) bool {COMMENT
LOWtest/cli/provider_test.go1821// closes the keystore. The line-scan below fails on the exactCOMMENT
LOWtest/cli/cid_profiles_test.go61 // SmallFileCID is the deterministic CID for "hello world" string.COMMENT
LOWtest/cli/cid_profiles_test.go681 cidLen intCOMMENT
LOWtest/cli/dag_layout_test.go21//COMMENT
LOWtest/cli/key_test.go21//COMMENT
LOWtest/cli/pubsub_test.go41 }COMMENT
LOWtest/cli/dag_test.go501 // leaves 2 blocks. Asserting the exact count proves --offline wasCOMMENT
LOWtest/cli/update_test.go161 t.Parallel()COMMENT
LOWtest/cli/update_test.go321 "binary at %s should contain the extracted archive content", tmpBinPath)COMMENT
LOWtest/cli/update_test.go481// "ipfs update check" and "ipfs update versions" without touching theCOMMENT
LOWtest/cli/block_size_test.go21 twoMiBPlus = twoMiB + 1 // 2097153COMMENT
LOWtest/cli/block_size_test.go201 t.Run("ipfs add non-raw-leaves", func(t *testing.T) {COMMENT
LOWtest/cli/provide_stats_test.go41// Tests will naturally fail if upstream removes/renames fields we depend on.COMMENT
LOWtest/cli/fuse/realworld_test.go1//go:build (linux || darwin || freebsd) && !nofuseCOMMENT
LOWtest/cli/harness/log.go21func (e events) Len() int { return len(e) }COMMENT
LOWtest/cli/autoconf/extensibility_test.go21// 1. New systems can be added via AutoConf's SystemRegistryCOMMENT
LOWtest/cli/autoconf/expand_comprehensive_test.go1// Package autoconf provides comprehensive tests for --expand-auto functionality.COMMENT
43 more matches not shown…
Hallucination Indicators7 hits · 100 pts
SeverityFileLineSnippetContext
CRITICALcore/node/groups.go116 enableTCPTransport := cfg.Swarm.Transports.Network.TCP.WithDefault(true)CODE
CRITICALcore/node/groups.go117 enableWebsocketTransport := cfg.Swarm.Transports.Network.Websocket.WithDefault(true)CODE
CRITICALcore/node/groups.go118 enableRelayTransport := cfg.Swarm.Transports.Network.Relay.WithDefault(true) // nolintCODE
CRITICALcore/node/bitswap.go134 maxProviders = int(in.Cfg.Internal.Bitswap.ProviderSearchMaxResults.WithDefault(DefaultMaxProviders))CODE
CRITICALplugin/plugins/telemetry/telemetry.go427 p.event.ProvideDHTSweepEnabled = p.config.Provide.DHT.SweepEnabled.WithDefault(config.DefaultProvideDHTSweepEnabled)CODE
CRITICALplugin/plugins/telemetry/telemetry.go428 p.event.ProvideDHTIntervalCustom = !p.config.Provide.DHT.Interval.IsDefault()CODE
CRITICALplugin/plugins/telemetry/telemetry.go429 p.event.ProvideDHTMaxWorkersCustom = !p.config.Provide.DHT.MaxWorkers.IsDefault()CODE
Structural Annotation Overuse11 hits · 19 pts
SeverityFileLineSnippetContext
LOWtest/cli/autoconf/autoconf_test.go423 // Step 1: Create bootstrap node (target for connections)COMMENT
LOWtest/cli/autoconf/autoconf_test.go443 // Step 2: Create autoconf server that returns bootstrap node's addressCOMMENT
LOWtest/cli/autoconf/autoconf_test.go466 // Step 3: Create autoconf-enabled node that should connect to bootstrap nodeCOMMENT
LOWtest/cli/autoconf/autoconf_test.go479 // Step 4: Give time for autoconf resolution and connection attemptsCOMMENT
LOWtest/cli/autoconf/autoconf_test.go482 // Step 5: Verify both nodes are responsiveCOMMENT
LOWtest/cli/autoconf/autoconf_test.go489 // Step 6: Verify that autoconf node connected to bootstrap nodeCOMMENT
LOWtest/cli/autoconf/autoconf_test.go511 // Step 7: Verify bootstrap configuration still shows "auto" (not resolved values)COMMENT
LOWdocs/add-code-flow.md55### Step 1: ChunkingCOMMENT
LOWdocs/add-code-flow.md75### Step 2: Building the DAGCOMMENT
LOWdocs/add-code-flow.md111### Step 3: Storing BlocksCOMMENT
LOWdocs/add-code-flow.md118### Step 4: PinningCOMMENT
Verbosity Indicators7 hits · 13 pts
SeverityFileLineSnippetContext
LOWtest/cli/autoconf/autoconf_test.go423 // Step 1: Create bootstrap node (target for connections)COMMENT
LOWtest/cli/autoconf/autoconf_test.go443 // Step 2: Create autoconf server that returns bootstrap node's addressCOMMENT
LOWtest/cli/autoconf/autoconf_test.go466 // Step 3: Create autoconf-enabled node that should connect to bootstrap nodeCOMMENT
LOWtest/cli/autoconf/autoconf_test.go479 // Step 4: Give time for autoconf resolution and connection attemptsCOMMENT
LOWtest/cli/autoconf/autoconf_test.go482 // Step 5: Verify both nodes are responsiveCOMMENT
LOWtest/cli/autoconf/autoconf_test.go489 // Step 6: Verify that autoconf node connected to bootstrap nodeCOMMENT
LOWtest/cli/autoconf/autoconf_test.go511 // Step 7: Verify bootstrap configuration still shows "auto" (not resolved values)COMMENT
AI Response Leakage1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHtracing/doc.go60// # In this example the Jaeger UI is available at http://localhost:16686.COMMENT
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMcmd/ipfs/kubo/daemon.go465 // Private setups can't leverage peers returned by default IPNIs (Routing.Type=auto)COMMENT
MEDIUM.github/workflows/gotest.yml190 # under the harness temp dir (ipfs/ipns/mfs subdirectories).COMMENT
Self-Referential Comments2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMtest/sharness/t0114-gateway-subdomains.sh28 # Create a raw URL version with IP to ensure hostname from Host header is usedCOMMENT
MEDIUMtest/sharness/t0250-files-api.sh70 # Create the files in reverse (unsorted) order (`seq 100 -1 1`)COMMENT
Example Usage Blocks2 hits · 3 pts
SeverityFileLineSnippetContext
LOWbin/push-docker-tags.sh15# Usage:COMMENT
LOWbin/get-docker-tags.sh5# Usage:COMMENT
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOWtest/cli/provider_test.go1768 fmt.Sprintf("/provider/keystore/%d/fake-key-%d", i%2, i),CODE
LOWtest/cli/provider_test.go1791 key := fmt.Sprintf("/provider/keystore/%d/fake-key-%d", i%2, i)CODE
Redundant / Tautological Comments1 hit · 1 pts
SeverityFileLineSnippetContext
LOWcore/commands/log.go87 ipfs log level all info # Set ALL to 'info' (including default)CODE