AI Slop Code Risk Monitor

bitcoinj/bitcoinj

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

A library for working with Bitcoin

0.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for bitcoinj/bitcoinj, a Java project with 5,236 GitHub stars. SynthScan examined 101,804 lines of code across 484 source files, recording 32 pattern matches distributed across 1 syntactic category. The legacy adjusted pattern signal is 0.3 (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.3
Adjusted Signal
0.3
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
5.2K
Stars
Java
Language
101.8K
Lines of Code
484
Files
32
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 1.6/100 · LOW

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

Which changes need focused human review? 32 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 0LOW 32

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 32 distinct pattern matches across 1 syntactic category. 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 Block32 hits · 32 pts
SeverityFileLineSnippetContext
LOW…re/src/test/java/org/bitcoinj/core/ChainSplitTest.java101 assertEquals(2, walletChanged.get());COMMENT
LOWcore/src/test/java/org/bitcoinj/wallet/WalletTest.java901 public void doubleSpendWeCreate() throws Exception {COMMENT
LOWcore/src/main/java/org/bitcoinj/crypto/ECKey.java1081 // - recId 0: x-coordinate of R was smaller than n, the y-coordinate of R was evenCOMMENT
LOWcore/src/main/java/org/bitcoinj/crypto/ECKey.java1101 //COMMENT
LOW…/main/java/org/bitcoinj/core/TransactionBroadcast.java161 // of the other half, e.g., with 4 peers connected we will send the tx to 2 randomly chosen peers, and thenCOMMENT
LOWcore/src/main/java/org/bitcoinj/core/PeerGroup.java241 // the spending transaction will always match (due to the outpoint structure).COMMENT
LOWcore/src/main/java/org/bitcoinj/core/Peer.java121 // message. This method can go wrong if the peer re-orgs onto a shorter (but harder) chain, however, this is rare.COMMENT
LOWcore/src/main/java/org/bitcoinj/core/Peer.java141 // Keeps track of things we requested internally with getdata but didn't receive yet, so we can avoid re-requests.COMMENT
LOWcore/src/main/java/org/bitcoinj/core/Peer.java761 }COMMENT
LOWcore/src/main/java/org/bitcoinj/core/Peer.java981 try {COMMENT
LOWcore/src/main/java/org/bitcoinj/core/Peer.java1041 // actually match our filter or which simply do not send us all the transactions we need: it can be fixedCOMMENT
LOWcore/src/main/java/org/bitcoinj/core/Peer.java1061 // Ask each wallet attached to the peer/blockchain if this block exhausts the list of data itemsCOMMENT
LOWcore/src/main/java/org/bitcoinj/core/Peer.java1241 if (blocks.size() > 0 && downloadData && blockChain != null) {COMMENT
LOWcore/src/main/java/org/bitcoinj/core/Peer.java1401 @GuardedBy("lock")COMMENT
LOWcore/src/main/java/org/bitcoinj/core/Peer.java1421 // That causes us to download the head block but then we find (in processBlock) that we can't connectCOMMENT
LOWcore/src/main/java/org/bitcoinj/core/Block.java561 }COMMENT
LOWcore/src/main/java/org/bitcoinj/core/Block.java581 // derive the root, which can be checked against the block header. These proofs aren't used right now butCOMMENT
LOW…src/main/java/org/bitcoinj/script/ScriptExecution.java221 if (requireMinimal && chunk.length > 0) {COMMENT
LOW…src/main/java/org/bitcoinj/script/ScriptExecution.java781COMMENT
LOW…src/main/java/org/bitcoinj/script/ScriptExecution.java801 private static void executeCheckSequenceVerify(Transaction txContainingThis, int index, LinkedList<byte[]> stack, SeCOMMENT
LOW…src/main/java/org/bitcoinj/script/ScriptExecution.java841COMMENT
LOW…src/main/java/org/bitcoinj/script/ScriptExecution.java1121 "Script resulted in a non-true stack: " + Utils.toString(stackCopy));COMMENT
LOW…in/java/org/bitcoinj/wallet/DeterministicKeyChain.java161 private int calcDefaultLookaheadThreshold() {COMMENT
LOW…in/java/org/bitcoinj/wallet/DeterministicKeyChain.java521 issuedInternalKeys += numberOfKeys;COMMENT
LOWcore/src/main/java/org/bitcoinj/wallet/Wallet.java141import static org.bitcoinj.base.internal.Preconditions.checkState;COMMENT
LOWcore/src/main/java/org/bitcoinj/wallet/Wallet.java201 // reason being that this simplifies handling of re-orgs. It would be worth fixing this in future.COMMENT
LOWcore/src/main/java/org/bitcoinj/wallet/Wallet.java4821 * cause the number of confirmations of a transaction to go higher, lower, drop to zero and can even result inCOMMENT
LOW…est/java/org/bitcoinj/core/FullBlockTestGenerator.java241 spendableOutputs.offer(b2.getCoinbaseOutput());COMMENT
LOW…est/java/org/bitcoinj/core/FullBlockTestGenerator.java421 NewBlock b20 = createNextBlock(b15.block, chainHeadHeight + 7, out7, null);COMMENT
LOWexamples/src/main/java/org/bitcoinj/examples/Kit.java41 // While developing your application you probably want to use the Regtest mode and run your local bitcoin networCOMMENT
LOW…s/src/main/java/org/bitcoinj/examples/SendRequest.java41 // How much coins do we want to send?COMMENT
LOWbase/src/main/java/org/bitcoinj/base/SegwitAddress.java161 throw new AddressFormatException.InvalidDataLength(COMMENT