Public report of lysine-dev/okio, published 13 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 13 November 2026, 18:44 UTC · Survey ID cd_6c696e6f92e94f24bef7dbf13e2e2d4d

lysine-dev/okio

Measured 13 November 2026, 18:44 UTC, at code version f0e3f47

Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.

Knowledge freshness is not measured: Freshness signal contradicted by repo activity.

CAI score 59out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 2 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 26,793 lines of product code in 9 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 47

Findings by how serious they are

29 critical 152 serious 26 minor

11 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
13 November 2026, 18:44 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

44of 44 dimensions measured by tools.
194of 207 findings point to an exact file and line, so you can open each one in the code. The other 13 concern the repository as a whole, such as missing documentation.
44dimensions across 6 lenses, read from 26,793 lines of product code in 9 projects.
Chapters

Executive summary

lysine-dev/okio falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 59 out of 100 and is rated Adequate, and 23 of its 29 critical findings are security problems.

Production Readiness, at 47, is the weakest lens and counts most in the score. The best first step is replacing the two packages under a banned licence, worth about 7 points. Adding automated security scanning would lift Production Readiness itself, also worth about 7. Raising Production Readiness to 70 would lift the score to about 66.

Twenty-one known security holes in the packages the code depends on can be used by attackers. One pipeline step installs packages that can change without warning, and two packages carry licence risk. Updating the vulnerable packages, pinning what the pipeline installs and replacing or clearing the banned-licence packages would close these risks. Reading outside data into plain values would fix the place where outside data is turned straight into objects. The two tests the project itself marks as unreliable need fixing or deleting.

The product code is 26,793 lines, about €52,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 47 · counts for 46%Maturity 55 · counts for 25%Security and Compliance 78 · counts for 14%Code Health 84 · counts for 8%Architecture 89 · counts for 4%Performance 91 · counts for 2%

If Production Readiness rose from 47 to 70, the lowest score rated Strong, the score would rise from 59 to about 66.

Code composition: what the lines of code are
Product code 54%Tests 46%
New since the last survey: 76 findings

These 76 critical or serious findings weren't in the previous survey, on 24 October 2026.

  • Code Duplication · Near-duplicate member family (4 members, 7 shared lines) okio/src/hashFunctions/kotlin/okio/internal/Md5.kt
  • Code Duplication · Near-duplicate member pair (23 shared lines) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Edited copy of a member (40 corresponding lines) okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt
  • Code Duplication · Edited copy of a member (36 corresponding lines) okio/src/commonMain/kotlin/okio/Utf8.kt
  • Code Duplication · Edited copy of a member (35 corresponding lines) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Edited copy of a member (40 corresponding lines) okio/src/jvmMain/kotlin/okio/Timeout.kt
  • Code Duplication · Edited copy of a member (26 corresponding lines) okio/src/jvmMain/kotlin/okio/HashingSource.kt
  • Code Duplication · Edited copy of a member (36 corresponding lines) okio/src/mingwX64Main/kotlin/okio/WindowsPosixVariant.kt
  • Code Duplication · Edited copy of a member (24 corresponding lines) okio/src/jvmMain/kotlin/okio/JvmOkio.kt
  • Code Duplication · Edited copy of a member (22 corresponding lines) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Edited copy of a member (26 corresponding lines) okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/FileSource.kt
  • Code Duplication · Edited copies of one member (4 members, 20+ corresponding lines) okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/FileSink.kt
  • Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt
  • Code Duplication · Edited copy of a member (20 corresponding lines) okio/src/jvmMain/kotlin/okio/Buffer.kt
  • Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) okio/src/commonMain/kotlin/okio/FileHandle.kt
  • Code Duplication · Edited copy of a member (12 corresponding lines) okio/src/jvmMain/kotlin/okio/Buffer.kt
  • Code Duplication · Edited copy of a member (18 corresponding lines) okio/src/mingwX64Main/kotlin/okio/WindowsFileHandle.kt
  • Code Duplication · Edited copy of a member (16 corresponding lines) okio/src/jvmMain/kotlin/okio/HashingSink.kt
  • Code Duplication · Edited copy of a member (15 corresponding lines) okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt
  • Code Duplication · Edited copy of a member (15 corresponding lines) okio/src/jvmMain/kotlin/okio/internal/ResourceFileSystem.kt
  • Code Duplication · Edited copy of a member (12 corresponding lines) okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt
  • Code Duplication · Edited copy of a member (14 corresponding lines) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Edited copy of a member (15 corresponding lines) okio/src/jvmMain/kotlin/okio/JvmSystemFileSystem.kt
  • Code Duplication · Edited copies of one member (4 members, 23+ corresponding lines) okio/src/commonMain/kotlin/okio/internal/RealBufferedSink.kt
  • Code Duplication · Edited copy of a member (23 corresponding lines) okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt
  • Code Duplication · Edited copy of a member (15 corresponding lines) okio-fakefilesystem/src/commonMain/kotlin/okio/fakefilesystem/FakeFileSystem.kt
  • Code Duplication · Edited copy of a member (10 corresponding lines) okio/src/commonMain/kotlin/okio/internal/SegmentedByteString.kt
  • Code Duplication · Edited copy of a member (11 corresponding lines) okio/src/unixMain/kotlin/okio/UnixPosixVariant.kt
  • Code Duplication · Edited copy of a member (13 corresponding lines) okio/src/jvmMain/kotlin/okio/JvmFileHandle.kt
  • Code Duplication · Edited copy of a member (11 corresponding lines) okio/src/unixMain/kotlin/okio/UnixFileHandle.kt
  • Code Duplication · Edited copy of a member (8 corresponding lines) okio/src/commonMain/kotlin/okio/internal/ByteString.kt
  • Code Duplication · Edited copy of a member (9 corresponding lines) okio/src/jvmMain/kotlin/okio/SegmentedByteString.kt
  • Code Duplication · Edited copy of a member (9 corresponding lines) okio/src/jvmMain/kotlin/okio/JvmFileHandle.kt
  • Code Duplication · Edited copy of a member (10 corresponding lines) okio/src/mingwX64Main/kotlin/okio/WindowsFileHandle.kt
  • Code Duplication · Edited copy of a member (9 corresponding lines) okio/src/mingwX64Main/kotlin/okio/WindowsPosixVariant.kt
  • Code Duplication · Edited copy of a member (9 corresponding lines) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Edited copy of a member (7 corresponding lines) okio/src/commonMain/kotlin/okio/internal/ByteString.kt
  • Code Duplication · Duplicated block (37 lines × 4) okio/src/hashFunctions/kotlin/okio/internal/Md5.kt
  • Code Duplication · Duplicated block (24–27 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt
  • Code Duplication · Duplicated block (24 lines × 2) okio/src/commonMain/kotlin/okio/internal/ByteString.kt
  • Code Duplication · Duplicated block (18–23 lines × 2) okio/src/commonMain/kotlin/okio/Utf8.kt
  • Code Duplication · Duplicated block (20 lines × 2) okio/src/jvmMain/kotlin/okio/DeflaterSink.kt
  • Code Duplication · Duplicated block (19 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt
  • Code Duplication · Duplicated block (15 lines × 3) okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt
  • Code Duplication · Duplicated block (15 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Duplicated block (14 lines × 2) okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt
  • Code Duplication · Duplicated block (14 lines × 2) okio/src/jvmMain/kotlin/okio/HashingSource.kt
  • Code Duplication · Duplicated block (8–12 lines × 2) okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/FileSource.kt
  • Code Duplication · Duplicated block (11 lines × 3) okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt
  • Code Duplication · Duplicated block (11 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Duplicated block (11 lines × 2) okio/src/jvmMain/kotlin/okio/JvmOkio.kt
  • Code Duplication · Duplicated block (7–10 lines × 10) okio/src/hashFunctions/kotlin/okio/internal/Md5.kt
  • Code Duplication · Duplicated block (9 lines × 2) okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/WasiFileHandle.kt
  • Code Duplication · Duplicated block (9 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Duplicated block (9 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Md5.kt
  • Code Duplication · Duplicated block (8 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Duplicated block (8 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt
  • Code Duplication · Duplicated block (6 lines × 3) okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt
  • Code Duplication · Duplicated block (6 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Duplicated block (7 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Duplicated block (8 lines × 2) okio/src/jvmMain/kotlin/okio/Buffer.kt
  • Code Duplication · Duplicated block (4–5 lines × 6) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Duplicated block (6 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Duplicated block (68 lines × 2) okio/src/appleMain/kotlin/okio/SegmentedByteString.kt
  • Code Duplication · Duplicated block (68 lines × 3) okio/src/jsMain/kotlin/okio/FileSystem.kt
  • Code Duplication · Duplicated block (31 lines × 2) okio/src/jvmMain/kotlin/okio/Path.kt
  • Code Duplication · Edited copy of a member (23 corresponding lines) REDACTED
  • Code Duplication · Edited copy of a member (13 corresponding lines) samples/src/jvmMain/java/okio/samples/WriteFile.java
  • Code Duplication · Edited copy of a member (15 corresponding lines) samples/src/jvmMain/java/okio/samples/ReadFileLineByLine.java
  • Code Duplication · Edited copy of a member (10 corresponding lines) samples/src/jvmMain/kotlin/okio/samples/WriteFile.kt
  • Code Duplication · Edited copy of a member (12 corresponding lines) samples/src/jvmMain/java/okio/samples/ReadFileLineByLine.kt
  • Code Duplication · Duplicated block (5 lines × 2) samples/src/jvmMain/kotlin/okio/samples/Hashing.kt
  • License Compliance · Banned license: org.openjdk.jmh:jmh-core
  • License Compliance · Banned license: org.openjdk.jmh:jmh-generator-annprocess
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 33 findings

These 33 critical or serious findings were in the previous survey, on 24 October 2026, and are gone from this one.

  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) okio/src/hashFunctions/kotlin/okio/internal/Md5.kt
  • Code Duplication · Duplicated block (37 lines × 4) okio/src/hashFunctions/kotlin/okio/internal/Md5.kt
  • Code Duplication · Duplicated block (24–27 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt
  • Code Duplication · Duplicated block (24 lines × 2) okio/src/commonMain/kotlin/okio/internal/ByteString.kt
  • Code Duplication · Duplicated block (22–23 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt
  • Code Duplication · Duplicated block (18–21 lines × 2) okio/src/commonMain/kotlin/okio/Utf8.kt
  • Code Duplication · Duplicated block (20 lines × 2) okio/src/jvmMain/kotlin/okio/DeflaterSink.kt
  • Code Duplication · Duplicated block (19 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt
  • Code Duplication · Duplicated block (15 lines × 3) okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt
  • Code Duplication · Duplicated block (14 lines × 2) okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt
  • Code Duplication · Duplicated block (14 lines × 2) okio/src/jvmMain/kotlin/okio/HashingSource.kt
  • Code Duplication · Duplicated block (8–12 lines × 2) okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/FileSource.kt
  • Code Duplication · Duplicated block (12 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Duplicated block (11 lines × 3) okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt
  • Code Duplication · Duplicated block (11 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Duplicated block (11 lines × 2) okio/src/jvmMain/kotlin/okio/JvmOkio.kt
  • Code Duplication · Duplicated block (10 lines × 4) okio/src/hashFunctions/kotlin/okio/internal/Md5.kt
  • Code Duplication · Duplicated block (8 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Md5.kt
  • Code Duplication · Duplicated block (7 lines × 3) okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt
  • Code Duplication · Duplicated block (7 lines × 3) okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt
  • Code Duplication · Duplicated block (7 lines × 3) okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt
  • Code Duplication · Duplicated block (7 lines × 3) okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt
  • Code Duplication · Duplicated block (7 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt
  • Code Duplication · Duplicated block (7 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt
  • Code Duplication · Duplicated block (7 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt
  • Code Duplication · Duplicated block (6 lines × 3) okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt
  • Code Duplication · Duplicated block (6 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Duplicated block (5 lines × 3) okio/src/commonMain/kotlin/okio/internal/Buffer.kt
  • Code Duplication · Duplicated block (68 lines × 2) okio/src/appleMain/kotlin/okio/SegmentedByteString.kt
  • Code Duplication · Duplicated block (68 lines × 3) okio/src/jsMain/kotlin/okio/FileSystem.kt
  • Code Duplication · Duplicated block (31 lines × 2) okio/src/jvmMain/kotlin/okio/Path.kt
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Rebuild cost: about €52,000 · Estimate
Cost to rebuild€17,000 to €86,000, for 287 to 910 hours of work, about 0.4 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 26,793 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 2 Banned license finding(s) in License Compliance.
Raises the score by about 7 points · Low effort · License Compliance
2
Record your significant design decisions.
Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Raises the score by about 7 points · Medium effort · Architecture documentation
3
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Raises the score by about 7 points · Medium effort · Security & performance tooling

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €52,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 47 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Banned license finding(s) in License Compliance. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for low effort, because it clears the 2 License Compliance findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch :android-test :android-test :okio :okio :okio-fakefilesystem :okio-fakefilesystem :okio->:okio-fakefilesystem :okio-testing-support :okio-testing-support :okio->:okio-testing-support :okio-assetfilesystem :okio-assetfilesystem :okio-assetfilesystem->:okio :okio-bom :okio-bom :okio-nodefilesystem :okio-nodefilesystem :okio-nodefilesystem->:okio :okio-nodefilesystem->:okio-fakefilesystem :okio-nodefilesystem->:okio-testing-support :okio-testing-support->:okio-fakefilesystem :okio-wasifilesystem :okio-wasifilesystem :okio-testing-support->:okio-wasifilesystem :okio-wasifilesystem->:okio okio-parent okio-parent

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

34 modules, with 37 dependencies between them. 2 loops run through 6 of the modules, marked above the diagonal.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 (global)2 okio.Segment3 okio.TestExecutor4 okio.internal.Md55 okio.internal.Sha2566 okio.internal.Sha5127 okio.internal.preview18 okio.Buffer9 okio.WasiFileSystem10 okio.internal.preview1.Errno11 okio.internal12 okio13 okio.AsyncTimeout14 okio.ByteString15 okio.CloseBehavior16 okio.FileHandle17 okio.FileSystem18 okio.HashingSink19 okio.HashingSource20 okio.Lock21 okio.Options22 okio.Path23 okio.Timeout24 okio.TypedOptions25 okio.ZipFileSystem26 okio.assetfilesystem27 okio.assetfilesystem.AssetFileSystem28 okio.fakefilesystem.FakeFileSystem.Element29 okio.internal.DefaultSocket30 okio.internal.Hmac31 okio.internal.ResourceFileSystem32 okio.fakefilesystem.FakeFileSystem33 okio.fakefilesystem34 okio.fakefilesystem.FakeFileSystem.Operation
1 (global)
2 okio.Segment
3 okio.TestExecutor
4 okio.internal.Md5
5 okio.internal.Sha256
6 okio.internal.Sha512
7 okio.internal.preview1
8 okio.Buffer3
9 okio.WasiFileSystem2
10 okio.internal.preview1.Errno77
11 okio.internal1149
12 okio115
13 okio.AsyncTimeout2
14 okio.ByteString1
15 okio.CloseBehavior3
16 okio.FileHandle8
17 okio.FileSystem2
18 okio.HashingSink3
19 okio.HashingSource3
20 okio.Lock1
21 okio.Options3
22 okio.Path1
23 okio.Timeout1
24 okio.TypedOptions2
25 okio.ZipFileSystem1
26 okio.assetfilesystem8
27 okio.assetfilesystem.AssetFileSystem1
28 okio.fakefilesystem.FakeFileSystem.Element63
29 okio.internal.DefaultSocket24
30 okio.internal.Hmac21
31 okio.internal.ResourceFileSystem1
32 okio.fakefilesystem.FakeFileSystem52
33 okio.fakefilesystem813
34 okio.fakefilesystem.FakeFileSystem.Operation2
Uses a module listed above itPart of a loopThe module itself
1 (global)2 okio.Segment3 okio.TestExecutor4 okio.internal.Md55 okio.internal.Sha2566 okio.internal.Sha5127 okio.internal.preview18 okio.Buffer9 okio.WasiFileSystem10 okio.internal.preview1.Errno11 okio.internal12 okio13 okio.AsyncTimeout14 okio.ByteString15 okio.CloseBehavior16 okio.FileHandle17 okio.FileSystem18 okio.HashingSink19 okio.HashingSource20 okio.Lock21 okio.Options22 okio.Path23 okio.Timeout24 okio.TypedOptions25 okio.ZipFileSystem26 okio.assetfilesystem27 okio.assetfilesystem.AssetFileSystem28 okio.fakefilesystem.FakeFileSystem.Element29 okio.internal.DefaultSocket30 okio.internal.Hmac31 okio.internal.ResourceFileSystem32 okio.fakefilesystem.FakeFileSystem33 okio.fakefilesystem34 okio.fakefilesystem.FakeFileSystem.Operation(global)1okio.Segment2okio.TestExecutor3okio.internal.Md54okio.internal.Sha2565okio.internal.Sha5126okio.internal.preview17okio.Buffer8okio.WasiFileSystem9okio.internal.preview1.Errno10okio.internal11okio12okio.AsyncTimeout13okio.ByteString14okio.CloseBehavior15okio.FileHandle16okio.FileSystem17okio.HashingSink18okio.HashingSource19okio.Lock20okio.Options21okio.Path22okio.Timeout23okio.TypedOptions24okio.ZipFileSystem25okio.assetfilesystem26okio.assetfilesystem.AssetFileSystem27okio.fakefilesystem.FakeFileSystem.Element28okio.internal.DefaultSocket29okio.internal.Hmac30okio.internal.ResourceFileSystem31okio.fakefilesystem.FakeFileSystem32okio.fakefilesystem33okio.fakefilesystem.FakeFileSystem.Operation34327711491152138233131121816324211528132

At a glance — Code Health · 84% · Strong ·

At a glance — Architecture · 89% · Adequate · gated by D5 ·

At a glance — Maturity · 55% · Adequate · gated by M2 ·

At a glance — Readiness · 47% · Weak · gated by P3 ·

At a glance — Security · 78% · Strong ·

At a glance — Performance · 91% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures30High / Critical
A05:2025 — Injection5High / Critical

Roadmap

Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 2 Banned license finding(s) in License Compliance.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 2 Banned license finding(s) in License Compliance.+6.8 ptsLowLicense Compliance
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+7.1 ptsMediumArchitecture documentation
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+6.9 ptsMediumSecurity & performance tooling
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.+2.9 ptsMediumDeployment & Rollback
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.+2.4 ptsMediumObservability
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.+2.0 ptsMediumDocumentation (README)
Hide `okio.internal.preview1` (`ClockidKt`, `Preview1ClockKt`, `Preview1EnvKt`, `FdflagsKt`, `FiletypeKt`, `LookupFlagsKt`, `OFlagsKt`, `Preview1Kt`, and 1 more) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.+1.9 ptsMediumLibrary API & versioning
Resolve the 20 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (20).+1.3 ptsMediumDependency Vulnerabilities

File quality

Per-file score 0–10 — a quality signature. Of 74 files carrying findings, judged against the Production bar: 1% slop · 46% mixed · 53% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
okio/src/commonMain/kotlin/okio/internal/Buffer.kt6.0MixedExplicit Debt: TodoComment
okio/src/commonMain/kotlin/okio/Utf8.kt6.0MixedExplicit Debt: TodoComment
okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt6.0MixedExplicit Debt: TodoComment
okio/src/commonMain/kotlin/okio/internal/SegmentedByteString.kt6.0MixedExplicit Debt: TodoComment
okio/src/commonMain/kotlin/okio/internal/ByteString.kt6.0MixedExplicit Debt: TodoComment
okio/src/commonMain/kotlin/okio/ByteString.kt6.7MixedExplicit Debt: HackComment
okio/src/jvmMain/kotlin/okio/internal/ResourceFileSystem.kt6.7MixedExplicit Debt: TodoComment
okio/src/commonMain/kotlin/okio/internal/RealBufferedSink.kt6.7MixedExplicit Debt: TodoComment
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
okio/src/commonMain/kotlin/okio/FileHandle.kt7.0MixedCode Duplication: Edited copies of one member (4 members, 19+ corresponding lines)
okio/src/hashFunctions/kotlin/okio/internal/Md5.kt7.1MixedCode Duplication: Near-duplicate member family (4 members, 7 shared lines)
okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt7.2MixedCyclomatic Complexity: ZipFilesKt.readCentralDirectoryZipEntry (cyclomatic 20)
okio/src/jvmMain/kotlin/okio/Buffer.kt7.2MixedGod Classes: TooManyMethods: Buffer
okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt7.2MixedCode Duplication: Edited copy of a member (40 corresponding lines)
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt7.4MixedCode Duplication: Edited copies of one member (3 members, 18+ corresponding lines)
okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt7.4MixedCode Duplication: Duplicated block (15 lines × 3)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 29

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 152

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 26

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 11

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 44 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 44 dimensions across the health lenses
D1D2D3D4D5D6D13D14D15D16D17D19D26D27D28D29D30D35D36D43D44AX10AX3AX4M1M2M3P1P10P2P3P4P6PF1PF3X1X12X16X18X21X27X28X3X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 194 of 207 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1d639-84e3-7bb9-b7ee-8a3c397d8c23.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 2 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Gradle build resolved 266 artifact(s) across its subprojects (143 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `okio/src/appleMain/kotlin/okio/ByteString.kt`, `okio/src/appleMain/kotlin/okio/SegmentedByteString.kt`, `okio/src/commonMain/kotlin/okio/internal/ByteString.kt`, `okio/src/jvmMain/kotlin/okio/ByteString.kt`, `okio/src/jvmMain/kotlin/okio/CipherSource.kt`, … (+10 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 38 commits in the last 90 days, yet 93 of 119 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (android-test/src/main/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin, c is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin, c is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity9.0 / 10Strong✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Prevented

6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PathKt.toPath at 25.

PathKt.toPath (cyclomatic 25)okio/src/commonMain/kotlin/okio/internal/Path.kt:304
ZipFilesKt.readCentralDirectoryZipEntry (cyclomatic 20)okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt:189
Base64Kt.decodeBase64ToArray (cyclomatic 19)okio/src/commonMain/kotlin/okio/Base64.kt:32
BufferKt.selectPrefix (cyclomatic 19)okio/src/commonMain/kotlin/okio/internal/Buffer.kt:144
BufferKt.commonReadDecimalLong (cyclomatic 19)okio/src/commonMain/kotlin/okio/internal/Buffer.kt:650

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with PathKt.toPath (cyclomatic 25), ZipFilesKt.readCentralDirectoryZipEntry (cyclomatic 20), Base64Kt.decodeBase64ToArray (cyclomatic 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cyclomatic Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity7.2 / 10Strong✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 7.2 / 10 · rule-coverage 100% · ceiling Prevented

18 method(s) exceeded the cognitive complexity threshold of 15; the worst was BufferKt.selectPrefix at 56.

BufferKt.selectPrefix (cognitive 56)okio/src/commonMain/kotlin/okio/internal/Buffer.kt:144
Options.buildTrieRecursive (cognitive 40)okio/src/commonMain/kotlin/okio/Options.kt:109
PathKt.toPath (cognitive 38)okio/src/commonMain/kotlin/okio/internal/Path.kt:304
BufferKt.commonReadDecimalLong (cognitive 36)okio/src/commonMain/kotlin/okio/internal/Buffer.kt:650
ZipFilesKt.readCentralDirectoryZipEntry (cognitive 32)okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt:189

+ 13 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 18 bodies over 15 down to 15 or less in Cognitive Complexity — start with BufferKt.selectPrefix (cognitive 56), Options.buildTrieRecursive (cognitive 40), PathKt.toPath (cognitive 38). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 18 together lifts Cognitive Complexity from 7.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes7.9 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 7.9 / 10 · rule-coverage 100% · ceiling Prevented

13 god class(es) detected.

TooManyMethods: Buffer · ×11okio/src/jvmMain/kotlin/okio/Buffer.kt:79
FileTooLong: internal/Buffer.ktokio/src/commonMain/kotlin/okio/internal/Buffer.kt
MethodTooLong: ByteString.<init>okio/src/jvmMain/kotlin/okio/ByteString.kt:62

What to do

  1. Resolve the 11 TooManyMethods finding(s) in God Classes — start with ByteString.kt (4), Buffer.kt (3), RealBufferedSource.kt (3). — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 1 FileTooLong finding(s) in God Classes — start with Buffer.kt. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 MethodTooLong finding(s) in God Classes — start with ByteString.kt. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication9.4 / 10Stronggated by 78 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Verified

35 duplicated block group(s) detected. A further 43 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 10 of the 78 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Edited copy of a member (15 corresponding lines) · ×5okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt:316
Edited copy of a member (9 corresponding lines) · ×4okio/src/jvmMain/kotlin/okio/SegmentedByteString.kt:62
Duplicated block (9 lines × 2) · ×4okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/WasiFileHandle.kt:60
Edited copy of a member (12 corresponding lines) · ×3okio/src/jvmMain/kotlin/okio/Buffer.kt:603
Edited copy of a member (10 corresponding lines) · ×3okio/src/commonMain/kotlin/okio/internal/SegmentedByteString.kt:176

+ 45 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 5 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with RealBufferedSource.kt, ResourceFileSystem.kt, JvmSystemFileSystem.kt. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 4 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with SegmentedByteString.kt, JvmFileHandle.kt, WindowsPosixVariant.kt. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 4 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with WasiFileHandle.kt, Buffer.kt, Md5.kt. — One of this dimension's main actionable groups (4 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling1.1 / 10Critical✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 1.1 / 10 · rule-coverage 100% · ceiling Prevented

9 production modules (Gradle), 1 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 7 of the 9 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Circular dependency

What to do

  1. Resolve the 1 Circular dependency finding(s) in Coupling. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Verified

1 of 56 classes have LCOM4 above 3.

Low cohesion: FileHandle (LCOM4 5)okio/src/commonMain/kotlin/okio/FileHandle.kt:35

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with FileHandle.kt. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance6.0 / 10Adequate✓ Tool-verified

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Verified

2 of 16 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 13 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 5 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.

Banned license: org.openjdk.jmh:jmh-core · ×2

What to do

  1. Resolve the 2 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (2 issue-level).

Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D16 · Bus Factor9.2 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 9.2 / 10 · rule-coverage 100% · ceiling Documented

9 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is okio/src/jvmMain/kotlin/okio/Buffer.kt. Counted over 112 of the 208 production source files in this repository: 89 are under the ~2,400-byte size floor this dimension measures over, and the remaining 7 have no attributable history left to measure.

Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt9.8 / 10Stronggated by 25 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Prevented

25 deducted task-comment markers across 26793 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×24okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/WasiFileSystem.kt:222
HackCommentokio/src/commonMain/kotlin/okio/ByteString.kt:121

What to do

  1. Resolve the 24 TodoComment finding(s) in Explicit Debt — start with Utf8.kt (4), ForwardingSource.kt (3), Buffer.kt (3). — One of this dimension's main actionable groups (24 warning-level).
  2. Resolve the 1 HackComment finding(s) in Explicit Debt — start with ByteString.kt. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 documentation facets pass in full. 15 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D26 · Project Cohesion7.5 / 10Strong✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 7.5 / 10 · rule-coverage 100% · ceiling Documented

1 of 8 build units (Gradle) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D27 · Navigability9.7 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Documented

7 % of calls cross a namespace and 4 % go through an interface, but 77 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)6.0 / 10Adequate✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Documented

5 finding(s): 0 critical, 2 high, 3 medium, 0 low. semgrep hit a parse error in 3 file(s) — `gradlew` (line 74, line 178), `okio/src/jvmMain/kotlin/okio/ByteString.kt` (line 63), `okio/src/jvmMain/kotlin/okio/SegmentedByteString.kt` (line 38, line 39) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

26 finding(s): 0 critical, 21 high, 3 medium, 2 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 20 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (20). — One of this dimension's main actionable groups (20 issue-level).
  2. Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing5.0 / 10Adequate✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Documented

2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 21 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX3 · Project dependency cycles5.6 / 10Adequate✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

  • The projects :okio → :okio-fakefilesystem → :okio (one cycle inside a mutually-dependent group of 4 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.

What to do

  • Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

M1 · Documentation (README)7.1 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 · Library API & versioning6.1 / 10Adequate✓ Tool-verified

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

  • 9 public types in `okio.internal.preview1` are marked as implementation by their own namespace, folder or name: `ClockidKt` (okio-testing-support/src/wasmWasiMain/kotlin/okio/internal/preview1/Clockid.kt:1, `internal`), `Preview1ClockKt` (okio-testing-support/src/wasmWasiMain/kotlin/okio/internal/preview1/Preview1Clock.kt:1, `internal`), `Preview1EnvKt` (okio-testing-support/src/wasmWasiMain/kotlin/okio/internal/preview1/Preview1Env.kt:1, `internal`), `FdflagsKt` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Fdflags.kt:1, `internal`), `FiletypeKt` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Filetype.kt:1, `internal`), `LookupFlagsKt` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/LookupFlags.kt:1, `internal`), `OFlagsKt` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/OFlags.kt:1, `internal`), `Preview1Kt` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Preview1.kt:1, `internal`), and 1 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — okio-testing-support/src/wasmWasiMain/kotlin/okio/internal/preview1/Clockid.kt:1
  • 20 public types in `okio.internal` are marked as implementation by their own namespace, folder or name: `WasiKt` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/Wasi.kt:1, `internal`), `-Utf16Kt` (okio/src/commonMain/kotlin/okio/internal/-Utf16.kt:1, `internal`), `-Utf8Kt` (okio/src/commonMain/kotlin/okio/internal/-Utf8.kt:1, `internal`), `BufferKt` (okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1, `internal`), `BufferedSourceKt` (okio/src/commonMain/kotlin/okio/internal/BufferedSource.kt:1, `internal`), `ByteStringKt` (okio/src/commonMain/kotlin/okio/internal/ByteString.kt:1, `internal`), `FileSystemKt` (okio/src/commonMain/kotlin/okio/internal/FileSystem.kt:1, `internal`), `PathKt` (okio/src/commonMain/kotlin/okio/internal/Path.kt:1, `internal`), and 12 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/Wasi.kt:1
  • 77 public types in `okio.internal.preview1.Errno` are marked as implementation by their own namespace, folder or name: `success` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:9, `internal`), `toobig` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:12, `internal`), `acces` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:15, `internal`), `addrinuse` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:18, `internal`), `addrnotavail` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:21, `internal`), `afnosupport` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:24, `internal`), `again` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:27, `internal`), `already` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:30, `internal`), and 69 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:9
  • 1 public type in `okio.internal.Hmac` is marked as implementation by its own namespace, folder or name: `Companion` (okio/src/hashFunctions/kotlin/okio/internal/Hmac.kt:38, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — okio/src/hashFunctions/kotlin/okio/internal/Hmac.kt:38
  • 1 public type in `okio.internal.Md5` is marked as implementation by its own namespace, folder or name: `Companion` (okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:187, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:187
  • 1 public type in `okio.internal.Sha256` is marked as implementation by its own namespace, folder or name: `Companion` (okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:240, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:240
  • 1 public type in `okio.internal.Sha512` is marked as implementation by its own namespace, folder or name: `Companion` (okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:267, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:267
  • 2 public types in `okio.internal.DefaultSocket` are marked as implementation by their own namespace, folder or name: `SocketSink` (okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt:60, `internal`), `SocketSource` (okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt:122, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt:60

What to do

  • Hide `okio.internal.preview1` (`ClockidKt`, `Preview1ClockKt`, `Preview1EnvKt`, `FdflagsKt`, `FiletypeKt`, `LookupFlagsKt`, `OFlagsKt`, `Preview1Kt`, and 1 more) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `okio.internal` (`WasiKt`, `-Utf16Kt`, `-Utf8Kt`, `BufferKt`, `BufferedSourceKt`, `ByteStringKt`, `FileSystemKt`, `PathKt`, and 12 more) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `okio.internal.preview1.Errno` (`success`, `toobig`, `acces`, `addrinuse`, `addrnotavail`, `afnosupport`, `again`, `already`, and 69 more) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `okio.internal.Hmac` (`Companion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `okio.internal.Md5` (`Companion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `okio.internal.Sha256` (`Companion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `okio.internal.Sha512` (`Companion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `okio.internal.DefaultSocket` (`SocketSink`, `SocketSource`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P2 · Observability5.5 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `okio/jvm/jmh`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4

What to do

  • Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

  • The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

PF1 · Benchmark discipline8.5 / 10Strong✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

  • A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — okio/jvm/jmh/src/jmh/java/com/squareup/okio/benchmarks/AsyncTimeoutBenchmark.java

What to do

  • Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X3 · Exception handling6.7 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — okio-nodefilesystem/src/commonMain/kotlin/okio/NodeJsFileSystem.kt:208
  • `catch (t: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — okio/src/jsMain/kotlin/okio/JsPlatform.kt:37, okio/src/jsMain/kotlin/okio/JsPlatform.kt:46

What to do

  • Swallowed exception (empty catch)
X5 · Nullable reference types9.2 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health84%StrongSolid.
Architecture89%Adequate — gated by D5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity55%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness47%Weak — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security78%StrongSolid.
Performance91%ExemplaryStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • D11 Test Reliability — 2 observation(s) recorded · This repository declares 2 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
  • X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 70 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — no public interfaces
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D10 Test Quality — ~22417 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D12 Dependency Hygiene — Not scored — a Gradle build resolved 266 artifact(s) across its subprojects (143 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed Kotlin surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 15 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (24 value object(s))
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • M4 Documentation accuracy — Not applicable: the 15 current-state document(s) make no claim of a kind M4 checks. 5 claim(s) of kinds M4 does not check were not checked (path 2, environment variable 3); M4 checks only links and versions and artefact counts.
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 29 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×20
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D11 · Test Reliability · Test declared unreliable · ×2
  • Test declared unreliable: sinkSplitsLargeWrites okio/src/jvmTest/kotlin/okio/AsyncTimeoutTest.kt:348 — This test is disabled or skipped with a reason naming unreliability — the repository's own words: "Flaky". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
  • Test declared unreliable: okio/src/jvmTest/kotlin/okio/ThrottlerTest.kt okio/src/jvmTest/kotlin/okio/ThrottlerTest.kt:24 — This test is disabled or skipped with a reason naming unreliability — the repository's own words: "These tests are flaky and fail on slower hardware, need to be improved". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
D14 · License Compliance · Banned license · ×2
  • Banned license: org.openjdk.jmh:jmh-core — `org.openjdk.jmh:jmh-core` 1.37 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
  • Banned license: org.openjdk.jmh:jmh-generator-annprocess — `org.openjdk.jmh:jmh-generator-annprocess` 1.37 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
AX3 · Project dependency cycles · Project dependency cycle · ×1
  • Project dependency cycle — The projects :okio → :okio-fakefilesystem → :okio (one cycle inside a mutually-dependent group of 4 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
D5 · Coupling · Circular dependency · ×1
  • Circular dependency — :okio → :okio-fakefilesystem → :okio (one cycle inside a mutually-dependent group of 4 modules)
Serious — 152 finding(s)
D17 · Explicit Debt · TodoComment · ×24
  • TodoComment okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/WasiFileSystem.kt:222 — // TODO: stop using exceptions for flow control. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio-testing-support/src/commonMain/kotlin/okio/AbstractFileSystemTest.kt:1618 — // TODO(swankjesse): configure a test directory in CI that exists, but that this process doesn't — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio/src/nonJvmMain/kotlin/okio/ForwardingSource.kt:21 — // TODO 'Source by delegate' once https://youtrack.jetbrains.com/issue/KT-23935 is fixed.
  • TodoComment okio/src/jvmMain/kotlin/okio/ForwardingSource.kt:24 — // TODO 'Source by delegate' once https://youtrack.jetbrains.com/issue/KT-23935 is fixed.
  • TodoComment okio/src/commonMain/kotlin/okio/ForwardingSource.kt:26 — // TODO 'Source by delegate' once https://youtrack.jetbrains.com/issue/KT-23935 is fixed.
  • TodoComment okio/src/jvmMain/kotlin/okio/-JvmPlatform.kt:28 — // TODO remove if https://youtrack.jetbrains.com/issue/KT-20641 provides a better solution
  • TodoComment okio/src/jvmMain/kotlin/okio/ForwardingSink.kt:26 — // TODO 'Sink by delegate' once https://youtrack.jetbrains.com/issue/KT-23935 is fixed.
  • TodoComment okio/src/jvmMain/kotlin/okio/SegmentPool.kt:46 — // TODO: Is 64 KiB a good maximum size? Do we ever have that many idle segments? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio/src/jvmMain/kotlin/okio/internal/ResourceFileSystem.kt:59 — // TODO(jwilson): throw FileNotFoundException if the canonical file doesn't exist. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio/src/commonTest/kotlin/okio/Utf8KotlinTest.kt:183 — // TODO Confirm we are consistent when writing one code point at a time. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio/src/commonMain/kotlin/okio/CommonPlatform.kt:26 — // TODO make internal https://youtrack.jetbrains.com/issue/KT-37316
  • TodoComment okio/src/commonMain/kotlin/okio/Utf8.kt:130 — // TODO combine with Buffer.writeUtf8? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio/src/commonMain/kotlin/okio/Utf8.kt:131 — // TODO combine with Buffer.writeUtf8CodePoint? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio/src/commonMain/kotlin/okio/Utf8.kt:206 — // TODO combine with Buffer.readUtf8CodePoint? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio/src/commonMain/kotlin/okio/Utf8.kt:254 — // TODO combine with Buffer.readUtf8? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio/src/commonMain/kotlin/okio/internal/-Utf8.kt:23 — // TODO For benchmarking, these methods need to be available but preferably invisible — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio/src/commonMain/kotlin/okio/internal/Buffer.kt:18 — // TODO move to Buffer class: https://youtrack.jetbrains.com/issue/KT-20427
  • TodoComment okio/src/commonMain/kotlin/okio/internal/Buffer.kt:233 — // TODO Kotlin's expect classes can't have default implementations, so platform implementations — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio/src/commonMain/kotlin/okio/internal/ByteString.kt:37 — // TODO Kotlin's expect classes can't have default implementations, so platform implementations — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio/src/commonMain/kotlin/okio/internal/SegmentedByteString.kt:99 — // TODO Kotlin's expect classes can't have default implementations, so platform implementations — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1701 — // TODO(jwilson): use edit counts or other information to track unexpected changes? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment okio/src/commonMain/kotlin/okio/internal/RealBufferedSink.kt:17 — // TODO move to RealBufferedSink class: https://youtrack.jetbrains.com/issue/KT-20427
  • TodoComment okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt:17 — // TODO move to RealBufferedSource class: https://youtrack.jetbrains.com/issue/KT-20427
  • TodoComment okio/src/commonMain/kotlin/okio/internal/SegmentedByteString.kt:17 — // TODO move to SegmentedByteString class: https://youtrack.jetbrains.com/issue/KT-20427
D3 · God Classes · TooManyMethods · ×11
  • TooManyMethods: Buffer okio/src/jvmMain/kotlin/okio/Buffer.kt:79 — TooManyMethods — 108 methods. The bar is 30 methods; this is 78 over it, 3.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Buffer okio/src/nonJvmMain/kotlin/okio/Buffer.kt:71 — TooManyMethods — 89 methods. The bar is 30 methods; this is 59 over it, 2.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Buffer okio/src/commonMain/kotlin/okio/Buffer.kt:31 — TooManyMethods — 85 methods. The bar is 30 methods; this is 55 over it, 2.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: RealBufferedSource okio/src/jvmMain/kotlin/okio/RealBufferedSource.kt:54 — TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ByteString okio/src/jvmMain/kotlin/okio/ByteString.kt:61 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: RealBufferedSource okio/src/nonJvmMain/kotlin/okio/RealBufferedSource.kt:49 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: RealBufferedSource okio/src/commonMain/kotlin/okio/RealBufferedSource.kt:19 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ByteString okio/src/appleMain/kotlin/okio/ByteString.kt:61 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ByteString okio/src/nonAppleMain/kotlin/okio/ByteString.kt:55 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ByteString okio/src/commonMain/kotlin/okio/ByteString.kt:36 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: RealBufferedSink okio/src/jvmMain/kotlin/okio/RealBufferedSink.kt:42 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×5
  • Edited copy of a member (15 corresponding lines) okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt:316 — okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt:316-334 | okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt:420-434 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) okio/src/jvmMain/kotlin/okio/internal/ResourceFileSystem.kt:68 — okio/src/jvmMain/kotlin/okio/internal/ResourceFileSystem.kt:68-83 | okio/src/jvmMain/kotlin/okio/internal/ResourceFileSystem.kt:85-99 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) okio/src/jvmMain/kotlin/okio/JvmSystemFileSystem.kt:66 — okio/src/jvmMain/kotlin/okio/JvmSystemFileSystem.kt:66-80 | okio/src/jvmMain/kotlin/okio/NioFileSystemWrappingFileSystem.kt:65-80 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) okio-fakefilesystem/src/commonMain/kotlin/okio/fakefilesystem/FakeFileSystem.kt:414 — okio-fakefilesystem/src/commonMain/kotlin/okio/fakefilesystem/FakeFileSystem.kt:414-431 | okio-fakefilesystem/src/commonMain/kotlin/okio/fakefilesystem/FakeFileSystem.kt:502-516 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) samples/src/jvmMain/java/okio/samples/ReadFileLineByLine.java:30 — samples/src/jvmMain/java/okio/samples/ReadFileLineByLine.java:30-44 | samples/src/jvmMain/java/okio/samples/ReadJavaIoFileLineByLine.java:29-43 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×4
  • Edited copy of a member (9 corresponding lines) okio/src/jvmMain/kotlin/okio/SegmentedByteString.kt:62 — okio/src/jvmMain/kotlin/okio/SegmentedByteString.kt:62-73 | okio/src/jvmMain/kotlin/okio/ByteString.kt:101-109 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) okio/src/jvmMain/kotlin/okio/JvmFileHandle.kt:26 — okio/src/jvmMain/kotlin/okio/JvmFileHandle.kt:26-34 | okio/src/jvmMain/kotlin/okio/NioFileSystemFileHandle.kt:27-35 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) okio/src/mingwX64Main/kotlin/okio/WindowsPosixVariant.kt:194 — okio/src/mingwX64Main/kotlin/okio/WindowsPosixVariant.kt:194-202 | okio/src/unixMain/kotlin/okio/UnixPosixVariant.kt:159-167 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1085 — okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1085-1093 | okio/src/commonMain/kotlin/okio/internal/RealBufferedSink.kt:93-102 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×4
  • Duplicated block (9 lines × 2) okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/WasiFileHandle.kt:60 — okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/WasiFileHandle.kt:60-68 | okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/WasiFileHandle.kt:93-101 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/WasiFileHandle.kt:60` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:974 — okio/src/commonMain/kotlin/okio/internal/Buffer.kt:974-982 | okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1040-1048 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/commonMain/kotlin/okio/internal/Buffer.kt:974` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:99 — okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:99-107 | okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:108-116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:99` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) REDACTED:105 — REDACTED:105-113 | REDACTED:142-150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:105` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D30 · Dependency Vulnerabilities · Medium CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×3
  • Edited copy of a member (12 corresponding lines) okio/src/jvmMain/kotlin/okio/Buffer.kt:603 — okio/src/jvmMain/kotlin/okio/Buffer.kt:603-614 | okio/src/jvmMain/kotlin/okio/Buffer.kt:625-641 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt:38 — okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt:38-50 | okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt:135-146 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) samples/src/jvmMain/java/okio/samples/ReadFileLineByLine.kt:25 — samples/src/jvmMain/java/okio/samples/ReadFileLineByLine.kt:25-36 | samples/src/jvmMain/kotlin/okio/samples/ReadJavaIoFileLineByLine.kt:24-35 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×3
  • Edited copy of a member (10 corresponding lines) okio/src/commonMain/kotlin/okio/internal/SegmentedByteString.kt:176 — okio/src/commonMain/kotlin/okio/internal/SegmentedByteString.kt:176-185 | okio/src/commonMain/kotlin/okio/internal/SegmentedByteString.kt:192-205 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) okio/src/mingwX64Main/kotlin/okio/WindowsFileHandle.kt:99 — okio/src/mingwX64Main/kotlin/okio/WindowsFileHandle.kt:99-108 | okio/src/unixMain/kotlin/okio/UnixFileHandle.kt:70-79 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) samples/src/jvmMain/kotlin/okio/samples/WriteFile.kt:25 — samples/src/jvmMain/kotlin/okio/samples/WriteFile.kt:25-34 | samples/src/jvmMain/kotlin/okio/samples/WriteJavaIoFile.kt:24-33 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×3
  • Duplicated block (11 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1404 — okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1404-1414 | okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt:446-456 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1404` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) okio/src/jvmMain/kotlin/okio/JvmOkio.kt:95 — okio/src/jvmMain/kotlin/okio/JvmOkio.kt:95-105 | okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt:140-151 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt:140` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11 lines × 2) samples/src/jvmMain/java/okio/samples/WriteFile.java:33 — samples/src/jvmMain/java/okio/samples/WriteFile.java:33-43 | samples/src/jvmMain/java/okio/samples/WriteJavaIoFile.java:32-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `samples/src/jvmMain/java/okio/samples/WriteFile.java:33` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×3
  • Duplicated block (8 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:350 — okio/src/commonMain/kotlin/okio/internal/Buffer.kt:350-357 | okio/src/commonMain/kotlin/okio/internal/Buffer.kt:384-391 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/commonMain/kotlin/okio/internal/Buffer.kt:350` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt:182 — okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt:182-189 | okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:214-221 — before extracting anything, compare `okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt` and `okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt:182` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) okio/src/jvmMain/kotlin/okio/Buffer.kt:605 — okio/src/jvmMain/kotlin/okio/Buffer.kt:605-612 | okio/src/jvmMain/kotlin/okio/Buffer.kt:629-636 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (40 corresponding lines) · ×2
  • Edited copy of a member (40 corresponding lines) okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:104 — okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:104-150 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:106-145 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) okio/src/jvmMain/kotlin/okio/Timeout.kt:175 — okio/src/jvmMain/kotlin/okio/Timeout.kt:175-214 | okio/src/jvmMain/kotlin/okio/Timeout.kt:253-295 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×2
  • Edited copy of a member (36 corresponding lines) okio/src/commonMain/kotlin/okio/Utf8.kt:211 — okio/src/commonMain/kotlin/okio/Utf8.kt:211-246 | okio/src/commonMain/kotlin/okio/Utf8.kt:259-307 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) okio/src/mingwX64Main/kotlin/okio/WindowsPosixVariant.kt:98 — okio/src/mingwX64Main/kotlin/okio/WindowsPosixVariant.kt:98-135 | okio/src/unixMain/kotlin/okio/UnixPosixVariant.kt:84-119 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×2
  • Edited copy of a member (26 corresponding lines) okio/src/jvmMain/kotlin/okio/HashingSource.kt:70 — okio/src/jvmMain/kotlin/okio/HashingSource.kt:70-99 | okio/src/nonJvmMain/kotlin/okio/HashingSource.kt:30-55 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/FileSource.kt:32 — okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/FileSource.kt:32-57 | okio/src/nativeMain/kotlin/okio/FileSource.kt:38-67 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×2
  • Edited copy of a member (23 corresponding lines) okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt:92 — okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt:92-115 | okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt:153-175 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) REDACTED:94 — REDACTED:94-116 | REDACTED:131-153 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) okio/src/unixMain/kotlin/okio/UnixPosixVariant.kt:200 — okio/src/unixMain/kotlin/okio/UnixPosixVariant.kt:200-213 | okio-nodefilesystem/src/commonMain/kotlin/okio/NodeJsFileSystem.kt:224-234 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) okio/src/unixMain/kotlin/okio/UnixFileHandle.kt:52 — okio/src/unixMain/kotlin/okio/UnixFileHandle.kt:52-63 | okio/src/mingwX64Main/kotlin/okio/WindowsFileHandle.kt:59-69 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×2
  • Edited copy of a member (13 corresponding lines) okio/src/jvmMain/kotlin/okio/JvmFileHandle.kt:47 — okio/src/jvmMain/kotlin/okio/JvmFileHandle.kt:47-59 | okio/src/jvmMain/kotlin/okio/NioFileSystemFileHandle.kt:48-61 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) samples/src/jvmMain/java/okio/samples/WriteFile.java:31 — samples/src/jvmMain/java/okio/samples/WriteFile.java:31-43 | samples/src/jvmMain/java/okio/samples/WriteJavaIoFile.java:30-42 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2
  • Duplicated block (15 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:356 — okio/src/commonMain/kotlin/okio/internal/Buffer.kt:356-370 | okio/src/commonMain/kotlin/okio/internal/Buffer.kt:394-408 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/commonMain/kotlin/okio/internal/Buffer.kt:356` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (15 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:224 — okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:224-238 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:251-265 — before extracting anything, compare `okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt` and `okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2
  • Duplicated block (14 lines × 2) okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt:33 — okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt:33-46 | okio/src/macosX64Main/kotlin/okio/MacosX64PosixVariant.kt:34-47 — before extracting anything, compare `okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt` and `okio/src/macosX64Main/kotlin/okio/MacosX64PosixVariant.kt` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt:33` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) okio/src/jvmMain/kotlin/okio/HashingSource.kt:73 — okio/src/jvmMain/kotlin/okio/HashingSource.kt:73-86 | okio/src/nonJvmMain/kotlin/okio/HashingSource.kt:33-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/jvmMain/kotlin/okio/HashingSource.kt:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1059 — okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1059-1064 | okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1071-1076 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1059` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1070` calls `toByte` and `okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1058` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1124 — okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1124-1129 | okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1137-1142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2
  • Duplicated block (7 lines × 2) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1128 — okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1128-1134 | okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1145-1151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1128` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) samples/src/jvmMain/java/okio/samples/Hashing.java:36 — samples/src/jvmMain/java/okio/samples/Hashing.java:36-42 | samples/src/jvmMain/java/okio/samples/Hashing.java:44-50 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×2
  • Swallowed exception (caught, then discarded) okio/src/jsMain/kotlin/okio/JsPlatform.kt:37 — `catch (t: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) okio/src/jsMain/kotlin/okio/JsPlatform.kt:46 — `catch (t: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D1 · Cyclomatic Complexity · PathKt.toPath (cyclomatic 25) · ×1
  • PathKt.toPath (cyclomatic 25) okio/src/commonMain/kotlin/okio/internal/Path.kt:304 — PathKt.toPath has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ZipFilesKt.readCentralDirectoryZipEntry (cyclomatic 20) · ×1
  • ZipFilesKt.readCentralDirectoryZipEntry (cyclomatic 20) okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt:189 — ZipFilesKt.readCentralDirectoryZipEntry has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Base64Kt.decodeBase64ToArray (cyclomatic 19) · ×1
  • Base64Kt.decodeBase64ToArray (cyclomatic 19) okio/src/commonMain/kotlin/okio/Base64.kt:32 — Base64Kt.decodeBase64ToArray has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · BufferKt.selectPrefix (cyclomatic 19) · ×1
  • BufferKt.selectPrefix (cyclomatic 19) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:144 — BufferKt.selectPrefix has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BufferKt.commonReadDecimalLong (cyclomatic 19) · ×1
  • BufferKt.commonReadDecimalLong (cyclomatic 19) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:650 — BufferKt.commonReadDecimalLong has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Options.buildTrieRecursive (cyclomatic 18) · ×1
  • Options.buildTrieRecursive (cyclomatic 18) okio/src/commonMain/kotlin/okio/Options.kt:109 — Options.buildTrieRecursive has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D17 · Explicit Debt · HackComment · ×1
  • HackComment okio/src/commonMain/kotlin/okio/ByteString.kt:121 — // Hack to work around Kotlin's limitation for using JvmName on open/override vals/funs — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 · Cognitive Complexity · BufferKt.selectPrefix (cognitive 56) · ×1
  • BufferKt.selectPrefix (cognitive 56) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:144 — BufferKt.selectPrefix has cognitive complexity 56 (threshold 15). Drivers by points: if/else 17 (49 pts), loops 3 (7 pts) (nesting depth added 36). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: okio/src/commonMain/kotlin/okio/internal/Buffer.kt holds 7 of the 18 methods over the threshold — including the worst — and 94 of the 188 points over it (50%), 3.4× the next-largest file (okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt at 28). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · Options.buildTrieRecursive (cognitive 40) · ×1
  • Options.buildTrieRecursive (cognitive 40) okio/src/commonMain/kotlin/okio/Options.kt:109 — Options.buildTrieRecursive has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (24 pts), loops 7 (14 pts), boolean chains 2 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PathKt.toPath (cognitive 38) · ×1
  • PathKt.toPath (cognitive 38) okio/src/commonMain/kotlin/okio/internal/Path.kt:304 — PathKt.toPath has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 8, loops 3, match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BufferKt.commonReadDecimalLong (cognitive 36) · ×1
  • BufferKt.commonReadDecimalLong (cognitive 36) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:650 — BufferKt.commonReadDecimalLong has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: okio/src/commonMain/kotlin/okio/internal/Buffer.kt holds 7 of the 18 methods over the threshold — including the worst — and 94 of the 188 points over it (50%), 3.4× the next-largest file (okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt at 28). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · ZipFilesKt.readCentralDirectoryZipEntry (cognitive 32) · ×1
  • ZipFilesKt.readCentralDirectoryZipEntry (cognitive 32) okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt:189 — ZipFilesKt.readCentralDirectoryZipEntry has cognitive complexity 32 (threshold 15). Drivers by points: if/else 18 (28 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BufferKt.commonIndexOfElement (cognitive 26) · ×1
  • BufferKt.commonIndexOfElement (cognitive 26) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1338 — BufferKt.commonIndexOfElement has cognitive complexity 26 (threshold 15). Drivers by points: loops 5 (14 pts), if/else 4 (11 pts), boolean chains 1 (nesting depth added 16). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: okio/src/commonMain/kotlin/okio/internal/Buffer.kt holds 7 of the 18 methods over the threshold — including the worst — and 94 of the 188 points over it (50%), 3.4× the next-largest file (okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt at 28). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · BufferKt.commonReadHexadecimalUnsignedLong (cognitive 24) · ×1
  • BufferKt.commonReadHexadecimalUnsignedLong (cognitive 24) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:713 — BufferKt.commonReadHexadecimalUnsignedLong has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: okio/src/commonMain/kotlin/okio/internal/Buffer.kt holds 7 of the 18 methods over the threshold — including the worst — and 94 of the 188 points over it (50%), 3.4× the next-largest file (okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt at 28). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · FileSystemKt.collectRecursively (cognitive 22) · ×1
  • FileSystemKt.collectRecursively (cognitive 22) okio/src/commonMain/kotlin/okio/internal/FileSystem.kt:107 — FileSystemKt.collectRecursively has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2 (5 pts), boolean chains 4 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ZipFilesKt.openZip (cognitive 21) · ×1
  • ZipFilesKt.openZip (cognitive 21) okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt:61 — ZipFilesKt.openZip has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2, boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Base64Kt.decodeBase64ToArray (cognitive 20) · ×1
  • Base64Kt.decodeBase64ToArray (cognitive 20) okio/src/commonMain/kotlin/okio/Base64.kt:32 — Base64Kt.decodeBase64ToArray has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4, loops 2, match/switch 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · BufferKt.commonWrite (cognitive 20) · ×1
  • BufferKt.commonWrite (cognitive 20) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1153 — BufferKt.commonWrite has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: okio/src/commonMain/kotlin/okio/internal/Buffer.kt holds 7 of the 18 methods over the threshold — including the worst — and 94 of the 188 points over it (50%), 3.4× the next-largest file (okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt at 28). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · ZipFilesKt.readOrSkipLocalHeader (cognitive 20) · ×1
  • ZipFilesKt.readOrSkipLocalHeader (cognitive 20) okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt:395 — ZipFilesKt.readOrSkipLocalHeader has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BufferKt.commonWriteUtf8 (cognitive 19) · ×1
  • BufferKt.commonWriteUtf8 (cognitive 19) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:941 — BufferKt.commonWriteUtf8 has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (4 pts), match/switch 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: okio/src/commonMain/kotlin/okio/internal/Buffer.kt holds 7 of the 18 methods over the threshold — including the worst — and 94 of the 188 points over it (50%), 3.4× the next-largest file (okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt at 28). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · BufferKt.commonSeek (cognitive 18) · ×1
  • BufferKt.commonSeek (cognitive 18) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1552 — BufferKt.commonSeek has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This file is where this pass's cognitive complexity CONCENTRATES: okio/src/commonMain/kotlin/okio/internal/Buffer.kt holds 7 of the 18 methods over the threshold — including the worst — and 94 of the 188 points over it (50%), 3.4× the next-largest file (okio/src/zlibMain/kotlin/okio/internal/ZipFiles.kt at 28). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · FakeFileSystem.open (cognitive 17) · ×1
  • FakeFileSystem.open (cognitive 17) okio-fakefilesystem/src/commonMain/kotlin/okio/fakefilesystem/FakeFileSystem.kt:338 — FakeFileSystem.open has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GzipSource.consumeHeader (cognitive 17) · ×1
  • GzipSource.consumeHeader (cognitive 17) okio/src/zlibMain/kotlin/okio/GzipSource.kt:95 — GzipSource.consumeHeader has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (17 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Utf8Kt.utf8Size (cognitive 16) · ×1
  • Utf8Kt.utf8Size (cognitive 16) okio/src/commonMain/kotlin/okio/Utf8.kt:77 — Utf8Kt.utf8Size has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RealBufferedSource.inputStream (cognitive 16) · ×1
  • RealBufferedSource.inputStream (cognitive 16) okio/src/jvmMain/kotlin/okio/RealBufferedSource.kt:153 — RealBufferedSource.inputStream has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: internal/Buffer.kt okio/src/commonMain/kotlin/okio/internal/Buffer.kt — FileTooLong — 1087 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 587 over it, 2.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D3 · God Classes · MethodTooLong · ×1
  • MethodTooLong: ByteString.<init> okio/src/jvmMain/kotlin/okio/ByteString.kt:62 — MethodTooLong — <init> runs 208 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 108 over it, 2.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Near-duplicate member family (4 members, 7 shared lines) · ×1
  • Near-duplicate member family (4 members, 7 shared lines) okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:140 — okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:140-184 | okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt:136-189 | okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:153-221 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:148-248 — These 4 members are variants of one another: a block of 7 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member pair (23 shared lines) · ×1
  • Near-duplicate member pair (23 shared lines) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:941 — okio/src/commonMain/kotlin/okio/internal/Buffer.kt:941-1032 | okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1034-1083 — These two members are variants of one another: 23 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:35 — okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:35-72 | okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt:36-73 | okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:39-76 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:39-76 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:336 — okio/src/commonMain/kotlin/okio/internal/Buffer.kt:336-370 | okio/src/commonMain/kotlin/okio/internal/Buffer.kt:372-408 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) okio/src/jvmMain/kotlin/okio/JvmOkio.kt:87 — okio/src/jvmMain/kotlin/okio/JvmOkio.kt:87-110 | okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt:126-151 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:811 — okio/src/commonMain/kotlin/okio/internal/Buffer.kt:811-833 | okio/src/jvmMain/kotlin/okio/Buffer.kt:374-395 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 20+ corresponding lines) okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/FileSink.kt:56 — okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/FileSink.kt:56-75 | okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/FileSource.kt:59-83 | okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/WasiFileHandle.kt:50-76 | okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/WasiFileHandle.kt:83-106 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt:29 — okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt:29-46 | okio/src/macosX64Main/kotlin/okio/MacosX64PosixVariant.kt:30-47 | okio/src/mingwX64Main/kotlin/okio/WindowsPosixVariant.kt:155-172 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) okio/src/jvmMain/kotlin/okio/Buffer.kt:218 — okio/src/jvmMain/kotlin/okio/Buffer.kt:218-242 | okio/src/zlibMain/kotlin/okio/GzipSource.kt:172-191 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 19+ corresponding lines) okio/src/commonMain/kotlin/okio/FileHandle.kt:366 — okio/src/commonMain/kotlin/okio/FileHandle.kt:366-386 | okio/src/jvmMain/kotlin/okio/DeflaterSink.kt:32-59 | okio/src/jvmMain/kotlin/okio/JvmOkio.kt:50-68 | okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt:64-84 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×1
  • Edited copy of a member (18 corresponding lines) okio/src/mingwX64Main/kotlin/okio/WindowsFileHandle.kt:75 — okio/src/mingwX64Main/kotlin/okio/WindowsFileHandle.kt:75-92 | okio/src/mingwX64Main/kotlin/okio/WindowsFileHandle.kt:114-131 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) okio/src/jvmMain/kotlin/okio/HashingSink.kt:69 — okio/src/jvmMain/kotlin/okio/HashingSink.kt:69-88 | okio/src/nonJvmMain/kotlin/okio/HashingSink.kt:30-45 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1401 — okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1401-1414 | okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt:441-456 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 23+ corresponding lines) okio/src/commonMain/kotlin/okio/internal/RealBufferedSink.kt:191 — okio/src/commonMain/kotlin/okio/internal/RealBufferedSink.kt:191-214 | okio/src/jvmMain/kotlin/okio/DeflaterSink.kt:111-138 | okio/src/nativeMain/kotlin/okio/DeflaterSink.kt:70-92 | okio/src/zlibMain/kotlin/okio/GzipSink.kt:87-118 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) okio/src/commonMain/kotlin/okio/internal/ByteString.kt:376 — okio/src/commonMain/kotlin/okio/internal/ByteString.kt:376-384 | okio/src/nonJsMain/kotlin/okio/internal/ByteStringNonJs.kt:35-42 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×1
  • Edited copy of a member (7 corresponding lines) okio/src/commonMain/kotlin/okio/internal/ByteString.kt:230 — okio/src/commonMain/kotlin/okio/internal/ByteString.kt:230-236 | okio/src/commonMain/kotlin/okio/internal/SegmentedByteString.kt:223-229 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (37 lines × 4) · ×1
  • Duplicated block (37 lines × 4) okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:36 — okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:36-72 | okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt:37-73 | okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:40-76 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:40-76 — before extracting anything, compare `okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt` and `okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (24–27 lines × 2) · ×1
  • Duplicated block (24–27 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:124 — okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:124-150 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:122-145 — before extracting anything, compare `okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt` and `okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:124` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `words` to `IntArray` in one and `LongArray` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) okio/src/commonMain/kotlin/okio/internal/ByteString.kt:74 — okio/src/commonMain/kotlin/okio/internal/ByteString.kt:74-97 | okio/src/commonMain/kotlin/okio/internal/ByteString.kt:102-125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (18–23 lines × 2) · ×1
  • Duplicated block (18–23 lines × 2) okio/src/commonMain/kotlin/okio/Utf8.kt:443 — okio/src/commonMain/kotlin/okio/Utf8.kt:443-465 | okio/src/commonMain/kotlin/okio/Utf8.kt:510-527 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/commonMain/kotlin/okio/Utf8.kt:443` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `okio/src/commonMain/kotlin/okio/Utf8.kt:507` calls `isUtf8Continuation` and `okio/src/commonMain/kotlin/okio/Utf8.kt:443` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) okio/src/jvmMain/kotlin/okio/DeflaterSink.kt:119 — okio/src/jvmMain/kotlin/okio/DeflaterSink.kt:119-138 | okio/src/zlibMain/kotlin/okio/GzipSink.kt:99-118 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/jvmMain/kotlin/okio/DeflaterSink.kt:119` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:172 — okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:172-190 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:167-185 — before extracting anything, compare `okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt` and `okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:191` calls `toByte` and `okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:186` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt:137 — okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt:137-151 | okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:154-168 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:149-163 — before extracting anything, compare `okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt` and `okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8–12 lines × 2) · ×1
  • Duplicated block (8–12 lines × 2) okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/FileSource.kt:33 — okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/FileSource.kt:33-40 | okio/src/nativeMain/kotlin/okio/FileSource.kt:39-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt:153 — okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt:153-163 | okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:170-180 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:165-175 — before extracting anything, compare `okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt` and `okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7–10 lines × 10) · ×1
  • Duplicated block (7–10 lines × 10) okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:168 — okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:168-174 | okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt:168-177 | okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:188-197 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:187-193 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:195-201 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:203-209 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:211-217 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:219-225 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:227-233 | okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:235-241 — before extracting anything, compare `okio/src/hashFunctions/kotlin/okio/internal/Sha1.kt` and `okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:175` calls `toByte` and `okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:194` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt:33 — okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt:33-38 | okio/src/macosX64Main/kotlin/okio/MacosX64PosixVariant.kt:34-39 | okio/src/mingwX64Main/kotlin/okio/WindowsPosixVariant.kt:159-164 — before extracting anything, compare `okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt` and `okio/src/macosX64Main/kotlin/okio/MacosX64PosixVariant.kt` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/appleNonMacosX64Main/kotlin/okio/NonMacosX64PosixVariant.kt:33` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (4–5 lines × 6) · ×1
  • Duplicated block (4–5 lines × 6) okio/src/commonMain/kotlin/okio/internal/Buffer.kt:997 — okio/src/commonMain/kotlin/okio/internal/Buffer.kt:997-1000 | okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1001-1005 | okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1021-1025 | okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1059-1063 | okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1067-1070 | okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1071-1075 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `okio/src/commonMain/kotlin/okio/internal/Buffer.kt:999` calls `toByte` and `okio/src/commonMain/kotlin/okio/internal/Buffer.kt:997` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (68 lines × 2) · ×1
  • Duplicated block (68 lines × 2) okio/src/appleMain/kotlin/okio/SegmentedByteString.kt:35 — okio/src/appleMain/kotlin/okio/SegmentedByteString.kt:35-102 | okio/src/nonAppleMain/kotlin/okio/SegmentedByteString.kt:35-102 — before extracting anything, compare `okio/src/appleMain/kotlin/okio/SegmentedByteString.kt` and `okio/src/nonAppleMain/kotlin/okio/SegmentedByteString.kt` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (68 lines × 3) · ×1
  • Duplicated block (68 lines × 3) okio/src/jsMain/kotlin/okio/FileSystem.kt:31 — okio/src/jsMain/kotlin/okio/FileSystem.kt:31-99 | okio/src/nativeMain/kotlin/okio/FileSystem.kt:32-118 | okio/src/wasmMain/kotlin/okio/FileSystem.kt:33-100 — before extracting anything, compare `okio/src/jsMain/kotlin/okio/FileSystem.kt` and `okio/src/wasmMain/kotlin/okio/FileSystem.kt` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `okio/src/wasmMain/kotlin/okio/FileSystem.kt:29` calls `OptIn` and `okio/src/jsMain/kotlin/okio/FileSystem.kt:26` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×1
  • Duplicated block (31 lines × 2) okio/src/jvmMain/kotlin/okio/Path.kt:78 — okio/src/jvmMain/kotlin/okio/Path.kt:78-129 | okio/src/nonJvmMain/kotlin/okio/Path.kt:70-100 — before extracting anything, compare `okio/src/jvmMain/kotlin/okio/Path.kt` and `okio/src/nonJvmMain/kotlin/okio/Path.kt` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `okio/src/jvmMain/kotlin/okio/Path.kt:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `okio/src/jvmMain/kotlin/okio/Path.kt:77` calls `JvmName` and `okio/src/nonJvmMain/kotlin/okio/Path.kt:68` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) samples/src/jvmMain/kotlin/okio/samples/Hashing.kt:36 — samples/src/jvmMain/kotlin/okio/samples/Hashing.kt:36-40 | samples/src/jvmMain/kotlin/okio/samples/Hashing.kt:44-48 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) samples/src/jvmMain/java/okio/samples/ReadFileLineByLine.java:32 — samples/src/jvmMain/java/okio/samples/ReadFileLineByLine.java:32-44 | samples/src/jvmMain/java/okio/samples/ReadJavaIoFileLineByLine.java:31-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `samples/src/jvmMain/java/okio/samples/ReadFileLineByLine.java:32` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: FileHandle (LCOM4 5) okio/src/commonMain/kotlin/okio/FileHandle.kt:35 — FileHandle's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) okio-nodefilesystem/src/commonMain/kotlin/okio/NodeJsFileSystem.kt:208 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Minor — 26 finding(s)
P10 · Library API & versioning · Implementation type on the public API · ×8
  • Implementation type on the public API okio-testing-support/src/wasmWasiMain/kotlin/okio/internal/preview1/Clockid.kt:1 — 9 public types in `okio.internal.preview1` are marked as implementation by their own namespace, folder or name: `ClockidKt` (okio-testing-support/src/wasmWasiMain/kotlin/okio/internal/preview1/Clockid.kt:1, `internal`), `Preview1ClockKt` (okio-testing-support/src/wasmWasiMain/kotlin/okio/internal/preview1/Preview1Clock.kt:1, `internal`), `Preview1EnvKt` (okio-testing-support/src/wasmWasiMain/kotlin/okio/internal/preview1/Preview1Env.kt:1, `internal`), `FdflagsKt` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Fdflags.kt:1, `internal`), `FiletypeKt` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Filetype.kt:1, `internal`), `LookupFlagsKt` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/LookupFlags.kt:1, `internal`), `OFlagsKt` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/OFlags.kt:1, `internal`), `Preview1Kt` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Preview1.kt:1, `internal`), and 1 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
  • Implementation type on the public API okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/Wasi.kt:1 — 20 public types in `okio.internal` are marked as implementation by their own namespace, folder or name: `WasiKt` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/Wasi.kt:1, `internal`), `-Utf16Kt` (okio/src/commonMain/kotlin/okio/internal/-Utf16.kt:1, `internal`), `-Utf8Kt` (okio/src/commonMain/kotlin/okio/internal/-Utf8.kt:1, `internal`), `BufferKt` (okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1, `internal`), `BufferedSourceKt` (okio/src/commonMain/kotlin/okio/internal/BufferedSource.kt:1, `internal`), `ByteStringKt` (okio/src/commonMain/kotlin/okio/internal/ByteString.kt:1, `internal`), `FileSystemKt` (okio/src/commonMain/kotlin/okio/internal/FileSystem.kt:1, `internal`), `PathKt` (okio/src/commonMain/kotlin/okio/internal/Path.kt:1, `internal`), and 12 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
  • Implementation type on the public API okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:9 — 77 public types in `okio.internal.preview1.Errno` are marked as implementation by their own namespace, folder or name: `success` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:9, `internal`), `toobig` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:12, `internal`), `acces` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:15, `internal`), `addrinuse` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:18, `internal`), `addrnotavail` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:21, `internal`), `afnosupport` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:24, `internal`), `again` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:27, `internal`), `already` (okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/internal/preview1/Errno.kt:30, `internal`), and 69 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
  • Implementation type on the public API okio/src/hashFunctions/kotlin/okio/internal/Hmac.kt:38 — 1 public type in `okio.internal.Hmac` is marked as implementation by its own namespace, folder or name: `Companion` (okio/src/hashFunctions/kotlin/okio/internal/Hmac.kt:38, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
  • Implementation type on the public API okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:187 — 1 public type in `okio.internal.Md5` is marked as implementation by its own namespace, folder or name: `Companion` (okio/src/hashFunctions/kotlin/okio/internal/Md5.kt:187, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
  • Implementation type on the public API okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:240 — 1 public type in `okio.internal.Sha256` is marked as implementation by its own namespace, folder or name: `Companion` (okio/src/hashFunctions/kotlin/okio/internal/Sha256.kt:240, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
  • Implementation type on the public API okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:267 — 1 public type in `okio.internal.Sha512` is marked as implementation by its own namespace, folder or name: `Companion` (okio/src/hashFunctions/kotlin/okio/internal/Sha512.kt:267, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
  • Implementation type on the public API okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt:60 — 2 public types in `okio.internal.DefaultSocket` are marked as implementation by their own namespace, folder or name: `SocketSink` (okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt:60, `internal`), `SocketSource` (okio/src/jvmMain/kotlin/okio/internal/DefaultSocket.kt:122, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
X10 · Duplicated predicate · Duplicated predicate · ×5
  • Duplicated predicate okio/src/nativeMain/kotlin/okio/Deflater.kt:76 — `0 <= sourcePos && sourcePos <= sourceLimit && sourceLimit <= source.size` appears character-identically in 2 files — okio/src/nativeMain/kotlin/okio/Deflater.kt, okio/src/nativeMain/kotlin/okio/Inflater.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate okio/src/nativeMain/kotlin/okio/Deflater.kt:77 — `0 <= targetPos && targetPos <= targetLimit && targetLimit <= target.size` appears character-identically in 2 files — okio/src/nativeMain/kotlin/okio/Deflater.kt, okio/src/nativeMain/kotlin/okio/Inflater.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate okio/src/commonMain/kotlin/okio/internal/Buffer.kt:1404 — `bytesOffset < 0 || bytesOffset + byteCount > bytes.size` appears character-identically in 2 files — okio/src/commonMain/kotlin/okio/internal/Buffer.kt, okio/src/commonMain/kotlin/okio/internal/RealBufferedSource.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate okio/src/mingwX64Main/kotlin/okio/WindowsPosixVariant.kt:115 — `childPath == SELF_DIRECTORY_ENTRY || childPath == PARENT_DIRECTORY_ENTRY` appears character-identically in 2 files — okio/src/mingwX64Main/kotlin/okio/WindowsPosixVariant.kt, okio/src/unixMain/kotlin/okio/UnixPosixVariant.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate okio-nodefilesystem/src/commonMain/kotlin/okio/NodeJsFileSystem.kt:225 — `source.parent == null || !exists(source.parent!!)` appears character-identically in 2 files — okio-nodefilesystem/src/commonMain/kotlin/okio/NodeJsFileSystem.kt, okio/src/unixMain/kotlin/okio/UnixPosixVariant.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D30 · Dependency Vulnerabilities · Low CVE · ×2
  • REDACTED
  • REDACTED
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: okio/src/jvmMain/kotlin/okio/Buffer.kt, okio-wasifilesystem/build.gradle.kts. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 7 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (9 single-owned of 112 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 112 of the 208 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)) (+1 more) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: okio-wasifilesystem/src/wasmWasiMain/kotlin/okio/WasiFileSystem.kt, okio/src/jvmMain/kotlin/okio/AsyncTimeout.kt, okio/src/commonMain/kotlin/okio/Unsigned.kt, okio/src/mingwX64Main/kotlin/okio/WindowsPosixVariant.kt, okio-assetfilesystem/src/main/kotlin/okio/assetfilesystem/AssetFileSystem.kt, okio/src/jvmMain/kotlin/okio/Throttler.kt, okio/src/commonMain/kotlin/okio/internal/FileSystem.kt.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 8 project(s) overshoot their size bounds, lowering Project Cohesion to 7.5/10. The most over is `okio` (19777 LoC, 204 module-visible types across 22 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `okio/jvm/jmh`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:4 — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
PF1 · Benchmark discipline · Benchmarks don't track allocations · ×1
  • Benchmarks don't track allocations okio/jvm/jmh/src/jmh/java/com/squareup/okio/benchmarks/AsyncTimeoutBenchmark.java — A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-722e16f9e89042f5b7839742841c703e/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-722e16f9e89042f5b7839742841c703e/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude kotlin-js-store .5artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .26artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 15 file(s) — `okio/src/appleMain/kotlin/okio/ByteString.kt`, `okio/src/appleMain/kotlin/okio/SegmentedByteString.kt`, `okio/src/commonMain/kotlin/okio/internal/ByteString.kt`, `okio/src/jvmMain/kotlin/okio/ByteString.kt`, `okio/src/jvmMain/kotlin/okio/CipherSource.kt`, … (+10 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1d639-84e3-7bb9-b7ee-8a3c397d8c23 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md