Home / alda-lang / alda
AI Slop Code Risk Monitor

alda-lang/alda

SlopCodeMonitor badge for alda-lang/alda Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

A music programming language for musicians. :notes:

1.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for alda-lang/alda, a Go project with 5,959 GitHub stars. SynthScan examined 40,641 lines of code across 190 source files, recording 64 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 1.8 (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.8
Adjusted Signal
1.8
Raw Pattern Score
100%
Time Factor
2026-10-23
Last Push
6.0K
Stars
Go
Language
40.6K
Lines of Code
190
Files
64
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 8.4/100 · LOW

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

Which changes need focused human review? 64 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 3LOW 61

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 64 distinct pattern matches across 3 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 Block58 hits · 58 pts
SeverityFileLineSnippetContext
LOWclient/main.go1package mainCOMMENT
LOWclient/cmd/update.go201 //COMMENT
LOWclient/cmd/update.go261COMMENT
LOWclient/cmd/play.go141 // Everything in this command is done via parsed CLI options, neverCOMMENT
LOWclient/cmd/doctor.go421 //COMMENT
LOWclient/cmd/parse.go121 }COMMENT
LOWclient/cmd/root.go61// Unfortunately, Cobra doesn't give you an easy way to consistently do that.COMMENT
LOWclient/cmd/root.go161 // to override the default UsageFunc with a function that might return anCOMMENT
LOWclient/cmd/root.go181 // sure that we print the notice about telemetry first, before the help textCOMMENT
LOWclient/cmd/root.go301COMMENT
LOWclient/cmd/root.go321 // ones without also spawning some implicit ones here.COMMENT
LOWclient/cmd/root.go361 // application will begin with the string "unknown command" and do the specialCOMMENT
LOWclient/transmitter/osc.go261 // Append tempo messages to the score, based on the tempo changes in theCOMMENT
LOWclient/transmitter/osc.go281 // We keep track of the known (audible) length of the score as we iterateCOMMENT
LOWclient/transmitter/osc.go321 // back by that amount so that playback starts as if those events were atCOMMENT
LOWclient/transmitter/osc.go341 // Guard against negative offsets. These shouldn't occur in practiceCOMMENT
LOWclient/transmitter/transmitter.go21 // for that part will have the indicated offset subtracted from its offset.COMMENT
LOWclient/interop/musicxml/importer/handlers.go21//COMMENT
LOWclient/interop/musicxml/importer/importer_test.go381// t.Errorf("filepath walk error %s", err)COMMENT
LOWclient/interop/musicxml/importer/importer_test.go401// t.Error(err)COMMENT
LOWclient/color/color.go21// check for NO_COLOR ourselves and disable color manually if needed.COMMENT
LOWclient/color/color_windows.go21//COMMENT
LOWclient/wasm/main.go1//go:build js || wasmCOMMENT
LOWclient/repl/server.go581 server.input += strings.TrimSpace(input) + "\n"COMMENT
LOWclient/repl/server.go721 // reset, so we keep track of it here. After we reset the state, we invokeCOMMENT
LOWclient/repl/server.go741 // player, and this should generally happen quickly. `server.evalAndPlay` willCOMMENT
LOWclient/repl/player_management.go81// (`system.PlayerState{}`), which means all the struct fields have zero valuesCOMMENT
LOWclient/repl/player_management.go101}COMMENT
LOWclient/repl/client.go601COMMENT
LOWclient/repl/client.go621// NOTE: The nREPL design actually specifies that a server may send more thanCOMMENT
LOWclient/repl/client.go981// StartSession starts an nREPL session by sending a "clone" request and keepingCOMMENT
LOWclient/parser/ast.go221COMMENT
LOWclient/parser/parser.go721 sourceContext: p.sourceContext(token),COMMENT
LOWclient/system/sysprocattr_windows.go1//go:build windowsCOMMENT
LOWclient/system/process_management.go81 ); err != nil {COMMENT
LOWclient/system/process_management.go161COMMENT
LOWclient/system/process_management.go361 },COMMENT
LOWclient/system/process_management.go581COMMENT
LOWclient/json/interface.go1package jsonCOMMENT
LOWclient/json/declarative.go1package jsonCOMMENT
LOWclient/model/lisp.go21//COMMENT
LOWclient/model/lisp.go61func (LispSpecialFormQuote) GetSourceContext() AldaSourceContext {COMMENT
LOWclient/model/lisp.go181 // We could represent the signatures here, too, but at some point, we areCOMMENT
LOWclient/model/duration.go21COMMENT
LOWclient/model/cram.go81// UpdateScore implements ScoreUpdate.UpdateScore by doing the following forCOMMENT
LOWclient/model/source_context.go41// here and instead, unwrapping until we reach the bottom-most AldaSourceErrorCOMMENT
LOWclient/model/score.go21 // DurationMs returns a number of milliseconds representing how long an eventCOMMENT
LOWclient/model/score.go201 color.Aurora.BrightYellow(reference),COMMENT
LOWclient/model/part.go61 // `midiChannel` will be updated.COMMENT
LOWclient/model/part.go401 // bassoon "baz":COMMENT
LOWclient/model/part.go441 parts = append(parts, part)COMMENT
LOWclient/model/pitch.go121COMMENT
LOWplayer/src/main/kotlin/io/alda/player/MidiEngine.kt41const val MIDI_REVERB = 91COMMENT
LOWplayer/src/main/kotlin/io/alda/player/MidiEngine.kt61//COMMENT
LOWplayer/src/main/kotlin/io/alda/player/MidiEngine.kt121// minute (BPM), but in microseconds per quarter note (I'll abbreviate this asCOMMENT
LOWplayer/src/main/kotlin/io/alda/player/Parser.kt81 // player into the "active" state and prolonging the expiration of theCOMMENT
LOWplayer/src/main/kotlin/io/alda/player/Player.kt101 // that signals the lookup and scheduling of the pattern's events.COMMENT
LOWplayer/src/main/kotlin/io/alda/player/Events.kt1package io.alda.playerCOMMENT
AI Slop Vocabulary3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMclient/color/color.go26// more robust way, something like checking the terminfo/termcap capabilities ofCOMMENT
MEDIUMclient/color/color_windows.go25// more robust way, something like checking the terminfo/termcap capabilities ofCOMMENT
MEDIUMclient/model/lisp.go1407 // This will require a more nuanced API design for the Lisp functionCOMMENT
Structural Annotation Overuse3 hits · 4 pts
SeverityFileLineSnippetContext
LOWdoc/implementing-an-alda-library.md77### Step 1: Write an `alda` command wrapper functionCOMMENT
LOWdoc/implementing-an-alda-library.md125### Step 2: Come up with an APICOMMENT
LOWdoc/implementing-an-alda-library.md265### Step 3: Generate Alda codeCOMMENT