AI Slop Code Risk Monitor

yarnpkg/yarn

Name: yarnpkg/yarn — 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).

The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry

0.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for yarnpkg/yarn, a JavaScript project with 41,466 GitHub stars. SynthScan examined 53,032 lines of code across 428 source files, recording 30 pattern matches distributed across 5 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-05-12

Last Push

41.5K

Stars

JavaScript

Language

53.0K

Lines of Code

428

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

Can maintainers explain intent, assumptions, and trade-offs? 30 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 1.6/100 · LOW

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

PR Review Velocity Impact 3.1/100 · LOW

Which changes need focused human review? 30 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 2LOW 28

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 30 distinct pattern matches across 5 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 Identifiers17 hits · 17 pts

Severity	File	Line	Snippet	Context
LOW	__tests__/index.js	86	function expectHelpOutputAsSubcommand(stdout) {	CODE
LOW	__tests__/index.js	101	function expectAnInfoMessageAfterError(command: Promise<Array<?string>>, expectedInfo: string): Promise<void> {	CODE
LOW	…ckages/pkg-tests/pkg-tests-core/sources/utils/tests.js	136	exports.getPackageHttpArchivePath = async function getPackageHttpArchivePath(	CODE
LOW	src/constants.js	47	function getPreferredCacheDirectories(): Array<string> {	CODE
LOW	src/util/package-name-utils.js	3	export function getPlatformSpecificPackageFilename(pkg: {name: string, version: string}): string {	CODE
LOW	src/util/generate-pnp-map.js	78	function generateFindPackageLocator(packageInformationStores: PackageInformationStores): string {	CODE
LOW	src/util/generate-pnp-map.js	129	async function getPackageInformationStores(	CODE
LOW	src/util/get-transitive-dev-dependencies.js	6	function dependenciesObjectToPatterns(dependencies: ?Object): Array<string> {	CODE
LOW	src/util/get-transitive-dev-dependencies.js	14	function getTransitiveDependencies(lockfile: Lockfile, roots: Array<string>): Set<string> {	CODE
LOW	src/util/get-transitive-dev-dependencies.js	64	export function getTransitiveDevDependencies(	CODE
LOW	src/util/generate-pnp-map-api.tpl.js	113	function getPackageInformationSafe(packageLocator) {	CODE
LOW	src/util/generate-pnp-map-api.tpl.js	130	function applyNodeExtensionResolution(unqualifiedPath, {extensions}) {	CODE
LOW	src/util/portable-script.js	15	async function makePortableProxyScriptUnix(	CODE
LOW	src/util/child.js	48	export function forwardSignalToSpawnedProcesses(signal: string) {	CODE
LOW	src/util/filter.js	154	export function filterOverridenGitignores(files: WalkFiles): WalkFiles {	CODE
LOW	src/cli/commands/upgrade.js	22	function setUserRequestedPackageVersions(	CODE
LOW	src/resolvers/index.js	55	export function hostedGitFragmentToGitUrl(fragment: string, reporter: Reporter): string {	CODE

Over-Commented Block8 hits · 8 pts

Severity	File	Line	Snippet	Context
LOW	__tests__/commands/install/integration-hoisting.js	21	// /hello	COMMENT
LOW	__tests__/commands/install/integration-deduping.js	21	// A@2.0.1 -> B@2.0.0	COMMENT
LOW	__tests__/commands/install/integration-deduping.js	141	// D@2	COMMENT
LOW	packages/pkg-tests/pkg-tests-specs/sources/dragon.js	21	[`dragon-test-1-e`]: `1.0.0`,	COMMENT
LOW	packages/pkg-tests/pkg-tests-specs/sources/dragon.js	41	// (so we merge their hoistedFrom fields), then B cannot be hoisted	COMMENT
LOW	packages/pkg-tests/pkg-tests-specs/sources/dragon.js	81	// Because the workspace B is also a dependency of the workspace A, it will be	COMMENT
LOW	src/util/generate-pnp-map-api.tpl.js	141	if (stat && !stat.isDirectory()) {	COMMENT
LOW	src/cli/commands/audit.js	321	this.auditData.actions.forEach(action => {	COMMENT

Slop Phrases2 hits · 4 pts

Severity	File	Line	Snippet	Context
MEDIUM	scripts/clean-mirror.sh	5	# If you only have a single project in your mirror, you can use the purge configuration to automatically remove packages	COMMENT
LOW	src/cli/index.js	363	// Don't forget to kill the sockets if we're being killed via signals	COMMENT

Self-Referential Comments1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	end_to_end_tests/data/run-yarn-test.sh	20	# Create the cache directory and remove it	COMMENT

Redundant / Tautological Comments2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	end_to_end_tests/data/run-ubuntu.sh	16	# Check if this is an old Ubuntu version that needs the NodeSource repo	COMMENT
LOW	scripts/update-npm.sh	15	# Check if this version is already published to npm.	COMMENT