Repository Analysis

fission/fission

Fast and Simple Serverless Functions for Kubernetes

2.4 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of fission/fission, a Go project with 8,880 GitHub stars. SynthScan v2.0 examined 183,258 lines of code across 1092 source files, recording 423 pattern matches distributed across 10 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-14
Last Push
8.9K
Stars
Go
Language
183.3K
Lines of Code
1.1K
Files
423
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 2HIGH 1MEDIUM 7LOW 413

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 423 distinct pattern matches across 10 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 Block407 hits · 368 pts
SeverityFileLineSnippetContext
LOWskaffold.yaml181 - op: replaceCOMMENT
LOWcmd/fetcher/app/server.go121 // ServiceFetcher so a leak of this fetcher's runtime memory cannotCOMMENT
LOWtest/benchmark/config/thresholds.yaml1# Absolute pass/fail bounds for `fission-benchmark report --thresholds`.COMMENT
LOWtest/benchmark/pkg/scenario/assets.go1// SPDX-FileCopyrightText: The Fission AuthorsCOMMENT
LOWtest/integration/testdata/embed.go1//go:build integrationCOMMENT
LOWtest/integration/suites/common/archive_pruner_test.go21 "github.com/stretchr/testify/require"COMMENT
LOWtest/integration/suites/common/cors_test.go21COMMENT
LOWtest/integration/suites/common/mcp_test.go21 "github.com/fission/fission/pkg/utils"COMMENT
LOWtest/integration/suites/common/kubectl_test.go21)COMMENT
LOW…t/integration/suites/common/function_logs_loki_test.go21// TestFunctionLogsLokiCorrelation exercises the RFC-0016 OTLP logging read pathCOMMENT
LOWtest/integration/suites/common/streaming_test.go21 "github.com/fission/fission/test/integration/framework"COMMENT
LOWtest/integration/suites/common/cli_inspect_test.go21// TestCLICommands covers fission CLI commands that had no integration coverage:COMMENT
LOWtest/integration/suites/common/spec_merge_test.go21COMMENT
LOWtest/integration/suites/common/secret_cfgmap_test.go21)COMMENT
LOWtest/integration/suites/common/jvm_jersey_env_test.go21// TestJVMJerseyEnv covers the jvm-jersey environment via two paths, merged intoCOMMENT
LOW…st/integration/suites/common/archive_isolation_test.go21 "github.com/fission/fission/pkg/fission-cli/cmd"COMMENT
LOWtest/integration/suites/common/go_env_test.go21 "github.com/fission/fission/test/integration/framework"COMMENT
LOWtest/integration/suites/common/java_env_test.go21// TestJavaEnv covers the JVM (Spring Boot) environment via two paths, mergedCOMMENT
LOWtest/integration/suites/common/spec_archive_test.go21)COMMENT
LOW…/integration/suites/common/idle_objects_reaper_test.go21COMMENT
LOWtest/integration/suites/common/env_podspec_test.go21)COMMENT
LOWtest/integration/suites/common/archive_cli_test.go21 "github.com/stretchr/testify/require"COMMENT
LOWtest/integration/suites/common/rust_env_test.go21// The Rust environment always builds through its builder image: even a singleCOMMENT
LOWtest/integration/suites/common/gateway_test.go21COMMENT
LOWtest/integration/suites/common/container_update_test.go21 "github.com/fission/fission/test/integration/framework"COMMENT
LOWtest/integration/suites/common/hpa_scale_test.go81 // applied its defaulting) so we can later prove the executor does not churnCOMMENT
LOW…gration/suites/common/router_internal_listener_test.go21)COMMENT
LOWtest/integration/suites/common/function_test_test.go21// (was bash-disabled per https://github.com/fission/fission/issues/653,COMMENT
LOWtest/integration/suites/serial/dynamic_tenant_test.go21)COMMENT
LOWtest/integration/suites/serial/cluster_tenant_test.go21)COMMENT
LOWtest/integration/suites/serial/adopt_existing_test.go21 appsv1 "k8s.io/api/apps/v1"COMMENT
LOWtest/integration/suites/serial/adopt_existing_test.go41// flipped to the new executor, plus the function keeps serving. This is reliableCOMMENT
LOWtest/integration/suites/serial/async_invocation_test.go1// SPDX-FileCopyrightText: The Fission AuthorsCOMMENT
LOWtest/integration/framework/env.go21// EnvOptions are the inputs to TestNamespace.CreateEnv.COMMENT
LOWtest/integration/framework/env.go41 Poolsize intCOMMENT
LOWtest/integration/framework/env.go121 // For builder envs, the very next step is usually a source-archiveCOMMENT
LOWtest/integration/framework/tenant.go161 _, err := f.fissionClient.CoreV1().FissionTenants().Get(ctx, namespace, metav1.GetOptions{})COMMENT
LOWtest/integration/framework/specs.go21)COMMENT
LOWtest/integration/framework/testdata.go41// (no subdirectory entries — matches the bash idiom `zip -jr out.zip dir/`)COMMENT
LOWtest/integration/framework/framework.go41// corresponding Service — no kubectl port-forward needed — and block untilCOMMENT
LOWtest/integration/framework/framework.go201// KubeClient returns the Kubernetes clientset.COMMENT
LOWtest/integration/framework/framework.go241// to sign /fission-function/... requests on the internal listener.COMMENT
LOWtest/integration/framework/canary.go21 // Name of the CanaryConfig CR.COMMENT
LOWtest/integration/framework/cli.go21 "github.com/fission/fission/cmd/fission-cli/app"COMMENT
LOWtest/integration/framework/executor_lifecycle.go21 authorizationv1 "k8s.io/api/authorization/v1"COMMENT
LOWtest/integration/framework/executor_lifecycle.go81 require.Truef(t, res.Status.Allowed,COMMENT
LOWtest/integration/framework/function.go21 metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"COMMENT
LOWtest/integration/framework/function.go41 Src stringCOMMENT
LOWtest/integration/framework/function.go61 StreamingProtocol stringCOMMENT
LOWtest/integration/framework/function.go221COMMENT
LOWtest/integration/framework/function.go261COMMENT
LOWtest/integration/framework/executor_resources.go21)COMMENT
LOWtest/integration/framework/cwd.go21var cwdMutex sync.MutexCOMMENT
LOWtest/integration/framework/namespace.go21COMMENT
LOWtest/integration/framework/router.go21 "github.com/stretchr/testify/require"COMMENT
LOWtest/integration/framework/router.go121}COMMENT
LOWtest/integration/otel/loki.yaml1# SPDX-FileCopyrightText: The Fission AuthorsCOMMENT
LOWtest/integration/otel/otel-collector.yaml1# SPDX-FileCopyrightText: The Fission AuthorsCOMMENT
LOWtest/integration/otel/otel-collector.yaml21 config.yaml: |COMMENT
LOWtest/integration/otel/metrics-collector.reference.yaml1# SPDX-FileCopyrightText: The Fission AuthorsCOMMENT
347 more matches not shown…
Hallucination Indicators2 hits · 30 pts
SeverityFileLineSnippetContext
CRITICALpkg/apis/core/v1/types.go850 // +kubebuilder:validation:XValidation:rule="!has(self.container) || !has(self.container.securityContext) || !has(self.COMMENT
CRITICALpkg/apis/core/v1/types.go906 // +kubebuilder:validation:XValidation:rule="!has(self.container) || !has(self.container.securityContext) || !has(self.COMMENT
AI Slop Vocabulary3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/benchmark.yaml48 # path (or the benchmark harness) is caught against a real cluster before merge.COMMENT
MEDIUMpkg/storagesvc/authz.go31// robust to a subDir change between releases. "" maps a legacy id to theCOMMENT
MEDIUMpkg/fission-cli/cmd/function/run.go72 // Phase 5 — debugger. Extra published port for delve/debugpy (0 = none).COMMENT
Self-Referential Comments3 hits · 8 pts
SeverityFileLineSnippetContext
MEDIUM…dejs/spec_archive/specs/fission-deployment-config.yaml1# This file is generated by the 'fission spec init' command.COMMENT
MEDIUM…nodejs/spec_merge/specs/fission-deployment-config.yaml1# This file is generated by the 'fission spec init' command.COMMENT
MEDIUMpkg/fission-cli/cmd/spec/init.go121 msg := []byte("# This file is generated by the 'fission spec init' command.\n" +CODE
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHpkg/router/endpointcache/metrics.go100// alertable as requested != effective rather than as an absent series.COMMENT
Redundant / Tautological Comments3 hits · 7 pts
SeverityFileLineSnippetContext
LOWhack/deploy.sh17# Check if kubectl is installedCOMMENT
LOWhack/deploy.sh23# Check if minikube is installedCOMMENT
LOWhack/deploy.sh29# Check if helm is installedCOMMENT
Modern AI Meta-Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMpkg/webhook/service.go23 //+kubebuilder:scaffold:importsCOMMENT
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOW…integration/testdata/misc/huge_response/generated.json1502 "about": "Aliqua ex mollit duis cupidatat aliqua mollit. Sunt ea sit culpa sit voluptate fugiat laboris sint. Et ullCODE
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWtest/integration/testdata/python/multifile/main.py2CODE
Slop Phrases1 hit · 1 pts
SeverityFileLineSnippetContext
LOWhack/release.sh82echo "Don't forget to push chart repo changes & update CHANGELOG.md"CODE