AI Slop Code Risk Monitor

greensock/GSAP

Name: greensock/GSAP — JavaScript Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

GSAP (GreenSock Animation Platform), a JavaScript animation library for the modern web

0.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for greensock/GSAP, a JavaScript project with 29,962 GitHub stars. SynthScan examined 54,652 lines of code across 103 source files, recording 25 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.7 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

0.7

Adjusted Signal

0.7

Raw Pattern Score

100%

Time Factor

2026-04-13

Last Push

30.0K

Stars

JavaScript

Language

54.7K

Lines of Code

103

Files

Pattern Hits

2026-10-31

Scan Date

0.00

HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 3.4/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 25 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

Are imports declared and package/API names verified? 0 finding(s).

Agent Over-Engineering Ratio 0.5/100 · LOW

Are wrappers, guards, and repeated structures necessary? 5 finding(s).

PR Review Velocity Impact 3.9/100 · LOW

Which changes need focused human review? 25 finding(s).

What These Metrics Mean

Adjusted Signal: Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score: Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor: A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits: Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate: High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files: Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 0MEDIUM 9LOW 16

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 25 distinct pattern matches across 4 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. 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 configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

AI Slop Vocabulary9 hits · 21 pts

Severity	File	Line	Snippet	Context
MEDIUM	esm/ScrollTrigger.js	2557	// iOS bug: it'll show the address bar but NOT fire the window "resize" event until the animation is done but we	COMMENT
MEDIUM	esm/ScrollTrigger.js	2685	// smaller file size way to leverage in ScrollSmoother and Observer	COMMENT
MEDIUM	esm/gsap-core.js	428	timeline._zTime = -_tinyNum; // helps ensure that the next render() will be forced (crossingStart = true in render()	CODE
MEDIUM	esm/gsap-core.js	695	//n:1 is just to indicate v was a number; we leverage that later to set v according to the length we get. If a num	COMMENT
MEDIUM	src/ScrollTrigger.js	1693	if (_fixIOSBug && tween.vars.scrollY >= maxY \|\| currentScroll >= maxY-1) { // iOS bug: it'll show the address bar bu	CODE
MEDIUM	src/ScrollTrigger.js	1773	ScrollTrigger.core = { // smaller file size way to leverage in ScrollSmoother and Observer	CODE
MEDIUM	src/gsap-core.js	284	timeline._zTime = -_tinyNum; // helps ensure that the next render() will be forced (crossingStart = true in render())	CODE
MEDIUM	src/gsap-core.js	456	let vars = _isObject(v) ? v : {each:v}, //n:1 is just to indicate v was a number; we leverage that later to set v acco	CODE
MEDIUM	src/SplitText.ts	490	if (anim) { // if the user returned an animation in the onSplit, we record the totalTime() here and revert() it and	CODE

Over-Commented Block9 hits · 9 pts

Severity	File	Line	Snippet	Context
LOW	types/scroll-smoother.d.ts	241	*	COMMENT
LOW	types/scroll-smoother.d.ts	261	// sections(targets: gsap.DOMTarget, vars?: ScrollSmoother.SectionVars \| null): ScrollTrigger[];	COMMENT
LOW	types/index.d.ts	1	// Type definitions for gsap 3	COMMENT
LOW	types/index.d.ts	21	/// <reference path="gsap-plugins.d.ts"/>	COMMENT
LOW	esm/utils/matrix.js	81	// let a = [],	COMMENT
LOW	src/MotionPathPlugin.js	41	// feed in an array of quadratic bezier points like [{x: 0, y: 0}, ...] and it'll convert it to cubic bezier	COMMENT
LOW	src/Flip.js	1041	}	COMMENT
LOW	src/utils/matrix.js	61	// _forceDisplay = e => {	COMMENT
LOW	src/utils/matrix.js	321	// export function getMatrix(element) {	COMMENT

Hyper-Verbose Identifiers5 hits · 5 pts

Severity	File	Line	Snippet	Context
LOW	esm/ScrollSmoother.js	231	adjustEffectRelatedTriggers = function adjustEffectRelatedTriggers(st, triggers, partial) {	CODE
LOW	esm/utils/paths.js	1103	export function segmentToDistributedPoints(segment, totalPoints) {	CODE
LOW	esm/utils/paths.js	1373	function getClosestProgressOnBezier(iterations, px, py, start, end, slices, x0, y0, x1, y1, x2, y2, x3, y3) {	CODE
LOW	src/utils/paths.js	905	export function segmentToDistributedPoints(segment, totalPoints) {	CODE
LOW	src/utils/paths.js	1108	function getClosestProgressOnBezier(iterations, px, py, start, end, slices, x0, y0, x1, y1, x2, y2, x3, y3) {	CODE

Verbosity Indicators2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	esm/ScrollToPlugin.js	215	//note: iOS has a bug that throws off the scroll by several pixels, so we need to check if it's within 7 pixels of	COMMENT
LOW	src/ScrollToPlugin.js	139	//note: iOS has a bug that throws off the scroll by several pixels, so we need to check if it's within 7 pixels of th	COMMENT