Home / wasm-bindgen / wasm-pack
AI Slop Code Risk Monitor

wasm-bindgen/wasm-pack

SlopCodeMonitor badge for wasm-bindgen/wasm-pack Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).
1.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for wasm-bindgen/wasm-pack. SynthScan examined 15,022 lines of code across 133 source files, recording 16 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 1.2 (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.2
Adjusted Signal
1.2
Raw Pattern Score
100%
Time Factor
—
Last Push
—
Stars
—
Language
15.0K
Lines of Code
133
Files
16
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 5.7/100 · LOW

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

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

PR Review Velocity Impact 5.2/100 · LOW

Which changes need focused human review? 16 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

Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.

No multi-scan history yet — run the scanner again to build trend data.

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 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 16 distinct pattern matches across 2 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.

Over-Commented Block13 hits · 13 pts
SeverityFileLineSnippetContext
LOWdocs/_installer/init.sh1#!/bin/shCOMMENT
LOWwasm-pack-template/src/utils.rs1pub fn set_panic_hook() {COMMENT
LOWsrc/emoji.rs1//! Emoji constants used by `wasm-pack`.COMMENT
LOWsrc/installer.rs1//! Self-installation of `wasm-pack`COMMENT
LOWsrc/test/webdriver/geckodriver.rs61 }COMMENT
LOWsrc/command/test.rs21/// Everything required to configure the `wasm-pack test` command.COMMENT
LOWsrc/command/test.rs41 /// If the `chromedriver` WebDriver client is not on the `$PATH`, and notCOMMENT
LOWsrc/command/test.rs61 pub safaridriver: Option<PathBuf>,COMMENT
LOWsrc/command/build.rs121#[command(allow_hyphen_values = true, trailing_var_arg = true)]COMMENT
LOWsrc/command/build.rs181 #[clap(long = "out-name")]COMMENT
LOWsrc/command/mod.rs61 Publish {COMMENT
LOWsrc/command/mod.rs81 path: Option<PathBuf>,COMMENT
LOWsrc/command/mod.rs101 #[clap(long = "auth-type", short = 't')]COMMENT
Structural Annotation Overuse3 hits · 4 pts
SeverityFileLineSnippetContext
LOW…s/npm-browser-packages/getting-started/manual-setup.md8### Step 1: Create a New Rust Library ProjectCOMMENT
LOW…s/npm-browser-packages/getting-started/manual-setup.md19### Step 2: Edit your `Cargo.toml` FileCOMMENT
LOW…s/npm-browser-packages/getting-started/manual-setup.md57### Step 3: Write some Rust!COMMENT