A library for working with Bitcoin
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.
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.
Can maintainers explain intent, assumptions, and trade-offs? 32 finding(s).
Are imports declared and package/API names verified? 0 finding(s).
Are wrappers, guards, and repeated structures necessary? 0 finding(s).
Which changes need focused human review? 32 finding(s).
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.
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.
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.
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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …re/src/test/java/org/bitcoinj/core/ChainSplitTest.java | 101 | assertEquals(2, walletChanged.get()); | COMMENT |
| LOW | core/src/test/java/org/bitcoinj/wallet/WalletTest.java | 901 | public void doubleSpendWeCreate() throws Exception { | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/crypto/ECKey.java | 1081 | // - recId 0: x-coordinate of R was smaller than n, the y-coordinate of R was even | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/crypto/ECKey.java | 1101 | // | COMMENT |
| LOW | …/main/java/org/bitcoinj/core/TransactionBroadcast.java | 161 | // of the other half, e.g., with 4 peers connected we will send the tx to 2 randomly chosen peers, and then | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/core/PeerGroup.java | 241 | // the spending transaction will always match (due to the outpoint structure). | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/core/Peer.java | 121 | // message. This method can go wrong if the peer re-orgs onto a shorter (but harder) chain, however, this is rare. | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/core/Peer.java | 141 | // Keeps track of things we requested internally with getdata but didn't receive yet, so we can avoid re-requests. | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/core/Peer.java | 761 | } | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/core/Peer.java | 981 | try { | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/core/Peer.java | 1041 | // actually match our filter or which simply do not send us all the transactions we need: it can be fixed | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/core/Peer.java | 1061 | // Ask each wallet attached to the peer/blockchain if this block exhausts the list of data items | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/core/Peer.java | 1241 | if (blocks.size() > 0 && downloadData && blockChain != null) { | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/core/Peer.java | 1401 | @GuardedBy("lock") | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/core/Peer.java | 1421 | // That causes us to download the head block but then we find (in processBlock) that we can't connect | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/core/Block.java | 561 | } | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/core/Block.java | 581 | // derive the root, which can be checked against the block header. These proofs aren't used right now but | COMMENT |
| LOW | …src/main/java/org/bitcoinj/script/ScriptExecution.java | 221 | if (requireMinimal && chunk.length > 0) { | COMMENT |
| LOW | …src/main/java/org/bitcoinj/script/ScriptExecution.java | 781 | COMMENT | |
| LOW | …src/main/java/org/bitcoinj/script/ScriptExecution.java | 801 | private static void executeCheckSequenceVerify(Transaction txContainingThis, int index, LinkedList<byte[]> stack, Se | COMMENT |
| LOW | …src/main/java/org/bitcoinj/script/ScriptExecution.java | 841 | COMMENT | |
| LOW | …src/main/java/org/bitcoinj/script/ScriptExecution.java | 1121 | "Script resulted in a non-true stack: " + Utils.toString(stackCopy)); | COMMENT |
| LOW | …in/java/org/bitcoinj/wallet/DeterministicKeyChain.java | 161 | private int calcDefaultLookaheadThreshold() { | COMMENT |
| LOW | …in/java/org/bitcoinj/wallet/DeterministicKeyChain.java | 521 | issuedInternalKeys += numberOfKeys; | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/wallet/Wallet.java | 141 | import static org.bitcoinj.base.internal.Preconditions.checkState; | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/wallet/Wallet.java | 201 | // reason being that this simplifies handling of re-orgs. It would be worth fixing this in future. | COMMENT |
| LOW | core/src/main/java/org/bitcoinj/wallet/Wallet.java | 4821 | * cause the number of confirmations of a transaction to go higher, lower, drop to zero and can even result in | COMMENT |
| LOW | …est/java/org/bitcoinj/core/FullBlockTestGenerator.java | 241 | spendableOutputs.offer(b2.getCoinbaseOutput()); | COMMENT |
| LOW | …est/java/org/bitcoinj/core/FullBlockTestGenerator.java | 421 | NewBlock b20 = createNextBlock(b15.block, chainHeadHeight + 7, out7, null); | COMMENT |
| LOW | examples/src/main/java/org/bitcoinj/examples/Kit.java | 41 | // While developing your application you probably want to use the Regtest mode and run your local bitcoin networ | COMMENT |
| LOW | …s/src/main/java/org/bitcoinj/examples/SendRequest.java | 41 | // How much coins do we want to send? | COMMENT |
| LOW | base/src/main/java/org/bitcoinj/base/SegwitAddress.java | 161 | throw new AddressFormatException.InvalidDataLength( | COMMENT |