Repository Analysis

fluxcd/flux2

Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.

4.8 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of fluxcd/flux2, a Go project with 8,273 GitHub stars. SynthScan v2.0 examined 58,639 lines of code across 612 source files, recording 84 pattern matches distributed across 4 syntactic categories. The overall adjusted score of 4.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).

4.8
Adjusted Score
4.8
Raw Score
100%
Time Factor
2026-07-13
Last Push
8.3K
Stars
Go
Language
58.6K
Lines of Code
612
Files
84
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 1HIGH 0MEDIUM 72LOW 11

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 84 distinct pattern matches across 4 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.

Self-Referential Comments72 hits · 259 pts
SeverityFileLineSnippetContext
MEDIUMcmd/flux/create_secret_notation.go40 Example: ` # Create a Notation configuration secret on disk and encrypt it with Mozilla SOPSCODE
MEDIUMcmd/flux/create_secret_receiver.go40 Example: ` # Create a receiver secret for a GitHub webhookCODE
MEDIUMcmd/flux/create_secret_receiver.go47 # Create a receiver secret for GCR with email claimCOMMENT
MEDIUMcmd/flux/create_source_bucket.go45 Example: ` # Create a source for a Bucket using static authenticationCODE
MEDIUMcmd/flux/create_source_bucket.go54 # Create a source for an Amazon S3 Bucket using IAM authenticationCOMMENT
MEDIUMcmd/flux/create_receiver.go41 Example: ` # Create a ReceiverCODE
MEDIUMcmd/flux/bootstrap_github.go47 Example: ` # Create a GitHub personal access token and export it as an env varCODE
MEDIUMcmd/flux/create_source_oci.go42 Example: ` # Create an OCIRepository for a public container imageCODE
MEDIUMcmd/flux/create_source_oci.go48 # Create an OCIRepository with OIDC signature verificationCOMMENT
MEDIUMcmd/flux/create_source_oci.go57 # Create an OCIRepository for a Helm chart layerCOMMENT
MEDIUMcmd/flux/create_kustomization.go45 Example: ` # Create a Kustomization resource from a source at a given pathCODE
MEDIUMcmd/flux/create_kustomization.go54 # Create a Kustomization resource that depends on the previous oneCOMMENT
MEDIUMcmd/flux/create_kustomization.go62 # Create a Kustomization using a source from a different namespaceCOMMENT
MEDIUMcmd/flux/create_kustomization.go70 # Create a Kustomization resource that references an OCIRepositoryCOMMENT
MEDIUMcmd/flux/create_kustomization.go77 # Create a Kustomization resource that references a BucketCOMMENT
MEDIUMcmd/flux/create_secret_tls.go36 Example: ` # Create a TLS secret on disk and encrypt it with SOPS.CODE
MEDIUMcmd/flux/create_helmrelease.go50 Example: ` # Create a HelmRelease with a chart from a HelmRepository sourceCODE
MEDIUMcmd/flux/create_helmrelease.go57 # Create a HelmRelease with a chart from a GitRepository sourceCOMMENT
MEDIUMcmd/flux/create_helmrelease.go63 # Create a HelmRelease with a chart from a Bucket sourceCOMMENT
MEDIUMcmd/flux/create_helmrelease.go69 # Create a HelmRelease with values from local YAML filesCOMMENT
MEDIUMcmd/flux/create_helmrelease.go76 # Create a HelmRelease with values from a Kubernetes secretCOMMENT
MEDIUMcmd/flux/create_helmrelease.go84 # Create a HelmRelease with a custom release nameCOMMENT
MEDIUMcmd/flux/create_helmrelease.go90 # Create a HelmRelease targeting another namespace than the resourceCOMMENT
MEDIUMcmd/flux/create_helmrelease.go97 # Create a HelmRelease with custom storage namespace for hub-and-spoke modelCOMMENT
MEDIUMcmd/flux/create_helmrelease.go104 # Create a HelmRelease using a source from a different namespaceCOMMENT
MEDIUMcmd/flux/create_helmrelease.go110 # Create a HelmRelease definition on disk without applying it on the clusterCOMMENT
MEDIUMcmd/flux/create_helmrelease.go117 # Create a HelmRelease using a chart from a HelmChart resourceCOMMENT
MEDIUMcmd/flux/create_helmrelease.go122 # Create a HelmRelease using a chart from an OCIRepository resourceCOMMENT
MEDIUMcmd/flux/create_secret_helm.go36 Example: ` # Create a Helm authentication secret on disk and encrypt it with Mozilla SOPSCODE
MEDIUMcmd/flux/create_source_git.go75 Example: ` # Create a source from a public Git repository master branchCODE
MEDIUMcmd/flux/create_source_git.go80 # Create a source for a Git repository pinned to specific git tagCOMMENT
MEDIUMcmd/flux/create_source_git.go85 # Create a source from a public Git repository tag that matches a semver rangeCOMMENT
MEDIUMcmd/flux/create_source_git.go90 # Create a source for a Git repository using SSH authenticationCOMMENT
MEDIUMcmd/flux/create_source_git.go95 # Create a source for a Git repository using SSH authentication and anCOMMENT
MEDIUMcmd/flux/create_source_git.go103 # Create a source for a Git repository using SSH authentication and aCOMMENT
MEDIUMcmd/flux/create_source_git.go111 # Create a source for a Git repository using SSH authentication and aCOMMENT
MEDIUMcmd/flux/create_source_git.go120 # Create a source for a Git repository using basic authenticationCOMMENT
MEDIUMcmd/flux/create_source_git.go127 # Create a source for a Git repository using AWS CodeCommit with IAM credentialsCOMMENT
MEDIUMcmd/flux/create_source_git.go133 # Create a source for a Git repository using azure providerCOMMENT
MEDIUMcmd/flux/create_alertprovider.go40 Example: ` # Create a Provider for a Slack channelCODE
MEDIUMcmd/flux/create_alertprovider.go47 # Create a Provider for a Github repositoryCOMMENT
MEDIUMcmd/flux/create_source_chart.go41 Example: ` # Create a source for a chart residing in a HelmRepositoryCODE
MEDIUMcmd/flux/create_source_chart.go47 # Create a source for a chart residing in a Git repositoryCOMMENT
MEDIUMcmd/flux/create_source_chart.go52 # Create a source for a chart residing in a S3 BucketCOMMENT
MEDIUMcmd/flux/create_source_chart.go57 # Create a source for a chart from OCI and verify its signatureCOMMENT
MEDIUMcmd/flux/bootstrap_bitbucket_server.go48 Example: ` # Create a Bitbucket Server API token and export it as an env varCODE
MEDIUMcmd/flux/bootstrap_gitlab.go51 Example: ` # Create a GitLab API token and export it as an env varCODE
MEDIUMcmd/flux/create_alert.go41 Example: ` # Create an Alert for kustomization eventsCODE
MEDIUMcmd/flux/create_secret_git.go43 Example: ` # Create a Git SSH authentication secret using an ECDSA P-521 curve public keyCODE
MEDIUMcmd/flux/create_secret_git.go50 # Create a Git SSH authentication secret with a passwordless private key from fileCOMMENT
MEDIUMcmd/flux/create_secret_git.go56 # Create a Git SSH authentication secret with a passworded private key from fileCOMMENT
MEDIUMcmd/flux/create_secret_git.go63 # Create a secret for a Git repository using basic authenticationCOMMENT
MEDIUMcmd/flux/create_secret_git.go69 # Create a Git SSH secret on diskCOMMENT
MEDIUMcmd/flux/create_source_helm.go46 Example: ` # Create a source for an HTTPS public Helm repositoryCODE
MEDIUMcmd/flux/create_source_helm.go51 # Create a source for an HTTPS Helm repository using basic authenticationCOMMENT
MEDIUMcmd/flux/create_source_helm.go57 # Create a source for an HTTPS Helm repository using TLS authenticationCOMMENT
MEDIUMcmd/flux/create_source_helm.go64 # Create a source for an OCI Helm repositoryCOMMENT
MEDIUMcmd/flux/create_source_helm.go70 # Create a source for an OCI Helm repository using an existing secret with basic auth or dockerconfig credentialsCOMMENT
MEDIUMcmd/flux/bootstrap_gitea.go47 Example: ` # Create a Gitea personal access token and export it as an env varCODE
MEDIUMcmd/flux/create_tenant.go43 Example: ` # Create a tenant with access to a namespaceCODE
12 more matches not shown…
Hallucination Indicators1 hit · 10 pts
SeverityFileLineSnippetContext
CRITICALcmd/flux/get_image_repository.go83 lastScan = item.Status.LastScanResult.ScanTime.Time.Format(time.RFC3339)CODE
Over-Commented Block10 hits · 10 pts
SeverityFileLineSnippetContext
LOWcmd/flux/cluster_info.go41// fluxClusterInfo contains information about an existing flux installation on a cluster.COMMENT
LOWcmd/flux/readiness.go61COMMENT
LOWrfcs/0012-external-artifact/README.md81status:COMMENT
LOWrfcs/0010-multi-tenant-workload-identity/README.md841 // the environment of the controller pod, e.g. files mounted in the pod,COMMENT
LOWrfcs/0010-multi-tenant-workload-identity/README.md861 serviceAccount corev1.ServiceAccount, opts ...Option) (Token, error)COMMENT
LOWrfcs/0010-multi-tenant-workload-identity/README.md961}COMMENT
LOW.github/runners/runner-setup.sh1#!/usr/bin/env bashCOMMENT
LOW.github/runners/prereq.sh1#!/usr/bin/env bashCOMMENT
LOWmanifests/scripts/bundle.sh1#!/usr/bin/env bashCOMMENT
LOWpkg/bootstrap/bootstrap.go61 ReconcileComponents(ctx context.Context, manifestsBase string, options install.Options, secretOpts sourcesecret.OptionsCOMMENT
Redundant / Tautological Comments1 hit · 1 pts
SeverityFileLineSnippetContext
LOWcmd/flux/diff_artifact.go36 Example: `# Check if local files differ from remoteCODE