AI Slop Code Risk Monitor

reduxjs/reselect

Name: reduxjs/reselect — TypeScript 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).

Selector library for Redux

1.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for reduxjs/reselect, a TypeScript project with 19,002 GitHub stars. SynthScan examined 21,344 lines of code across 102 source files, recording 36 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 1.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.

1.7

Adjusted Signal

1.7

Raw Pattern Score

100%

Time Factor

2026-10-28

Last Push

19.0K

Stars

TypeScript

Language

21.3K

Lines of Code

102

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 7.9/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.5/100 · LOW

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

Agent Over-Engineering Ratio 4.1/100 · LOW

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

PR Review Velocity Impact 8.1/100 · LOW

Which changes need focused human review? 36 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 0LOW 36

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

Hyper-Verbose Identifiers18 hits · 18 pts

Severity	File	Line	Snippet	Context
LOW	typescript_test/test.ts	178	function testInvalidTypeInCombinator() {	CODE
LOW	typescript_test/test.ts	495	function testOptionalArgumentsConflicting() {	CODE
LOW	typescript_test/test.ts	626	function testCreateSelectorCreator() {	CODE
LOW	typescript_test/test.ts	662	function testCreateStructuredSelector() {	CODE
LOW	typescript_test/test.ts	749	function testTypedCreateStructuredSelector() {	CODE
LOW	typescript_test/test.ts	832	function testStructuredSelectorTypeParams() {	CODE
LOW	typescript_test/test.ts	1030	function customMemoizationOptionTypes() {	CODE
LOW	typescript_test/test.ts	1056	function createSelectorConfigOptions() {	CODE
LOW	typescript_test/test.ts	1228	function testInputSelectorWithUndefinedReturn() {	CODE
LOW	typescript_test/test.ts	1438	function handleNestedIncompatTypes() {	CODE
LOW	typescript_test/test.ts	1594	function testCreateStructuredSelectorNew() {	CODE
LOW	typescript_test/argsMemoize.typetest.ts	24	function overrideOnlyMemoizeInCreateSelector() {	CODE
LOW	typescript_test/argsMemoize.typetest.ts	90	function overrideOnlyArgsMemoizeInCreateSelector() {	CODE
LOW	typescript_test/argsMemoize.typetest.ts	185	function overrideMemoizeAndArgsMemoizeInCreateSelector() {	CODE
LOW	typescript_test/argsMemoize.typetest.ts	572	function memoizeAndArgsMemoizeInCreateSelectorCreator() {	CODE
LOW	typescript_test/argsMemoize.typetest.ts	966	function clearCacheExistsOnDefaultSelectorAndMemoizedResultFunc() {	CODE
LOW	src/utils.ts	104	export function collectInputSelectorResults(	CODE
LOW	src/lruMemoize.ts	143	return function areArgumentsShallowlyEqual(	CODE

Over-Commented Block14 hits · 14 pts

Severity	File	Line	Snippet	Context
LOW	pnpm-workspace.yaml	1	# pnpm settings file.	COMMENT
LOW	test/computationComparisons.spec.tsx	201	// })	COMMENT
LOW	test/benchmarks/weakMapMemoize.bench.ts	161	})	COMMENT
LOW	test/benchmarks/weakMapMemoize.bench.ts	181	// (todos, id) => todos.map(todo => todo.id === id),	COMMENT
LOW	test/benchmarks/weakMapMemoize.bench.ts	201	// (state: RootState, id: number) => id,	COMMENT
LOW	test/benchmarks/weakMapMemoize.bench.ts	221	// nonMemoizedSelector	COMMENT
LOW	test/benchmarks/weakMapMemoize.bench.ts	241	// selectorDefaultWithCacheSize,	COMMENT
LOW	test/benchmarks/weakMapMemoize.bench.ts	261	// bench(	COMMENT
LOW	test/benchmarks/weakMapMemoize.bench.ts	281	// )	COMMENT
LOW	typescript_test/test.ts	561	selector5({} as State, 'blach', 4)	COMMENT
LOW	typescript_test/test.ts	941	// ################ Tests ################	COMMENT
LOW	docs/examples/createSelector/annotateResultFunction.ts	21	// Type of `state` is set to `RootState`, no need to manually set the type	COMMENT
LOW	src/createSelectorCreator.ts	401	ExtractMemoizerFields<OverrideMemoizeFunction>	COMMENT
LOW	src/createSelectorCreator.ts	421	const inputSelectorResults = new Array(length)	COMMENT

TODO Padding2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	test/lruMemoize.test.ts	1	// TODO: Add test for React Redux connect function	COMMENT
LOW	test/reselect.spec.ts	1	// TODO: Add test for React Redux connect function	COMMENT

Fake / Example Data2 hits · 2 pts

Severity	File	Line	Snippet	Context
LOW	test/testUtils.ts	192	name: 'John Doe',	CODE
LOW	test/testUtils.ts	195	street: '123 Main St',	CODE