AI Slop Code Risk Monitor

browserbase/skills

Name: browserbase/skills — 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).

Browserbase's official collection of agent skills to access the web.

3.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for browserbase/skills, a JavaScript project with 3,748 GitHub stars. SynthScan examined 25,061 lines of code across 126 source files, recording 52 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 3.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.

3.7

Adjusted Signal

3.7

Raw Pattern Score

100%

Time Factor

2026-10-27

Last Push

3.7K

Stars

JavaScript

Language

25.1K

Lines of Code

126

Files

Pattern Hits

2026-10-31

Scan Date

0.02

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

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

Hallucinated Dependency & Supply Chain Risk 4.3/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 12.9/100 · LOW

Which changes need focused human review? 52 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 3MEDIUM 1LOW 48

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

Structural Annotation Overuse41 hits · 67 pts

Severity	File	Line	Snippet	Context
LOW	skills/company-research/SKILL.md	69	## Step 0: Setup Output Directory	COMMENT
LOW	skills/company-research/SKILL.md	85	## Step 1: Deep Company Research	COMMENT
LOW	skills/company-research/SKILL.md	124	## Step 2: Depth Mode Selection	COMMENT
LOW	skills/company-research/SKILL.md	132	## Step 3: Discovery	COMMENT
LOW	skills/company-research/SKILL.md	156	## Step 4: Deep Research & Scoring	COMMENT
LOW	skills/company-research/SKILL.md	179	## Step 5: Report & CSV	COMMENT
LOW	skills/ui-test/EXAMPLES.md	402	# Step 1: Sync cookies	COMMENT
LOW	skills/ui-test/EXAMPLES.md	406	# Step 2: Remote mode with the synced context	COMMENT
LOW	skills/ui-test/SKILL.md	224	# Step 1: Sync cookies from local Chrome to Browserbase	COMMENT
LOW	skills/ui-test/SKILL.md	228	# Step 2: Open in remote mode with the synced context	COMMENT
LOW⚡	skills/ui-test/references/browser-recipes.md	15	# Step 1: Load axe-core	COMMENT
LOW⚡	skills/ui-test/references/browser-recipes.md	18	# Step 2: Wait for script to load	COMMENT
LOW⚡	skills/ui-test/references/browser-recipes.md	21	# Step 3: Run audit	COMMENT
LOW	skills/ui-test/references/design-consistency.md	30	# Step 1: Capture baseline from existing pages	COMMENT
LOW	skills/ui-test/references/design-consistency.md	39	# Step 2: Now visit the changed page	COMMENT
LOW	skills/event-prospecting/SKILL.md	73	## Step 0: Setup Output Directory	COMMENT
LOW	skills/event-prospecting/SKILL.md	87	## Step 1: Load User Profile	COMMENT
LOW	skills/event-prospecting/SKILL.md	126	## Step 2: Recon	COMMENT
LOW	skills/event-prospecting/SKILL.md	142	## Step 3: Extract People	COMMENT
LOW	skills/event-prospecting/SKILL.md	160	## Step 4: Group by Company	COMMENT
LOW	skills/event-prospecting/SKILL.md	170	## Step 5: ICP Triage	COMMENT
LOW	skills/event-prospecting/SKILL.md	236	## Step 6: Filter by ICP Threshold	COMMENT
LOW	skills/event-prospecting/SKILL.md	254	## Step 7: Deep Research	COMMENT
LOW	skills/event-prospecting/SKILL.md	298	## Step 8: Enrich Speakers	COMMENT
LOW	skills/event-prospecting/SKILL.md	414	## Step 9: Compile Report	COMMENT
LOW⚡	skills/cookie-sync/REFERENCE.md	37	### Step 1: Connect to Local Chrome	COMMENT
LOW⚡	skills/cookie-sync/REFERENCE.md	44	### Step 2: Export Cookies	COMMENT
LOW⚡	skills/cookie-sync/REFERENCE.md	48	### Step 3: Create Context and Session	COMMENT
LOW⚡	skills/cookie-sync/REFERENCE.md	55	### Step 4: Inject Cookies	COMMENT
LOW	skills/cookie-sync/SKILL.md	97	# Step 1: Sync cookies for Twitter	COMMENT
LOW	skills/cookie-sync/SKILL.md	101	# Step 2: Browse authenticated Twitter	COMMENT
LOW	skills/search/EXAMPLES.md	47	# Step 1: Search	COMMENT
LOW	skills/search/EXAMPLES.md	53	# Step 2: Fetch the top result	COMMENT
LOW	skills/competitor-analysis/SKILL.md	69	## Step 0: Setup Output Directory	COMMENT
LOW	skills/competitor-analysis/SKILL.md	88	## Step 1: User Company Research	COMMENT
LOW	skills/competitor-analysis/SKILL.md	119	## Step 2: Depth Mode + Seed Input	COMMENT
LOW	skills/competitor-analysis/SKILL.md	137	## Step 3: Discovery (3 parallel waves)	COMMENT
LOW	skills/competitor-analysis/SKILL.md	169	## Step 4: Gate (category-fit filter)	COMMENT
LOW	skills/competitor-analysis/SKILL.md	221	## Step 5: Deep Enrichment	COMMENT
LOW	skills/competitor-analysis/SKILL.md	372	## Step 6: Screenshots	COMMENT
LOW	skills/competitor-analysis/SKILL.md	383	## Step 7: HTML Report	COMMENT

Magic Placeholder Names3 hits · 15 pts

Severity	File	Line	Snippet	Context
HIGH	skills/search/SKILL.md	18	export BROWSERBASE_API_KEY="your_api_key"	CODE
HIGH	skills/fetch/SKILL.md	18	export BROWSERBASE_API_KEY="your_api_key"	CODE
HIGH	skills/functions/SKILL.md	18	export BROWSERBASE_API_KEY="your_api_key"	CODE

Fake / Example Data7 hits · 7 pts

Severity	File	Line	Snippet	Context
LOW	skills/ui-test/EXAMPLES.md	88	browse fill "input[name=email]" "user@example.com"	CODE
LOW	skills/ui-test/EXAMPLES.md	486	browse fill "input[name=email]" "test@test.com"	CODE
LOW	skills/search/REFERENCE.md	104	"author": "Jane Doe",	CODE
LOW	skills/browser/EXAMPLES.md	36	browse type "John Doe"	CODE
LOW	skills/browser/EXAMPLES.md	117	browse type "user@example.com"	CODE
LOW	skills/browser/REFERENCE.md	182	browse fill "input[name=email]" "user@example.com"	CODE
LOW	skills/browser-trace/EXAMPLES.md	19	browse fill 'input[name=email]' 'user@example.com'	CODE

Modern AI Meta-Vocabulary1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	…lls/browser-use-to-stagehand/references/determinism.md	10	## The spectrum (most → least agentic)	COMMENT