AI Slop Code Risk Monitor

scalaz/scalaz

SlopCodeMonitor badge for scalaz/scalaz Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).
0.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for scalaz/scalaz. SynthScan examined 66,907 lines of code across 576 source files, recording 48 pattern matches distributed across 3 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
—
Last Push
—
Stars
—
Language
66.9K
Lines of Code
576
Files
48
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.6/100 · LOW

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

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

PR Review Velocity Impact 3.7/100 · LOW

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

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

Hyper-Verbose Identifiers29 hits · 29 pts
SeverityFileLineSnippetContext
LOWcore/src/main/scala/scalaz/Either.scala213 def getOrElse[BB >: B](x: => BB): BB =CODE
LOWcore/src/main/scala/scalaz/LazyEitherT.scala22 def getOrElse(default: => B)(implicit F: Functor[F]): F[B] =CODE
LOWcore/src/main/scala/scalaz/LazyEitherT.scala139 def getOrElse(default: => A)(implicit F: Functor[F]): F[A] =CODE
LOWcore/src/main/scala/scalaz/Id.scala65 override def getOrElse[A](a: Id[A])(d: => A): A = aCODE
LOWcore/src/main/scala/scalaz/LazyOptionT.scala18 def getOrElse(default: => A)(implicit F: Functor[F]): F[A] =CODE
LOWcore/src/main/scala/scalaz/EitherT.scala148 def getOrElse(default: => B)(implicit F: Functor[F]): F[B] =CODE
LOWcore/src/main/scala/scalaz/TheseT.scala48 def getOrElse(default: => B)(implicit F: Functor[F]): F[B]CODE
LOWcore/src/main/scala/scalaz/OptionT.scala73 def getOrElse(default: => A)(implicit F: Functor[F]): F[A] = mapO(_.getOrElse(default))CODE
LOWcore/src/main/scala/scalaz/OptionT.scala78 def getOrElseF(default: => F[A])(implicit F: Monad[F]): F[A] =CODE
LOWcore/src/main/scala/scalaz/These.scala208 def getOrElse[BB >: B](bb: => BB): BB =CODE
LOWcore/src/main/scala/scalaz/Validation.scala210 def getOrElse[AA >: A](x: => AA): AA =CODE
LOWcore/src/main/scala/scalaz/Maybe.scala32 final def getOrElse(a: => A): A =CODE
LOWcore/src/main/scala/scalaz/Maybe.scala88 final def getOrElseF[F[_]: Applicative](fa: => F[A]): F[A] =CODE
LOWcore/src/main/scala/scalaz/PLens.scala53 def getOrZ(a: A1)(implicit M: Monoid[B1]): B1 =CODE
LOWcore/src/main/scala/scalaz/PLens.scala65 def setOrZ(a: A1, b: B2)(implicit M: Monoid[A2]): A2 =CODE
LOWcore/src/main/scala/scalaz/LazyOption.scala25 def getOrElse[AA >: A](default: => AA): AA =CODE
LOWcore/src/main/scala/scalaz/MaybeT.scala63 def getOrElse(default: => A)(implicit F: Functor[F]): F[A] = mapO(_.getOrElse(default))CODE
LOWcore/src/main/scala/scalaz/MaybeT.scala69 def getOrElseF(default: => F[A])(implicit F: Monad[F]): F[A] =CODE
LOWcore/src/main/scala/scalaz/LazyEither.scala37 def getOrElse[BB >: B](default: => BB): BB =CODE
LOWcore/src/main/scala/scalaz/LazyEither.scala127 def getOrElse[AA >: A](default: => AA): AA =CODE
LOWcore/src/main/scala/scalaz/Optional.scala22 def getOrElse[A](fa: F[A])(default: => A): A = pextract(fa) | defaultCODE
LOWcore/src/main/scala/scalaz/std/SortedMap.scala193 final def getOrAdd[F[_], K, A](m: SortedMap[K, A], k: K)(fa: => F[A])(implicit F: Applicative[F]): F[(SortedMap[K, A],CODE
LOWcore/src/main/scala/scalaz/std/Option.scala92 override def getOrElse[A](o: Option[A])(d: => A) = o getOrElse dCODE
LOWcore/src/main/scala/scalaz/std/Option.scala286 final def getOrElseF[A, F[_] : Applicative](oa: Option[A])(fa: => F[A]): F[A] = oa match {CODE
LOWcore/src/main/scala/scalaz/std/Map.scala190 final def getOrAdd[F[_], K, A](m: Map[K, A], k: K)(fa: => F[A])(implicit F: Applicative[F]): F[(Map[K, A], A)] =CODE
LOWcore/src/main/scala/scalaz/syntax/OptionalSyntax.scala14 def getOrElse(default: => A): A = F.getOrElse(self)(default)CODE
LOWcore/src/main/scala/scalaz/syntax/std/MapOps.scala14 final def getOrAdd[F[_]](k: K)(fa: => F[A])(implicit F: Applicative[F]): F[(Map[K, A], A)] = dict.getOrAdd[F, K, A](seCODE
LOWcore/src/main/scala/scalaz/syntax/std/OptionOps.scala56 final def getOrElseF[F[_]: Applicative](fa: => F[A]): F[A] = o.getOrElseF[A, F](self)(fa)CODE
LOW…re/src/main/scala/scalaz/syntax/std/SortedMapOps.scala30 def getOrAdd[F[_]](k: K)(fa: => F[A])(implicit F: Applicative[F]): F[(SortedMap[K, A], A)] =CODE
Over-Commented Block18 hits · 18 pts
SeverityFileLineSnippetContext
LOW…ample/src/main/scala/scalaz/example/KleisliUsage.scala41COMMENT
LOW…/scala/scalaz/example/ContravariantCoyonedaUsage.scala81COMMENT
LOW…/scala/scalaz/example/ContravariantCoyonedaUsage.scala101 xs.sorted(using Order.orderBy(f).toScalaOrdering)COMMENT
LOW…/scala/scalaz/example/ContravariantCoyonedaUsage.scala161 // We can no longer use `schwartzian', though, because there is noCOMMENT
LOW…/scala/scalaz/example/ContravariantCoyonedaUsage.scala181 // *existential*, and the main feature of theCOMMENT
LOW…/scala/scalaz/example/ContravariantCoyonedaUsage.scala221 // type member is usually inferred as well as normal Scala types,COMMENT
LOW…/scala/scalaz/example/ContravariantCoyonedaUsage.scala261COMMENT
LOW…/scala/scalaz/example/ContravariantCoyonedaUsage.scala281 // `[A, B](Order[A], Order[B]): Order[(A, B)]'.COMMENT
LOW…/scala/scalaz/example/ContravariantCoyonedaUsage.scala341 // Induction stepsCOMMENT
LOW…/scala/scalaz/example/ContravariantCoyonedaUsage.scala401 // (((Unit, String),COMMENT
LOW…/scala/scalaz/example/ContravariantCoyonedaUsage.scala421 //COMMENT
LOW…/scala/scalaz/example/ContravariantCoyonedaUsage.scala441 // `I', and that’s all you get. Nothing that actually knows how toCOMMENT
LOW…/scala/scalaz/example/ContravariantCoyonedaUsage.scala481 |+| b.describe |+| ">")COMMENT
LOW…/scala/scalaz/example/ContravariantCoyonedaUsage.scala541 // willynilly for `Binfmt'. I have to prove at each step that *theCOMMENT
LOW…ample/src/main/scala/scalaz/example/FunctorUsage.scala41 assert(Functor[List].map(List("qwer", "adsfg"))(len) === List(4,5))COMMENT
LOW…ple/src/main/scala/scalaz/example/Foldable1Usage.scala41 // create our above tree can create a right leaning, or a leftCOMMENT
LOW…mple/src/main/scala/scalaz/example/TraverseUsage.scala21COMMENT
LOWtests/src/test/scala/scalaz/OptionalTest.scala41// """LazyEither instance tests""" in {COMMENT
Slop Phrases1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUMcore/src/main/scala/scalaz/ISet.scala443 -- It's worth noting that the size of the result may be smaller if,CODE