Public report of masesgroup/JNet, published 17 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.4). 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, 17 November 2026, 13:41 UTC · Survey ID cd_c762d29bdddb419e9729f660f568752a

masesgroup/JNet

Measured 17 November 2026, 13:35 UTC, at code version 513db26

First survey, so nothing to compare with yet Boundary Type-Coupling: not measured

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 53.4out of 100 Adequate
CriticalWeakAdequateStrongExemplary

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: 41,905 lines of product code in 24 projects, tests not counted · Estimated rebuild effort: about 1.4 person-years · Weakest lens: Maturity, 46.8

Findings by how serious they are

24 critical 176 serious 144 minor

19 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
17 November 2026, 13:35 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 ▸

45of 45 dimensions measured by tools.
335of 344 findings point to an exact file and line, so you can open each one in the code. The other 9 concern the repository as a whole, such as missing documentation.
45dimensions across 6 lenses, read from 41,905 lines of product code in 24 projects.
Chapters

Executive summary

masesgroup/JNet falls short of our standard for production because the documentation refers to links that don't exist and the project keeps no record of its design decisions. It scores 53.4 out of 100 and is rated Adequate, and two of its 24 critical findings are security problems.

Maturity, at 46.8, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6.2 points. Bringing the documentation in line with the code comes next, worth about 5.9 points. Raising Maturity to 70 would lift the score to about 59.2.

One password or key is open to anyone who can read the repository. One setting leaves the servers or containers unsafe. Replacing the exposed password or key and correcting the unsafe settings would close both risks. The eight loops of parts of the code that depend on each other need breaking by moving the shared parts into a project of their own.

The product code is 41,905 lines, about €200,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.
Maturity 46.8 · counts for 46%Security and Compliance 53.4 · counts for 25%Code Health 56.4 · counts for 14%Architecture 70.7 · counts for 8%Production Readiness 71.0 · counts for 4%Performance 77.1 · counts for 2%

If Maturity rose from 46.8 to 70, the lowest score rated Strong, the score would rise from 53.4 to about 59.2.

Code composition: what the lines of code are
Business logic 43%Supporting code 29%Tests 28%
Rebuild cost: about €200,000 · Estimate
Cost to rebuild€65,000 to €340,000, for 1,083 to 3,545 hours of work, about 1.4 person-years for 1 to 3 engineers
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.7 at a score of 53. 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: 41,905 lines of product code
Comment linesThe estimate prices 40,166 lines. Comment lines count towards the size of 41,905 lines but aren't priced as work.
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.

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 1 No ADRs found finding(s) in ADR Quality — start with JNetCLI.csproj.
Raises the score by about 6.2 points · Low effort · ADR Quality
2
Reconcile the README with reality: CONTRIBUTING.md links to `PULL_REQUEST_TEMPLATE.md`, but `PULL_REQUEST_TEMPLATE.md` does not exist; README.md links to `articles/usage.md#intel-cet-and-jnet`, but `articles/usage.md` does not exist; README.md links to `articles/usageReflector.md`, but `articles/usageReflector.md` does not exist; src/documentation/articles/performance.md names .NET 8, but the projects target .NET 10, 11; src/documentation/articles/support.md names .NET 8, but the projects target .NET 10, 11.
Raises the score by about 5.9 points · Medium effort · Documentation accuracy
3
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 5.2 points · Medium effort · Architecture documentation

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 €200,000 to build again, about 1.4 person-years of work. Its weakest lens is Maturity, at 46.8 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 6.2 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.3 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 372,996 lines over the last 90 days, which is about 1,512,706 lines a year. At that pace, the extra work comes to an estimated 75.6 to 504.2 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

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 JNet JNet JNetCLI JNetCLI JNetCLICore JNetCLICore JNetCLI->JNetCLICore JNetCLICore->JNet JNetPS JNetPS JNetPSCore JNetPSCore JNetPS->JNetPSCore JNetPSCore->JNet JNetReflector JNetReflector jnetAWTApp jnetAWTApp jnetAWTApp->JNet jnetApp jnetApp jnetApp->JNet templatepack templatepack

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.

235 modules, with 1020 dependencies between them. 8 loops run through 81 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 195 more are left out to keep it readable.

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 Java.Lang.Annotation2 Java.Nio3 Java.Time4 Java.Util5 Java.Math6 MASES.JNet.Specific7 Java.Security.Cert8 Java.Security9 Java.Util.Concurrent10 Java.Nio.File.Attribute11 Java.Nio.File12 Java.Nio.Channels13 Java.Net14 Java.Io15 Java.Lang.Reflect16 Java.Lang17 Java.Awt.ImageNs18 Java.Sql19 Java.Text20 Javax.Management21 Javax.Net.Ssl22 Javax.Xml.Namespace23 Javax.Xml.Transform24 Org.W3c.Dom25 Org.Xml.Sax26 Java.Awt.EventNs27 Java.Beans28 Javax.Xml.Stream29 Javax.Swing.Tree30 Javax.Xml.Bind31 Javax.Swing.Event32 Javax.Swing.Plaf33 Javax.Xml.Ws34 Javax.Swing35 Javax.Xml.Ws.Spi36 Javax.Swing.Plaf.Basic37 Javax.Swing.Text38 Javax.Accessibility39 Java.Awt40 Javax.Imageio
1 Java.Lang.Annotation11
2 Java.Nio15
3 Java.Time81336
4 Java.Util4421114578
5 Java.Math119
6 MASES.JNet.Specific718
7 Java.Security.Cert385211744
8 Java.Security221932651
9 Java.Util.Concurrent73121649
10 Java.Nio.File.Attribute211121127
11 Java.Nio.File141212341142
12 Java.Nio.Channels1851024241028
13 Java.Net162632349
14 Java.Io13213250
15 Java.Lang.Reflect51128
16 Java.Lang13210131142410
17 Java.Awt.ImageNs91732
18 Java.Sql3271012104277
19 Java.Text201435
20 Javax.Management41323112575
21 Javax.Net.Ssl112210187230
22 Javax.Xml.Namespace213
23 Javax.Xml.Transform3114
24 Org.W3c.Dom41
25 Org.Xml.Sax2221
26 Java.Awt.EventNs19267129
27 Java.Beans4634639112
28 Javax.Xml.Stream1422102
29 Javax.Swing.Tree54623101112
30 Javax.Xml.Bind4616183087768
31 Javax.Swing.Event35241141213765
32 Javax.Swing.Plaf45121184127
33 Javax.Xml.Ws26103611461533
34 Javax.Swing2712230110244013859321444189
35 Javax.Xml.Ws.Spi23121821118
36 Javax.Swing.Plaf.Basic141731151213960662
37 Javax.Swing.Text122354651231201649
38 Javax.Accessibility322021520
39 Java.Awt2013348138568515
40 Javax.Imageio8143156
Uses a module listed above itPart of a loopThe module itself
1 Java.Lang.Annotation2 Java.Nio3 Java.Time4 Java.Util5 Java.Math6 MASES.JNet.Specific7 Java.Security.Cert8 Java.Security9 Java.Util.Concurrent10 Java.Nio.File.Attribute11 Java.Nio.File12 Java.Nio.Channels13 Java.Net14 Java.Io15 Java.Lang.Reflect16 Java.Lang17 Java.Awt.ImageNs18 Java.Sql19 Java.Text20 Javax.Management21 Javax.Net.Ssl22 Javax.Xml.Namespace23 Javax.Xml.Transform24 Org.W3c.Dom25 Org.Xml.Sax26 Java.Awt.EventNs27 Java.Beans28 Javax.Xml.Stream29 Javax.Swing.Tree30 Javax.Xml.Bind31 Javax.Swing.Event32 Javax.Swing.Plaf33 Javax.Xml.Ws34 Javax.Swing35 Javax.Xml.Ws.Spi36 Javax.Swing.Plaf.Basic37 Javax.Swing.Text38 Javax.Accessibility39 Java.Awt40 Javax.ImageioJava.Lang.Annotation1Java.Nio2Java.Time3Java.Util4Java.Math5MASES.JNet.Specific6Java.Security.Cert7Java.Security8Java.Util.Concurrent9Java.Nio.File.Attribute10Java.Nio.File11Java.Nio.Channels12Java.Net13Java.Io14Java.Lang.Reflect15Java.Lang16Java.Awt.ImageNs17Java.Sql18Java.Text19Javax.Management20Javax.Net.Ssl21Javax.Xml.Namespace22Javax.Xml.Transform23Org.W3c.Dom24Org.Xml.Sax25Java.Awt.EventNs26Java.Beans27Javax.Xml.Stream28Javax.Swing.Tree29Javax.Xml.Bind30Javax.Swing.Event31Javax.Swing.Plaf32Javax.Xml.Ws33Javax.Swing34Javax.Xml.Ws.Spi35Javax.Swing.Plaf.Basic36Javax.Swing.Text37Javax.Accessibility38Java.Awt39Javax.Imageio401115813364421114578119718385211744221932651731216492111211271412123411421851024241028162632349132132505112813210131142410917323271012104277201435413231125751122101872302133114412221192671294634639112142210254623101112461618308776835241141213765451211841272610361146153327122301102440138593214441892312182111814173115121396066212235465123120164932202152020133481385685158143156+195 more modules (most-connected shown)

At a glance — Code Health · 56.4 · Adequate · gated by X5 ·

At a glance — Architecture · 70.7 · Adequate · gated by AX2 ·

At a glance — Maturity · 46.8 · Weak · gated by M2, M4 ·

At a glance — Readiness · 71.0 · Strong ·

At a glance — Security · 53.4 · Adequate · gated by C1 ·

At a glance — Performance · 77.1 · Strong ·

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 Failures16Medium
A02:2025 — Security Misconfiguration4High / Critical
A07:2025 — Authentication Failures1High / Critical

Roadmap

Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with JNetCLI.csproj; Reconcile the README with reality: CONTRIBUTING.md links to `PULL_REQUEST_TEMPLATE.md`, but `PULL_REQUEST_TEMPLATE.md` does not exist; README.md links to `articles/usage.md#intel-cet-and-jnet`, but `articles/usage.md` does not exist; README.md links to `articles/usageReflector.md`, but `articles/usageReflector.md` does not exist; src/documentation/articles/performance.md names .NET 8, but the projects target .NET 10, 11; src/documentation/articles/support.md names .NET 8, but the projects target .NET 10, 11; 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.

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

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with JNetCLI.csproj.+6.2 ptsLowADR Quality
Reconcile the README with reality: CONTRIBUTING.md links to `PULL_REQUEST_TEMPLATE.md`, but `PULL_REQUEST_TEMPLATE.md` does not exist; README.md links to `articles/usage.md#intel-cet-and-jnet`, but `articles/usage.md` does not exist; README.md links to `articles/usageReflector.md`, but `articles/usageReflector.md` does not exist; src/documentation/articles/performance.md names .NET 8, but the projects target .NET 10, 11; src/documentation/articles/support.md names .NET 8, but the projects target .NET 10, 11.+5.9 ptsMediumDocumentation accuracy
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.+5.2 ptsMediumArchitecture documentation
Resolve the 2 BlanketAnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (2).+2.3 ptsLowExplicit Debt
Resolve the 4 EmptyCatchBlock finding(s) in Explicit Debt — start with JNetReflectorHelper.cs (4).+2.3 ptsLowExplicit Debt
Resolve the 7 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (7).+2.3 ptsLowExplicit Debt
Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.+2.6 ptsMediumData Protection
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).+2.5 ptsMediumNullable reference types

File quality

Per-file score 0–10 — a quality signature. Of 45 files carrying findings, judged against the Production bar: 4% slop · 67% mixed · 29% near-clean.

FileScoreBandWorst signal
src/net/JNetReflector/JNetReflectorHelper.cs1.0SlopExplicit Debt: EmptyCatchBlock
REDACTED3.4SlopIaC & Container Security: High IaC: REDACTED
src/net/JNet/Generated/.editorconfig5.3MixedExplicit Debt: BlanketAnalyzerSeverityNone
src/net/JNet/Developed/.editorconfig5.8MixedExplicit Debt: BlanketAnalyzerSeverityNone
src/net/JNetReflector/InternalExtensions.cs6.0MixedExplicit Debt: CommentedOutCode
src/net/JNetReflector/InternalMethods.cs7.0MixedCyclomatic Complexity: ReflectionUtils.AnalyzeMethods (cyclomatic 253)
src/net/JNetReflector/JNetReflectorCore.cs7.2MixedCyclomatic Complexity: JNetReflectorCore.ProcessCommandLine (cyclomatic 74)
src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs7.2MixedCode Duplication: Edited copy of a member (28 corresponding lines)
REDACTED7.2MixedSecret Scanning: Leaked secret: REDACTED
src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java7.4MixedCyclomatic Complexity: JNetHelper.listFromPrimitiveArray (cyclomatic 19)
src/net/Common/Common.props7.6MixedExplicit Debt: NoWarnInCsproj
src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs7.8MixedCyclomatic Complexity: ParserAdapter.ListenerShallManageEventHandlers (cyclomatic 23)
src/net/JNet/Specific/CLI/JNetCLICoreHelper.cs7.8MixedCyclomatic Complexity: JNetCLICoreHelper.ProcessCLIParsedArgs (cyclomatic 21)
src/net/JNetCLICore/ProgramBase.cs7.8MixedCyclomatic Complexity: ProgramBase.Start (cyclomatic 20)
src/net/JNet/Generated/Org/Xml/Sax/Helpers/XMLReaderAdapter.cs7.8MixedCyclomatic Complexity: XMLReaderAdapter.ListenerShallManageEventHandlers (cyclomatic 19)
src/net/JNet/JNetCoreBase.cs7.8MixedCognitive Complexity: JNetCoreBase.Launch (cognitive 25)
src/net/JNetPS/Cmdlet/JMX/NewMBeanProxyCmdletCommand.cs7.8MixedCode Duplication: Duplicated block (33 lines × 2)
src/net/JNetPS/Cmdlet/JMX/InvokeQueryAnySubStringCmdletCommand.cs7.8MixedCode Duplication: Duplicated block (15 lines × 3)
REDACTED7.9MixedSupply-chain Provenance & Signing: REDACTED
REDACTED7.9MixedSupply-chain Provenance & Signing: REDACTED

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 — 24

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 — 176

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 — 144

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

Could not be resolved — 19

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 45 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, 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 — 45 dimensions across the health lenses
D1D2D3D4D5D6D13D14D15D17D19D20D24D26D29D30D31D34D35D36D43D44AX10AX2AX3AX5AX6AX9C1C4C5GD1M1M2M3M4P1P10P3P4P6PF1PF3X20X5

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, 335 of 344 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 · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1e9b8-2136-7006-b8bd-38a77f08e5f9.

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: this repository's production source spans .cs, .java, and our analyzer cannot run the .java test suite(s) — so no coverage was collected for the repository as a whole. The .NET half may well have built and run; what is missing is a coverage figure that covers the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
  • 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. Test source is present (.java) and this repository declares a JVM test suite (tests/jvm/jnettest, Maven), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
  • D16 Bus Factor — 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. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 958 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D17 Explicit Debt — 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. The 20 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .java (13,903 lines, 56% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
  • 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — evaluation did not complete — Naming Consistency not included (check did not complete) — excluded from the score.
  • D22 Internal API Consistency — 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D23 Boundary Type-Coupling — 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. Large codebase (638,261 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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 — 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 source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D28 Secrets (history) — 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. `gitleaks` TIMED OUT after 266.8s against a 266.8s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. Nothing about this repository is asserted by the absence of a result; the budget is ours to raise, and raising it is our backlog item, not an action for this repository's owner.
  • D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
  • AX6 Interface segregation — 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. 31 further occurrence(s) are not listed individually; the score already reflects all 71.
  • 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • P10 Library API & versioning — 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. 88 further occurrence(s) are not listed individually; the score already reflects all 128.
  • 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.
  • X1 Async correctness — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X10 Duplicated predicate — 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. 35 further occurrence(s) are not listed individually; the score already reflects all 75.
  • X12 Unreachable branch — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X13 Undrained process stream — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X16 Unfloored truncation loop — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X18 Disposal-pattern correctness — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X2 Cancellation propagation — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X27 Collection changed while being enumerated — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X28 Index access outside its own emptiness guard — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X29 Per-element action decided by a fixed element — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X3 Exception handling — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X30 Support guard that admits what it rejects — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X5 Nullable reference types — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/net/templates/templatepack.csproj, src/net/JNet/JNet.csproj, src/net/JNetCLI/JNetCLI.csproj, src/net/JNetPS/JNetPS.csproj, src/net/JNetPSCore/JNetPSCore.csproj and 1 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.

Repo exclusion declarations: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

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.
  • 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.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • 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.
  • 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.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • 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.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
  • C5 Data-Subject Rights: This control is scored from in-repo evidence only — absence of evidence here means the scan found no in-repo trace, not that the control does not exist.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • 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 Complexity5.2 / 10Adequate✓ 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 5.2 / 10 · rule-coverage 100% · ceiling Prevented

23 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ReflectionUtils.AnalyzeMethods at 253. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being JNetReflectorExtensions.IsNetNativeType at 22 — they are counted neither in the figure above nor in this dimension's score.

ReflectionUtils.AnalyzeMethods (cyclomatic 253)src/net/JNetReflector/InternalMethods.cs:1303
JNetReflectorCore.ProcessCommandLine (cyclomatic 74)src/net/JNetReflector/JNetReflectorCore.cs:603
ReflectionUtils.AnalyzeJavaMethods (cyclomatic 70)src/net/JNetReflector/InternalMethods.cs:2222
JNetReflectorExtensions.ToNetType (cyclomatic 67)src/net/JNetReflector/InternalExtensions.cs:2042
ReflectionUtils.AnalyzeConstructors (cyclomatic 53)src/net/JNetReflector/InternalMethods.cs:931

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

What to do

  1. Bring the 1 body over 120 down to 120 or less in Cyclomatic Complexity — start with ReflectionUtils.AnalyzeMethods (cyclomatic 253). — Refactoring it lifts Cyclomatic Complexity from 5.2 to about 6.0/10.

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

D2 · Cognitive Complexity4.0 / 10Weak✓ 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 4.0 / 10 · rule-coverage 100% · ceiling Prevented

35 method(s) exceeded the cognitive complexity threshold of 15; the worst was ReflectionUtils.AnalyzeMethods at 671.

ReflectionUtils.AnalyzeMethods (cognitive 671)src/net/JNetReflector/InternalMethods.cs:1303
JNetReflectorExtensions.GetGenerics (cognitive 168)src/net/JNetReflector/InternalExtensions.cs:964
ReflectionUtils.AnalyzeJavaMethods (cognitive 151)src/net/JNetReflector/InternalMethods.cs:2222
JNetReflectorCore.ProcessCommandLine (cognitive 128)src/net/JNetReflector/JNetReflectorCore.cs:603
ReflectionUtils.AnalyzeConstructors (cognitive 123)src/net/JNetReflector/InternalMethods.cs:931

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

What to do

  1. Bring the 1 body over 240 down to 240 or less in Cognitive Complexity — start with ReflectionUtils.AnalyzeMethods (cognitive 671). — Refactoring it lifts Cognitive Complexity from 4.0 to about 5.1/10.

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

D3 · God Classes10.0 / 10Stronggated by 9 serious findings✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

9 god class(es) detected.

MethodTooLong: ReflectionUtils.AnalyzeMethods · ×6src/net/JNetReflector/InternalMethods.cs:1303
FileTooLong: JNetReflector/InternalMethods.cs · ×2src/net/JNetReflector/InternalMethods.cs
ClassTooLong: ReflectionUtilssrc/net/JNetReflector/InternalMethods.cs

What to do

  1. Resolve the 6 MethodTooLong finding(s) in God Classes — start with InternalMethods.cs (4), JNetReflectorCore.cs, InternalExtensions.cs. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 2 FileTooLong finding(s) in God Classes — start with InternalMethods.cs, JNetReflectorCore.cs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 ClassTooLong finding(s) in God Classes — start with InternalMethods.cs. — 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.9 / 10Stronggated by 50 serious findings✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

40 duplicated block group(s) detected. 0.2 % of the production lines (1,315 of 638,261) are in a reported copy. A further 12 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (7 lines × 2) · ×4src/net/JNetReflector/InternalMethods.cs:1197
Duplicated block (6 lines × 2) · ×4src/net/JNetReflector/InternalMethods.cs:1868
Duplicated block (15 lines × 2) · ×3src/net/JNetReflector/InternalExtensions.cs:2296
Duplicated block (11 lines × 2) · ×3src/net/JNetReflector/InternalExtensions.cs:984
Duplicated block (8 lines × 2) · ×3src/net/JNetReflector/InternalMethods.cs:1363

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

What to do

  1. Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with InternalMethods.cs (3), JNetReflectorHelper.cs. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 4 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with InternalMethods.cs (4). — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 3 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with InternalExtensions.cs, InvokeQueryAndCmdletCommand.cs, InternalMethods.cs. — One of this dimension's main actionable groups (3 warning-level).

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

D5 · Coupling9.7 / 10Stronggated by 1 serious finding✓ 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 9.7 / 10 · rule-coverage 100% · ceiling Prevented

24 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

Off the main sequence: JNet(net462)src/net/JNet/JNet.csproj:1

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling — start with JNet.csproj. — One of this dimension's main actionable groups (1 warning-level).

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

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 105 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D13 · Secret Scanning5.0 / 10Adequate✓ Tool-verified

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 5.0 / 10 · rule-coverage 100% · ceiling Prevented

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 130 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 9 direct `PackageReference`(s), and 117 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.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.

D17 · Explicit Debt9.9 / 10Adequategated by 14 critical 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.9 / 10 · rule-coverage 100% · ceiling Prevented

20 deducted debt markers + 5 dead symbols across 638261 LoC in the .NET projects (0.0/KLoC) → score 9.9. Measured on the .NET source only: .java (56% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).

AnalyzerSeverityNone · ×7src/net/JNet/Developed/.editorconfig:4
EmptyCatchBlock · ×4src/net/JNetReflector/JNetReflectorHelper.cs:217
BlanketAnalyzerSeverityNone · ×2src/net/JNet/Developed/.editorconfig:3
NoWarnInCsprojsrc/net/Common/Common.props:21
Dead code: IAsyncEnumerator<TObject>.Current · ×5src/net/JNet/Specific/AsyncEnumerable.cs:72

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

What to do

  1. Resolve the 7 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (7). — One of this dimension's main actionable groups (7 issue-level).
  2. Resolve the 4 EmptyCatchBlock finding(s) in Explicit Debt — start with JNetReflectorHelper.cs (4). — One of this dimension's main actionable groups (4 issue-level).
  3. Resolve the 2 BlanketAnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (2). — One of this dimension's main actionable groups (2 issue-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

2 of 2 documentation facets pass in full. 21 document(s) read across 9 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

No architecture decision records were found.

No ADRs foundsrc/net/JNetCLI/JNetCLI.csproj:5

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with JNetCLI.csproj. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment Value10.0 10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

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

0 of 445 judged comments only repeat the code they sit on (0.0 %). 2 comment(s) in another language or script were not judged.

doc comments repeat the names · ×3src/net/JNet/Developed/Java/Awt/Container.cs:29

✓ On the Gold path — maintain.

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

D26 · Project Cohesion7.8 / 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.8 / 10 · rule-coverage 100% · ceiling Documented

1 of 9 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionsrc/net/JNet/JNet.csproj:1

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with JNet.csproj. — 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.

D29 · Static Analysis (SAST)10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Documented

semgrep found no security issues.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (osv). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D31 · IaC & Container Security9.4 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

4 finding(s): 0 critical, 1 high, 2 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 22 of the 64 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.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 & Signing7.5 / 10Strong✓ 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 7.5 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 10 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (10 warning-level).
  2. Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-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 9 platform declaration(s) and 4 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.

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.

AX2 · Stateful singletons1.0 / 10Critical✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

  • `JNetCLICoreHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_mainClassToRun, _classToRun, _Interactive, _RunCommand, _NoLogo, _Script; e.g. `_mainClassToRun` at line 249). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/net/JNet/Specific/CLI/JNetCLICoreHelper.cs:32
  • `JNetReflectorExtensions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_CurrentJavadocBaseUrl, _CurrentJavadocVersion, _CurrentNoModule; e.g. `_CurrentJavadocBaseUrl` at line 50). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/net/JNetReflector/InternalExtensions.cs:38
  • `ReflectionUtils` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (TraceReportHandler, Level, namespaces, classes, JarOrModuleName, CancellationTokenSource; e.g. `TraceReportHandler` at line 56). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/net/JNetReflector/InternalMethods.cs:36
  • `JNetReflectorCore` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_CopyrightFile, _JavaPLocationPath, _ConfigurationFromFile, _ClassesToAnalyze, _OriginRootPath, _JarsToAddInClassPath; e.g. `_CopyrightFile` at line 607). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/net/JNetReflector/JNetReflectorCore.cs:34
  • `JNetReflectorCore` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (CurrentClassPath; e.g. `CurrentClassPath` at line 913). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/net/JNetReflector/JNetReflectorCore.cs:905
  • `JNetPSHelperExtensions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (processExited, cancelKeyRaised; e.g. `processExited` at line 127). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/net/JNetPSCore/JNetPSHelper.cs:37

What to do

  • A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ 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 namespaces Java.Applet ↔ Java.Awt ↔ Java.Awt.ColorNs ↔ Java.Awt.Datatransfer ↔ Java.Awt.Dnd ↔ Java.Awt.Dnd.Peer ↔ Java.Awt.EventNs ↔ Java.Awt.FontNs ↔ Java.Awt.Geom ↔ Java.Awt.Im ↔ Java.Awt.ImageNs ↔ Java.Awt.ImageNs.Renderable ↔ Java.Awt.Print ↔ Java.Beans ↔ Java.Beans.Beancontext ↔ Java.Io ↔ Java.Lang ↔ Java.Lang.Annotation ↔ Java.Lang.Reflect ↔ Java.Math ↔ Java.Net ↔ Java.Nio ↔ Java.Nio.Channels ↔ Java.Nio.Channels.Spi ↔ Java.Nio.Charset ↔ Java.Nio.File ↔ Java.Nio.File.Attribute ↔ Java.Nio.File.Spi ↔ Java.Security ↔ Java.Security.Cert ↔ Java.Text ↔ Java.Time ↔ Java.Time.Chrono ↔ Java.Time.Format ↔ Java.Time.Temporal ↔ Java.Time.Zone ↔ Java.Util ↔ Java.Util.Concurrent ↔ Java.Util.Jar ↔ Java.Util.Regex ↔ Java.Util.Stream ↔ Java.Util.Zip ↔ Javax.Accessibility ↔ Javax.Print ↔ Javax.Print.Attribute ↔ Javax.Print.Event ↔ Javax.Security.Auth ↔ Javax.Security.Auth.Callback ↔ Javax.Security.Auth.X500 ↔ Javax.Swing ↔ Javax.Swing.Border ↔ Javax.Swing.Colorchooser ↔ Javax.Swing.Event ↔ Javax.Swing.Filechooser ↔ Javax.Swing.Plaf ↔ Javax.Swing.Plaf.Basic ↔ Javax.Swing.Table ↔ Javax.Swing.Text ↔ Javax.Swing.Tree ↔ Javax.Swing.Undo ↔ MASES.JNet.Specific ↔ MASES.JNet.Specific.Extensions ↔ Org.Xml.Sax ↔ Org.Xml.Sax.Helpers depend on each other. The lightest dependency in the cycle is Java.Awt → Java.Awt.ColorNs (Java.Awt.Color → Java.Awt.ColorNs.ColorSpace, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Java/Awt/Color.cs:32
  • The namespaces Javax.Management ↔ Javax.Management.Loading depend on each other. The lightest dependency in the cycle is Javax.Management → Javax.Management.Loading (Javax.Management.IMBeanServer → Javax.Management.Loading.ClassLoaderRepository, 3 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Management/MBeanServer.cs:66
  • The namespaces Javax.Lang.Model.Element ↔ Javax.Lang.Model.Type depend on each other. The lightest dependency in the cycle is Javax.Lang.Model.Type → Javax.Lang.Model.Element (Javax.Lang.Model.Type.DeclaredType → Javax.Lang.Model.Element.Element, 4 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Lang/Model/Type/DeclaredType.cs:32
  • The namespaces Javax.Imageio ↔ Javax.Imageio.Event ↔ Javax.Imageio.Metadata ↔ Javax.Imageio.Spi depend on each other. The lightest dependency in the cycle is Javax.Imageio.Spi → Javax.Imageio.Metadata (Javax.Imageio.Spi.ImageReaderWriterSpi → Javax.Imageio.Metadata.IIOMetadataFormat, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Imageio/Spi/ImageReaderWriterSpi.cs:32
  • The namespaces Javax.Sql.Rowset ↔ Javax.Sql.Rowset.Spi depend on each other. The lightest dependency in the cycle is Javax.Sql.Rowset → Javax.Sql.Rowset.Spi (Javax.Sql.Rowset.CachedRowSet → Javax.Sql.Rowset.Spi.SyncProvider, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Sql/Rowset/CachedRowSet.cs:32
  • The namespaces Javax.Xml.Stream ↔ Javax.Xml.Stream.Events ↔ Javax.Xml.Stream.Util depend on each other. The lightest dependency in the cycle is Javax.Xml.Stream → Javax.Xml.Stream.Util (Javax.Xml.Stream.IXMLEventWriter → Javax.Xml.Stream.Util.IXMLEventConsumer, 3 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Xml/Stream/XMLEventWriter.cs:66
  • The namespaces Javax.Xml.Crypto ↔ Javax.Xml.Crypto.Dsig.Keyinfo depend on each other. The lightest dependency in the cycle is Javax.Xml.Crypto → Javax.Xml.Crypto.Dsig.Keyinfo (Javax.Xml.Crypto.KeySelector → Javax.Xml.Crypto.Dsig.Keyinfo.KeyInfo, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Xml/Crypto/KeySelector.cs:32
  • The namespaces Javax.Xml.Ws ↔ Javax.Xml.Ws.Handler depend on each other. The lightest dependency in the cycle is Javax.Xml.Ws.Handler → Javax.Xml.Ws (Javax.Xml.Ws.Handler.ILogicalMessageContext → Javax.Xml.Ws.LogicalMessage, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Xml/Ws/Handler/LogicalMessageContext.cs:66

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation9.7 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `IInputMethod` declares 16 members: `ControlObject`, `Locale`, `IsCompositionEnabled`, `SetLocale`, `Activate`, `Deactivate`, `DispatchEvent`, `DisposeJVM`, `EndComposition`, `HideWindows`, `NotifyClientWindowChange`, `Reconvert`, `RemoveNotify`, `SetCharacterSubsets`, `SetCompositionEnabled`, `SetInputMethodContext`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Awt/Im/Spi/InputMethod.cs:66
  • `IRenderedImage` declares 21 members: `ColorModel`, `Data`, `Height`, `MinTileX`, `MinTileY`, `MinX`, `MinY`, `NumXTiles`, `NumYTiles`, `PropertyNames`, `SampleModel`, `Sources`, `TileGridXOffset`, `TileGridYOffset`, `TileHeight`, `TileWidth`, `Width`, `GetData`, `GetTile`, `CopyData`, `GetProperty`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Awt/ImageNs/RenderedImage.cs:66
  • `IMemoryPoolMXBean` declares 16 members: `CollectionUsage`, `CollectionUsageThreshold`, `CollectionUsageThresholdCount`, `MemoryManagerNames`, `Name`, `PeakUsage`, `Type`, `Usage`, `UsageThreshold`, `UsageThresholdCount`, `IsCollectionUsageThresholdExceeded`, `IsCollectionUsageThresholdSupported`, `IsUsageThresholdExceeded`, `IsUsageThresholdSupported`, `IsValid`, `ResetPeakUsage`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Lang/Management/MemoryPoolMXBean.cs:66
  • `IRuntimeMXBean` declares 16 members: `BootClassPath`, `ClassPath`, `InputArguments`, `LibraryPath`, `ManagementSpecVersion`, `Name`, `SpecName`, `SpecVendor`, `SpecVersion`, `StartTime`, `SystemProperties`, `Uptime`, `VmName`, `VmVendor`, `VmVersion`, `IsBootClassPathSupported`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Lang/Management/RuntimeMXBean.cs:66
  • `IThreadMXBean` declares 27 members: `AllThreadIds`, `CurrentThreadCpuTime`, `CurrentThreadUserTime`, `DaemonThreadCount`, `PeakThreadCount`, `ThreadCount`, `TotalStartedThreadCount`, `IsCurrentThreadCpuTimeSupported`, `IsObjectMonitorUsageSupported`, `IsSynchronizerUsageSupported`, `IsThreadContentionMonitoringEnabled`, `IsThreadContentionMonitoringSupported`, `IsThreadCpuTimeEnabled`, `IsThreadCpuTimeSupported`, `GetThreadInfo`, `GetThreadInfo`, `DumpAllThreads`, `GetThreadInfo`, `GetThreadInfo`, `GetThreadInfo`, `GetThreadCpuTime`, `GetThreadUserTime`, `FindDeadlockedThreads`, `FindMonitorDeadlockedThreads`, `ResetPeakThreadCount`, `SetThreadContentionMonitoringEnabled`, `SetThreadCpuTimeEnabled`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 27 declarations carry 23 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 23 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Lang/Management/ThreadMXBean.cs:66
  • `IPath` declares 27 members: `FileName`, `FileSystem`, `NameCount`, `Parent`, `Root`, `EndsWith`, `EndsWith`, `IsAbsolute`, `StartsWith`, `StartsWith`, `CompareTo`, `ToFile`, `ToUri`, `GetName`, `Normalize`, `Relativize`, `Resolve`, `Resolve`, `ResolveSibling`, `ResolveSibling`, `Subpath`, `ToAbsolutePath`, `ToRealPath`, `Register`, `Register`, `Iterator`, `CompareTo`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 27 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Nio/File/Path.cs:66
  • `IChronoLocalDate` declares 25 members: `Chronology`, `Era`, `LengthOfMonth`, `Until`, `Until`, `Query`, `IsAfter`, `IsBefore`, `IsEqual`, `IsLeapYear`, `IsSupported`, `IsSupported`, `CompareTo`, `CompareTo`, `LengthOfYear`, `Format`, `AtTime`, `AdjustInto`, `Minus`, `Minus`, `Plus`, `Plus`, `With`, `With`, `ToEpochDay`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 25 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Time/Chrono/ChronoLocalDate.cs:66
  • `IChronology` declares 24 members: `CalendarType`, `Id`, `IsLeapYear`, `CompareTo`, `ProlepticYear`, `Date`, `Date`, `DateEpochDay`, `DateYearDay`, `ResolveDate`, `EraOf`, `Range`, `Eras`, `CompareTo`, `GetDisplayName`, `Date`, `DateNow`, `DateNow`, `DateNow`, `DateYearDay`, `LocalDateTime`, `Period`, `ZonedDateTime`, `ZonedDateTime`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 24 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Time/Chrono/Chronology.cs:66
  • `ICollection<E>` declares 17 members: `ToArray`, `Add`, `AddAll`, `Contains`, `ContainsAll`, `IsEmpty`, `Remove`, `RemoveAll`, `RetainAll`, `Size`, `ToArray`, `Iterator`, `Clear`, `RemoveIf`, `Spliterator`, `ParallelStream`, `Stream`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 17 declarations carry 16 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 16 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Collection.cs:276
  • `IDeque<E>` declares 27 members: `First`, `Last`, `Add`, `Contains`, `Offer`, `OfferFirst`, `OfferLast`, `Remove`, `RemoveFirstOccurrence`, `RemoveLastOccurrence`, `Element`, `Peek`, `PeekFirst`, `PeekLast`, `Poll`, `PollFirst`, `PollLast`, `Pop`, `Remove`, `RemoveFirst`, `RemoveLast`, `Size`, `DescendingIterator`, `Iterator`, `AddFirst`, `AddLast`, `Push`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 27 declarations carry 26 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 26 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Deque.cs:354
  • `IList<E>` declares 26 members: `ToArray`, `Add`, `AddAll`, `AddAll`, `Contains`, `ContainsAll`, `IsEmpty`, `Remove`, `RemoveAll`, `RetainAll`, `Get`, `Remove`, `Set`, `IndexOf`, `LastIndexOf`, `Size`, `ToArray`, `Iterator`, `SubList`, `ListIterator`, `ListIterator`, `Add`, `Clear`, `Spliterator`, `ReplaceAll`, `Sort`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 26 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/List.cs:359
  • `IMap<K, V>` declares 23 members: `ContainsKey`, `ContainsValue`, `IsEmpty`, `Size`, `Values`, `EntrySet`, `KeySet`, `Get`, `Put`, `Remove`, `Clear`, `PutAll`, `Remove`, `Replace`, `Compute`, `ComputeIfAbsent`, `ComputeIfPresent`, `GetOrDefault`, `Merge`, `PutIfAbsent`, `Replace`, `ForEach`, `ReplaceAll`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 23 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Map.cs:594
  • `INavigableMap<K, V>` declares 21 members: `CeilingEntry`, `FirstEntry`, `FloorEntry`, `HigherEntry`, `LastEntry`, `LowerEntry`, `PollFirstEntry`, `PollLastEntry`, `DescendingMap`, `HeadMap`, `SubMap`, `TailMap`, `DescendingKeySet`, `NavigableKeySet`, `HeadMap`, `SubMap`, `TailMap`, `CeilingKey`, `FloorKey`, `HigherKey`, `LowerKey`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 21 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/NavigableMap.cs:321
  • `IBlockingDeque<E>` declares 29 members: `Add`, `Contains`, `Offer`, `Offer`, `OfferFirst`, `OfferFirst`, `OfferLast`, `OfferLast`, `Remove`, `RemoveFirstOccurrence`, `RemoveLastOccurrence`, `Element`, `Peek`, `Poll`, `Poll`, `PollFirst`, `PollLast`, `Remove`, `Take`, `TakeFirst`, `TakeLast`, `Size`, `Iterator`, `AddFirst`, `AddLast`, `Push`, `Put`, `PutFirst`, `PutLast`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 29 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Concurrent/BlockingDeque.cs:407
  • `ICompletionStage<T>` declares 38 members: `ThenCombine`, `ThenCombineAsync`, `ThenCombineAsync`, `ThenAcceptBoth`, `ThenAcceptBothAsync`, `ThenAcceptBothAsync`, `ApplyToEither`, `ApplyToEitherAsync`, `ApplyToEitherAsync`, `Handle`, `HandleAsync`, `HandleAsync`, `ThenApply`, `ThenApplyAsync`, `ThenApplyAsync`, `ThenCompose`, `ThenComposeAsync`, `ThenComposeAsync`, `ToCompletableFuture`, `AcceptEither`, `AcceptEitherAsync`, `AcceptEitherAsync`, `RunAfterBoth`, `RunAfterBothAsync`, `RunAfterBothAsync`, `RunAfterEither`, `RunAfterEitherAsync`, `RunAfterEitherAsync`, `ThenAccept`, `ThenAcceptAsync`, `ThenAcceptAsync`, `ThenRun`, `ThenRunAsync`, `ThenRunAsync`, `Exceptionally`, `WhenComplete`, `WhenCompleteAsync`, `WhenCompleteAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 38 declarations carry 26 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 26 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Concurrent/CompletionStage.cs:503
  • `IDoubleStream` declares 33 members: `Collect`, `MapToObj`, `AllMatch`, `AnyMatch`, `NoneMatch`, `Reduce`, `Sum`, `ToArray`, `SummaryStatistics`, `Average`, `FindAny`, `FindFirst`, `Max`, `Min`, `Reduce`, `Distinct`, `Filter`, `FlatMap`, `Limit`, `Map`, `Peek`, `Skip`, `Sorted`, `MapToInt`, `MapToLong`, `Boxed`, `Count`, `ForEach`, `ForEachOrdered`, `Iterator`, `Spliterator`, `Parallel`, `Sequential`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 33 declarations carry 32 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 32 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Stream/DoubleStream.cs:66
  • `IIntStream` declares 35 members: `Collect`, `MapToObj`, `AllMatch`, `AnyMatch`, `NoneMatch`, `Reduce`, `Sum`, `ToArray`, `SummaryStatistics`, `Average`, `FindAny`, `FindFirst`, `Max`, `Min`, `Reduce`, `AsDoubleStream`, `MapToDouble`, `Distinct`, `Filter`, `FlatMap`, `Limit`, `Map`, `Peek`, `Skip`, `Sorted`, `AsLongStream`, `MapToLong`, `Boxed`, `Count`, `ForEach`, `ForEachOrdered`, `Iterator`, `Spliterator`, `Parallel`, `Sequential`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 35 declarations carry 34 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 34 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Stream/IntStream.cs:66
  • `ILongStream` declares 34 members: `Collect`, `MapToObj`, `AllMatch`, `AnyMatch`, `NoneMatch`, `SummaryStatistics`, `Average`, `FindAny`, `FindFirst`, `Max`, `Min`, `Reduce`, `AsDoubleStream`, `MapToDouble`, `MapToInt`, `Distinct`, `Filter`, `FlatMap`, `Limit`, `Map`, `Peek`, `Skip`, `Sorted`, `Boxed`, `Count`, `Reduce`, `Sum`, `ToArray`, `ForEach`, `ForEachOrdered`, `Iterator`, `Spliterator`, `Parallel`, `Sequential`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 34 declarations carry 33 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 33 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Stream/LongStream.cs:66
  • `IStream<T>` declares 32 members: `ToArray`, `Collect`, `FlatMap`, `Map`, `Collect`, `Reduce`, `AllMatch`, `AnyMatch`, `NoneMatch`, `ToArray`, `FindAny`, `FindFirst`, `Max`, `Min`, `Reduce`, `FlatMapToDouble`, `MapToDouble`, `FlatMapToInt`, `MapToInt`, `FlatMapToLong`, `MapToLong`, `Distinct`, `Filter`, `Limit`, `Peek`, `Skip`, `Sorted`, `Sorted`, `Count`, `Reduce`, `ForEach`, `ForEachOrdered`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 32 declarations carry 27 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 27 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Stream/Stream.cs:472
  • `ICallableStatement` declares 121 members: `GetObject`, `GetObject`, `GetBoolean`, `GetBoolean`, `WasNull`, `GetByte`, `GetByte`, `GetBytes`, `GetBytes`, `GetDouble`, `GetDouble`, `GetFloat`, `GetFloat`, `GetInt`, `GetInt`, `GetCharacterStream`, `GetCharacterStream`, `GetNCharacterStream`, `GetNCharacterStream`, `GetObject`, `GetObject`, `GetObject`, `GetObject`, `GetNString`, `GetNString`, `GetString`, `GetString`, `GetBigDecimal`, `GetBigDecimal`, `GetBigDecimal`, `GetURL`, `GetURL`, `GetArray`, `GetArray`, `GetBlob`, `GetBlob`, `GetClob`, `GetClob`, `GetDate`, `GetDate`, and 81 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 121 declarations carry 53 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 53 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/CallableStatement.cs:66
  • `IConnection` declares 45 members: `AutoCommit`, `Catalog`, `ClientInfo`, `Holdability`, `MetaData`, `NetworkTimeout`, `Schema`, `TransactionIsolation`, `TypeMap`, `Warnings`, `IsClosed`, `IsReadOnly`, `IsValid`, `GetClientInfo`, `NativeSQL`, `CreateArrayOf`, `CreateBlob`, `PrepareCall`, `PrepareCall`, `PrepareCall`, `CreateClob`, `CreateNClob`, `PrepareStatement`, `PrepareStatement`, `PrepareStatement`, `PrepareStatement`, `PrepareStatement`, `PrepareStatement`, `SetSavepoint`, `SetSavepoint`, `CreateSQLXML`, `CreateStatement`, `CreateStatement`, `CreateStatement`, `CreateStruct`, `Abort`, `ClearWarnings`, `Close`, `Commit`, `ReleaseSavepoint`, and 5 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 45 declarations carry 34 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 34 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/Connection.cs:66
  • `IDatabaseMetaData` declares 176 members: `Catalogs`, `CatalogSeparator`, `CatalogTerm`, `ClientInfoProperties`, `Connection`, `DatabaseMajorVersion`, `DatabaseMinorVersion`, `DatabaseProductName`, `DatabaseProductVersion`, `DefaultTransactionIsolation`, `DriverMajorVersion`, `DriverMinorVersion`, `DriverName`, `DriverVersion`, `ExtraNameCharacters`, `IdentifierQuoteString`, `JDBCMajorVersion`, `JDBCMinorVersion`, `MaxBinaryLiteralLength`, `MaxCatalogNameLength`, `MaxCharLiteralLength`, `MaxColumnNameLength`, `MaxColumnsInGroupBy`, `MaxColumnsInIndex`, `MaxColumnsInOrderBy`, `MaxColumnsInSelect`, `MaxColumnsInTable`, `MaxConnections`, `MaxCursorNameLength`, `MaxIndexLength`, `MaxLogicalLobSize`, `MaxProcedureNameLength`, `MaxRowSize`, `MaxSchemaNameLength`, `MaxStatementLength`, `MaxStatements`, `MaxTableNameLength`, `MaxTablesInSelect`, `MaxUserNameLength`, `NumericFunctions`, and 136 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 176 declarations carry 175 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 175 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/DatabaseMetaData.cs:66
  • `IPreparedStatement` declares 58 members: `MetaData`, `ParameterMetaData`, `Execute`, `ExecuteUpdate`, `ExecuteQuery`, `AddBatch`, `ClearParameters`, `SetArray`, `SetAsciiStream`, `SetAsciiStream`, `SetAsciiStream`, `SetBigDecimal`, `SetBinaryStream`, `SetBinaryStream`, `SetBinaryStream`, `SetBlob`, `SetBlob`, `SetBlob`, `SetBoolean`, `SetByte`, `SetBytes`, `SetCharacterStream`, `SetCharacterStream`, `SetCharacterStream`, `SetClob`, `SetClob`, `SetClob`, `SetDate`, `SetDate`, `SetDouble`, `SetFloat`, `SetInt`, `SetLong`, `SetNCharacterStream`, `SetNCharacterStream`, `SetNClob`, `SetNClob`, `SetNClob`, `SetNString`, `SetNull`, and 18 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 58 declarations carry 37 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 37 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/PreparedStatement.cs:66
  • `IResultSet` declares 191 members: `Concurrency`, `CursorName`, `FetchDirection`, `FetchSize`, `Holdability`, `MetaData`, `Row`, `Statement`, `Type`, `Warnings`, `GetObject`, `GetObject`, `Absolute`, `First`, `GetBoolean`, `GetBoolean`, `IsAfterLast`, `IsBeforeFirst`, `IsClosed`, `IsFirst`, `IsLast`, `Last`, `Next`, `Previous`, `Relative`, `RowDeleted`, `RowInserted`, `RowUpdated`, `WasNull`, `GetByte`, `GetByte`, `GetBytes`, `GetBytes`, `GetDouble`, `GetDouble`, `GetFloat`, `GetFloat`, `FindColumn`, `GetInt`, `GetInt`, and 151 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 191 declarations carry 92 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 92 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/ResultSet.cs:66
  • `IResultSetMetaData` declares 21 members: `ColumnCount`, `IsAutoIncrement`, `IsCaseSensitive`, `IsCurrency`, `IsDefinitelyWritable`, `IsReadOnly`, `IsSearchable`, `IsSigned`, `IsWritable`, `GetColumnDisplaySize`, `GetColumnType`, `GetPrecision`, `GetScale`, `IsNullable`, `GetCatalogName`, `GetColumnClassName`, `GetColumnLabel`, `GetColumnName`, `GetColumnTypeName`, `GetSchemaName`, `GetTableName`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/ResultSetMetaData.cs:66
  • `ISQLInput` declares 28 members: `ReadBoolean`, `WasNull`, `ReadByte`, `ReadBytes`, `ReadDouble`, `ReadFloat`, `ReadInt`, `ReadAsciiStream`, `ReadBinaryStream`, `ReadCharacterStream`, `ReadObject`, `ReadNString`, `ReadString`, `ReadBigDecimal`, `ReadURL`, `ReadArray`, `ReadBlob`, `ReadClob`, `ReadDate`, `ReadNClob`, `ReadRef`, `ReadRowId`, `ReadSQLXML`, `ReadTime`, `ReadTimestamp`, `ReadLong`, `ReadShort`, `ReadObject`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 28 declarations carry 27 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 27 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/SQLInput.cs:66
  • `ISQLOutput` declares 28 members: `WriteArray`, `WriteAsciiStream`, `WriteBigDecimal`, `WriteBinaryStream`, `WriteBlob`, `WriteBoolean`, `WriteByte`, `WriteBytes`, `WriteCharacterStream`, `WriteClob`, `WriteDate`, `WriteDouble`, `WriteFloat`, `WriteInt`, `WriteLong`, `WriteNClob`, `WriteNString`, `WriteObject`, `WriteRef`, `WriteRowId`, `WriteShort`, `WriteSQLXML`, `WriteString`, `WriteStruct`, `WriteTime`, `WriteTimestamp`, `WriteURL`, `WriteObject`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 28 declarations carry 27 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 27 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/SQLOutput.cs:66
  • `IStatement` declares 44 members: `Connection`, `FetchDirection`, `FetchSize`, `GeneratedKeys`, `LargeMaxRows`, `LargeUpdateCount`, `MaxFieldSize`, `MaxRows`, `MoreResults`, `QueryTimeout`, `ResultSet`, `ResultSetConcurrency`, `ResultSetHoldability`, `ResultSetType`, `UpdateCount`, `Warnings`, `Execute`, `Execute`, `Execute`, `Execute`, `GetMoreResults`, `IsClosed`, `IsCloseOnCompletion`, `IsPoolable`, `ExecuteUpdate`, `ExecuteUpdate`, `ExecuteUpdate`, `ExecuteUpdate`, `ExecuteBatch`, `ExecuteQuery`, `AddBatch`, `Cancel`, `ClearBatch`, `ClearWarnings`, `Close`, `CloseOnCompletion`, `SetCursorName`, `SetEscapeProcessing`, `SetPoolable`, `ExecuteLargeUpdate`, and 4 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 44 declarations carry 35 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 35 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/Statement.cs:66
  • `IMBeanServer` declares 36 members: `ClassLoaderRepository`, `DefaultDomain`, `Domains`, `MBeanCount`, `IsInstanceOf`, `IsRegistered`, `Deserialize`, `Deserialize`, `Deserialize`, `GetClassLoader`, `GetClassLoaderFor`, `GetAttribute`, `Instantiate`, `Instantiate`, `Instantiate`, `Instantiate`, `Invoke`, `QueryMBeans`, `QueryNames`, `GetAttributes`, `SetAttributes`, `GetMBeanInfo`, `CreateMBean`, `CreateMBean`, `CreateMBean`, `CreateMBean`, `GetObjectInstance`, `RegisterMBean`, `AddNotificationListener`, `AddNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListener`, `SetAttribute`, `UnregisterMBean`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 36 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Management/MBeanServer.cs:66
  • `IMBeanServerConnection` declares 25 members: `DefaultDomain`, `Domains`, `MBeanCount`, `IsInstanceOf`, `IsRegistered`, `GetAttribute`, `Invoke`, `QueryMBeans`, `QueryNames`, `GetAttributes`, `SetAttributes`, `GetMBeanInfo`, `CreateMBean`, `CreateMBean`, `CreateMBean`, `CreateMBean`, `GetObjectInstance`, `AddNotificationListener`, `AddNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListener`, `SetAttribute`, `UnregisterMBean`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 25 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Management/MBeanServerConnection.cs:66
  • `IRelationServiceMBean` declares 33 members: `AllRelationIds`, `AllRelationTypeNames`, `PurgeFlag`, `HasRelation`, `CheckRoleReading`, `CheckRoleWriting`, `GetRoleCardinality`, `GetRelationTypeName`, `IsRelation`, `FindRelationsOfType`, `GetRole`, `GetRoleInfos`, `FindReferencingRelations`, `FindAssociatedMBeans`, `GetReferencedMBeans`, `IsRelationMBean`, `GetRoleInfo`, `GetAllRoles`, `GetRoles`, `SetRoles`, `AddRelation`, `AddRelationType`, `CreateRelation`, `CreateRelationType`, `IsActive`, `PurgeRelations`, `RemoveRelation`, `RemoveRelationType`, `SendRelationCreationNotification`, `SendRelationRemovalNotification`, `SendRoleUpdateNotification`, `SetRole`, `UpdateRoleMap`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Management/Relation/RelationServiceMBean.cs:66
  • `IRMIConnection` declares 27 members: `ConnectionId`, `IsInstanceOf`, `IsRegistered`, `GetMBeanCount`, `AddNotificationListeners`, `GetAttribute`, `Invoke`, `GetDefaultDomain`, `GetDomains`, `QueryMBeans`, `QueryNames`, `GetAttributes`, `SetAttributes`, `GetMBeanInfo`, `CreateMBean`, `CreateMBean`, `CreateMBean`, `CreateMBean`, `GetObjectInstance`, `FetchNotifications`, `AddNotificationListener`, `Close`, `RemoveNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListeners`, `SetAttribute`, `UnregisterMBean`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 27 declarations carry 23 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 23 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnection.cs:66
  • `ITimerMBean` declares 22 members: `AllNotificationIDs`, `NbNotifications`, `SendPastNotifications`, `IsActive`, `IsEmpty`, `GetFixedRate`, `AddNotification`, `AddNotification`, `AddNotification`, `AddNotification`, `GetNbOccurences`, `GetPeriod`, `GetNotificationUserData`, `GetNotificationMessage`, `GetNotificationType`, `GetDate`, `GetNotificationIDs`, `RemoveAllNotifications`, `RemoveNotification`, `RemoveNotifications`, `Start`, `Stop`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 22 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Management/Timer/TimerMBean.cs:66
  • `IContext` declares 29 members: `Environment`, `NameInNamespace`, `AddToEnvironment`, `Lookup`, `Lookup`, `LookupLink`, `LookupLink`, `RemoveFromEnvironment`, `ComposeName`, `CreateSubcontext`, `CreateSubcontext`, `ComposeName`, `GetNameParser`, `GetNameParser`, `ListBindings`, `ListBindings`, `List`, `List`, `Bind`, `Bind`, `Close`, `DestroySubcontext`, `DestroySubcontext`, `Rebind`, `Rebind`, `Rename`, `Rename`, `Unbind`, `Unbind`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 29 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Naming/Context.cs:66
  • `IDirContext` declares 26 members under just 8 distinct name(s): `GetAttributes`, `GetAttributes`, `GetAttributes`, `GetAttributes`, `CreateSubcontext`, `CreateSubcontext`, `GetSchema`, `GetSchema`, `GetSchemaClassDefinition`, `GetSchemaClassDefinition`, `Search`, `Search`, `Search`, `Search`, `Search`, `Search`, `Search`, `Search`, `Bind`, `Bind`, `ModifyAttributes`, `ModifyAttributes`, `ModifyAttributes`, `ModifyAttributes`, `Rebind`, `Rebind`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 26 separate responsibilities: a caller binds to 8 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 26 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/net/JNet/Generated/Javax/Naming/Directory/DirContext.cs:66
  • `IRowSet` declares 104 members: `Command`, `DataSourceName`, `EscapeProcessing`, `MaxFieldSize`, `MaxRows`, `Password`, `QueryTimeout`, `TransactionIsolation`, `TypeMap`, `Url`, `Username`, `IsReadOnly`, `AddRowSetListener`, `ClearParameters`, `Execute`, `RemoveRowSetListener`, `SetArray`, `SetAsciiStream`, `SetAsciiStream`, `SetAsciiStream`, `SetAsciiStream`, `SetBigDecimal`, `SetBigDecimal`, `SetBinaryStream`, `SetBinaryStream`, `SetBinaryStream`, `SetBinaryStream`, `SetBlob`, `SetBlob`, `SetBlob`, `SetBlob`, `SetBlob`, `SetBlob`, `SetBoolean`, `SetBoolean`, `SetByte`, `SetByte`, `SetBytes`, `SetBytes`, `SetCharacterStream`, and 64 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 104 declarations carry 47 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 47 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Sql/RowSet.cs:66
  • `IRowSetMetaData` declares 17 members: `SetAutoIncrement`, `SetCaseSensitive`, `SetCatalogName`, `SetColumnCount`, `SetColumnDisplaySize`, `SetColumnLabel`, `SetColumnName`, `SetColumnType`, `SetColumnTypeName`, `SetCurrency`, `SetNullable`, `SetPrecision`, `SetScale`, `SetSchemaName`, `SetSearchable`, `SetSigned`, `SetTableName`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Sql/RowSetMetaData.cs:66
  • `ICachedRowSet` declares 36 members: `KeyColumns`, `Original`, `OriginalRow`, `PageSize`, `RowSetWarnings`, `ShowDeleted`, `SyncProvider`, `TableName`, `ColumnUpdated`, `ColumnUpdated`, `NextPage`, `PreviousPage`, `Size`, `ToCollection`, `ToCollection`, `ToCollection`, `CreateShared`, `CreateCopy`, `CreateCopyNoConstraints`, `CreateCopySchema`, `AcceptChanges`, `AcceptChanges`, `Commit`, `Execute`, `Populate`, `Populate`, `Release`, `RestoreOriginal`, `Rollback`, `Rollback`, `RowSetPopulated`, `SetMetaData`, `SetOriginalRow`, `UndoDelete`, `UndoInsert`, `UndoUpdate`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 36 declarations carry 30 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 30 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Sql/Rowset/CachedRowSet.cs:66
  • `IButtonModel` declares 19 members: `ActionCommand`, `Mnemonic`, `IsArmed`, `IsEnabled`, `IsPressed`, `IsRollover`, `IsSelected`, `AddActionListener`, `AddChangeListener`, `AddItemListener`, `RemoveActionListener`, `RemoveChangeListener`, `RemoveItemListener`, `SetArmed`, `SetEnabled`, `SetGroup`, `SetPressed`, `SetRollover`, `SetSelected`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Swing/ButtonModel.cs:66
  • `IListSelectionModel` declares 16 members: `AnchorSelectionIndex`, `LeadSelectionIndex`, `MaxSelectionIndex`, `MinSelectionIndex`, `SelectionMode`, `ValueIsAdjusting`, `IsSelectedIndex`, `IsSelectionEmpty`, `AddListSelectionListener`, `AddSelectionInterval`, `ClearSelection`, `InsertIndexInterval`, `RemoveIndexInterval`, `RemoveListSelectionListener`, `RemoveSelectionInterval`, `SetSelectionInterval`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Swing/ListSelectionModel.cs:66

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
  • Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

C1 · Data Protection3.5 / 10Weak✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

What to do

  • Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
  • Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C4 · Data Retention7.5 / 10Strong✓ Tool-verified

Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).

Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.

  • A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).

What to do

  • Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
C5 · Data-Subject Rights4.0 / 10Weak✓ Tool-verified

Other · Security — Whether GDPR data-subject requests are supported in code — erasure, export/portability, consent.

Method: Roslyn scan: GDPR data-subject-rights corroboration (erasure/export/consent vocabulary co-occurring with subject-id store crossing or explicit GDPR pattern). Deterministic, gated by PII.

  • Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.

What to do

  • Implement data export/portability for a data subject (a machine-readable export of their personal data).
  • Track GDPR consent (lawful basis) alongside the personal data it authorises.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

M1 · Documentation (README)9.6 / 10Exemplary✓ 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.

M2 · Architecture documentation2.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.

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

M4 · Documentation accuracy0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

  • CONTRIBUTING.md links to `PULL_REQUEST_TEMPLATE.md`, but `PULL_REQUEST_TEMPLATE.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:48
  • README.md links to `articles/usage.md#intel-cet-and-jnet`, but `articles/usage.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:120
  • README.md links to `articles/usageReflector.md`, but `articles/usageReflector.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:138
  • src/documentation/articles/performance.md names .NET 8, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/documentation/articles/performance.md:30
  • src/documentation/articles/support.md names .NET 8, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/documentation/articles/support.md:17
  • src/documentation/articles/usage.md names .NET 9, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/documentation/articles/usage.md:66
  • src/documentation/articles/usageCLI.md names .NET 6, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/documentation/articles/usageCLI.md:12

What to do

  • Reconcile the README with reality: CONTRIBUTING.md links to `PULL_REQUEST_TEMPLATE.md`, but `PULL_REQUEST_TEMPLATE.md` does not exist; README.md links to `articles/usage.md#intel-cet-and-jnet`, but `articles/usage.md` does not exist; README.md links to `articles/usageReflector.md`, but `articles/usageReflector.md` does not exist; src/documentation/articles/performance.md names .NET 8, but the projects target .NET 10, 11; src/documentation/articles/support.md names .NET 8, but the projects target .NET 10, 11.
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 & versioning9.9 / 10Exemplary✓ 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.

  • 6 public types in `Java.Net` are marked as implementation by their own namespace, folder or name: `DatagramSocketImpl` (src/net/JNet/Generated/Java/Net/DatagramSocketImpl.cs:32, name ends in `Impl`), `DatagramSocketImpl` (src/net/JNet/Generated/Java/Net/DatagramSocketImpl.cs:32, name ends in `Impl`), `DatagramSocketImpl` (src/net/JNet/Generated/Java/Net/DatagramSocketImpl.cs:32, name ends in `Impl`), `SocketImpl` (src/net/JNet/Generated/Java/Net/SocketImpl.cs:32, name ends in `Impl`), `SocketImpl` (src/net/JNet/Generated/Java/Net/SocketImpl.cs:32, name ends in `Impl`), `SocketImpl` (src/net/JNet/Generated/Java/Net/SocketImpl.cs:32, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Java/Net/DatagramSocketImpl.cs:32
  • 3 public types in `Javax.Imageio.Metadata` are marked as implementation by their own namespace, folder or name: `IIOMetadataFormatImpl` (src/net/JNet/Generated/Javax/Imageio/Metadata/IIOMetadataFormatImpl.cs:32, name ends in `Impl`), `IIOMetadataFormatImpl` (src/net/JNet/Generated/Javax/Imageio/Metadata/IIOMetadataFormatImpl.cs:32, name ends in `Impl`), `IIOMetadataFormatImpl` (src/net/JNet/Generated/Javax/Imageio/Metadata/IIOMetadataFormatImpl.cs:32, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Javax/Imageio/Metadata/IIOMetadataFormatImpl.cs:32
  • 6 public types in `Javax.Imageio.Stream` are marked as implementation by their own namespace, folder or name: `ImageInputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageInputStreamImpl.cs:32, name ends in `Impl`), `ImageInputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageInputStreamImpl.cs:32, name ends in `Impl`), `ImageInputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageInputStreamImpl.cs:32, name ends in `Impl`), `ImageOutputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageOutputStreamImpl.cs:32, name ends in `Impl`), `ImageOutputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageOutputStreamImpl.cs:32, name ends in `Impl`), `ImageOutputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageOutputStreamImpl.cs:32, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Javax/Imageio/Stream/ImageInputStreamImpl.cs:32
  • 12 public types in `Javax.Management.Remote.Rmi` are marked as implementation by their own namespace, folder or name: `RMIConnectionImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnectionImpl.cs:32, name ends in `Impl`), `RMIConnectionImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnectionImpl.cs:32, name ends in `Impl`), `RMIConnectionImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnectionImpl.cs:32, name ends in `Impl`), `RMIIIOPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIIIOPServerImpl.cs:32, name ends in `Impl`), `RMIIIOPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIIIOPServerImpl.cs:32, name ends in `Impl`), `RMIIIOPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIIIOPServerImpl.cs:32, name ends in `Impl`), `RMIJRMPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIJRMPServerImpl.cs:32, name ends in `Impl`), `RMIJRMPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIJRMPServerImpl.cs:32, name ends in `Impl`), and 4 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnectionImpl.cs:32
  • 3 public types in `Javax.Sql.Rowset` are marked as implementation by their own namespace, folder or name: `RowSetMetaDataImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/RowSetMetaDataImpl.cs:32, name ends in `Impl`), `RowSetMetaDataImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/RowSetMetaDataImpl.cs:32, name ends in `Impl`), `RowSetMetaDataImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/RowSetMetaDataImpl.cs:32, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Javax/Sql/Rowset/RowSetMetaDataImpl.cs:32
  • 6 public types in `Javax.Sql.Rowset.Serial` are marked as implementation by their own namespace, folder or name: `SQLInputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLInputImpl.cs:32, name ends in `Impl`), `SQLInputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLInputImpl.cs:32, name ends in `Impl`), `SQLInputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLInputImpl.cs:32, name ends in `Impl`), `SQLOutputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLOutputImpl.cs:32, name ends in `Impl`), `SQLOutputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLOutputImpl.cs:32, name ends in `Impl`), `SQLOutputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLOutputImpl.cs:32, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLInputImpl.cs:32
  • 21 public types in `Javax.Xml.Bind.Helpers` are marked as implementation by their own namespace, folder or name: `AbstractMarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractMarshallerImpl.cs:32, name ends in `Impl`), `AbstractMarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractMarshallerImpl.cs:32, name ends in `Impl`), `AbstractMarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractMarshallerImpl.cs:32, name ends in `Impl`), `AbstractUnmarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractUnmarshallerImpl.cs:32, name ends in `Impl`), `AbstractUnmarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractUnmarshallerImpl.cs:32, name ends in `Impl`), `AbstractUnmarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractUnmarshallerImpl.cs:32, name ends in `Impl`), `NotIdentifiableEventImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/NotIdentifiableEventImpl.cs:32, name ends in `Impl`), `NotIdentifiableEventImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/NotIdentifiableEventImpl.cs:32, name ends in `Impl`), and 13 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractMarshallerImpl.cs:32
  • 6 public types in `Org.Xml.Sax.Ext` are marked as implementation by their own namespace, folder or name: `Attributes2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Attributes2Impl.cs:32, name ends in `Impl`), `Attributes2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Attributes2Impl.cs:32, name ends in `Impl`), `Attributes2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Attributes2Impl.cs:32, name ends in `Impl`), `Locator2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Locator2Impl.cs:32, name ends in `Impl`), `Locator2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Locator2Impl.cs:32, name ends in `Impl`), `Locator2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Locator2Impl.cs:32, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Org/Xml/Sax/Ext/Attributes2Impl.cs:32
  • 12 public types in `Org.Xml.Sax.Helpers` are marked as implementation by their own namespace, folder or name: `AttributeListImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributeListImpl.cs:32, name ends in `Impl`), `AttributeListImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributeListImpl.cs:32, name ends in `Impl`), `AttributeListImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributeListImpl.cs:32, name ends in `Impl`), `AttributesImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributesImpl.cs:32, name ends in `Impl`), `AttributesImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributesImpl.cs:32, name ends in `Impl`), `AttributesImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributesImpl.cs:32, name ends in `Impl`), `LocatorImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/LocatorImpl.cs:32, name ends in `Impl`), `LocatorImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/LocatorImpl.cs:32, name ends in `Impl`), and 4 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributeListImpl.cs:32
  • `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57
  • `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138
  • `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57
  • `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138
  • `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57
  • `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138
  • `Java.Util.Function.BiFunctionDirect` (src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58
  • `Java.Util.Function.BiFunctionDirect` (src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58
  • `Java.Util.Function.BiFunctionDirect` (src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58
  • `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57
  • `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150
  • `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57
  • `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150
  • `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57
  • `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150
  • `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:56) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Function.cs:56
  • `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:152) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Function.cs:152
  • `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:56) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Function.cs:56
  • `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:152) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Function.cs:152
  • `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:56) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Function.cs:56
  • `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:152) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Function.cs:152
  • `Java.Util.Function.PredicateDirect` (src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149
  • `Java.Util.Function.PredicateDirect` (src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149
  • `Java.Util.Function.PredicateDirect` (src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149
  • `Java.Util.Function.SupplierDirect` (src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54
  • `Java.Util.Function.SupplierDirect` (src/net/JNet/Developed/Java/Util/Function/Supplier.cs:129) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Supplier.cs:129
  • `Java.Util.Function.SupplierDirect` (src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54
  • `Java.Util.Function.SupplierDirect` (src/net/JNet/Developed/Java/Util/Function/Supplier.cs:129) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Supplier.cs:129
  • `Java.Util.Function.SupplierDirect` (src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54
  • `Java.Util.Function.SupplierDirect` (src/net/JNet/Developed/Java/Util/Function/Supplier.cs:129) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Supplier.cs:129
  • `Java.Awt.EventNs.ActionListenerDirect` (src/net/JNet/Generated/Java/Awt/EventNs/ActionListener.cs:103) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Generated/Java/Awt/EventNs/ActionListener.cs:103

What to do

  • Hide `Java.Net` (`DatagramSocketImpl`, `DatagramSocketImpl`, `DatagramSocketImpl`, `SocketImpl`, `SocketImpl`, `SocketImpl`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `Javax.Imageio.Metadata` (`IIOMetadataFormatImpl`, `IIOMetadataFormatImpl`, `IIOMetadataFormatImpl`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `Javax.Imageio.Stream` (`ImageInputStreamImpl`, `ImageInputStreamImpl`, `ImageInputStreamImpl`, `ImageOutputStreamImpl`, `ImageOutputStreamImpl`, `ImageOutputStreamImpl`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `Javax.Management.Remote.Rmi` (`RMIConnectionImpl`, `RMIConnectionImpl`, `RMIConnectionImpl`, `RMIIIOPServerImpl`, `RMIIIOPServerImpl`, `RMIIIOPServerImpl`, `RMIJRMPServerImpl`, `RMIJRMPServerImpl`, and 4 more) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `Javax.Sql.Rowset` (`RowSetMetaDataImpl`, `RowSetMetaDataImpl`, `RowSetMetaDataImpl`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `Javax.Sql.Rowset.Serial` (`SQLInputImpl`, `SQLInputImpl`, `SQLInputImpl`, `SQLOutputImpl`, `SQLOutputImpl`, `SQLOutputImpl`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `Javax.Xml.Bind.Helpers` (`AbstractMarshallerImpl`, `AbstractMarshallerImpl`, `AbstractMarshallerImpl`, `AbstractUnmarshallerImpl`, `AbstractUnmarshallerImpl`, `AbstractUnmarshallerImpl`, `NotIdentifiableEventImpl`, `NotIdentifiableEventImpl`, and 13 more) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `Org.Xml.Sax.Ext` (`Attributes2Impl`, `Attributes2Impl`, `Attributes2Impl`, `Locator2Impl`, `Locator2Impl`, `Locator2Impl`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `Org.Xml.Sax.Helpers` (`AttributeListImpl`, `AttributeListImpl`, `AttributeListImpl`, `AttributesImpl`, `AttributesImpl`, `AttributesImpl`, `LocatorImpl`, `LocatorImpl`, and 4 more) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Make `Java.Util.Function.BiConsumerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BiConsumerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BiConsumerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BiConsumerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BiConsumerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BiConsumerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BiFunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BiFunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BiFunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BinaryOperatorDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BinaryOperatorDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BinaryOperatorDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BinaryOperatorDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BinaryOperatorDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.BinaryOperatorDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.FunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.FunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.FunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.FunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.FunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.FunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.PredicateDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.PredicateDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.PredicateDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.SupplierDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.SupplierDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.SupplierDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.SupplierDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.SupplierDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Function.SupplierDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.ActionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.ActionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.ActionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.AdjustmentListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.AdjustmentListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.AdjustmentListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.ComponentListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.ComponentListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.ComponentListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.ContainerListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.ContainerListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.ContainerListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.FocusListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.FocusListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.FocusListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.HierarchyBoundsListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.HierarchyBoundsListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.HierarchyBoundsListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.HierarchyListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.HierarchyListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.HierarchyListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.InputMethodListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.InputMethodListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.InputMethodListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.ItemListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.ItemListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.ItemListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.KeyListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.KeyListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.KeyListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.MouseListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.MouseListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.MouseListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.MouseMotionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.MouseMotionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.MouseMotionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.MouseWheelListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.MouseWheelListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.MouseWheelListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.TextListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.TextListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.TextListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.WindowFocusListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.WindowFocusListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.WindowFocusListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.WindowListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.WindowListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.WindowListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.WindowStateListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.WindowStateListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Awt.EventNs.WindowStateListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Beans.PropertyChangeListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Beans.PropertyChangeListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Beans.PropertyChangeListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Lang.InterruptedException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Lang.InterruptedException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Lang.InterruptedException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Concurrent.CallableDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Concurrent.CallableDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Concurrent.CallableDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Concurrent.CancellationException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Concurrent.CancellationException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Concurrent.CancellationException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Concurrent.ExecutionException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Concurrent.ExecutionException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Java.Util.Concurrent.ExecutionException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Jws.Soap.SOAPBinding` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Jws.Soap.SOAPBinding` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Jws.Soap.SOAPBinding` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Jws.WebParam` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Jws.WebParam` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Jws.WebParam` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Naming.Spi.DirStateFactory` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Naming.Spi.DirStateFactory` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Naming.Spi.DirStateFactory` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Swing.ActionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Swing.ActionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Swing.ActionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Swing.Event.ListSelectionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Swing.Event.ListSelectionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `Javax.Swing.Event.ListSelectionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `MASES.JNet.Specific.JNetAsyncEnumerator` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `MASES.JNet.Specific.JNetAsyncEnumerator` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `MASES.JNet.Specific.JNetAsyncEnumerator` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `MASES.JNet.Specific.JNetEventData` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `MASES.JNet.Specific.JNetEventData` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `MASES.JNet.Specific.JNetEventData` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `MASES.JNet.PowerShell.JNetPSHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `MASES.JNet.PowerShell.JNetPSHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
P3 · Security & performance tooling8.0 / 10Strong✓ 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.

What to do

  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ 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.

P6 · Release Hygiene5.0 / 10Adequate✓ 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.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline10.0 / 10Exemplary✓ 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.

PF3 · Async & latency hygiene6.0 / 10Adequate✓ 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.

  • Only 0/8 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
  • `await Task<object>.Run(() => { try { token.ThrowIfCancellationRequested(); object r...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/net/JNet/Developed/Java/Util/Concurrent/CompletableFuture.cs:36, src/net/JNet/Developed/Java/Util/Concurrent/Future.cs:35
  • `await Task<T>.Run(() => { try { token.ThrowIfCancellationRequested(); T _result = t...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/net/JNet/Developed/Java/Util/Concurrent/CompletableFuture.cs:93
  • `await Task<V>.Run(() => { try { token.ThrowIfCancellationRequested(); V result = th...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/net/JNet/Developed/Java/Util/Concurrent/Future.cs:73
  • `await CSharpScript.RunAsync(codeToEval, options)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/net/JNetCLICore/ProgramBase.cs:65
  • `await state.ContinueWithAsync(codeToEval, options, (o) => { if (o is CompilationErr...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/net/JNetCLICore/ProgramBase.cs:69
  • `await script.RunAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/net/JNetCLICore/ProgramBase.cs:108
  • `await main.Start()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/net/JNetCLICore/ProgramBase.cs:151

What to do

  • In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.

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

  • 0/22 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
  • This method contradicts itself about `types`: line 921 writes `types?.ApplyGenerics`, which says `types` can be null, but line 906 then dereferences it directly as `types.Add` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `types` truly cannot be null here, the `?.` is misleading. Settle it one way — test `types` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/net/JNetReflector/InternalExtensions.cs:906
  • This method contradicts itself about `jClass`: line 156 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 157 then dereferences `jClass` as `jClass.Classes` AFTER the block has closed, where the guard no longer applies. A null `jClass` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `jClass` truly cannot be null by then, the guard above is misleading and should go. — src/net/JNetReflector/InternalMethods.cs:157
  • This method contradicts itself about `attribute`: line 252 assigns it with `as CmdletAttribute`, which hands back null rather than throwing when the value is not a `CmdletAttribute`, but line 253 then dereferences it directly as `attribute.NounName` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `attribute` once before the first use and handle the null case, or cast with `(CmdletAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/net/JNetPSCore/JNetPSHelper.cs:253
  • This method contradicts itself about `attribute`: line 273 assigns it with `as CmdletAttribute`, which hands back null rather than throwing when the value is not a `CmdletAttribute`, but line 274 then dereferences it directly as `attribute.VerbName` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `attribute` once before the first use and handle the null case, or cast with `(CmdletAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/net/JNetPSCore/JNetPSHelper.cs:274
  • 0/6 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

What to do

  • Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
  • Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
  • Where a method null-tests a symbol and then uses it after the guarded block closes, move the trailing work inside the block — the guard skips its body on null, it does not stop the method.
  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

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 Health56.4Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture70.7Adequate — gated by AX2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity46.8Weak — gated by M2, M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness71.0StrongSolid.
Security53.4Adequate — gated by C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance77.1StrongStrongest area.
Unscored — 3 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.

  • SC1 Supply-chain hygiene — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.

  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 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 user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AX1 Captive dependencies — no DI registrations detected
  • AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:6 -------------------- 4 | 5 | # Copy everything 6 | >>> COPY ./src/net ./ 7 | ENV JNET_DOCKER_BUILD_ACTIONS=true 8 | # Restore as distinct layers -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref fd3becf8-094b-49ee-aa4d-29727f62c9ff::rzeo7v7n9nzkiyla4o801krp8: "net": not found; likely cause (the repository): a file the Dockerfile copies (`src/net`) is not in the repository's build context (it may be produced by a build step outside the Dockerfile, or excluded by .dockerignore); runtime evidence skipped The cause is in the repository, not in our sandbox: a file the Dockerfile copies (`src/net`) is not in the repository's build context (it may be produced by a build step outside the Dockerfile, or excluded by .dockerignore). Nothing here says the surface is inaccessible, only that it was never rendered.
  • C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • D10 Test Quality — ~3370 lines of test source are present (.java) 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.
  • D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .java, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D21 Naming Consistency — Naming Consistency not included (check did not complete)
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — symbol resolution incomplete — too few calls resolved to assess navigability
  • D28 Secrets (history) — gitleaks killed before it finished — this repository's working tree not scanned
  • D32 Data Compliance (PII/GDPR) — 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.
  • 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 dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — analyzer environment
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (27 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
  • ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 33 event handler(s); 42 CQRS handler(s)
  • ED5 Idempotency — 63 mutating command handler(s)/consumer(s) detected and 81 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • IC1 Incompleteness & stubs — IC1 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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'.
  • P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • P8 Schema migrations — no EF Core usage detected
  • 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 — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • X1 Async correctness — X1 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X12 Unreachable branch — X12 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — X13 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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
  • X16 Unfloored truncation loop — X16 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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
  • X18 Disposal-pattern correctness — X18 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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 — X2 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X21 Side-effecting pattern 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X27 Collection changed while being enumerated — X27 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X28 Index access outside its own emptiness guard — X28 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X29 Per-element action decided by a fixed element — X29 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X3 Exception handling — X3 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X30 Support guard that admits what it rejects — X30 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X6 Hand-rolled structured-format parsing — 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 — 24 finding(s)
AX3 · Project dependency cycles · Namespace dependency cycle · ×8
  • Namespace dependency cycle src/net/JNet/Generated/Java/Awt/Color.cs:32 — The namespaces Java.Applet ↔ Java.Awt ↔ Java.Awt.ColorNs ↔ Java.Awt.Datatransfer ↔ Java.Awt.Dnd ↔ Java.Awt.Dnd.Peer ↔ Java.Awt.EventNs ↔ Java.Awt.FontNs ↔ Java.Awt.Geom ↔ Java.Awt.Im ↔ Java.Awt.ImageNs ↔ Java.Awt.ImageNs.Renderable ↔ Java.Awt.Print ↔ Java.Beans ↔ Java.Beans.Beancontext ↔ Java.Io ↔ Java.Lang ↔ Java.Lang.Annotation ↔ Java.Lang.Reflect ↔ Java.Math ↔ Java.Net ↔ Java.Nio ↔ Java.Nio.Channels ↔ Java.Nio.Channels.Spi ↔ Java.Nio.Charset ↔ Java.Nio.File ↔ Java.Nio.File.Attribute ↔ Java.Nio.File.Spi ↔ Java.Security ↔ Java.Security.Cert ↔ Java.Text ↔ Java.Time ↔ Java.Time.Chrono ↔ Java.Time.Format ↔ Java.Time.Temporal ↔ Java.Time.Zone ↔ Java.Util ↔ Java.Util.Concurrent ↔ Java.Util.Jar ↔ Java.Util.Regex ↔ Java.Util.Stream ↔ Java.Util.Zip ↔ Javax.Accessibility ↔ Javax.Print ↔ Javax.Print.Attribute ↔ Javax.Print.Event ↔ Javax.Security.Auth ↔ Javax.Security.Auth.Callback ↔ Javax.Security.Auth.X500 ↔ Javax.Swing ↔ Javax.Swing.Border ↔ Javax.Swing.Colorchooser ↔ Javax.Swing.Event ↔ Javax.Swing.Filechooser ↔ Javax.Swing.Plaf ↔ Javax.Swing.Plaf.Basic ↔ Javax.Swing.Table ↔ Javax.Swing.Text ↔ Javax.Swing.Tree ↔ Javax.Swing.Undo ↔ MASES.JNet.Specific ↔ MASES.JNet.Specific.Extensions ↔ Org.Xml.Sax ↔ Org.Xml.Sax.Helpers depend on each other. The lightest dependency in the cycle is Java.Awt → Java.Awt.ColorNs (Java.Awt.Color → Java.Awt.ColorNs.ColorSpace, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/net/JNet/Generated/Javax/Management/MBeanServer.cs:66 — The namespaces Javax.Management ↔ Javax.Management.Loading depend on each other. The lightest dependency in the cycle is Javax.Management → Javax.Management.Loading (Javax.Management.IMBeanServer → Javax.Management.Loading.ClassLoaderRepository, 3 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/net/JNet/Generated/Javax/Lang/Model/Type/DeclaredType.cs:32 — The namespaces Javax.Lang.Model.Element ↔ Javax.Lang.Model.Type depend on each other. The lightest dependency in the cycle is Javax.Lang.Model.Type → Javax.Lang.Model.Element (Javax.Lang.Model.Type.DeclaredType → Javax.Lang.Model.Element.Element, 4 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/net/JNet/Generated/Javax/Imageio/Spi/ImageReaderWriterSpi.cs:32 — The namespaces Javax.Imageio ↔ Javax.Imageio.Event ↔ Javax.Imageio.Metadata ↔ Javax.Imageio.Spi depend on each other. The lightest dependency in the cycle is Javax.Imageio.Spi → Javax.Imageio.Metadata (Javax.Imageio.Spi.ImageReaderWriterSpi → Javax.Imageio.Metadata.IIOMetadataFormat, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/net/JNet/Generated/Javax/Sql/Rowset/CachedRowSet.cs:32 — The namespaces Javax.Sql.Rowset ↔ Javax.Sql.Rowset.Spi depend on each other. The lightest dependency in the cycle is Javax.Sql.Rowset → Javax.Sql.Rowset.Spi (Javax.Sql.Rowset.CachedRowSet → Javax.Sql.Rowset.Spi.SyncProvider, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/net/JNet/Generated/Javax/Xml/Stream/XMLEventWriter.cs:66 — The namespaces Javax.Xml.Stream ↔ Javax.Xml.Stream.Events ↔ Javax.Xml.Stream.Util depend on each other. The lightest dependency in the cycle is Javax.Xml.Stream → Javax.Xml.Stream.Util (Javax.Xml.Stream.IXMLEventWriter → Javax.Xml.Stream.Util.IXMLEventConsumer, 3 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/net/JNet/Generated/Javax/Xml/Crypto/KeySelector.cs:32 — The namespaces Javax.Xml.Crypto ↔ Javax.Xml.Crypto.Dsig.Keyinfo depend on each other. The lightest dependency in the cycle is Javax.Xml.Crypto → Javax.Xml.Crypto.Dsig.Keyinfo (Javax.Xml.Crypto.KeySelector → Javax.Xml.Crypto.Dsig.Keyinfo.KeyInfo, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/net/JNet/Generated/Javax/Xml/Ws/Handler/LogicalMessageContext.cs:66 — The namespaces Javax.Xml.Ws ↔ Javax.Xml.Ws.Handler depend on each other. The lightest dependency in the cycle is Javax.Xml.Ws.Handler → Javax.Xml.Ws (Javax.Xml.Ws.Handler.ILogicalMessageContext → Javax.Xml.Ws.LogicalMessage, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D17 · Explicit Debt · AnalyzerSeverityNone · ×7
  • AnalyzerSeverityNone src/net/JNet/Developed/.editorconfig:4 — CS0108 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/net/JNet/Generated/.editorconfig:4 — CS0108 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/net/JNet/Developed/.editorconfig:5 — CS0612 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/net/JNet/Generated/.editorconfig:8 — CS0612 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/net/JNet/Generated/.editorconfig:5 — CS0114 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/net/JNet/Generated/.editorconfig:6 — CS0419 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/net/JNet/Generated/.editorconfig:7 — CS1574 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
D17 · Explicit Debt · EmptyCatchBlock · ×4
  • EmptyCatchBlock src/net/JNetReflector/JNetReflectorHelper.cs:217 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/net/JNetReflector/JNetReflectorHelper.cs:220 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/net/JNetReflector/JNetReflectorHelper.cs:274 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/net/JNetReflector/JNetReflectorHelper.cs:277 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D17 · Explicit Debt · BlanketAnalyzerSeverityNone · ×2
  • BlanketAnalyzerSeverityNone src/net/JNet/Developed/.editorconfig:3 — dotnet_analyzer_diagnostic.severity = none — every analyzer rule — this is not one rule switched off, it is a whole set the file never lists: every rule the entry covers is silenced for every file the section matches, in every project under this directory, and any rule added to that set by a future analyzer upgrade is silenced too, without anybody deciding so. It reads as narrower than it is — the analyzers still run and the build still looks configured — and because no rule is named there is nothing for a reader to look up and no list that will ever disclose what is covered. Replace it with the rules you actually mean to switch off, each on its own line, so the set is finite, visible and reviewable, and the ones nobody chose keep protecting the tree. If the blanket entry is genuinely right, link the decision from a comment above it: a comment that only restates the entry is what the editor generates when it writes this line, so it is a reference to the decision — an issue or a ticket — that clears this row.
  • BlanketAnalyzerSeverityNone src/net/JNet/Generated/.editorconfig:3 — dotnet_analyzer_diagnostic.severity = none — every analyzer rule — this is not one rule switched off, it is a whole set the file never lists: every rule the entry covers is silenced for every file the section matches, in every project under this directory, and any rule added to that set by a future analyzer upgrade is silenced too, without anybody deciding so. It reads as narrower than it is — the analyzers still run and the build still looks configured — and because no rule is named there is nothing for a reader to look up and no list that will ever disclose what is covered. Replace it with the rules you actually mean to switch off, each on its own line, so the set is finite, visible and reviewable, and the ones nobody chose keep protecting the tree. If the blanket entry is genuinely right, link the decision from a comment above it: a comment that only restates the entry is what the editor generates when it writes this line, so it is a reference to the decision — an issue or a ticket — that clears this row.
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
D17 · Explicit Debt · NoWarnInCsproj · ×1
  • NoWarnInCsproj src/net/Common/Common.props:21 — 0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
D31 · IaC & Container Security · High IaC · ×1
  • REDACTED
Serious — 176 finding(s)
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×10
  • NuGet dependencies are not locked src/net/Directory.Build.targets:11 — src/net/Directory.Build.targets declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked src/net/JNet/JNet.csproj:52 — src/net/JNet/JNet.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked src/net/JNetCLICore/JNetCLICore.csproj:24 — src/net/JNetCLICore/JNetCLICore.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked src/net/JNetPS/JNetPS.csproj:32 — src/net/JNetPS/JNetPS.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked src/net/JNetPSCore/JNetPSCore.csproj:21 — src/net/JNetPSCore/JNetPSCore.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked src/net/JNetReflector/JNetReflector.csproj:119 — src/net/JNetReflector/JNetReflector.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked src/net/templates/templates/jnetAWTApp/jnetAWTApp.csproj:17 — src/net/templates/templates/jnetAWTApp/jnetAWTApp.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked src/net/templates/templates/jnetApp/jnetApp.csproj:17 — src/net/templates/templates/jnetApp/jnetApp.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked tests/net/JNetBenchmarksTest/JNetBenchmarksTest.csproj:12 — tests/net/JNetBenchmarksTest/JNetBenchmarksTest.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked tests/net/JNetTest/JNetTest.csproj:14 — tests/net/JNetTest/JNetTest.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
PF3 · Async & latency hygiene · Awaits without ConfigureAwait(false) · ×9
  • Awaits without ConfigureAwait(false) — Only 0/8 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
  • Awaits without ConfigureAwait(false) src/net/JNet/Developed/Java/Util/Concurrent/CompletableFuture.cs:36 — `await Task<object>.Run(() => { try { token.ThrowIfCancellationRequested(); object r...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/net/JNet/Developed/Java/Util/Concurrent/CompletableFuture.cs:93 — `await Task<T>.Run(() => { try { token.ThrowIfCancellationRequested(); T _result = t...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/net/JNet/Developed/Java/Util/Concurrent/Future.cs:35 — `await Task<object>.Run(() => { try { token.ThrowIfCancellationRequested(); object r...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/net/JNet/Developed/Java/Util/Concurrent/Future.cs:73 — `await Task<V>.Run(() => { try { token.ThrowIfCancellationRequested(); V result = th...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/net/JNetCLICore/ProgramBase.cs:65 — `await CSharpScript.RunAsync(codeToEval, options)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/net/JNetCLICore/ProgramBase.cs:69 — `await state.ContinueWithAsync(codeToEval, options, (o) => { if (o is CompilationErr...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/net/JNetCLICore/ProgramBase.cs:108 — `await script.RunAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/net/JNetCLICore/ProgramBase.cs:151 — `await main.Start()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
AX2 · Stateful singletons · Process-global static state · ×6
  • Process-global static state: JNetCLICoreHelper src/net/JNet/Specific/CLI/JNetCLICoreHelper.cs:32 — `JNetCLICoreHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_mainClassToRun, _classToRun, _Interactive, _RunCommand, _NoLogo, _Script; e.g. `_mainClassToRun` at line 249). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: JNetReflectorExtensions src/net/JNetReflector/InternalExtensions.cs:38 — `JNetReflectorExtensions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_CurrentJavadocBaseUrl, _CurrentJavadocVersion, _CurrentNoModule; e.g. `_CurrentJavadocBaseUrl` at line 50). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ReflectionUtils src/net/JNetReflector/InternalMethods.cs:36 — `ReflectionUtils` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (TraceReportHandler, Level, namespaces, classes, JarOrModuleName, CancellationTokenSource; e.g. `TraceReportHandler` at line 56). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: JNetReflectorCore src/net/JNetReflector/JNetReflectorCore.cs:34 — `JNetReflectorCore` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_CopyrightFile, _JavaPLocationPath, _ConfigurationFromFile, _ClassesToAnalyze, _OriginRootPath, _JarsToAddInClassPath; e.g. `_CopyrightFile` at line 607). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: JNetReflectorCore src/net/JNetReflector/JNetReflectorCore.cs:905 — `JNetReflectorCore` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (CurrentClassPath; e.g. `CurrentClassPath` at line 913). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: JNetPSHelperExtensions src/net/JNetPSCore/JNetPSHelper.cs:37 — `JNetPSHelperExtensions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (processExited, cancelKeyRaised; e.g. `processExited` at line 127). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
D3 · God Classes · MethodTooLong · ×6
  • MethodTooLong: ReflectionUtils.AnalyzeMethods src/net/JNetReflector/InternalMethods.cs:1303 — MethodTooLong — AnalyzeMethods runs 578 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 478 over it, 5.78× 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.
  • MethodTooLong: ReflectionUtils.PrepareSingleClass src/net/JNetReflector/InternalMethods.cs:672 — MethodTooLong — PrepareSingleClass runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× 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.
  • MethodTooLong: JNetReflectorCore.ProcessCommandLine src/net/JNetReflector/JNetReflectorCore.cs:603 — MethodTooLong — ProcessCommandLine runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× 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.
  • MethodTooLong: ReflectionUtils.AnalyzeJavaMethods src/net/JNetReflector/InternalMethods.cs:2222 — MethodTooLong — AnalyzeJavaMethods runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× 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.
  • MethodTooLong: ReflectionUtils.AnalyzeConstructors src/net/JNetReflector/InternalMethods.cs:931 — MethodTooLong — AnalyzeConstructors runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× 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.
  • MethodTooLong: JNetReflectorExtensions.ToNetType src/net/JNetReflector/InternalExtensions.cs:2042 — MethodTooLong — ToNetType runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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.
D17 · Explicit Debt · Dead code · ×5
  • Dead code: IAsyncEnumerator<TObject>.Current src/net/JNet/Specific/AsyncEnumerable.cs:72 — Property IAsyncEnumerator<TObject>.Current — Roslyn's SymbolFinder walked every project the solution loads, including JNet(net462), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: LocalBridgeClazz src/net/JNet/Specific/JNetEventResult.cs:40 — Property LocalBridgeClazz — Roslyn's SymbolFinder walked every project the solution loads, including JNet(net462), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: InternalConst src/net/JNetCLI/InternalConst.cs:21 — NamedType InternalConst — Roslyn's SymbolFinder walked every project the solution loads, including JNetCLI(net462), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: GetRelativePath src/net/JNetReflector/InternalConst.cs:259 — Method GetRelativePath — Roslyn's SymbolFinder walked every project the solution loads, including JNetReflector, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: InternalConst src/net/JNetCLICore/InternalConst.cs:21 — NamedType InternalConst — Roslyn's SymbolFinder walked every project the solution loads, including JNetCLICore(net462), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
D17 · Explicit Debt · DeadPreprocessorBranch · ×4
  • DeadPreprocessorBranch src/net/JNetReflector/InternalExtensions.cs:2172 — #if USE_MODULEINFO — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch src/net/JNetReflector/InternalExtensions.cs:2571 — #if TEST — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch src/net/JNetReflector/InternalExtensions.cs:2593 — #if TEST — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
  • DeadPreprocessorBranch src/net/JNetReflector/JNetReflectorHelper.cs:136 — #if OLD_ALGORITHM — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×4
  • Duplicated block (7 lines × 2) src/net/JNetReflector/InternalMethods.cs:1197 — src/net/JNetReflector/InternalMethods.cs:1197-1203 | src/net/JNetReflector/InternalMethods.cs:1213-1219 — 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 `src/net/JNetReflector/InternalMethods.cs:1197` 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 (7 lines × 2) src/net/JNetReflector/InternalMethods.cs:367 — src/net/JNetReflector/InternalMethods.cs:367-373 | src/net/JNetReflector/InternalMethods.cs:387-393 — 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.
  • Duplicated block (7 lines × 2) src/net/JNetReflector/InternalMethods.cs:1847 — src/net/JNetReflector/InternalMethods.cs:1847-1853 | src/net/JNetReflector/InternalMethods.cs:1890-1896 — 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 `src/net/JNetReflector/InternalMethods.cs:1847` 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 (7 lines × 2) src/net/JNetReflector/JNetReflectorHelper.cs:109 — src/net/JNetReflector/JNetReflectorHelper.cs:109-115 | src/net/JNetReflector/JNetReflectorHelper.cs:234-240 — 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 (6 lines × 2) · ×4
  • Duplicated block (6 lines × 2) src/net/JNetReflector/InternalMethods.cs:1868 — src/net/JNetReflector/InternalMethods.cs:1868-1873 | src/net/JNetReflector/InternalMethods.cs:1877-1882 — 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 `src/net/JNetReflector/InternalMethods.cs:1868` 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 (6 lines × 2) src/net/JNetReflector/InternalMethods.cs:2069 — src/net/JNetReflector/InternalMethods.cs:2069-2074 | src/net/JNetReflector/InternalMethods.cs:2099-2104 — 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 `src/net/JNetReflector/InternalMethods.cs:2069` 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 (6 lines × 2) src/net/JNetReflector/InternalMethods.cs:2172 — src/net/JNetReflector/InternalMethods.cs:2172-2177 | src/net/JNetReflector/InternalMethods.cs:2202-2207 — 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 `src/net/JNetReflector/InternalMethods.cs:2172` 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 (6 lines × 2) src/net/JNetReflector/InternalMethods.cs:2303 — src/net/JNetReflector/InternalMethods.cs:2303-2308 | src/net/JNetReflector/InternalMethods.cs:2339-2344 — 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.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×3
  • Duplicated block (15 lines × 2) src/net/JNetReflector/InternalExtensions.cs:2296 — src/net/JNetReflector/InternalExtensions.cs:2296-2310 | src/net/JNetReflector/InternalExtensions.cs:2657-2671 — 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 `src/net/JNetReflector/InternalExtensions.cs:2296` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `entry` to `this Constructor` in one and `this Method` 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.
  • Duplicated block (15 lines × 2) src/net/JNetPS/Cmdlet/JMX/InvokeQueryAndCmdletCommand.cs:29 — src/net/JNetPS/Cmdlet/JMX/InvokeQueryAndCmdletCommand.cs:29-43 | src/net/JNetPS/Cmdlet/JMX/InvokeQueryOrCmdletCommand.cs:29-43 — before extracting anything, compare `src/net/JNetPS/Cmdlet/JMX/InvokeQueryAndCmdletCommand.cs` and `src/net/JNetPS/Cmdlet/JMX/InvokeQueryOrCmdletCommand.cs` as WHOLE FILES: 88% 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. 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.
  • Duplicated block (15 lines × 2) src/net/JNetReflector/InternalMethods.cs:428 — src/net/JNetReflector/InternalMethods.cs:428-442 | src/net/JNetReflector/InternalMethods.cs:575-589 — 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 `src/net/JNetReflector/InternalMethods.cs:428` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/net/JNetReflector/InternalMethods.cs:425` calls `IsJVMNestedClass` and `src/net/JNetReflector/InternalMethods.cs:572` 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 (11 lines × 2) · ×3
  • Duplicated block (11 lines × 2) src/net/JNetReflector/InternalExtensions.cs:984 — src/net/JNetReflector/InternalExtensions.cs:984-994 | src/net/JNetReflector/InternalExtensions.cs:1061-1071 — 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 `src/net/JNetReflector/InternalExtensions.cs:984` 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 (11 lines × 2) src/net/JNetReflector/InternalMethods.cs:1696 — src/net/JNetReflector/InternalMethods.cs:1696-1706 | src/net/JNetReflector/InternalMethods.cs:1711-1721 — 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 `src/net/JNetReflector/InternalMethods.cs:1696` 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 (11 lines × 2) src/net/JNetReflector/InternalMethods.cs:2040 — src/net/JNetReflector/InternalMethods.cs:2040-2050 | src/net/JNetReflector/InternalMethods.cs:2070-2080 — 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 `src/net/JNetReflector/InternalMethods.cs:2040` 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 (8 lines × 2) · ×3
  • Duplicated block (8 lines × 2) src/net/JNetReflector/InternalMethods.cs:1363 — src/net/JNetReflector/InternalMethods.cs:1363-1370 | src/net/JNetReflector/InternalMethods.cs:1394-1401 — 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.
  • Duplicated block (8 lines × 2) src/net/JNetReflector/InternalExtensions.cs:1494 — src/net/JNetReflector/InternalExtensions.cs:1494-1502 | src/net/JNetReflector/InternalExtensions.cs:1505-1512 — 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 `src/net/JNetReflector/InternalExtensions.cs:1494` 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. 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 (8 lines × 2) src/net/JNetReflector/InternalMethods.cs:1512 — src/net/JNetReflector/InternalMethods.cs:1512-1519 | src/net/JNetReflector/InternalMethods.cs:1810-1817 — 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 `src/net/JNetReflector/InternalMethods.cs:1512` 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×3
  • Duplicated block (5 lines × 2) src/net/JNetReflector/InternalMethods.cs:1685 — src/net/JNetReflector/InternalMethods.cs:1685-1689 | src/net/JNetReflector/InternalMethods.cs:1971-1975 — 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.
  • Duplicated block (5 lines × 2) src/net/JNetReflector/InternalMethods.cs:1022 — src/net/JNetReflector/InternalMethods.cs:1022-1026 | src/net/JNetReflector/InternalMethods.cs:1657-1661 — 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 `src/net/JNetReflector/InternalMethods.cs:1022` 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 (5 lines × 2) src/net/JNetReflector/InternalMethods.cs:2438 — src/net/JNetReflector/InternalMethods.cs:2438-2443 | src/net/JNetReflector/InternalMethods.cs:2454-2458 — 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 `src/net/JNetReflector/InternalMethods.cs:2454` 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.
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×3
  • Symbol treated as nullable, then dereferenced unguarded src/net/JNetReflector/InternalExtensions.cs:906 — This method contradicts itself about `types`: line 921 writes `types?.ApplyGenerics`, which says `types` can be null, but line 906 then dereferences it directly as `types.Add` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `types` truly cannot be null here, the `?.` is misleading. Settle it one way — test `types` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/net/JNetPSCore/JNetPSHelper.cs:253 — This method contradicts itself about `attribute`: line 252 assigns it with `as CmdletAttribute`, which hands back null rather than throwing when the value is not a `CmdletAttribute`, but line 253 then dereferences it directly as `attribute.NounName` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `attribute` once before the first use and handle the null case, or cast with `(CmdletAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/net/JNetPSCore/JNetPSHelper.cs:274 — This method contradicts itself about `attribute`: line 273 assigns it with `as CmdletAttribute`, which hands back null rather than throwing when the value is not a `CmdletAttribute`, but line 274 then dereferences it directly as `attribute.VerbName` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `attribute` once before the first use and handle the null case, or cast with `(CmdletAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side.
D17 · Explicit Debt · CommentedOutCode · ×2
  • CommentedOutCode src/net/JNetReflector/InternalExtensions.cs:931 — 10 consecutive commented-code lines
  • CommentedOutCode src/net/JNetReflector/InternalExtensions.cs:1917 — 6 consecutive commented-code lines
D3 · God Classes · FileTooLong · ×2
  • FileTooLong: JNetReflector/InternalMethods.cs src/net/JNetReflector/InternalMethods.cs — FileTooLong — 1557 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1057 over it, 3.11× 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.
  • FileTooLong: JNetReflector/JNetReflectorCore.cs src/net/JNetReflector/JNetReflectorCore.cs — FileTooLong — 539 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 39 over it, 1.08× 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.
D31 · IaC & Container Security · Medium IaC · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×2
  • Duplicated block (12 lines × 2) src/net/JNetReflector/InternalMethods.cs:1855 — src/net/JNetReflector/InternalMethods.cs:1855-1866 | src/net/JNetReflector/InternalMethods.cs:1899-1910 — 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 `src/net/JNetReflector/InternalMethods.cs:1855` 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 (12 lines × 2) src/net/JNetReflector/InternalExtensions.cs:2269 — src/net/JNetReflector/InternalExtensions.cs:2269-2280 | src/net/JNetReflector/InternalExtensions.cs:2636-2647 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `entry` to `this Constructor` in one and `this Method` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/net/JNetReflector/InternalExtensions.cs:2635` calls `Substring`, `IndexOf` and `src/net/JNetReflector/InternalExtensions.cs:2268` 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 (10 lines × 2) · ×2
  • Duplicated block (10 lines × 2) src/net/JNetReflector/InternalExtensions.cs:1461 — src/net/JNetReflector/InternalExtensions.cs:1461-1470 | src/net/JNetReflector/InternalExtensions.cs:1479-1488 — 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 `src/net/JNetReflector/InternalExtensions.cs:1461` 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. 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 (10 lines × 2) src/net/JNetReflector/InternalMethods.cs:1085 — src/net/JNetReflector/InternalMethods.cs:1085-1095 | src/net/JNetReflector/InternalMethods.cs:1980-1989 — 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 `src/net/JNetReflector/InternalMethods.cs:1085` 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.
D1 · Cyclomatic Complexity · ReflectionUtils.AnalyzeMethods (cyclomatic 253) · ×1
  • ReflectionUtils.AnalyzeMethods (cyclomatic 253) src/net/JNetReflector/InternalMethods.cs:1303 — ReflectionUtils.AnalyzeMethods has cyclomatic complexity 253 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: src/net/JNetReflector/InternalMethods.cs holds 9 of the 23 methods over the threshold — including the worst — and 425 of the 671 points over it (63%), 2.9× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 147). 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.
D1 · Cyclomatic Complexity · JNetReflectorCore.ProcessCommandLine (cyclomatic 74) · ×1
  • JNetReflectorCore.ProcessCommandLine (cyclomatic 74) src/net/JNetReflector/JNetReflectorCore.cs:603 — JNetReflectorCore.ProcessCommandLine has cyclomatic complexity 74 (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 · ReflectionUtils.AnalyzeJavaMethods (cyclomatic 70) · ×1
  • ReflectionUtils.AnalyzeJavaMethods (cyclomatic 70) src/net/JNetReflector/InternalMethods.cs:2222 — ReflectionUtils.AnalyzeJavaMethods has cyclomatic complexity 70 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: src/net/JNetReflector/InternalMethods.cs holds 9 of the 23 methods over the threshold — including the worst — and 425 of the 671 points over it (63%), 2.9× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 147). 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.
D1 · Cyclomatic Complexity · JNetReflectorExtensions.ToNetType (cyclomatic 67) · ×1
  • JNetReflectorExtensions.ToNetType (cyclomatic 67) src/net/JNetReflector/InternalExtensions.cs:2042 — JNetReflectorExtensions.ToNetType has cyclomatic complexity 67 (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 · ReflectionUtils.AnalyzeConstructors (cyclomatic 53) · ×1
  • ReflectionUtils.AnalyzeConstructors (cyclomatic 53) src/net/JNetReflector/InternalMethods.cs:931 — ReflectionUtils.AnalyzeConstructors has cyclomatic complexity 53 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: src/net/JNetReflector/InternalMethods.cs holds 9 of the 23 methods over the threshold — including the worst — and 425 of the 671 points over it (63%), 2.9× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 147). 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.
D1 · Cyclomatic Complexity · ReflectionUtils.PrepareSingleClass (cyclomatic 52) · ×1
  • ReflectionUtils.PrepareSingleClass (cyclomatic 52) src/net/JNetReflector/InternalMethods.cs:672 — ReflectionUtils.PrepareSingleClass has cyclomatic complexity 52 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: src/net/JNetReflector/InternalMethods.cs holds 9 of the 23 methods over the threshold — including the worst — and 425 of the 671 points over it (63%), 2.9× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 147). 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.
D1 · Cyclomatic Complexity · JNetReflectorExtensions.JVMBaseClassName (cyclomatic 48) · ×1
  • JNetReflectorExtensions.JVMBaseClassName (cyclomatic 48) src/net/JNetReflector/InternalExtensions.cs:1424 — JNetReflectorExtensions.JVMBaseClassName has cyclomatic complexity 48 (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 · JNetReflectorExtensions.GetGenerics (cyclomatic 47) · ×1
  • JNetReflectorExtensions.GetGenerics (cyclomatic 47) src/net/JNetReflector/InternalExtensions.cs:964 — JNetReflectorExtensions.GetGenerics has cyclomatic complexity 47 (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 · ReflectionUtils.PrefilterMethods (cyclomatic 34) · ×1
  • ReflectionUtils.PrefilterMethods (cyclomatic 34) src/net/JNetReflector/InternalMethods.cs:1224 — ReflectionUtils.PrefilterMethods has cyclomatic complexity 34 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: src/net/JNetReflector/InternalMethods.cs holds 9 of the 23 methods over the threshold — including the worst — and 425 of the 671 points over it (63%), 2.9× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 147). 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.
D1 · Cyclomatic Complexity · JNetReflectorExtensions.NeedsOperators (cyclomatic 29) · ×1
  • JNetReflectorExtensions.NeedsOperators (cyclomatic 29) src/net/JNetReflector/InternalExtensions.cs:1309 — JNetReflectorExtensions.NeedsOperators has cyclomatic complexity 29 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ReflectionUtils.AnalyzeClasses (cyclomatic 28) · ×1
  • ReflectionUtils.AnalyzeClasses (cyclomatic 28) src/net/JNetReflector/InternalMethods.cs:397 — ReflectionUtils.AnalyzeClasses has cyclomatic complexity 28 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: src/net/JNetReflector/InternalMethods.cs holds 9 of the 23 methods over the threshold — including the worst — and 425 of the 671 points over it (63%), 2.9× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 147). 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.
D1 · Cyclomatic Complexity · ReflectionUtils.AnalyzeNestedClasses (cyclomatic 28) · ×1
  • ReflectionUtils.AnalyzeNestedClasses (cyclomatic 28) src/net/JNetReflector/InternalMethods.cs:551 — ReflectionUtils.AnalyzeNestedClasses has cyclomatic complexity 28 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: src/net/JNetReflector/InternalMethods.cs holds 9 of the 23 methods over the threshold — including the worst — and 425 of the 671 points over it (63%), 2.9× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 147). 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.
D1 · Cyclomatic Complexity · JNetReflectorHelper.ExtractJavaInfo (cyclomatic 28) · ×1
  • JNetReflectorHelper.ExtractJavaInfo (cyclomatic 28) src/net/JNetReflector/JNetReflectorHelper.cs:76 — JNetReflectorHelper.ExtractJavaInfo has cyclomatic complexity 28 (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 · JNetReflectorExtensions.HasJVMBaseClassName (cyclomatic 26) · ×1
  • JNetReflectorExtensions.HasJVMBaseClassName (cyclomatic 26) src/net/JNetReflector/InternalExtensions.cs:1370 — JNetReflectorExtensions.HasJVMBaseClassName has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ReflectionUtils.AnalyzeFields (cyclomatic 25) · ×1
  • ReflectionUtils.AnalyzeFields (cyclomatic 25) src/net/JNetReflector/InternalMethods.cs:2472 — ReflectionUtils.AnalyzeFields 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. This file is where this pass's cyclomatic complexity CONCENTRATES: src/net/JNetReflector/InternalMethods.cs holds 9 of the 23 methods over the threshold — including the worst — and 425 of the 671 points over it (63%), 2.9× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 147). 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.
D1 · Cyclomatic Complexity · ParserAdapter.ListenerShallManageEventHandlers (cyclomatic 23) · ×1
  • ParserAdapter.ListenerShallManageEventHandlers (cyclomatic 23) src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs:235 — ParserAdapter.ListenerShallManageEventHandlers has cyclomatic complexity 23 (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 · JNetCLICoreHelper.ProcessCLIParsedArgs (cyclomatic 21) · ×1
  • JNetCLICoreHelper.ProcessCLIParsedArgs (cyclomatic 21) src/net/JNet/Specific/CLI/JNetCLICoreHelper.cs:346 — JNetCLICoreHelper.ProcessCLIParsedArgs has cyclomatic complexity 21 (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 · ProgramBase.Start (cyclomatic 20) · ×1
  • ProgramBase.Start (cyclomatic 20) src/net/JNetCLICore/ProgramBase.cs:49 — ProgramBase.Start has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. 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 · XMLReaderAdapter.ListenerShallManageEventHandlers (cyclomatic 19) · ×1
  • XMLReaderAdapter.ListenerShallManageEventHandlers (cyclomatic 19) src/net/JNet/Generated/Org/Xml/Sax/Helpers/XMLReaderAdapter.cs:227 — XMLReaderAdapter.ListenerShallManageEventHandlers 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 · JNetHelper.listFromPrimitiveArray (cyclomatic 19) · ×1
  • JNetHelper.listFromPrimitiveArray (cyclomatic 19) src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java:33 — JNetHelper.listFromPrimitiveArray has cyclomatic complexity 19 (threshold 15). 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.
D1 · Cyclomatic Complexity · JNetReflectorExtensions.PropertyName (cyclomatic 18) · ×1
  • JNetReflectorExtensions.PropertyName (cyclomatic 18) src/net/JNetReflector/InternalExtensions.cs:2468 — JNetReflectorExtensions.PropertyName has cyclomatic complexity 18 (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. This is NOT this file's highest cyclomatic complexity: JNetReflectorExtensions.IsNetNativeType (cyclomatic 22) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · JNetReflectorExtensions.Type (cyclomatic 17) · ×1
  • JNetReflectorExtensions.Type (cyclomatic 17) src/net/JNetReflector/InternalExtensions.cs:615 — JNetReflectorExtensions.Type has cyclomatic complexity 17 (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. This is NOT this file's highest cyclomatic complexity: JNetReflectorExtensions.IsNetNativeType (cyclomatic 22) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · ReflectionUtils.AnalyzeOperators (cyclomatic 17) · ×1
  • ReflectionUtils.AnalyzeOperators (cyclomatic 17) src/net/JNetReflector/InternalMethods.cs:1141 — ReflectionUtils.AnalyzeOperators has cyclomatic complexity 17 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: src/net/JNetReflector/InternalMethods.cs holds 9 of the 23 methods over the threshold — including the worst — and 425 of the 671 points over it (63%), 2.9× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 147). 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 · ReflectionUtils.AnalyzeMethods (cognitive 671) · ×1
  • ReflectionUtils.AnalyzeMethods (cognitive 671) src/net/JNetReflector/InternalMethods.cs:1303 — ReflectionUtils.AnalyzeMethods has cognitive complexity 671 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: src/net/JNetReflector/InternalMethods.cs holds 9 of the 35 methods over the threshold — including the worst — and 1134 of the 1750 points over it (65%), 3.1× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 364). 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 · JNetReflectorExtensions.GetGenerics (cognitive 168) · ×1
  • JNetReflectorExtensions.GetGenerics (cognitive 168) src/net/JNetReflector/InternalExtensions.cs:964 — JNetReflectorExtensions.GetGenerics has cognitive complexity 168 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ReflectionUtils.AnalyzeJavaMethods (cognitive 151) · ×1
  • ReflectionUtils.AnalyzeJavaMethods (cognitive 151) src/net/JNetReflector/InternalMethods.cs:2222 — ReflectionUtils.AnalyzeJavaMethods has cognitive complexity 151 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: src/net/JNetReflector/InternalMethods.cs holds 9 of the 35 methods over the threshold — including the worst — and 1134 of the 1750 points over it (65%), 3.1× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 364). 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 · JNetReflectorCore.ProcessCommandLine (cognitive 128) · ×1
  • JNetReflectorCore.ProcessCommandLine (cognitive 128) src/net/JNetReflector/JNetReflectorCore.cs:603 — JNetReflectorCore.ProcessCommandLine has cognitive complexity 128 (threshold 15). 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 · ReflectionUtils.AnalyzeConstructors (cognitive 123) · ×1
  • ReflectionUtils.AnalyzeConstructors (cognitive 123) src/net/JNetReflector/InternalMethods.cs:931 — ReflectionUtils.AnalyzeConstructors has cognitive complexity 123 (threshold 15). 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: src/net/JNetReflector/InternalMethods.cs holds 9 of the 35 methods over the threshold — including the worst — and 1134 of the 1750 points over it (65%), 3.1× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 364). 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 · ReflectionUtils.PrepareSingleClass (cognitive 94) · ×1
  • ReflectionUtils.PrepareSingleClass (cognitive 94) src/net/JNetReflector/InternalMethods.cs:672 — ReflectionUtils.PrepareSingleClass has cognitive complexity 94 (threshold 15). 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: src/net/JNetReflector/InternalMethods.cs holds 9 of the 35 methods over the threshold — including the worst — and 1134 of the 1750 points over it (65%), 3.1× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 364). 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 · JNetReflectorExtensions.ToNetType (cognitive 82) · ×1
  • JNetReflectorExtensions.ToNetType (cognitive 82) src/net/JNetReflector/InternalExtensions.cs:2042 — JNetReflectorExtensions.ToNetType has cognitive complexity 82 (threshold 15). 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 · JNetReflectorHelper.ExtractJavaInfo (cognitive 66) · ×1
  • JNetReflectorHelper.ExtractJavaInfo (cognitive 66) src/net/JNetReflector/JNetReflectorHelper.cs:76 — JNetReflectorHelper.ExtractJavaInfo has cognitive complexity 66 (threshold 15). 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 · ReflectionUtils.AnalyzeNestedClasses (cognitive 65) · ×1
  • ReflectionUtils.AnalyzeNestedClasses (cognitive 65) src/net/JNetReflector/InternalMethods.cs:551 — ReflectionUtils.AnalyzeNestedClasses has cognitive complexity 65 (threshold 15). 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: src/net/JNetReflector/InternalMethods.cs holds 9 of the 35 methods over the threshold — including the worst — and 1134 of the 1750 points over it (65%), 3.1× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 364). 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 · JNetReflectorExtensions.JVMBaseClassName (cognitive 64) · ×1
  • JNetReflectorExtensions.JVMBaseClassName (cognitive 64) src/net/JNetReflector/InternalExtensions.cs:1424 — JNetReflectorExtensions.JVMBaseClassName has cognitive complexity 64 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ReflectionUtils.AnalyzeFields (cognitive 48) · ×1
  • ReflectionUtils.AnalyzeFields (cognitive 48) src/net/JNetReflector/InternalMethods.cs:2472 — ReflectionUtils.AnalyzeFields has cognitive complexity 48 (threshold 15). 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: src/net/JNetReflector/InternalMethods.cs holds 9 of the 35 methods over the threshold — including the worst — and 1134 of the 1750 points over it (65%), 3.1× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 364). 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 · ReflectionUtils.AnalyzeClasses (cognitive 42) · ×1
  • ReflectionUtils.AnalyzeClasses (cognitive 42) src/net/JNetReflector/InternalMethods.cs:397 — ReflectionUtils.AnalyzeClasses has cognitive complexity 42 (threshold 15). 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: src/net/JNetReflector/InternalMethods.cs holds 9 of the 35 methods over the threshold — including the worst — and 1134 of the 1750 points over it (65%), 3.1× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 364). 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 · JNetReflectorExtensions.Type (cognitive 40) · ×1
  • JNetReflectorExtensions.Type (cognitive 40) src/net/JNetReflector/InternalExtensions.cs:615 — JNetReflectorExtensions.Type has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ReflectionUtils.PrefilterMethods (cognitive 39) · ×1
  • ReflectionUtils.PrefilterMethods (cognitive 39) src/net/JNetReflector/InternalMethods.cs:1224 — ReflectionUtils.PrefilterMethods has cognitive complexity 39 (threshold 15). 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: src/net/JNetReflector/InternalMethods.cs holds 9 of the 35 methods over the threshold — including the worst — and 1134 of the 1750 points over it (65%), 3.1× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 364). 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 · ProgramBase.Start (cognitive 37) · ×1
  • ProgramBase.Start (cognitive 37) src/net/JNetCLICore/ProgramBase.cs:49 — ProgramBase.Start has cognitive complexity 37 (threshold 15). Of this number, 32 points are the body's own statements and 5 belong to one function literal inside it that branches. 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 · ReflectionUtils.AnalyzeOperators (cognitive 36) · ×1
  • ReflectionUtils.AnalyzeOperators (cognitive 36) src/net/JNetReflector/InternalMethods.cs:1141 — ReflectionUtils.AnalyzeOperators has cognitive complexity 36 (threshold 15). 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: src/net/JNetReflector/InternalMethods.cs holds 9 of the 35 methods over the threshold — including the worst — and 1134 of the 1750 points over it (65%), 3.1× the next-largest file (src/net/JNetReflector/InternalExtensions.cs at 364). 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 · JNetCLICoreHelper.ProcessCLIParsedArgs (cognitive 32) · ×1
  • JNetCLICoreHelper.ProcessCLIParsedArgs (cognitive 32) src/net/JNet/Specific/CLI/JNetCLICoreHelper.cs:346 — JNetCLICoreHelper.ProcessCLIParsedArgs has cognitive complexity 32 (threshold 15). 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 · JNetReflectorExtensions.WhereClauses (cognitive 28) · ×1
  • JNetReflectorExtensions.WhereClauses (cognitive 28) src/net/JNetReflector/InternalExtensions.cs:1250 — JNetReflectorExtensions.WhereClauses has cognitive complexity 28 (threshold 15). 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 · JNetPSHelperExtensions.InvokeExternal (cognitive 28) · ×1
  • JNetPSHelperExtensions.InvokeExternal (cognitive 28) src/net/JNetPSCore/JNetPSHelper.cs:65 — JNetPSHelperExtensions.InvokeExternal has cognitive complexity 28 (threshold 15). 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 · JNetReflectorExtensions.JVMGenericInterfaces (cognitive 27) · ×1
  • JNetReflectorExtensions.JVMGenericInterfaces (cognitive 27) src/net/JNetReflector/InternalExtensions.cs:1586 — JNetReflectorExtensions.JVMGenericInterfaces has cognitive complexity 27 (threshold 15). 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 · JNetHelper.listFromPrimitiveArray (cognitive 26) · ×1
  • JNetHelper.listFromPrimitiveArray (cognitive 26) src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java:33 — JNetHelper.listFromPrimitiveArray has cognitive complexity 26 (threshold 15). Drivers by points: loops 8 (16 pts), if/else 10 (nesting depth added 8). 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.
D2 · Cognitive Complexity · JNetCoreBase.Launch (cognitive 25) · ×1
  • JNetCoreBase.Launch (cognitive 25) src/net/JNet/JNetCoreBase.cs:440 — JNetCoreBase.Launch has cognitive complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · JNetReflectorExtensions.GetGenerics (cognitive 25) · ×1
  • JNetReflectorExtensions.GetGenerics (cognitive 25) src/net/JNetReflector/InternalExtensions.cs:458 — JNetReflectorExtensions.GetGenerics has cognitive complexity 25 (threshold 15). 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 · JNetReflectorExtensions.NeedsOperators (cognitive 24) · ×1
  • JNetReflectorExtensions.NeedsOperators (cognitive 24) src/net/JNetReflector/InternalExtensions.cs:1309 — JNetReflectorExtensions.NeedsOperators has cognitive complexity 24 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
D2 · Cognitive Complexity · JNetReflectorExtensions.JavadocUrl (cognitive 23) · ×1
  • JNetReflectorExtensions.JavadocUrl (cognitive 23) src/net/JNetReflector/InternalExtensions.cs:2263 — JNetReflectorExtensions.JavadocUrl has cognitive complexity 23 (threshold 15). 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 · ParserAdapter.ListenerShallManageEventHandlers (cognitive 22) · ×1
  • ParserAdapter.ListenerShallManageEventHandlers (cognitive 22) src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs:235 — ParserAdapter.ListenerShallManageEventHandlers has cognitive complexity 22 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
D2 · Cognitive Complexity · JNetReflectorExtensions.HasJVMBaseClassName (cognitive 21) · ×1
  • JNetReflectorExtensions.HasJVMBaseClassName (cognitive 21) src/net/JNetReflector/InternalExtensions.cs:1370 — JNetReflectorExtensions.HasJVMBaseClassName has cognitive complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · JNetReflectorExtensions.JavadocUrl (cognitive 19) · ×1
  • JNetReflectorExtensions.JavadocUrl (cognitive 19) src/net/JNetReflector/InternalExtensions.cs:2629 — JNetReflectorExtensions.JavadocUrl has cognitive complexity 19 (threshold 15). 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 · XMLReaderAdapter.ListenerShallManageEventHandlers (cognitive 18) · ×1
  • XMLReaderAdapter.ListenerShallManageEventHandlers (cognitive 18) src/net/JNet/Generated/Org/Xml/Sax/Helpers/XMLReaderAdapter.cs:227 — XMLReaderAdapter.ListenerShallManageEventHandlers has cognitive complexity 18 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
D2 · Cognitive Complexity · JNetHelper.ListFrom (cognitive 18) · ×1
  • JNetHelper.ListFrom (cognitive 18) src/net/JNet/Specific/JNetHelper.cs:92 — JNetHelper.ListFrom has cognitive complexity 18 (threshold 15). 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 · JNetReflectorExtensions.GetGenerics (cognitive 18) · ×1
  • JNetReflectorExtensions.GetGenerics (cognitive 18) src/net/JNetReflector/InternalExtensions.cs:850 — JNetReflectorExtensions.GetGenerics has cognitive complexity 18 (threshold 15). 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 · JNetReflectorExtensions.GetGenerics (cognitive 17) · ×1
  • JNetReflectorExtensions.GetGenerics (cognitive 17) src/net/JNetReflector/InternalExtensions.cs:877 — JNetReflectorExtensions.GetGenerics has cognitive complexity 17 (threshold 15). 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 · JNetReflectorExtensions.JVMInterfaces (cognitive 17) · ×1
  • JNetReflectorExtensions.JVMInterfaces (cognitive 17) src/net/JNetReflector/InternalExtensions.cs:1553 — JNetReflectorExtensions.JVMInterfaces has cognitive complexity 17 (threshold 15). 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 · JNetReflectorHelper.ExtractJavaInfo (cognitive 17) · ×1
  • JNetReflectorHelper.ExtractJavaInfo (cognitive 17) src/net/JNetReflector/JNetReflectorHelper.cs:225 — JNetReflectorHelper.ExtractJavaInfo has cognitive complexity 17 (threshold 15). 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 · JNetReflectorExtensions.TypeNameMustBeAvoided (cognitive 16) · ×1
  • JNetReflectorExtensions.TypeNameMustBeAvoided (cognitive 16) src/net/JNetReflector/InternalExtensions.cs:553 — JNetReflectorExtensions.TypeNameMustBeAvoided has cognitive complexity 16 (threshold 15). 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.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: ReflectionUtils src/net/JNetReflector/InternalMethods.cs — ClassTooLong — 1542 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 1142 over it, 3.86× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (45 corresponding lines) · ×1
  • Edited copy of a member (45 corresponding lines) src/net/JNetReflector/InternalExtensions.cs:2264 — src/net/JNetReflector/InternalExtensions.cs:2264-2313 | src/net/JNetReflector/InternalExtensions.cs:2630-2674 — These two members are one piece of code written twice and then edited apart: 45 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 (52 corresponding lines) · ×1
  • Edited copy of a member (52 corresponding lines) src/net/JNetReflector/InternalExtensions.cs:1310 — src/net/JNetReflector/InternalExtensions.cs:1310-1368 | src/net/JNetReflector/InternalExtensions.cs:1371-1422 — These two members are one piece of code written twice and then edited apart: 52 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 (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) src/net/JNetReflector/InternalExtensions.cs:459 — src/net/JNetReflector/InternalExtensions.cs:459-487 | src/net/JNetReflector/InternalExtensions.cs:851-875 — These two members are one piece of code written twice and then edited apart: 25 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 (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) src/net/JNetReflector/InternalExtensions.cs:1554 — src/net/JNetReflector/InternalExtensions.cs:1554-1584 | src/net/JNetReflector/InternalExtensions.cs:1587-1621 — These two members are one piece of code written twice and then edited apart: 31 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 (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:264 — src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:264-291 | src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:339-366 — These two members are one piece of code written twice and then edited apart: 28 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) src/net/JNetReflector/InternalExtensions.cs:541 — src/net/JNetReflector/InternalExtensions.cs:541-547 | src/net/JNetReflector/InternalExtensions.cs:1664-1670 — 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 · Edited copies of one member (7 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 11+ corresponding lines) src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java:98 — src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java:98-108 | src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java:110-120 | src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java:122-132 | src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java:134-144 | src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java:146-156 | src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java:158-168 | src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java:170-180 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 11 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 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:305 — src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:305-321 | src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:380-394 — 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 copies of one member (3 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:264 — src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:264-291 | src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:339-366 | src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:380-394 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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 (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) src/net/JNetReflector/InternalExtensions.cs:2374 — src/net/JNetReflector/InternalExtensions.cs:2374-2383 | src/net/JNetReflector/InternalExtensions.cs:2386-2395 — 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 (37 lines × 2) · ×1
  • Duplicated block (37 lines × 2) src/net/JNetPS/Cmdlet/JMX/AddNotificationListenerCmdletCommand.cs:30 — src/net/JNetPS/Cmdlet/JMX/AddNotificationListenerCmdletCommand.cs:30-66 | src/net/JNetPS/Cmdlet/JMX/RemoveNotificationListenerCmdletCommand.cs:30-66 — before extracting anything, compare `src/net/JNetPS/Cmdlet/JMX/AddNotificationListenerCmdletCommand.cs` and `src/net/JNetPS/Cmdlet/JMX/RemoveNotificationListenerCmdletCommand.cs` as WHOLE FILES: 93% 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. 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 (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) src/net/JNetReflector/InternalExtensions.cs:1015 — src/net/JNetReflector/InternalExtensions.cs:1015-1034 | src/net/JNetReflector/InternalExtensions.cs:1092-1111 — 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 `src/net/JNetReflector/InternalExtensions.cs:1015` 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 (33 lines × 2) · ×1
  • Duplicated block (33 lines × 2) src/net/JNetPS/Cmdlet/JMX/NewMBeanProxyCmdletCommand.cs:31 — src/net/JNetPS/Cmdlet/JMX/NewMBeanProxyCmdletCommand.cs:31-63 | src/net/JNetPS/Cmdlet/JMX/NewMXBeanProxyCmdletCommand.cs:31-63 — before extracting anything, compare `src/net/JNetPS/Cmdlet/JMX/NewMBeanProxyCmdletCommand.cs` and `src/net/JNetPS/Cmdlet/JMX/NewMXBeanProxyCmdletCommand.cs` as WHOLE FILES: 82% 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. 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 (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) src/net/JNetReflector/InternalMethods.cs:599 — src/net/JNetReflector/InternalMethods.cs:599-622 | src/net/JNetReflector/InternalMethods.cs:640-663 — 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 (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) src/net/JNetReflector/InternalExtensions.cs:1560 — src/net/JNetReflector/InternalExtensions.cs:1560-1578 | src/net/JNetReflector/InternalExtensions.cs:1597-1615 — 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 `src/net/JNetReflector/InternalExtensions.cs:1560` 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 (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) src/net/JNetReflector/Program.cs:52 — src/net/JNetReflector/Program.cs:52-69 | src/net/JNetReflector/Program.cs:73-90 — 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 `src/net/JNetReflector/Program.cs:52` 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 (15 lines × 5) · ×1
  • Duplicated block (15 lines × 5) src/net/JNetPS/Cmdlet/JMX/InvokeQueryEqCmdletCommand.cs:29 — src/net/JNetPS/Cmdlet/JMX/InvokeQueryEqCmdletCommand.cs:29-43 | src/net/JNetPS/Cmdlet/JMX/InvokeQueryGeqCmdletCommand.cs:29-43 | src/net/JNetPS/Cmdlet/JMX/InvokeQueryGtCmdletCommand.cs:29-43 | src/net/JNetPS/Cmdlet/JMX/InvokeQueryLeqCmdletCommand.cs:29-43 | src/net/JNetPS/Cmdlet/JMX/InvokeQueryLtCmdletCommand.cs:29-43 — before extracting anything, compare `src/net/JNetPS/Cmdlet/JMX/InvokeQueryEqCmdletCommand.cs` and `src/net/JNetPS/Cmdlet/JMX/InvokeQueryGeqCmdletCommand.cs` as WHOLE FILES: 88% 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. 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 (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) src/net/JNetPS/Cmdlet/JMX/InvokeQueryAnySubStringCmdletCommand.cs:29 — src/net/JNetPS/Cmdlet/JMX/InvokeQueryAnySubStringCmdletCommand.cs:29-43 | src/net/JNetPS/Cmdlet/JMX/InvokeQueryFinalSubStringCmdletCommand.cs:29-43 | src/net/JNetPS/Cmdlet/JMX/InvokeQueryInitialSubStringCmdletCommand.cs:29-43 — before extracting anything, compare `src/net/JNetPS/Cmdlet/JMX/InvokeQueryAnySubStringCmdletCommand.cs` and `src/net/JNetPS/Cmdlet/JMX/InvokeQueryFinalSubStringCmdletCommand.cs` as WHOLE FILES: 88% 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. 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 (13 lines × 4) · ×1
  • Duplicated block (13 lines × 4) src/net/JNetPS/Cmdlet/JMX/InvokeQueryAnySubStringCmdletCommand.cs:29 — src/net/JNetPS/Cmdlet/JMX/InvokeQueryAnySubStringCmdletCommand.cs:29-41 | src/net/JNetPS/Cmdlet/JMX/InvokeQueryFinalSubStringCmdletCommand.cs:29-41 | src/net/JNetPS/Cmdlet/JMX/InvokeQueryInitialSubStringCmdletCommand.cs:29-41 | src/net/JNetPS/Cmdlet/JMX/InvokeQueryMatchCmdletCommand.cs:29-41 — before extracting anything, compare `src/net/JNetPS/Cmdlet/JMX/InvokeQueryAnySubStringCmdletCommand.cs` and `src/net/JNetPS/Cmdlet/JMX/InvokeQueryFinalSubStringCmdletCommand.cs` as WHOLE FILES: 88% 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. 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 `src/net/JNetPS/Cmdlet/JMX/InvokeQueryAnySubStringCmdletCommand.cs:29` 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 (11–16 lines × 3) · ×1
  • Duplicated block (11–16 lines × 3) src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:276 — src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:276-291 | src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:351-366 | src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:384-394 — all 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:276` 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.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1
  • Duplicated block (9 lines × 2) src/net/JNet/JNetCoreBase.cs:315 — src/net/JNet/JNetCoreBase.cs:315-323 | src/net/JNet/JNetCoreBase.cs:327-335 — 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 (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) src/net/JNetReflector/InternalExtensions.cs:1319 — src/net/JNetReflector/InternalExtensions.cs:1319-1326 | src/net/JNetReflector/InternalExtensions.cs:1383-1390 | src/net/JNetReflector/InternalExtensions.cs:1448-1455 — all 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/net/JNetReflector/InternalExtensions.cs:1319` 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 (9–10 lines × 2) · ×1
  • Duplicated block (9–10 lines × 2) src/net/JNetReflector/InternalMethods.cs:1911 — src/net/JNetReflector/InternalMethods.cs:1911-1919 | src/net/JNetReflector/InternalMethods.cs:1923-1932 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/net/JNetReflector/InternalMethods.cs:1910` calls `IsStatic` and `src/net/JNetReflector/InternalMethods.cs:1922` 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 (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) src/net/JNetReflector/InternalMethods.cs:2069 — src/net/JNetReflector/InternalMethods.cs:2069-2074 | src/net/JNetReflector/InternalMethods.cs:2099-2104 | src/net/JNetReflector/InternalMethods.cs:2171-2176 | src/net/JNetReflector/InternalMethods.cs:2201-2206 — all 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/net/JNetReflector/InternalMethods.cs:2069` 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. 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 after the matched lines, `src/net/JNetReflector/InternalMethods.cs:2104` calls `StringBuilder` and `src/net/JNetReflector/InternalMethods.cs:2176` 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 (4–5 lines × 5) · ×1
  • Duplicated block (4–5 lines × 5) src/net/JNetReflector/InternalMethods.cs:2028 — src/net/JNetReflector/InternalMethods.cs:2028-2032 | src/net/JNetReflector/InternalMethods.cs:2058-2062 | src/net/JNetReflector/InternalMethods.cs:2088-2092 | src/net/JNetReflector/InternalMethods.cs:2162-2165 | src/net/JNetReflector/InternalMethods.cs:2192-2195 — all 5 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 after the matched lines, `src/net/JNetReflector/InternalMethods.cs:2032` calls `Replace` and `src/net/JNetReflector/InternalMethods.cs:2165` does not — after which the two agree again for 5 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 (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) src/net/JNetPS/Cmdlet/JMX/NewMBeanProxyCmdletCommand.cs:68 — src/net/JNetPS/Cmdlet/JMX/NewMBeanProxyCmdletCommand.cs:68-94 | src/net/JNetPS/Cmdlet/JMX/NewMXBeanProxyCmdletCommand.cs:68-94 — before extracting anything, compare `src/net/JNetPS/Cmdlet/JMX/NewMBeanProxyCmdletCommand.cs` and `src/net/JNetPS/Cmdlet/JMX/NewMXBeanProxyCmdletCommand.cs` as WHOLE FILES: 82% 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. 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.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: JNet(net462) src/net/JNet/JNet.csproj:1 — JNet(net462): abstractness 0.21, instability 0.00, distance 0.79 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
X5 · Nullable reference types · Null guard scopes only part of the work it protects · ×1
  • Null guard scopes only part of the work it protects src/net/JNetReflector/InternalMethods.cs:157 — This method contradicts itself about `jClass`: line 156 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 157 then dereferences `jClass` as `jClass.Classes` AFTER the block has closed, where the guard no longer applies. A null `jClass` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `jClass` truly cannot be null by then, the guard above is misleading and should go.
Minor — 141 finding(s)
AX6 · Interface segregation · Fat interface · ×40
  • Fat interface: IInputMethod (16 members) src/net/JNet/Generated/Java/Awt/Im/Spi/InputMethod.cs:66 — `IInputMethod` declares 16 members: `ControlObject`, `Locale`, `IsCompositionEnabled`, `SetLocale`, `Activate`, `Deactivate`, `DispatchEvent`, `DisposeJVM`, `EndComposition`, `HideWindows`, `NotifyClientWindowChange`, `Reconvert`, `RemoveNotify`, `SetCharacterSubsets`, `SetCompositionEnabled`, `SetInputMethodContext`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IRenderedImage (21 members) src/net/JNet/Generated/Java/Awt/ImageNs/RenderedImage.cs:66 — `IRenderedImage` declares 21 members: `ColorModel`, `Data`, `Height`, `MinTileX`, `MinTileY`, `MinX`, `MinY`, `NumXTiles`, `NumYTiles`, `PropertyNames`, `SampleModel`, `Sources`, `TileGridXOffset`, `TileGridYOffset`, `TileHeight`, `TileWidth`, `Width`, `GetData`, `GetTile`, `CopyData`, `GetProperty`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IMemoryPoolMXBean (16 members) src/net/JNet/Generated/Java/Lang/Management/MemoryPoolMXBean.cs:66 — `IMemoryPoolMXBean` declares 16 members: `CollectionUsage`, `CollectionUsageThreshold`, `CollectionUsageThresholdCount`, `MemoryManagerNames`, `Name`, `PeakUsage`, `Type`, `Usage`, `UsageThreshold`, `UsageThresholdCount`, `IsCollectionUsageThresholdExceeded`, `IsCollectionUsageThresholdSupported`, `IsUsageThresholdExceeded`, `IsUsageThresholdSupported`, `IsValid`, `ResetPeakUsage`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IRuntimeMXBean (16 members) src/net/JNet/Generated/Java/Lang/Management/RuntimeMXBean.cs:66 — `IRuntimeMXBean` declares 16 members: `BootClassPath`, `ClassPath`, `InputArguments`, `LibraryPath`, `ManagementSpecVersion`, `Name`, `SpecName`, `SpecVendor`, `SpecVersion`, `StartTime`, `SystemProperties`, `Uptime`, `VmName`, `VmVendor`, `VmVersion`, `IsBootClassPathSupported`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IThreadMXBean (27 members) src/net/JNet/Generated/Java/Lang/Management/ThreadMXBean.cs:66 — `IThreadMXBean` declares 27 members: `AllThreadIds`, `CurrentThreadCpuTime`, `CurrentThreadUserTime`, `DaemonThreadCount`, `PeakThreadCount`, `ThreadCount`, `TotalStartedThreadCount`, `IsCurrentThreadCpuTimeSupported`, `IsObjectMonitorUsageSupported`, `IsSynchronizerUsageSupported`, `IsThreadContentionMonitoringEnabled`, `IsThreadContentionMonitoringSupported`, `IsThreadCpuTimeEnabled`, `IsThreadCpuTimeSupported`, `GetThreadInfo`, `GetThreadInfo`, `DumpAllThreads`, `GetThreadInfo`, `GetThreadInfo`, `GetThreadInfo`, `GetThreadCpuTime`, `GetThreadUserTime`, `FindDeadlockedThreads`, `FindMonitorDeadlockedThreads`, `ResetPeakThreadCount`, `SetThreadContentionMonitoringEnabled`, `SetThreadCpuTimeEnabled`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 27 declarations carry 23 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 23 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IPath (27 members) src/net/JNet/Generated/Java/Nio/File/Path.cs:66 — `IPath` declares 27 members: `FileName`, `FileSystem`, `NameCount`, `Parent`, `Root`, `EndsWith`, `EndsWith`, `IsAbsolute`, `StartsWith`, `StartsWith`, `CompareTo`, `ToFile`, `ToUri`, `GetName`, `Normalize`, `Relativize`, `Resolve`, `Resolve`, `ResolveSibling`, `ResolveSibling`, `Subpath`, `ToAbsolutePath`, `ToRealPath`, `Register`, `Register`, `Iterator`, `CompareTo`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 27 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IChronoLocalDate (25 members) src/net/JNet/Generated/Java/Time/Chrono/ChronoLocalDate.cs:66 — `IChronoLocalDate` declares 25 members: `Chronology`, `Era`, `LengthOfMonth`, `Until`, `Until`, `Query`, `IsAfter`, `IsBefore`, `IsEqual`, `IsLeapYear`, `IsSupported`, `IsSupported`, `CompareTo`, `CompareTo`, `LengthOfYear`, `Format`, `AtTime`, `AdjustInto`, `Minus`, `Minus`, `Plus`, `Plus`, `With`, `With`, `ToEpochDay`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 25 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IChronology (24 members) src/net/JNet/Generated/Java/Time/Chrono/Chronology.cs:66 — `IChronology` declares 24 members: `CalendarType`, `Id`, `IsLeapYear`, `CompareTo`, `ProlepticYear`, `Date`, `Date`, `DateEpochDay`, `DateYearDay`, `ResolveDate`, `EraOf`, `Range`, `Eras`, `CompareTo`, `GetDisplayName`, `Date`, `DateNow`, `DateNow`, `DateNow`, `DateYearDay`, `LocalDateTime`, `Period`, `ZonedDateTime`, `ZonedDateTime`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 24 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: ICollection<E> (17 members) src/net/JNet/Generated/Java/Util/Collection.cs:276 — `ICollection<E>` declares 17 members: `ToArray`, `Add`, `AddAll`, `Contains`, `ContainsAll`, `IsEmpty`, `Remove`, `RemoveAll`, `RetainAll`, `Size`, `ToArray`, `Iterator`, `Clear`, `RemoveIf`, `Spliterator`, `ParallelStream`, `Stream`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 17 declarations carry 16 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 16 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IDeque<E> (27 members) src/net/JNet/Generated/Java/Util/Deque.cs:354 — `IDeque<E>` declares 27 members: `First`, `Last`, `Add`, `Contains`, `Offer`, `OfferFirst`, `OfferLast`, `Remove`, `RemoveFirstOccurrence`, `RemoveLastOccurrence`, `Element`, `Peek`, `PeekFirst`, `PeekLast`, `Poll`, `PollFirst`, `PollLast`, `Pop`, `Remove`, `RemoveFirst`, `RemoveLast`, `Size`, `DescendingIterator`, `Iterator`, `AddFirst`, `AddLast`, `Push`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 27 declarations carry 26 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 26 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IList<E> (26 members) src/net/JNet/Generated/Java/Util/List.cs:359 — `IList<E>` declares 26 members: `ToArray`, `Add`, `AddAll`, `AddAll`, `Contains`, `ContainsAll`, `IsEmpty`, `Remove`, `RemoveAll`, `RetainAll`, `Get`, `Remove`, `Set`, `IndexOf`, `LastIndexOf`, `Size`, `ToArray`, `Iterator`, `SubList`, `ListIterator`, `ListIterator`, `Add`, `Clear`, `Spliterator`, `ReplaceAll`, `Sort`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 26 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IMap<K, V> (23 members) src/net/JNet/Generated/Java/Util/Map.cs:594 — `IMap<K, V>` declares 23 members: `ContainsKey`, `ContainsValue`, `IsEmpty`, `Size`, `Values`, `EntrySet`, `KeySet`, `Get`, `Put`, `Remove`, `Clear`, `PutAll`, `Remove`, `Replace`, `Compute`, `ComputeIfAbsent`, `ComputeIfPresent`, `GetOrDefault`, `Merge`, `PutIfAbsent`, `Replace`, `ForEach`, `ReplaceAll`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 23 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: INavigableMap<K, V> (21 members) src/net/JNet/Generated/Java/Util/NavigableMap.cs:321 — `INavigableMap<K, V>` declares 21 members: `CeilingEntry`, `FirstEntry`, `FloorEntry`, `HigherEntry`, `LastEntry`, `LowerEntry`, `PollFirstEntry`, `PollLastEntry`, `DescendingMap`, `HeadMap`, `SubMap`, `TailMap`, `DescendingKeySet`, `NavigableKeySet`, `HeadMap`, `SubMap`, `TailMap`, `CeilingKey`, `FloorKey`, `HigherKey`, `LowerKey`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 21 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IBlockingDeque<E> (29 members) src/net/JNet/Generated/Java/Util/Concurrent/BlockingDeque.cs:407 — `IBlockingDeque<E>` declares 29 members: `Add`, `Contains`, `Offer`, `Offer`, `OfferFirst`, `OfferFirst`, `OfferLast`, `OfferLast`, `Remove`, `RemoveFirstOccurrence`, `RemoveLastOccurrence`, `Element`, `Peek`, `Poll`, `Poll`, `PollFirst`, `PollLast`, `Remove`, `Take`, `TakeFirst`, `TakeLast`, `Size`, `Iterator`, `AddFirst`, `AddLast`, `Push`, `Put`, `PutFirst`, `PutLast`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 29 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: ICompletionStage<T> (38 members) src/net/JNet/Generated/Java/Util/Concurrent/CompletionStage.cs:503 — `ICompletionStage<T>` declares 38 members: `ThenCombine`, `ThenCombineAsync`, `ThenCombineAsync`, `ThenAcceptBoth`, `ThenAcceptBothAsync`, `ThenAcceptBothAsync`, `ApplyToEither`, `ApplyToEitherAsync`, `ApplyToEitherAsync`, `Handle`, `HandleAsync`, `HandleAsync`, `ThenApply`, `ThenApplyAsync`, `ThenApplyAsync`, `ThenCompose`, `ThenComposeAsync`, `ThenComposeAsync`, `ToCompletableFuture`, `AcceptEither`, `AcceptEitherAsync`, `AcceptEitherAsync`, `RunAfterBoth`, `RunAfterBothAsync`, `RunAfterBothAsync`, `RunAfterEither`, `RunAfterEitherAsync`, `RunAfterEitherAsync`, `ThenAccept`, `ThenAcceptAsync`, `ThenAcceptAsync`, `ThenRun`, `ThenRunAsync`, `ThenRunAsync`, `Exceptionally`, `WhenComplete`, `WhenCompleteAsync`, `WhenCompleteAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 38 declarations carry 26 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 26 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IDoubleStream (33 members) src/net/JNet/Generated/Java/Util/Stream/DoubleStream.cs:66 — `IDoubleStream` declares 33 members: `Collect`, `MapToObj`, `AllMatch`, `AnyMatch`, `NoneMatch`, `Reduce`, `Sum`, `ToArray`, `SummaryStatistics`, `Average`, `FindAny`, `FindFirst`, `Max`, `Min`, `Reduce`, `Distinct`, `Filter`, `FlatMap`, `Limit`, `Map`, `Peek`, `Skip`, `Sorted`, `MapToInt`, `MapToLong`, `Boxed`, `Count`, `ForEach`, `ForEachOrdered`, `Iterator`, `Spliterator`, `Parallel`, `Sequential`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 33 declarations carry 32 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 32 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IIntStream (35 members) src/net/JNet/Generated/Java/Util/Stream/IntStream.cs:66 — `IIntStream` declares 35 members: `Collect`, `MapToObj`, `AllMatch`, `AnyMatch`, `NoneMatch`, `Reduce`, `Sum`, `ToArray`, `SummaryStatistics`, `Average`, `FindAny`, `FindFirst`, `Max`, `Min`, `Reduce`, `AsDoubleStream`, `MapToDouble`, `Distinct`, `Filter`, `FlatMap`, `Limit`, `Map`, `Peek`, `Skip`, `Sorted`, `AsLongStream`, `MapToLong`, `Boxed`, `Count`, `ForEach`, `ForEachOrdered`, `Iterator`, `Spliterator`, `Parallel`, `Sequential`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 35 declarations carry 34 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 34 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: ILongStream (34 members) src/net/JNet/Generated/Java/Util/Stream/LongStream.cs:66 — `ILongStream` declares 34 members: `Collect`, `MapToObj`, `AllMatch`, `AnyMatch`, `NoneMatch`, `SummaryStatistics`, `Average`, `FindAny`, `FindFirst`, `Max`, `Min`, `Reduce`, `AsDoubleStream`, `MapToDouble`, `MapToInt`, `Distinct`, `Filter`, `FlatMap`, `Limit`, `Map`, `Peek`, `Skip`, `Sorted`, `Boxed`, `Count`, `Reduce`, `Sum`, `ToArray`, `ForEach`, `ForEachOrdered`, `Iterator`, `Spliterator`, `Parallel`, `Sequential`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 34 declarations carry 33 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 33 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IStream<T> (32 members) src/net/JNet/Generated/Java/Util/Stream/Stream.cs:472 — `IStream<T>` declares 32 members: `ToArray`, `Collect`, `FlatMap`, `Map`, `Collect`, `Reduce`, `AllMatch`, `AnyMatch`, `NoneMatch`, `ToArray`, `FindAny`, `FindFirst`, `Max`, `Min`, `Reduce`, `FlatMapToDouble`, `MapToDouble`, `FlatMapToInt`, `MapToInt`, `FlatMapToLong`, `MapToLong`, `Distinct`, `Filter`, `Limit`, `Peek`, `Skip`, `Sorted`, `Sorted`, `Count`, `Reduce`, `ForEach`, `ForEachOrdered`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 32 declarations carry 27 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 27 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: ICallableStatement (121 members) src/net/JNet/Generated/Java/Sql/CallableStatement.cs:66 — `ICallableStatement` declares 121 members: `GetObject`, `GetObject`, `GetBoolean`, `GetBoolean`, `WasNull`, `GetByte`, `GetByte`, `GetBytes`, `GetBytes`, `GetDouble`, `GetDouble`, `GetFloat`, `GetFloat`, `GetInt`, `GetInt`, `GetCharacterStream`, `GetCharacterStream`, `GetNCharacterStream`, `GetNCharacterStream`, `GetObject`, `GetObject`, `GetObject`, `GetObject`, `GetNString`, `GetNString`, `GetString`, `GetString`, `GetBigDecimal`, `GetBigDecimal`, `GetBigDecimal`, `GetURL`, `GetURL`, `GetArray`, `GetArray`, `GetBlob`, `GetBlob`, `GetClob`, `GetClob`, `GetDate`, `GetDate`, and 81 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 121 declarations carry 53 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 53 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IConnection (45 members) src/net/JNet/Generated/Java/Sql/Connection.cs:66 — `IConnection` declares 45 members: `AutoCommit`, `Catalog`, `ClientInfo`, `Holdability`, `MetaData`, `NetworkTimeout`, `Schema`, `TransactionIsolation`, `TypeMap`, `Warnings`, `IsClosed`, `IsReadOnly`, `IsValid`, `GetClientInfo`, `NativeSQL`, `CreateArrayOf`, `CreateBlob`, `PrepareCall`, `PrepareCall`, `PrepareCall`, `CreateClob`, `CreateNClob`, `PrepareStatement`, `PrepareStatement`, `PrepareStatement`, `PrepareStatement`, `PrepareStatement`, `PrepareStatement`, `SetSavepoint`, `SetSavepoint`, `CreateSQLXML`, `CreateStatement`, `CreateStatement`, `CreateStatement`, `CreateStruct`, `Abort`, `ClearWarnings`, `Close`, `Commit`, `ReleaseSavepoint`, and 5 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 45 declarations carry 34 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 34 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IDatabaseMetaData (176 members) src/net/JNet/Generated/Java/Sql/DatabaseMetaData.cs:66 — `IDatabaseMetaData` declares 176 members: `Catalogs`, `CatalogSeparator`, `CatalogTerm`, `ClientInfoProperties`, `Connection`, `DatabaseMajorVersion`, `DatabaseMinorVersion`, `DatabaseProductName`, `DatabaseProductVersion`, `DefaultTransactionIsolation`, `DriverMajorVersion`, `DriverMinorVersion`, `DriverName`, `DriverVersion`, `ExtraNameCharacters`, `IdentifierQuoteString`, `JDBCMajorVersion`, `JDBCMinorVersion`, `MaxBinaryLiteralLength`, `MaxCatalogNameLength`, `MaxCharLiteralLength`, `MaxColumnNameLength`, `MaxColumnsInGroupBy`, `MaxColumnsInIndex`, `MaxColumnsInOrderBy`, `MaxColumnsInSelect`, `MaxColumnsInTable`, `MaxConnections`, `MaxCursorNameLength`, `MaxIndexLength`, `MaxLogicalLobSize`, `MaxProcedureNameLength`, `MaxRowSize`, `MaxSchemaNameLength`, `MaxStatementLength`, `MaxStatements`, `MaxTableNameLength`, `MaxTablesInSelect`, `MaxUserNameLength`, `NumericFunctions`, and 136 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 176 declarations carry 175 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 175 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IPreparedStatement (58 members) src/net/JNet/Generated/Java/Sql/PreparedStatement.cs:66 — `IPreparedStatement` declares 58 members: `MetaData`, `ParameterMetaData`, `Execute`, `ExecuteUpdate`, `ExecuteQuery`, `AddBatch`, `ClearParameters`, `SetArray`, `SetAsciiStream`, `SetAsciiStream`, `SetAsciiStream`, `SetBigDecimal`, `SetBinaryStream`, `SetBinaryStream`, `SetBinaryStream`, `SetBlob`, `SetBlob`, `SetBlob`, `SetBoolean`, `SetByte`, `SetBytes`, `SetCharacterStream`, `SetCharacterStream`, `SetCharacterStream`, `SetClob`, `SetClob`, `SetClob`, `SetDate`, `SetDate`, `SetDouble`, `SetFloat`, `SetInt`, `SetLong`, `SetNCharacterStream`, `SetNCharacterStream`, `SetNClob`, `SetNClob`, `SetNClob`, `SetNString`, `SetNull`, and 18 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 58 declarations carry 37 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 37 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IResultSet (191 members) src/net/JNet/Generated/Java/Sql/ResultSet.cs:66 — `IResultSet` declares 191 members: `Concurrency`, `CursorName`, `FetchDirection`, `FetchSize`, `Holdability`, `MetaData`, `Row`, `Statement`, `Type`, `Warnings`, `GetObject`, `GetObject`, `Absolute`, `First`, `GetBoolean`, `GetBoolean`, `IsAfterLast`, `IsBeforeFirst`, `IsClosed`, `IsFirst`, `IsLast`, `Last`, `Next`, `Previous`, `Relative`, `RowDeleted`, `RowInserted`, `RowUpdated`, `WasNull`, `GetByte`, `GetByte`, `GetBytes`, `GetBytes`, `GetDouble`, `GetDouble`, `GetFloat`, `GetFloat`, `FindColumn`, `GetInt`, `GetInt`, and 151 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 191 declarations carry 92 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 92 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IResultSetMetaData (21 members) src/net/JNet/Generated/Java/Sql/ResultSetMetaData.cs:66 — `IResultSetMetaData` declares 21 members: `ColumnCount`, `IsAutoIncrement`, `IsCaseSensitive`, `IsCurrency`, `IsDefinitelyWritable`, `IsReadOnly`, `IsSearchable`, `IsSigned`, `IsWritable`, `GetColumnDisplaySize`, `GetColumnType`, `GetPrecision`, `GetScale`, `IsNullable`, `GetCatalogName`, `GetColumnClassName`, `GetColumnLabel`, `GetColumnName`, `GetColumnTypeName`, `GetSchemaName`, `GetTableName`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • + 15 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate src/net/JNetReflector/InternalExtensions.cs:1908 — `!JNetReflectorCore.ReflectDeprecated && entry.IsDeprecated()` appears character-identically in 2 files — src/net/JNetReflector/InternalExtensions.cs, src/net/JNetReflector/InternalMethods.cs. 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 src/net/JNet/Generated/Java/Awt/EventNs/ActionListener.cs:223 — `_hasOverrideActionPerformed || OnActionPerformed != null` appears character-identically in 2 files — src/net/JNet/Generated/Java/Awt/EventNs/ActionListener.cs, src/net/JNet/Generated/Javax/Swing/Action.cs. 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 src/net/JNet/Generated/Java/Awt/EventNs/HierarchyBoundsAdapter.cs:210 — `_hasOverrideAncestorMoved || OnAncestorMoved != null` appears character-identically in 3 files — src/net/JNet/Generated/Java/Awt/EventNs/HierarchyBoundsAdapter.cs, src/net/JNet/Generated/Java/Awt/EventNs/HierarchyBoundsListener.cs, src/net/JNet/Generated/Javax/Swing/Event/AncestorListener.cs. 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 src/net/JNet/Generated/Java/Awt/EventNs/HierarchyBoundsAdapter.cs:252 — `_hasOverrideAncestorResized || OnAncestorResized != null` appears character-identically in 2 files — src/net/JNet/Generated/Java/Awt/EventNs/HierarchyBoundsAdapter.cs, src/net/JNet/Generated/Java/Awt/EventNs/HierarchyBoundsListener.cs. 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 src/net/JNet/Generated/Javax/Print/Event/PrintJobAttributeListener.cs:223 — `_hasOverrideAttributeUpdate || OnAttributeUpdate != null` appears character-identically in 2 files — src/net/JNet/Generated/Javax/Print/Event/PrintJobAttributeListener.cs, src/net/JNet/Generated/Javax/Print/Event/PrintServiceAttributeListener.cs. 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 src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs:604 — `_hasOverrideCharacters || OnCharacters != null` appears character-identically in 2 files — src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs, src/net/JNet/Generated/Org/Xml/Sax/Helpers/XMLReaderAdapter.cs. 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 src/net/JNet/Generated/Java/Awt/EventNs/ContainerAdapter.cs:210 — `_hasOverrideComponentAdded || OnComponentAdded != null` appears character-identically in 2 files — src/net/JNet/Generated/Java/Awt/EventNs/ContainerAdapter.cs, src/net/JNet/Generated/Java/Awt/EventNs/ContainerListener.cs. 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 src/net/JNet/Generated/Java/Awt/EventNs/ComponentAdapter.cs:216 — `_hasOverrideComponentHidden || OnComponentHidden != null` appears character-identically in 2 files — src/net/JNet/Generated/Java/Awt/EventNs/ComponentAdapter.cs, src/net/JNet/Generated/Java/Awt/EventNs/ComponentListener.cs. 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 src/net/JNet/Generated/Java/Awt/EventNs/ComponentAdapter.cs:258 — `_hasOverrideComponentMoved || OnComponentMoved != null` appears character-identically in 2 files — src/net/JNet/Generated/Java/Awt/EventNs/ComponentAdapter.cs, src/net/JNet/Generated/Java/Awt/EventNs/ComponentListener.cs. 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 src/net/JNet/Generated/Java/Awt/EventNs/ContainerAdapter.cs:252 — `_hasOverrideComponentRemoved || OnComponentRemoved != null` appears character-identically in 2 files — src/net/JNet/Generated/Java/Awt/EventNs/ContainerAdapter.cs, src/net/JNet/Generated/Java/Awt/EventNs/ContainerListener.cs. 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 src/net/JNet/Generated/Java/Awt/EventNs/ComponentAdapter.cs:300 — `_hasOverrideComponentResized || OnComponentResized != null` appears character-identically in 2 files — src/net/JNet/Generated/Java/Awt/EventNs/ComponentAdapter.cs, src/net/JNet/Generated/Java/Awt/EventNs/ComponentListener.cs. 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 src/net/JNet/Generated/Java/Awt/EventNs/ComponentAdapter.cs:342 — `_hasOverrideComponentShown || OnComponentShown != null` appears character-identically in 2 files — src/net/JNet/Generated/Java/Awt/EventNs/ComponentAdapter.cs, src/net/JNet/Generated/Java/Awt/EventNs/ComponentListener.cs. 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 src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs:222 — `_hasOverrideDragDropEnd || OnDragDropEnd != null` appears character-identically in 2 files — src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs, src/net/JNet/Generated/Java/Awt/Dnd/DragSourceListener.cs. 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 src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs:264 — `_hasOverrideDragEnter || OnDragEnter != null` appears character-identically in 4 files — src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs, src/net/JNet/Generated/Java/Awt/Dnd/DragSourceListener.cs, src/net/JNet/Generated/Java/Awt/Dnd/DropTargetAdapter.cs, src/net/JNet/Generated/Java/Awt/Dnd/DropTargetListener.cs. 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 src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs:306 — `_hasOverrideDragExit || OnDragExit != null` appears character-identically in 4 files — src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs, src/net/JNet/Generated/Java/Awt/Dnd/DragSourceListener.cs, src/net/JNet/Generated/Java/Awt/Dnd/DropTargetAdapter.cs, src/net/JNet/Generated/Java/Awt/Dnd/DropTargetListener.cs. 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 src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs:348 — `_hasOverrideDragMouseMoved || OnDragMouseMoved != null` appears character-identically in 2 files — src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs, src/net/JNet/Generated/Java/Awt/Dnd/DragSourceMotionListener.cs. 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 src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs:390 — `_hasOverrideDragOver || OnDragOver != null` appears character-identically in 4 files — src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs, src/net/JNet/Generated/Java/Awt/Dnd/DragSourceListener.cs, src/net/JNet/Generated/Java/Awt/Dnd/DropTargetAdapter.cs, src/net/JNet/Generated/Java/Awt/Dnd/DropTargetListener.cs. 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 src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs:432 — `_hasOverrideDropActionChanged || OnDropActionChanged != null` appears character-identically in 4 files — src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs, src/net/JNet/Generated/Java/Awt/Dnd/DragSourceListener.cs, src/net/JNet/Generated/Java/Awt/Dnd/DropTargetAdapter.cs, src/net/JNet/Generated/Java/Awt/Dnd/DropTargetListener.cs. 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 src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs:649 — `_hasOverrideEndDocument || OnEndDocument != null` appears character-identically in 2 files — src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs, src/net/JNet/Generated/Org/Xml/Sax/Helpers/XMLReaderAdapter.cs. 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 src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs:691 — `_hasOverrideEndElement || OnEndElement != null` appears character-identically in 2 files — src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs, src/net/JNet/Generated/Org/Xml/Sax/Helpers/XMLReaderAdapter.cs. 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 src/net/JNet/Generated/Java/Awt/EventNs/FocusAdapter.cs:210 — `_hasOverrideFocusGained || OnFocusGained != null` appears character-identically in 2 files — src/net/JNet/Generated/Java/Awt/EventNs/FocusAdapter.cs, src/net/JNet/Generated/Java/Awt/EventNs/FocusListener.cs. 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 src/net/JNet/Generated/Java/Awt/EventNs/FocusAdapter.cs:252 — `_hasOverrideFocusLost || OnFocusLost != null` appears character-identically in 2 files — src/net/JNet/Generated/Java/Awt/EventNs/FocusAdapter.cs, src/net/JNet/Generated/Java/Awt/EventNs/FocusListener.cs. 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 src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs:734 — `_hasOverrideIgnorableWhitespace || OnIgnorableWhitespace != null` appears character-identically in 2 files — src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs, src/net/JNet/Generated/Org/Xml/Sax/Helpers/XMLReaderAdapter.cs. 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 src/net/JNet/Generated/Javax/Imageio/Event/IIOReadProgressListener.cs:293 — `_hasOverrideImageComplete || OnImageComplete != null` appears character-identically in 2 files — src/net/JNet/Generated/Javax/Imageio/Event/IIOReadProgressListener.cs, src/net/JNet/Generated/Javax/Imageio/Event/IIOWriteProgressListener.cs. 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 src/net/JNet/Generated/Javax/Imageio/Event/IIOReadProgressListener.cs:335 — `_hasOverrideImageProgress || OnImageProgress != null` appears character-identically in 2 files — src/net/JNet/Generated/Javax/Imageio/Event/IIOReadProgressListener.cs, src/net/JNet/Generated/Javax/Imageio/Event/IIOWriteProgressListener.cs. 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.
  • + 15 more in this group — see findings.md.
P10 · Library API & versioning · Public type used only inside its own library · ×31
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57 — `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138 — `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57 — `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138 — `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57 — `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138 — `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58 — `Java.Util.Function.BiFunctionDirect` (src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58 — `Java.Util.Function.BiFunctionDirect` (src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58 — `Java.Util.Function.BiFunctionDirect` (src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57 — `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150 — `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57 — `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150 — `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57 — `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150 — `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Function.cs:56 — `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:56) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Function.cs:152 — `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:152) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Function.cs:56 — `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:56) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Function.cs:152 — `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:152) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Function.cs:56 — `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:56) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Function.cs:152 — `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:152) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149 — `Java.Util.Function.PredicateDirect` (src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149 — `Java.Util.Function.PredicateDirect` (src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149 — `Java.Util.Function.PredicateDirect` (src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54 — `Java.Util.Function.SupplierDirect` (src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • + 6 more in this group — see findings.md.
P10 · Library API & versioning · Implementation type on the public API · ×9
  • Implementation type on the public API src/net/JNet/Generated/Java/Net/DatagramSocketImpl.cs:32 — 6 public types in `Java.Net` are marked as implementation by their own namespace, folder or name: `DatagramSocketImpl` (src/net/JNet/Generated/Java/Net/DatagramSocketImpl.cs:32, name ends in `Impl`), `DatagramSocketImpl` (src/net/JNet/Generated/Java/Net/DatagramSocketImpl.cs:32, name ends in `Impl`), `DatagramSocketImpl` (src/net/JNet/Generated/Java/Net/DatagramSocketImpl.cs:32, name ends in `Impl`), `SocketImpl` (src/net/JNet/Generated/Java/Net/SocketImpl.cs:32, name ends in `Impl`), `SocketImpl` (src/net/JNet/Generated/Java/Net/SocketImpl.cs:32, name ends in `Impl`), `SocketImpl` (src/net/JNet/Generated/Java/Net/SocketImpl.cs:32, name ends in `Impl`). 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 src/net/JNet/Generated/Javax/Imageio/Metadata/IIOMetadataFormatImpl.cs:32 — 3 public types in `Javax.Imageio.Metadata` are marked as implementation by their own namespace, folder or name: `IIOMetadataFormatImpl` (src/net/JNet/Generated/Javax/Imageio/Metadata/IIOMetadataFormatImpl.cs:32, name ends in `Impl`), `IIOMetadataFormatImpl` (src/net/JNet/Generated/Javax/Imageio/Metadata/IIOMetadataFormatImpl.cs:32, name ends in `Impl`), `IIOMetadataFormatImpl` (src/net/JNet/Generated/Javax/Imageio/Metadata/IIOMetadataFormatImpl.cs:32, name ends in `Impl`). 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 src/net/JNet/Generated/Javax/Imageio/Stream/ImageInputStreamImpl.cs:32 — 6 public types in `Javax.Imageio.Stream` are marked as implementation by their own namespace, folder or name: `ImageInputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageInputStreamImpl.cs:32, name ends in `Impl`), `ImageInputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageInputStreamImpl.cs:32, name ends in `Impl`), `ImageInputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageInputStreamImpl.cs:32, name ends in `Impl`), `ImageOutputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageOutputStreamImpl.cs:32, name ends in `Impl`), `ImageOutputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageOutputStreamImpl.cs:32, name ends in `Impl`), `ImageOutputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageOutputStreamImpl.cs:32, name ends in `Impl`). 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 src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnectionImpl.cs:32 — 12 public types in `Javax.Management.Remote.Rmi` are marked as implementation by their own namespace, folder or name: `RMIConnectionImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnectionImpl.cs:32, name ends in `Impl`), `RMIConnectionImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnectionImpl.cs:32, name ends in `Impl`), `RMIConnectionImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnectionImpl.cs:32, name ends in `Impl`), `RMIIIOPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIIIOPServerImpl.cs:32, name ends in `Impl`), `RMIIIOPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIIIOPServerImpl.cs:32, name ends in `Impl`), `RMIIIOPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIIIOPServerImpl.cs:32, name ends in `Impl`), `RMIJRMPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIJRMPServerImpl.cs:32, name ends in `Impl`), `RMIJRMPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIJRMPServerImpl.cs:32, name ends in `Impl`), and 4 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 src/net/JNet/Generated/Javax/Sql/Rowset/RowSetMetaDataImpl.cs:32 — 3 public types in `Javax.Sql.Rowset` are marked as implementation by their own namespace, folder or name: `RowSetMetaDataImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/RowSetMetaDataImpl.cs:32, name ends in `Impl`), `RowSetMetaDataImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/RowSetMetaDataImpl.cs:32, name ends in `Impl`), `RowSetMetaDataImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/RowSetMetaDataImpl.cs:32, name ends in `Impl`). 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 src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLInputImpl.cs:32 — 6 public types in `Javax.Sql.Rowset.Serial` are marked as implementation by their own namespace, folder or name: `SQLInputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLInputImpl.cs:32, name ends in `Impl`), `SQLInputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLInputImpl.cs:32, name ends in `Impl`), `SQLInputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLInputImpl.cs:32, name ends in `Impl`), `SQLOutputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLOutputImpl.cs:32, name ends in `Impl`), `SQLOutputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLOutputImpl.cs:32, name ends in `Impl`), `SQLOutputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLOutputImpl.cs:32, name ends in `Impl`). 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 src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractMarshallerImpl.cs:32 — 21 public types in `Javax.Xml.Bind.Helpers` are marked as implementation by their own namespace, folder or name: `AbstractMarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractMarshallerImpl.cs:32, name ends in `Impl`), `AbstractMarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractMarshallerImpl.cs:32, name ends in `Impl`), `AbstractMarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractMarshallerImpl.cs:32, name ends in `Impl`), `AbstractUnmarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractUnmarshallerImpl.cs:32, name ends in `Impl`), `AbstractUnmarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractUnmarshallerImpl.cs:32, name ends in `Impl`), `AbstractUnmarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractUnmarshallerImpl.cs:32, name ends in `Impl`), `NotIdentifiableEventImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/NotIdentifiableEventImpl.cs:32, name ends in `Impl`), `NotIdentifiableEventImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/NotIdentifiableEventImpl.cs:32, name ends in `Impl`), and 13 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 src/net/JNet/Generated/Org/Xml/Sax/Ext/Attributes2Impl.cs:32 — 6 public types in `Org.Xml.Sax.Ext` are marked as implementation by their own namespace, folder or name: `Attributes2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Attributes2Impl.cs:32, name ends in `Impl`), `Attributes2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Attributes2Impl.cs:32, name ends in `Impl`), `Attributes2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Attributes2Impl.cs:32, name ends in `Impl`), `Locator2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Locator2Impl.cs:32, name ends in `Impl`), `Locator2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Locator2Impl.cs:32, name ends in `Impl`), `Locator2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Locator2Impl.cs:32, name ends in `Impl`). 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 src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributeListImpl.cs:32 — 12 public types in `Org.Xml.Sax.Helpers` are marked as implementation by their own namespace, folder or name: `AttributeListImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributeListImpl.cs:32, name ends in `Impl`), `AttributeListImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributeListImpl.cs:32, name ends in `Impl`), `AttributeListImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributeListImpl.cs:32, name ends in `Impl`), `AttributesImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributesImpl.cs:32, name ends in `Impl`), `AttributesImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributesImpl.cs:32, name ends in `Impl`), `AttributesImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributesImpl.cs:32, name ends in `Impl`), `LocatorImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/LocatorImpl.cs:32, name ends in `Impl`), `LocatorImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/LocatorImpl.cs:32, name ends in `Impl`), and 4 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
M4 · Documentation accuracy · README/code drift · ×7
  • README/code drift CONTRIBUTING.md:48 — CONTRIBUTING.md links to `PULL_REQUEST_TEMPLATE.md`, but `PULL_REQUEST_TEMPLATE.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:120 — README.md links to `articles/usage.md#intel-cet-and-jnet`, but `articles/usage.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:138 — README.md links to `articles/usageReflector.md`, but `articles/usageReflector.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift src/documentation/articles/performance.md:30 — src/documentation/articles/performance.md names .NET 8, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift src/documentation/articles/support.md:17 — src/documentation/articles/support.md names .NET 8, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift src/documentation/articles/usage.md:66 — src/documentation/articles/usage.md names .NET 9, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift src/documentation/articles/usageCLI.md:12 — src/documentation/articles/usageCLI.md names .NET 6, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X7 · Silent fallback defaults · Silent fallback default in catch · ×5
  • Silent fallback default in catch src/net/JNetReflector/InternalExtensions.cs:353 — `SignatureFromGenericString` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/net/JNetReflector/InternalExtensions.cs:448 — `JVMClass` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/net/JNetReflector/InternalExtensions.cs:1364 — `NeedsOperators` swallows every exception into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/net/JNetReflector/InternalExtensions.cs:1418 — `HasJVMBaseClassName` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/net/JNetReflector/JNetReflectorHelper.cs:274 — `ExtractJavaInfo` swallows every exception and returns `result` still holding `null` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
C4 · Data Retention · Partial data-retention evidence · ×1
  • Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
C5 · Data-Subject Rights · Partial data-subject-rights support · ×1
  • Partial data-subject-rights support — Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found src/net/JNetCLI/JNetCLI.csproj:5 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `src/net/JNetCLI/JNetCLI.csproj` makes this repository a deployable product (line 5).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion src/net/JNet/JNet.csproj:1 — `JNet(net462)` overshoots its size bounds (627564 LoC, 5322 public types across 199 namespaces). 1 of 9 project(s) overshoot their size bounds, lowering Project Cohesion to 7.8/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
D31 · IaC & Container Security · Low IaC · ×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.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X5 · Nullable reference types · Java packages are not null-marked everywhere · ×1
  • Java packages are not null-marked everywhere — 0/22 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 0/6 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Minor — 3 finding(s)
D24 · Comment Value · doc comments repeat the names · ×3
  • doc comments repeat the names src/net/JNet/Developed/Java/Awt/Container.cs:29 — 49 of 34107 documented parameters and 16 of 9814 summaries in `JNet(net462)` only repeat the member or parameter name (e.g. "Creates the and returns" for `CreateHostedContainer`). 10 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/net/JNetCLICore/ProgramBase.cs:195 — 0 of 0 documented parameters and 3 of 13 summaries in `JNetCLICore(net462)` only repeat the member or parameter name (e.g. "The project of the" for `ProjectName`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/net/JNetPSCore/Cmdlet/StartJNetPSCmdletCommandBase.cs:236 — 2 of 20 documented parameters and 3 of 49 summaries in `JNetPSCore(net462)` only repeat the member or parameter name (e.g. "The JVM option name" for `jvmOptionName`). Delete the restating tags, or add what the name does not say.

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-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d63d0aaa08714ee8b0a6a71468a3021d/tree.json --exit-code 0 --source .0—
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 src/jvm/jnet/src/main/java/org/mases/jnet/generated/java/awt/dnd --exclude src/jvm/jnet/src/main/java/org/mases/jnet/generated/java/awt/event --exclude src/jvm/jnet/src/main/java/org/mases/jnet/generated/java/util/function --exclude src/jvm/jnet/src/main/java/org/mases/jnet/generated/javax/imageio --exclude src/jvm/jnet/src/main/java/org/mases/jnet/generated/javax/print --exclude src/jvm/jnet/src/main/java/org/mases/jnet/generated/javax/swing/event --exclude src/net/JNet/Developed/Java --exclude src/net/JNet/Developed/Javax --exclude src/net/JNet/Generated/Java --exclude src/net/JNet/Generated/Javax --exclude src/net/JNet/Generated/Org .0—
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan0—
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-492a043998d149f293d9ffa2011e9b2d0artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .4artifacts/raw/trivy-config.json
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.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 Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-492a043998d149f293d9ffa2011e9b2d0artifacts/raw/osv-scanner.json

Run 01a1e9b8-2136-7006-b8bd-38a77f08e5f9 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 1 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Name — 1 field(s)
  • GraphicsEnvironment.AvailableFontFamilyNames src/net/JNet/Generated/Java/Awt/GraphicsEnvironment.cs:107

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