Public report of chirichexe/unibo-computer-eng-toolkit, 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 reportMeasured 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, 17:05 UTC · Survey ID cd_2795646caddb4484ac8598a570704146
chirichexe/unibo-computer-eng-toolkit
Measured 17 November 2026, 17:04 UTC, at code version 2d67cc5
First survey, so nothing to compare with yet
CAI scoreCritical ⚠
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: 22,157 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Production Readiness, 8.2
Findings by how serious they are
335 critical371 serious26 minor
27 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 17:04 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 ▸
40of 40 dimensions measured by tools.
720of 732 findings point to an exact file and line, so you can open each one in the code. The other 12 concern the repository as a whole, such as missing documentation.
40dimensions across 7 lenses, read from 22,157 lines of product code in 1 project.
chirichexe/unibo-computer-eng-toolkit falls short of our standard for production because the project has no automated tests and we found no working pipeline that builds or tests changes to the code. It scores 20.3 out of 100 and is rated Critical, and 276 of its 335 critical findings are security problems.
Production Readiness, at 8.2, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 11.1 points. Raising Production Readiness to 70 would lift the score to about 30.4.
228 weaknesses in the code could be used by an attacker. Twenty-six places in the code run text as code, which an attacker could use, and twenty-two passwords or keys are open to anyone who can read the repository. Fixing the weaknesses the scanner points to, replacing text run as code with direct calls and replacing each exposed password or key would close these risks. The 40 form fields without a label need a label.
The product code is 22,157 lines, about €19,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 forThe 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.
If Production Readiness rose from 8.2 to 70, the lowest score rated Strong, the score would rise from 20.3 to about 30.4.
Code composition: what the lines of code are
Product code 100%
Rebuild cost: about €19,000 · Estimate
Cost to rebuild
€6,300 to €31,000, for 104 to 331 hours of work, about 0.1 person-years for one engineer
Difficulty of the problem
Standard, 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 20. 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.
Size
Medium: 22,157 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 11.1 points · High effort · Code Coverage
2
Resolve the 5 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (4), REDACTED.
Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2), REDACTED (2).
Raises the score by about 1.8 points · Low effort · Secrets (history)
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 €19,000 to build again, about 0.1 person-years of work. Its weakest lens is Production Readiness, at 8.2 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No automated tests finding(s) in Code Coverage. Of all the actions in this report, it raises the score most for the work it takes: about 11.1 points for high effort, because it clears the 1 Code Coverage 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.
How this is estimated: It rests on an assumption 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. The result is a range for planning, not a measurement.
Based on: Code Duplication · Cohesion (LCOM4)
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: 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.
83 modules, with 2 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 43 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.
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 category
Findings
Severity
A05:2025 — Injection
302
High / Critical
A07:2025 — Authentication Failures
23
High / Critical
A01:2025 — Broken Access Control
5
Medium
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 15 High secret finding(s) in Secrets (history) — start with REDACTED (6), REDACTED (4), REDACTED (3); Add a CI workflow that builds and runs the test suite on every push/PR.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No automated tests finding(s) in Code Coverage.
Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Per-file score 0–10 — a quality signature. Of 232 files carrying findings, judged against the Production bar: 0% slop · 87% mixed · 13% near-clean.
File
Score
Band
Worst signal
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: 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 — 335
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 — 371
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 26
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 27
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 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, 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 — 40 dimensions across the health lenses
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
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, 720 of 732 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.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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.
D1 Cyclomatic Complexity — 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. Most of this repository's production source (.c, .java) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
D2 Cognitive Complexity — 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. Most of this repository's production source (.c, .java) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
D4 Code Duplication — 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 58 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .java (22,157 lines, 54% of production source), .c (19,250 lines, 46% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
D5 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
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. No dependency manifest this pass reads for hygiene (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable.
D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — no dependency manifest this pass reads for licence data (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so it declares no third-party dependency closure to grade. A gap in the analyzer, NOT a finding that this repository's licences are compliant: a manifest in an ecosystem outside that list, or third-party code copied into the tree, is not read — so this dimension asserts nothing about this repository's licensing in either direction.
D15 Churn × Complexity Hotspots — 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. A hotspot is churn × complexity. Churn was measured (10536 line(s) across the 90-day window), but no complexity could be computed for .c, .java, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
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-maintainer repository — bus factor is not applicable (2 contributor(s) across 58 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 1 hold 3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D19 Documentation Quality — 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 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.
D20 ADR Quality — 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. The ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository. No manifest, project file or entry point of any ecosystem it reads exists in this tree.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
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. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
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.
D26 Project Cohesion — 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. Project size and spread are measured over build units whose source a code model reads. This repository's .c source is a material share of its production lines and was read by none, so the score is a verdict about the units that were read. Not a finding that the unread source is cohesive — it is unmeasured.
D26 Project Cohesion — 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. `(repository root)` (41067 LoC, 309 module-visible types across 109 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 182 sampled here came from .java files. This repository's .c source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
D32 Data Compliance (PII/GDPR) — 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. `terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame05092025/java/RMI_Server.java`, `terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame24012025_Bea/java/RMI_Servergennaio25.java` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
AC2 Forms & labels — 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. 70 further occurrence(s) are not listed individually; the score already reflects all 110.
AC3 Page structure — 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. 203 further occurrence(s) are not listed individually; the score already reflects all 243.
AX3 Project dependency cycles — 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 is computed over which project references which. That is a language-neutral question, but the project-reference graph is collected from MSBuild .csproj/.fsproj/.vbproj, Gradle, Maven, Cargo, npm/pnpm/yarn, Go module (and dep/glide/godep), Python pyproject.toml/setup.cfg/setup.py, SwiftPM, sbt, Mill, RubyGems, Composer, Mix/rebar3, pub, Unity assembly-definition, Deno/JSR, Tuist, CMake, Bazel, Xcode and XcodeGen builds and uni-app uni_modules plugins, or — when none declares a module — from the imports between a JavaScript/TypeScript, Python, Ruby, loose Rust, build-less C# or manifest-less Go tree's top-level directories, or as one module when all of a tree's source is one directory, and this repository offers none of them — so there was no graph to read, and re-running the same commit reads the same nothing. No module manifest of any ecosystem this engine recognises was found either, and the source's own imports could not stand in: they are read for JavaScript/TypeScript, Python and Ruby only, and only when those languages are the product — in any other language a tree is read only when its whole source is one directory, which this one's is not. The collector owed is an import reader for this repository's languages. That is a COLLECTOR gap in this analyzer — no change to the scan image closes it — and not a finding that the repository is free of what this check looks for.
AX4 Dependency direction — 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 is computed over the direction each project reference points. That is a language-neutral question, but the project-reference graph is collected from MSBuild .csproj/.fsproj/.vbproj, Gradle, Maven, Cargo, npm/pnpm/yarn, Go module (and dep/glide/godep), Python pyproject.toml/setup.cfg/setup.py, SwiftPM, sbt, Mill, RubyGems, Composer, Mix/rebar3, pub, Unity assembly-definition, Deno/JSR, Tuist, CMake, Bazel, Xcode and XcodeGen builds and uni-app uni_modules plugins, or — when none declares a module — from the imports between a JavaScript/TypeScript, Python, Ruby, loose Rust, build-less C# or manifest-less Go tree's top-level directories, or as one module when all of a tree's source is one directory, and this repository offers none of them — so there was no graph to read, and re-running the same commit reads the same nothing. No module manifest of any ecosystem this engine recognises was found either, and the source's own imports could not stand in: they are read for JavaScript/TypeScript, Python and Ruby only, and only when those languages are the product — in any other language a tree is read only when its whole source is one directory, which this one's is not. The collector owed is an import reader for this repository's languages. That is a COLLECTOR gap in this analyzer — no change to the scan image closes it — and not a finding that the repository is free of what this check looks for.
AX8 Test isolation — 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 is computed over which projects are test projects, and what they reference. That is a language-neutral question, but the project-reference graph is collected from MSBuild .csproj/.fsproj/.vbproj, Gradle, Maven, Cargo, npm/pnpm/yarn, Go module (and dep/glide/godep), Python pyproject.toml/setup.cfg/setup.py, SwiftPM, sbt, Mill, RubyGems, Composer, Mix/rebar3, pub, Unity assembly-definition, Deno/JSR, Tuist, CMake, Bazel, Xcode and XcodeGen builds and uni-app uni_modules plugins, or — when none declares a module — from the imports between a JavaScript/TypeScript, Python, Ruby, loose Rust, build-less C# or manifest-less Go tree's top-level directories, or as one module when all of a tree's source is one directory, and this repository offers none of them — so there was no graph to read, and re-running the same commit reads the same nothing. No module manifest of any ecosystem this engine recognises was found either, and the source's own imports could not stand in: they are read for JavaScript/TypeScript, Python and Ruby only, and only when those languages are the product — in any other language a tree is read only when its whole source is one directory, which this one's is not. The collector owed is an import reader for this repository's languages. That is a COLLECTOR gap in this analyzer — no change to the scan image closes it — and not a finding that the repository is free of what this check looks for.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 177 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P10 Library API & versioning — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads NuGet packaging and C# public API, and npm, PyPI, crates.io, Maven/Gradle, Go module, RubyGems, Composer, SwiftPM, CocoaPods, pub.dev, Hex, sbt, Mill and scala-cli package manifests only, and no .NET project and no package manifest of those ecosystems was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found. Whether there is anything here to recover could NOT be determined: persistence is detected from deployment/container manifests and from dependency manifests, and neither was readable by this pass, so a data store this code opens directly — a file, an embedded database — would not be visible to it. The blindness is this analyzer's, not a finding that the repository holds no data. You can widen what we reach: keep the deployment/container manifest or a dependency manifest in this repository — or a link to the ops repo that holds the DR evidence — so the persistence probe has something to read.
R10 Code Duplication — 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. 29 further occurrence(s) are not listed individually; the score already reflects all 69.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
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.
X12 Unreachable branch — 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.
X16 Unfloored truncation loop — 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.
X2 Cancellation propagation — 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.
X21 Side-effecting pattern guard — 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.
X24 Document value interpolated into markup unescaped — 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.
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.
X29 Per-element action decided by a fixed element — 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.
X3 Exception handling — 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.
X3 Exception handling — 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. 12 further occurrence(s) are not listed individually; the score already reflects all 52.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
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.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D13 REDACTED Scanning: REDACTED 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").
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.
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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
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
D4 · Code Duplication4.5 / 10Weak✓ 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.
58 duplicated block group(s) detected. 13.6 % of the production lines (3,019 of 22,157) are in a reported copy. A further 19 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .java, .c (100% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
+ 62 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with Login.java (2), FilesManager.java. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Members sharing a duplicated core (16 members, 50+ identical tokens) finding(s) in Code Duplication — start with SessionListener.java, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Edited copy of a member (18 corresponding lines) finding(s) in Code Duplication — start with Login.java, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
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.
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.
16 deducted task-comment markers across 22157 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 14 XxxComment finding(s) in Explicit Debt — start with Utente.java (8), REDACTED (6). — One of this dimension's main actionable groups (14 warning-level).
Resolve the 2 TodoComment finding(s) in Explicit Debt — start with Guida.java, Singolo.java. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 of 795 judged comments only repeat the code they sit on (0.0 %). 693 comment(s) in another language or script were not judged.
Detailed fixes: d24_recommendation.md.
Do you agree with this assessment?
D27 · Navigability8.9 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
30 % of calls cross a namespace and 0 % go through an interface, but 24 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .java source only — this repository's .c was not sampled for call sites, so this score covers part of the tree, not all of it.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
44 finding(s): 0 critical, 44 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 15 High secret finding(s) in Secrets (history) — start with REDACTED (6), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (15 issue-level).
Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (7 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
302 finding(s): 0 critical, 254 high, 48 medium, 0 low. semgrep hit a parse error in 6 file(s) — `terzo-anno/reti-di-calcolatori/esami/esame06052019/c/server.c`, `terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame05092025/SC&sottoDIR&cifraUtente&lettParoladive/server.c` (line 319), `terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame05092025/java/RMI_Server.java` (line 357), `terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame06052019-1/c/server.c`, `terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame14062018-1/c/Server.c`, … (+1 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 139 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (76), REDACTED (21), REDACTED (16). — One of this dimension's main actionable groups (139 issue-level).
Resolve the 42 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (13), REDACTED (13), REDACTED (4). — One of this dimension's main actionable groups (42 issue-level).
Resolve the 33 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (19), REDACTED (7), REDACTED (4). — One of this dimension's main actionable groups (33 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)6.0 / 10Adequate✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
5 finding(s): 0 critical, 0 high, 5 medium, 0 low. semgrep could not parse 2 file(s) — `terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame05092025/java/RMI_Server.java`, `terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame24012025_Bea/java/RMI_Servergennaio25.java` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
REDACTED
What to do
Resolve the 5 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 136 of the 293 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
No strong hidden change-coupling between production files.
✓ On the Gold path — maintain.
Detailed fixes: d35_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives1.0 / 10Critical✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×3) — terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/contents/feed.jsp:60, terzo-anno/tecnologie-web/esami/PingPong/web/contents/feed.jsp:60, terzo-anno/tecnologie-web/esami/RicercaCognome/web/contents/feed.jsp:60
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels4.3 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×40) — terzo-anno/tecnologie-web/esami/Anagrammi/web/index.jsp:25, terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/articolo.jsp:27, terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/index.jsp:28, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure3.9 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×14) — terzo-anno/tecnologie-web/esami/Anagrammi/web/admin.jsp:63, terzo-anno/tecnologie-web/esami/Anagrammi/web/errors/exception.html:3, terzo-anno/tecnologie-web/esami/Anagrammi/web/errors/failure.jsp:12, …
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×25) — terzo-anno/tecnologie-web/esami/Anagrammi/web/admin.jsp:63, terzo-anno/tecnologie-web/esami/Anagrammi/web/errors/exception.html:3, terzo-anno/tecnologie-web/esami/Anagrammi/web/errors/failure.jsp:12, …
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — terzo-anno/tecnologie-web/esami/CalcoloFile/web/remove.jsp:1
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
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.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging call was found in the 347 JVM, JavaScript/TypeScript production file(s) this check read across 2 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run.
Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×39) — terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/functions.js:75, terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/functions.js:96, terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/articolo.js:12, …
What to do
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
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.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 151 plain JS — the untyped files are terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/functions.js, REDACTED, terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/utils.js, terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/articolo.js, terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/functions.js, terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/interval.js (+145 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
26 duplicated blocks under terzo-anno/tecnologie-web/ have copies in at least two of the sibling directories esami, esami_react_Achille_Pisani, template — 25 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 26 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — REDACTED:202
22 duplicated blocks under terzo-anno/tecnologie-web/esami_react_Achille_Pisani/ have copies in at least two of the sibling directories campominato11gen2022B, corsa24giu2024, dado10set2025, lago10set2024_RIFATTO, lotto9giu2022A, memory15lug2024 (+3 more sibling(s) not listed) — 20 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 22 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/App.js:113
15 duplicated blocks under terzo-anno/tecnologie-web/esami/ have copies in at least two of the sibling directories ArticoloCollaborativo, CalcoloFile, CarrelloCondiviso, ChatNonProibita, Cifratura, ConteggioMaiuscolo (+11 more sibling(s) not listed) — 14 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — terzo-anno/tecnologie-web/esami/PingPong/web/scripts/functions.js:37
REDACTED:202 · REDACTED:202 · REDACTED:202 · REDACTED:202 · +22 more site(s) not listed — the 26 copies are spread across 26 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 26 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — REDACTED:202
terzo-anno/tecnologie-web/esami/PingPong/web/scripts/functions.js:37 · terzo-anno/tecnologie-web/esami/StampaFile/web/scripts/functions.js:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — terzo-anno/tecnologie-web/esami/PingPong/web/scripts/functions.js:37
terzo-anno/tecnologie-web/esami/NomeFileTarget/web/scripts/functions.js:13 · terzo-anno/tecnologie-web/template/es1/web/scripts/functions.js:12 — the two spans are one implementation copied and then locally edited — 322 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — terzo-anno/tecnologie-web/esami/NomeFileTarget/web/scripts/functions.js:13
terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/utils.js:4 · terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/utils.js:4 · terzo-anno/tecnologie-web/esami/CalcoloFile/web/scripts/utils.js:4 · terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/utils.js:4 · +22 more site(s) not listed — the 26 copies are spread across 26 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 26 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/utils.js:4
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/App.js:113 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/App.js:95 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/tesoro7set2022/src/App.js:91 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/App.js:113
terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/functions.js:60 · terzo-anno/tecnologie-web/esami/StampaFile/web/scripts/functions.js:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/functions.js:60
terzo-anno/tecnologie-web/esami/MaxMinMatr/web/scripts/functions.js:71 · terzo-anno/tecnologie-web/esami/RicercaVia/web/scripts/functions.js:64 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — terzo-anno/tecnologie-web/esami/MaxMinMatr/web/scripts/functions.js:71
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/App.js:118 · terzo-anno/tecnologie-web/template/es3-react/App.js:56 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/App.js:118
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/App.js:119 · terzo-anno/tecnologie-web/template/es3-react/App.js:102 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/App.js:119
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Sezione1.js:11 · terzo-anno/tecnologie-web/template/es3-react/Sezione1.js:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Sezione1.js:11
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rigori20dic2024/src/Cella.js:21 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/tesoro7set2022/src/Cella.js:21 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rigori20dic2024/src/Cella.js:21
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione1.js:24 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/tesoro7set2022/src/Sezione1.js:24 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione1.js:24
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione1.js:24 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/Sezione1.js:23 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Sezione1.js:25 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione1.js:24
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/corsa24giu2024/src/Sezione1.js:25 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/tesoro7set2022/src/Sezione1.js:24 · terzo-anno/tecnologie-web/template/es3-react/Sezione1.js:25 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/corsa24giu2024/src/Sezione1.js:25
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/memory15lug2024/src/Cella.js:21 · terzo-anno/tecnologie-web/template/es3-react/Cella.js:21 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/memory15lug2024/src/Cella.js:21
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Cella.js:11 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rigori20dic2024/src/Cella.js:11 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/tesoro7set2022/src/Cella.js:11 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Cella.js:11
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/App.js:116 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rigori20dic2024/src/App.js:220 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/App.js:116
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/Sezione1.js:15 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/Sezione3.js:16 — the two spans are one implementation copied and then locally edited — 152 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/Sezione1.js:15
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione2.js:16 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Sezione2.js:16 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Sezione2.js:16 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/memory15lug2024/src/Sezione2.js:18 · +1 more site(s) not listed — the 5 copies are spread across 5 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 5 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione2.js:16
terzo-anno/tecnologie-web/esami/TestoMinoreMille/web/scripts/functions.js:18 · terzo-anno/tecnologie-web/template/es1/web/scripts/functions.js:20 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — terzo-anno/tecnologie-web/esami/TestoMinoreMille/web/scripts/functions.js:18
terzo-anno/tecnologie-web/esami/PingPong/web/scripts/functions.js:9 · terzo-anno/tecnologie-web/esami/StampaFile/web/scripts/interval.js:12 — the two spans are one implementation copied and then locally edited — 125 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — terzo-anno/tecnologie-web/esami/PingPong/web/scripts/functions.js:9
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Cella.js:31 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Cella.js:31 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/memory15lug2024/src/Cella.js:28 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rigori20dic2024/src/Cella.js:31 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Cella.js:31
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione1.js:24 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/Sezione1.js:23 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Sezione1.js:25 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Sezione1.js:27 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione1.js:24
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/Cella.js:43 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Cella.js:34 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/Cella.js:43
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/memory15lug2024/src/Sezione3.js:9 · terzo-anno/tecnologie-web/template/es3-react/Sezione3.js:9 — the two spans are one implementation copied and then locally edited — 131 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/memory15lug2024/src/Sezione3.js:9
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione3.js:11 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Sezione3.js:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione3.js:11
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/App.js:35 · terzo-anno/tecnologie-web/template/es3-react/App.js:34 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/App.js:35
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Sezione3.js:34 · terzo-anno/tecnologie-web/template/es3-react/Sezione3.js:13 — the two spans are one implementation copied and then locally edited — 117 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Sezione3.js:34
terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:87 · terzo-anno/tecnologie-web/esami/MaxMinMatr/web/scripts/functions.js:103 · terzo-anno/tecnologie-web/esami/RicercaVia/web/scripts/functions.js:95 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:87
terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/articolo.js:14 · terzo-anno/tecnologie-web/esami/MatriceSimmetrica/web/scripts/functions.js:68 — the two spans are one implementation copied and then locally edited — 81 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/articolo.js:14
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/Sezione2.js:13 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rigori20dic2024/src/Sezione2.js:30 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/Sezione2.js:13
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/Sezione2.js:18 · terzo-anno/tecnologie-web/template/es3-react/Sezione2.js:16 — the two spans are one implementation copied and then locally edited — 70 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/Sezione2.js:18
terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/interval.js:12 · terzo-anno/tecnologie-web/esami/DrinkDiscoteca/web/scripts/interval.js:12 · terzo-anno/tecnologie-web/esami/LavagnaCondivisa/web/scripts/interval.js:12 · terzo-anno/tecnologie-web/esami/NomeFileTarget/web/scripts/interval.js:12 · +2 more site(s) not listed — the 6 copies are spread across 6 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 6 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/interval.js:12
terzo-anno/tecnologie-web/esami/Cifratura/web/scripts/functions.js:65 · terzo-anno/tecnologie-web/esami/RicercaCognome/web/scripts/functions.js:52 — the two spans are one implementation copied and then locally edited — 75 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — terzo-anno/tecnologie-web/esami/Cifratura/web/scripts/functions.js:65
terzo-anno/tecnologie-web/esami/UfficioPostale/web/scripts/functions.js:19 · terzo-anno/tecnologie-web/esami/UfficioPostale/web/scripts/functions.js:35 — 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. — terzo-anno/tecnologie-web/esami/UfficioPostale/web/scripts/functions.js:19
terzo-anno/tecnologie-web/esami_react_Achille_Pisani/corsa24giu2024/src/Sezione3.js:45 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Sezione3.js:28 — the two spans are one implementation copied and then locally edited — 70 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/corsa24giu2024/src/Sezione3.js:45
terzo-anno/tecnologie-web/esami/DrinkDiscoteca/web/scripts/functions.js:16 · terzo-anno/tecnologie-web/esami/UfficioPostale/web/scripts/functions.js:24 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — terzo-anno/tecnologie-web/esami/DrinkDiscoteca/web/scripts/functions.js:16
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×26) — REDACTED:262, REDACTED:262, REDACTED:262, …
(anonymous) has cyclomatic complexity 17 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/web/scripts/functions.js:13
schedinaRandom has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/App.js:58
checkText has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — terzo-anno/tecnologie-web/esami/TestoMinoreMille/web/scripts/functions.js:17, terzo-anno/tecnologie-web/template/es1/web/scripts/functions.js:18
checkText has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/functions.js:19
sendMatrix has cyclomatic complexity 11 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:11
checkText has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — terzo-anno/tecnologie-web/esami/NomeFileTarget/web/scripts/functions.js:19
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
Do you agree with this assessment?
R4 · Test Coverage0.0 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
0% of 151 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/5 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`sendName` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — terzo-anno/tecnologie-web/esami/UsOpen/web/scripts/functions.js:12
`sendMatrix` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — terzo-anno/tecnologie-web/esami/MatriceSimmetrica/web/scripts/functions.js:15, terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:11
`sendFile` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — terzo-anno/tecnologie-web/esami/ContaCaratteri/web/scripts/functions.js:11
`sendWithAjax` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — terzo-anno/tecnologie-web/esami/CalcoloFile/web/scripts/functions.js:22
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped2.2 / 10Critical✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×12) — terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/functions.js:86, terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/interval.js:21, terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/functions.js:21, …
`item` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/functions.js:46
`error.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×7) — terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/functions.js:117, terzo-anno/tecnologie-web/esami/MaxMinMatr/web/scripts/functions.js:80, terzo-anno/tecnologie-web/esami/PingPong/web/scripts/functions.js:94, …
`data.chat` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/ChatNonProibita/web/scripts/websocket.js:15
`data.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/ChatNonProibita/web/scripts/websocket.js:17
`data+" - Arrivata per prima S"+i` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/Cifratura/web/scripts/functions.js:78
`"Risultato = "+risultato` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:82
`"Tempo totale impiegato in millis. = "+tempo` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:83
`event.data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×3) — terzo-anno/tecnologie-web/esami/DispositiviIOT/web/scripts/websocket.js:35, terzo-anno/tecnologie-web/esami/Tombola/web/scripts/websocket.js:16, terzo-anno/tecnologie-web/template/es3-websocket/web/scripts/websocket.js:16
`data.data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/InfoProbabili/web/scripts/websocket.js:16
`data.messages` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/InfoProbabili/web/scripts/websocket.js:18
`max` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/MaxMinMatr/web/scripts/functions.js:70
`"Sono state trovae "+a+" + "+b+" = "+occorrenze+"occorrenze di Ugo Bassi negli indirizzi"` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/RicercaVia/web/scripts/functions.js:63
`data.error` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — terzo-anno/tecnologie-web/esami/UsOpen/web/scripts/functions.js:31, terzo-anno/tecnologie-web/template/es2/web/scripts/functions.js:69
`giocatore.cognome` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/UsOpen/web/scripts/functions.js:58
`giocatore.rankingATP` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/UsOpen/web/scripts/functions.js:59
`giocatore.titoliVinti` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/UsOpen/web/scripts/functions.js:60
`giocatore.numPartiteVinte` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/UsOpen/web/scripts/functions.js:61
`giocatore.numPartitePerse` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — terzo-anno/tecnologie-web/esami/UsOpen/web/scripts/functions.js:62
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×40) — terzo-anno/tecnologie-web/template/es3-websocket/web/scripts/utils.js:42, terzo-anno/tecnologie-web/template/es3-websocket/web/scripts/utils.js:56, terzo-anno/tecnologie-web/template/es2/web/scripts/utils.js:42, …
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/110 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`.
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).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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.
Unscored — 1 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.
X10 Duplicated predicate — 19 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 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 — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 81 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.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository commits no project file of a kind this check models. This is a gap in the analyzer, not a finding about this repository
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository commits no project file of a kind this check models. This is a gap in the analyzer, not a finding about this repository
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no public interfaces
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) that was not loaded for this repository, because the repository commits no project file of a kind this check models. This is a gap in the analyzer, not a finding about this repository
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D1 Cyclomatic Complexity — cyclomatic complexity not measured — .c, .java exposed no member bodies
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D12 Dependency Hygiene — Dependency hygiene not measured — no supported dependency manifest was read
D14 License Compliance — No dependency manifest found — no declared dependency closure to grade for licences
D15 Churn × Complexity Hotspots — complexity unreadable for .c, .java — churn × complexity hotspots could not be measured
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D19 Documentation Quality — D19 withholds "Documentation: empty section": 4 candidate(s) were measured and not published.
D2 Cognitive Complexity — cognitive complexity not measured — .c, .java exposed no member bodies
D20 ADR Quality — Repository kind not determined
D21 Naming Consistency — N/A — too few peers to establish a naming convention (1926 declarations, no unit with a dominant convention).
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — project cohesion not measured for .c
D3 God Classes — Most of this repository's production source (.c, .java) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
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.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D5 Coupling — D5 reads a .NET project-reference graph only — this repository's production source is .java, .c, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
M4 Documentation accuracy — Not applicable: the 7 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (path 1); M4 checks only links and versions and artefact counts.
P10 Library API & versioning — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — no CI workflow found
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
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.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
R7 Dead Code — Not measured — no application, tooling or test entry point was detected, so no file can be shown to be reachable or unreachable. Declare an entry (package.json main/module/exports, src/index.*, or an index.html script) to enable reachability.
R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — X1 reached only 31% of this repository's production lines — java (22,157 lines), c (19,250 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 37% of this repository's production lines — c (19,250 lines), javascript (18,910 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC2 · Forms & labels· <input> without a programmatic label · ×39
<input> without a programmatic label terzo-anno/tecnologie-web/esami/Anagrammi/web/index.jsp:25— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/index.jsp:28— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/CalcoloFile/web/admin.jsp:30— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/CalcoloFile/web/admin.jsp:31— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/CalcoloFile/web/user.jsp:31— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/ChatNonProibita/web/index.jsp:28— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/Cifratura/web/index.jsp:23— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/ContaCaratteri/web/index.jsp:26— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/ContaCaratteri/web/index.jsp:27— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/web/user.jsp:32— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/web/user.jsp:33— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:27— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:28— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:29— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:30— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:32— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:33— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:34— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:35— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:37— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:38— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:39— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:40— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:42— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/index.jsp:43— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<html> without a lang terzo-anno/tecnologie-web/esami/Anagrammi/web/admin.jsp:63— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang terzo-anno/tecnologie-web/esami/Anagrammi/web/errors/exception.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang terzo-anno/tecnologie-web/esami/Anagrammi/web/errors/failure.jsp:12— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang terzo-anno/tecnologie-web/esami/Anagrammi/web/errors/notfound.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/errors/exception.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/errors/failure.jsp:12— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/errors/notfound.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang terzo-anno/tecnologie-web/esami/CalcoloFile/web/errors/exception.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang terzo-anno/tecnologie-web/esami/CalcoloFile/web/errors/failure.jsp:12— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang terzo-anno/tecnologie-web/esami/CalcoloFile/web/errors/notfound.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang terzo-anno/tecnologie-web/esami/CalcoloFile/web/remove.jsp:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/errors/exception.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/errors/failure.jsp:12— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/errors/notfound.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC1 · Text alternatives· <img> without a text alternative · ×3
<img> without a text alternative terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/contents/feed.jsp:60— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative terzo-anno/tecnologie-web/esami/PingPong/web/contents/feed.jsp:60— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative terzo-anno/tecnologie-web/esami/RicercaCognome/web/contents/feed.jsp:60— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/articolo.jsp:27— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> terzo-anno/tecnologie-web/esami/CalcoloFile/web/remove.jsp:1— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (JUnit (with Kotest or MockK on Kotlin)), and run it in CI so the gap cannot reopen.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/template/es3-websocket/web/scripts/utils.js:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/template/es3-websocket/web/scripts/utils.js:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/template/es2/web/scripts/utils.js:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/template/es2/web/scripts/utils.js:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/template/es1/web/scripts/utils.js:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/template/es1/web/scripts/utils.js:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/UsOpen/web/scripts/utils.js:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/UsOpen/web/scripts/utils.js:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/UfficioPostale/web/scripts/utils.js:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/UfficioPostale/web/scripts/utils.js:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/Tombola/web/scripts/utils.js:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/Tombola/web/scripts/utils.js:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/TestoMinoreMille/web/scripts/utils.js:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/TestoMinoreMille/web/scripts/utils.js:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/StampaFile/web/scripts/utils.js:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/StampaFile/web/scripts/utils.js:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/RicercaVia/web/scripts/utils.js:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/RicercaVia/web/scripts/utils.js:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/RicercaCognome/web/scripts/utils.js:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/RicercaCognome/web/scripts/utils.js:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/web/scripts/utils.js:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/web/scripts/utils.js:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/PingPong/web/scripts/utils.js:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/PingPong/web/scripts/utils.js:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) terzo-anno/tecnologie-web/esami/NomeFileTarget/web/scripts/utils.js:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/functions.js:75— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/functions.js:96— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/articolo.js:12— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/articolo.js:23— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/interval.js:15— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/CalcoloFile/web/scripts/functions.js:34— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/functions.js:15— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/functions.js:34— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/functions.js:99— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/Cifratura/web/scripts/functions.js:65— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/ContaCaratteri/web/scripts/functions.js:48— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:59— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:91— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/DrinkDiscoteca/web/scripts/functions.js:13— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/DrinkDiscoteca/web/scripts/functions.js:28— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/DrinkDiscoteca/web/scripts/interval.js:15— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/LavagnaCondivisa/web/scripts/functions.js:10— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/LavagnaCondivisa/web/scripts/interval.js:15— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/MatriceSimmetrica/web/scripts/functions.js:43— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/MatriceSimmetrica/web/scripts/functions.js:81— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/MaxMinMatr/web/scripts/functions.js:53— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/MaxMinMatr/web/scripts/functions.js:107— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/NomeFileTarget/web/scripts/functions.js:71— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/NomeFileTarget/web/scripts/interval.js:15— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience terzo-anno/tecnologie-web/esami/PingPong/web/scripts/functions.js:12— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
+ 14 more in this group — see findings.md.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×39
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/functions.js:86— `data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/interval.js:21— `data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/functions.js:21— `data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/functions.js:46— `item` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/functions.js:117— `error.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/ChatNonProibita/web/scripts/websocket.js:15— `data.chat` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/ChatNonProibita/web/scripts/websocket.js:17— `data.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/Cifratura/web/scripts/functions.js:78— `data+" - Arrivata per prima S"+i` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:82— `"Risultato = "+risultato` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:83— `"Tempo totale impiegato in millis. = "+tempo` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/DispositiviIOT/web/scripts/websocket.js:35— `event.data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/DrinkDiscoteca/web/scripts/interval.js:21— `data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/InfoProbabili/web/scripts/websocket.js:16— `data.data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/InfoProbabili/web/scripts/websocket.js:18— `data.messages` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/LavagnaCondivisa/web/scripts/functions.js:16— `data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/LavagnaCondivisa/web/scripts/interval.js:21— `data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/MaxMinMatr/web/scripts/functions.js:70— `max` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/MaxMinMatr/web/scripts/functions.js:80— `error.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/NomeFileTarget/web/scripts/interval.js:21— `data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/PingPong/web/scripts/functions.js:94— `error.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/RicercaCognome/web/scripts/functions.js:62— `data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/RicercaCognome/web/scripts/functions.js:76— `error.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/RicercaVia/web/scripts/functions.js:57— `data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/RicercaVia/web/scripts/functions.js:63— `"Sono state trovae "+a+" + "+b+" = "+occorrenze+"occorrenze di Ugo Bassi negli indirizzi"` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped terzo-anno/tecnologie-web/esami/RicercaVia/web/scripts/functions.js:73— `error.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function str (cyclomatic 29, cognitive 65) REDACTED:262— str has cyclomatic complexity 29 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
+ 1 more in this group — see findings.md.
AC3 · Page structure· Page without a main landmark · ×25
Page without a main landmark terzo-anno/tecnologie-web/esami/Anagrammi/web/admin.jsp:63— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/Anagrammi/web/errors/exception.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/Anagrammi/web/errors/failure.jsp:12— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/Anagrammi/web/errors/notfound.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/Anagrammi/web/index.jsp:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/admin.jsp:20— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/articolo.jsp:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/errors/exception.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/errors/failure.jsp:12— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/errors/notfound.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/index.jsp:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CalcoloFile/web/admin.jsp:20— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CalcoloFile/web/errors/exception.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CalcoloFile/web/errors/failure.jsp:12— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CalcoloFile/web/errors/notfound.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CalcoloFile/web/index.jsp:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CalcoloFile/web/remove.jsp:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CalcoloFile/web/user.jsp:21— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/errors/exception.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/errors/failure.jsp:12— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/errors/notfound.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/index.jsp:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/read.jsp:22— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/user.jsp:21— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/write.jsp:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
XxxComment terzo-anno/tecnologie-web/template/es3-websocket/src/classes/Utente.java:17— // 1= utente, 2=admin, 3= XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment terzo-anno/tecnologie-web/template/es1/src/classes/Utente.java:17— // 1= utente, 2=admin, 3= XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment terzo-anno/tecnologie-web/esami/Tombola/src/classes/Utente.java:17— // 1= utente, 2=admin, 3= XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/classes/Utente.java:17— // 1= utente, 2=admin, 3= XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment terzo-anno/tecnologie-web/esami/InfoProbabili/src/beans/Utente.java:16— // 1= utente, 2=admin, 3= XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/beans/Utente.java:17— // 1= utente, 2=admin, 3= XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Utente.java:17— // 1= utente, 2=admin, 3= XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/beans/Utente.java:17— // 1= utente, 2=admin, 3= XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment terzo-anno/tecnologie-web/template/es3-websocket/src/beans/Dati.java:40— // Utente XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment terzo-anno/tecnologie-web/template/es1/src/beans/Dati.java:40— // Utente XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment terzo-anno/tecnologie-web/esami/Tombola/src/beans/Dati.java:40— // Utente XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/beans/Dati.java:40— // Utente XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/beans/Dati.java:43— // Utente XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java:43— // Utente XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
X2 · Cancellation propagation· Async function without AbortSignal · ×5
Async function without AbortSignal: sendName terzo-anno/tecnologie-web/esami/UsOpen/web/scripts/functions.js:12— `sendName` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: sendMatrix terzo-anno/tecnologie-web/esami/MatriceSimmetrica/web/scripts/functions.js:15— `sendMatrix` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: sendMatrix terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:11— `sendMatrix` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: sendFile terzo-anno/tecnologie-web/esami/ContaCaratteri/web/scripts/functions.js:11— `sendFile` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: sendWithAjax terzo-anno/tecnologie-web/esami/CalcoloFile/web/scripts/functions.js:22— `sendWithAjax` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Duplicated block (10 lines × 2) terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java:69— terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java:69-78 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/Login.java:60-69 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java` and `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/Login.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java:69` 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 (10 lines × 2) terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/Login.java:60— terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/Login.java:60-69 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/Login.java:69-78 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/Login.java` and `terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/Login.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/Login.java:60` 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 (10 lines × 2) terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/FilesManager.java:102— terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/FilesManager.java:102-111 | terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/FilesManager.java:124-133 — 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 `terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/FilesManager.java:102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
TodoComment secondo-anno/sistemi-operativi/template/java/tomba/Guida.java:42— // TODO Auto-generated catch block — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment secondo-anno/sistemi-operativi/template/java/tomba/Singolo.java:37— // TODO Auto-generated catch block — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication· Members sharing a duplicated core (16 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (16 members, 50+ identical tokens) terzo-anno/tecnologie-web/esami/Anagrammi/src/listener/SessionListener.java:29— terzo-anno/tecnologie-web/esami/Anagrammi/src/listener/SessionListener.java:29-42 | terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/SessionListener.java:50-62 | terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/SessionListener.java:50-62 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/SessionListener.java:50-62 | terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/SessionListener.java:26-46 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/SessionListener.java:50-62 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/SessionListener.java:50-64 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/SessionListener.java:50-62 | terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/SessionListener.java:50-62 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/SessionListener.java:50-64 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/SessionListener.java:50-64 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/SessionListener.java:50-62 | terzo-anno/tecnologie-web/esami/RicercaVia/src/servlets/SessionListener.java:51-65 | terzo-anno/tecnologie-web/esami/StampaFile/src/servlets/SessionListener.java:50-62 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/SessionListener.java:50-62 | terzo-anno/tecnologie-web/template/es2/src/listener/SessionListener.java:29-42 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
Members sharing a duplicated core (16 members, 50+ identical tokens) terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:40— terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:40-105 | terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java:40-104 | terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/S1.java:45-89 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:42-116 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S2.java:42-114 | terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/TXTServlet.java:51-141 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/JSONServlet.java:52-117 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S1.java:32-106 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S2.java:30-104 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/JSONServlet.java:49-113 | terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/DataServlet.java:65-151 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/CognomeServlet.java:47-100 | terzo-anno/tecnologie-web/esami/RicercaVia/src/servlets/JSONServlet.java:54-119 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/servlets/S1.java:29-88 | terzo-anno/tecnologie-web/template/es1/src/servlets/DataServlet.java:65-151 | terzo-anno/tecnologie-web/template/es2/src/servlets/JSONServlet.java:40-114 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java:34— terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java:34-51 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/Login.java:34-51 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) REDACTED:33— REDACTED:33-50 | REDACTED:53-70 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×2
Edited copies of one member (3 members, 20+ corresponding lines) terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/DataServlet.java:54— terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/DataServlet.java:54-75 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/servlets/DataServlet.java:59-86 | REDACTED:38-57 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 20+ corresponding lines) terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/beans/Dati.java:22— terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/beans/Dati.java:22-41 | terzo-anno/tecnologie-web/esami/DispositiviIOT/src/beans/Dati.java:22-43 | terzo-anno/tecnologie-web/esami/InfoProbabili/src/beans/Dati.java:22-41 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (29 lines × 2) terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:47— terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:47-75 | terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java:47-75 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java` and `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:47` 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 (29 lines × 2) terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:83— terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:83-111 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S2.java:81-109 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java` and `terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S2.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:83` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:81` calls `containsValue` and `terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S2.java:79` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (27 lines × 2) terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:49— terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:49-75 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S2.java:49-75 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java` and `terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S2.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:49` 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 (27 lines × 2) terzo-anno/tecnologie-web/esami/DispositiviIOT/src/beans/Utente.java:17— terzo-anno/tecnologie-web/esami/DispositiviIOT/src/beans/Utente.java:17-43 | terzo-anno/tecnologie-web/esami/InfoProbabili/src/beans/Utente.java:18-45 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/DispositiviIOT/src/beans/Utente.java` and `terzo-anno/tecnologie-web/esami/InfoProbabili/src/beans/Utente.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (12 lines × 3) terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/TXTServlet.java:38— terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/TXTServlet.java:38-49 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/JSONServlet.java:36-47 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/CognomeServlet.java:34-45 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/TXTServlet.java` and `terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/JSONServlet.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
Duplicated block (12 lines × 3) terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/beans/GroupsManager.java:60— terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/beans/GroupsManager.java:60-71 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java:37-48 | terzo-anno/tecnologie-web/template/es1/src/beans/GroupsManager.java:39-50 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java` and `terzo-anno/tecnologie-web/template/es1/src/beans/GroupsManager.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 8) terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:95— terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:95-105 | terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java:94-104 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:106-116 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S2.java:104-114 | terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/TXTServlet.java:131-141 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/JSONServlet.java:103-113 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/CognomeServlet.java:90-100 | terzo-anno/tecnologie-web/esami/RicercaVia/src/servlets/JSONServlet.java:109-119 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java` and `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:95` 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, `terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/JSONServlet.java:102` calls `setContentType` and `terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/CognomeServlet.java:89` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 8) terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java:34— terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java:34-44 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/beans/Dati.java:34-44 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/Dati.java:34-44 | terzo-anno/tecnologie-web/esami/StampaFile/src/beans/Dati.java:29-39 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/beans/Dati.java:31-41 | terzo-anno/tecnologie-web/esami/Tombola/src/beans/Dati.java:31-41 | terzo-anno/tecnologie-web/template/es1/src/beans/Dati.java:31-41 | terzo-anno/tecnologie-web/template/es3-websocket/src/beans/Dati.java:31-41 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java` and `terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/beans/Dati.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/Login.java:69— terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/Login.java:69-77 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/servlets/Login.java:69-77 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/Login.java` and `terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/servlets/Login.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java:26— terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java:26-34 | terzo-anno/tecnologie-web/template/es1/src/beans/GroupsManager.java:28-36 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java` and `terzo-anno/tecnologie-web/template/es1/src/beans/GroupsManager.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (35 lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/App.js:118— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/App.js:118 · terzo-anno/tecnologie-web/template/es3-react/App.js:56 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (35 lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/App.js:119— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/App.js:119 · terzo-anno/tecnologie-web/template/es3-react/App.js:102 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (27 lines × 3 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione1.js:24— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione1.js:24 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/Sezione1.js:23 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Sezione1.js:25 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (27 lines × 3 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/corsa24giu2024/src/Sezione1.js:25— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/corsa24giu2024/src/Sezione1.js:25 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/tesoro7set2022/src/Sezione1.js:24 · terzo-anno/tecnologie-web/template/es3-react/Sezione1.js:25 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication· Duplicated block with local edits (20 matched lines × 2 locations) · ×2
Duplicated block with local edits (20 matched lines × 2 locations) terzo-anno/tecnologie-web/esami/PingPong/web/scripts/functions.js:9— terzo-anno/tecnologie-web/esami/PingPong/web/scripts/functions.js:9 · terzo-anno/tecnologie-web/esami/StampaFile/web/scripts/interval.js:12 — the two spans are one implementation copied and then locally edited — 125 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (20 matched lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/memory15lug2024/src/Sezione3.js:9— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/memory15lug2024/src/Sezione3.js:9 · terzo-anno/tecnologie-web/template/es3-react/Sezione3.js:9 — the two spans are one implementation copied and then locally edited — 131 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (19 lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione3.js:11— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione3.js:11 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Sezione3.js:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/App.js:35— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/App.js:35 · terzo-anno/tecnologie-web/template/es3-react/App.js:34 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (16 matched lines × 2 locations) · ×2
Duplicated block with local edits (16 matched lines × 2 locations) terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/articolo.js:14— terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/articolo.js:14 · terzo-anno/tecnologie-web/esami/MatriceSimmetrica/web/scripts/functions.js:68 — the two spans are one implementation copied and then locally edited — 81 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (16 matched lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/Sezione2.js:18— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/Sezione2.js:18 · terzo-anno/tecnologie-web/template/es3-react/Sezione2.js:16 — the two spans are one implementation copied and then locally edited — 70 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Complex function checkText (cyclomatic 12, cognitive 13) terzo-anno/tecnologie-web/esami/TestoMinoreMille/web/scripts/functions.js:17— checkText has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function checkText (cyclomatic 12, cognitive 13) terzo-anno/tecnologie-web/template/es1/web/scripts/functions.js:18— checkText has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
D4 · Code Duplication· Members sharing a duplicated core (26 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (26 members, 50+ identical tokens) terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/Login.java:37— terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/Login.java:37-55 | terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/servlets/Login.java:46-61 | terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java:54-78 | terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/Login.java:40-83 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/Login.java:45-69 | terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/Login.java:37-55 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/Login.java:45-69 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/Login.java:37-55 | terzo-anno/tecnologie-web/esami/DispositiviIOT/src/servlets/Login.java:45-60 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/Login.java:45-60 | terzo-anno/tecnologie-web/esami/InfoProbabili/src/servlets/Login.java:45-60 | terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/Login.java:54-82 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/Login.java:37-55 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/Login.java:37-55 | terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/Login.java:54-90 | terzo-anno/tecnologie-web/esami/PingPong/src/servlets/Login.java:38-60 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/servlets/Login.java:54-82 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/Login.java:40-58 | terzo-anno/tecnologie-web/esami/RicercaVia/src/servlets/Login.java:37-55 | terzo-anno/tecnologie-web/esami/StampaFile/src/servlets/Login.java:40-59 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/servlets/Login.java:54-90 | terzo-anno/tecnologie-web/esami/Tombola/src/servlets/Login.java:45-71 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/Login.java:54-78 | terzo-anno/tecnologie-web/template/es1/src/servlets/Login.java:54-90 | terzo-anno/tecnologie-web/template/es2/src/servlets/Login.java:37-53 | terzo-anno/tecnologie-web/template/es3-websocket/src/servlets/Login.java:45-71 — These 26 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 26 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 26 times.
D4 · Code Duplication· Members sharing a duplicated core (12 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (12 members, 50+ identical tokens) terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java:22— terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java:22-43 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java:22-48 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/beans/Dati.java:22-44 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/beans/Dati.java:22-48 | terzo-anno/tecnologie-web/esami/NomeFileTarget/src/beans/Dati.java:25-40 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/Dati.java:22-48 | terzo-anno/tecnologie-web/esami/StampaFile/src/beans/Dati.java:19-47 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/beans/Dati.java:25-45 | terzo-anno/tecnologie-web/esami/Tombola/src/beans/Dati.java:25-45 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/beans/Dati.java:22-42 | terzo-anno/tecnologie-web/template/es1/src/beans/Dati.java:25-45 | terzo-anno/tecnologie-web/template/es3-websocket/src/beans/Dati.java:25-45 — These 12 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/SessionListener.java:65— terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/SessionListener.java:65-75 | terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/SessionListener.java:65-75 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/SessionListener.java:65-75 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/SessionListener.java:65-75 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/SessionListener.java:65-75 | terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/SessionListener.java:65-75 | terzo-anno/tecnologie-web/esami/StampaFile/src/servlets/SessionListener.java:65-75 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/SessionListener.java:65-75 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) terzo-anno/tecnologie-web/esami/Anagrammi/src/listener/SessionListener.java:45— terzo-anno/tecnologie-web/esami/Anagrammi/src/listener/SessionListener.java:45-55 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/SessionListener.java:67-77 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/SessionListener.java:67-77 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/SessionListener.java:67-77 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/SessionListener.java:65-75 | terzo-anno/tecnologie-web/template/es2/src/listener/SessionListener.java:45-55 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/Login.java:40— terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/Login.java:40-83 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/AdminServlet.java:29-52 | terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/AdminServlet.java:29-52 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/servlets/AdminServlet.java:29-52 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/AdminServlet.java:29-52 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/FilesManager.java:101— terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/FilesManager.java:101-121 | terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/FilesManager.java:123-143 — These two members are one piece of code written twice and then edited apart: 21 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, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/beans/GroupsManager.java:74— terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/beans/GroupsManager.java:74-91 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java:51-68 | terzo-anno/tecnologie-web/template/es1/src/beans/GroupsManager.java:53-70 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) terzo-anno/tecnologie-web/template/es1/src/servlets/S1.java:20— terzo-anno/tecnologie-web/template/es1/src/servlets/S1.java:20-39 | terzo-anno/tecnologie-web/template/es1/src/servlets/S2.java:21-43 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) REDACTED:26— REDACTED:26-41 | REDACTED:26-38 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/beans/GroupsManager.java:94— terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/beans/GroupsManager.java:94-101 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java:71-78 | terzo-anno/tecnologie-web/template/es1/src/beans/GroupsManager.java:73-80 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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 (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) REDACTED:22— REDACTED:22-29 | REDACTED:23-30 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) terzo-anno/tecnologie-web/esami/Tombola/src/servlets/WebSocket.java:89— terzo-anno/tecnologie-web/esami/Tombola/src/servlets/WebSocket.java:89-99 | terzo-anno/tecnologie-web/template/es3-websocket/src/servlets/WebSocket.java:74-82 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 3+ corresponding lines) · ×1
Edited copies of one member (4 members, 3+ corresponding lines) terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:107— terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:107-109 | terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java:106-108 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:118-120 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S2.java:116-118 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (85 lines × 2) terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/DataServlet.java:67— terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/DataServlet.java:67-151 | terzo-anno/tecnologie-web/template/es1/src/servlets/DataServlet.java:67-151 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/DataServlet.java` and `terzo-anno/tecnologie-web/template/es1/src/servlets/DataServlet.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
Duplicated block (32–33 lines × 2) terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S1.java:34— terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S1.java:34-66 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S2.java:32-63 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S1.java` and `terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S2.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S1.java:34` 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 (6–21 lines × 5) terzo-anno/tecnologie-web/esami/StampaFile/src/servlets/Login.java:46— terzo-anno/tecnologie-web/esami/StampaFile/src/servlets/Login.java:46-59 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/servlets/Login.java:60-65 | terzo-anno/tecnologie-web/esami/Tombola/src/servlets/Login.java:51-71 | terzo-anno/tecnologie-web/template/es1/src/servlets/Login.java:60-65 | terzo-anno/tecnologie-web/template/es3-websocket/src/servlets/Login.java:51-71 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/servlets/Login.java` and `terzo-anno/tecnologie-web/esami/Tombola/src/servlets/Login.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/StampaFile/src/servlets/Login.java:46` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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, `terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/servlets/Login.java:65` calls `setAttribute`, `get`, `sendRedirect` and `terzo-anno/tecnologie-web/esami/StampaFile/src/servlets/Login.java:59` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21 lines × 2) terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:81— terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:81-101 | terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java:80-100 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java` and `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:81` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:80` calls `sleep` and `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java:79` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 3) terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/DataServlet.java:44— terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/DataServlet.java:44-62 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/servlets/DataServlet.java:38-56 | terzo-anno/tecnologie-web/template/es1/src/servlets/DataServlet.java:44-62 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/DataServlet.java` and `terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/servlets/DataServlet.java` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
Duplicated block (18–19 lines × 2) terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S1.java:88— terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S1.java:88-106 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S2.java:87-104 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S1.java` and `terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S2.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S1.java:88` 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 (17 lines × 2) terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/Login.java:35— terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/Login.java:35-51 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/servlets/Login.java:35-51 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/Login.java` and `terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/servlets/Login.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
Duplicated block (14–16 lines × 3) terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/beans/Dati.java:28— terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/beans/Dati.java:28-41 | terzo-anno/tecnologie-web/esami/DispositiviIOT/src/beans/Dati.java:28-43 | terzo-anno/tecnologie-web/esami/InfoProbabili/src/beans/Dati.java:28-41 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/beans/Dati.java` and `terzo-anno/tecnologie-web/esami/DispositiviIOT/src/beans/Dati.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
Duplicated block (11–14 lines × 7) terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java:58— terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java:58-68 | terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/Login.java:44-57 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/Login.java:49-59 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/Login.java:49-59 | terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/Login.java:58-68 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/servlets/Login.java:58-68 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/Login.java:58-68 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java` and `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/Login.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java:58` 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 (14 lines × 6) terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java:35— terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java:35-48 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/beans/Dati.java:35-48 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/beans/Dati.java:32-45 | terzo-anno/tecnologie-web/esami/Tombola/src/beans/Dati.java:32-45 | terzo-anno/tecnologie-web/template/es1/src/beans/Dati.java:32-45 | terzo-anno/tecnologie-web/template/es3-websocket/src/beans/Dati.java:32-45 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java` and `terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/beans/Dati.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java:35` 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 (13–14 lines × 2) terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/TXTServlet.java:57— terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/TXTServlet.java:57-70 | terzo-anno/tecnologie-web/esami/RicercaVia/src/servlets/JSONServlet.java:63-75 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/TXTServlet.java` and `terzo-anno/tecnologie-web/esami/RicercaVia/src/servlets/JSONServlet.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/TXTServlet.java:57` 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–14 lines × 2) REDACTED:28— REDACTED:28-41 | REDACTED:28-38 — before extracting anything, compare `REDACTED` and `REDACTED` 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. 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.
Duplicated block (10–13 lines × 15) terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:45— terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:45-57 | terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java:45-57 | terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/S1.java:56-68 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:47-59 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S2.java:47-59 | terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/TXTServlet.java:56-68 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/JSONServlet.java:57-69 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S1.java:49-61 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S2.java:46-58 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/JSONServlet.java:54-66 | terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/DataServlet.java:104-113 | terzo-anno/tecnologie-web/esami/RicercaVia/src/servlets/JSONServlet.java:62-74 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/servlets/S1.java:46-58 | terzo-anno/tecnologie-web/template/es1/src/servlets/DataServlet.java:104-113 | terzo-anno/tecnologie-web/template/es2/src/servlets/JSONServlet.java:45-54 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java` and `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `terzo-anno/tecnologie-web/esami/RicercaVia/src/servlets/JSONServlet.java:57` calls `currentTimeMillis` and `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:41` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6–13 lines × 13) terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/Login.java:43— terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/Login.java:43-55 | terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/servlets/Login.java:52-61 | terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/Login.java:43-55 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/Login.java:43-55 | terzo-anno/tecnologie-web/esami/DispositiviIOT/src/servlets/Login.java:51-60 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/Login.java:51-60 | terzo-anno/tecnologie-web/esami/InfoProbabili/src/servlets/Login.java:51-60 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/Login.java:43-55 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/Login.java:43-55 | terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/Login.java:60-65 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/Login.java:46-58 | terzo-anno/tecnologie-web/esami/RicercaVia/src/servlets/Login.java:43-55 | terzo-anno/tecnologie-web/template/es2/src/servlets/Login.java:43-53 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/Login.java` and `terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/Login.java` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/Login.java:43` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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, `terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/Login.java:65` calls `setAttribute`, `get`, `sendRedirect` and `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/Login.java:55` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12–13 lines × 3) terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/DataServlet.java:56— terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/DataServlet.java:56-67 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/servlets/DataServlet.java:61-73 | REDACTED:40-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: `Utente` names `beans.Utente` in one and `classes.Utente` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (13 lines × 2) terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java:56— terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java:56-68 | terzo-anno/tecnologie-web/template/es1/src/beans/GroupsManager.java:58-70 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java` and `terzo-anno/tecnologie-web/template/es1/src/beans/GroupsManager.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java:56` 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 (9–12 lines × 26) terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/Login.java:38— terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/Login.java:38-49 | terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/servlets/Login.java:47-55 | terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java:55-63 | terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/Login.java:41-52 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/Login.java:46-54 | terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/Login.java:38-49 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/Login.java:46-54 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/Login.java:38-49 | terzo-anno/tecnologie-web/esami/DispositiviIOT/src/servlets/Login.java:46-54 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/Login.java:46-54 | terzo-anno/tecnologie-web/esami/InfoProbabili/src/servlets/Login.java:46-54 | terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/Login.java:55-63 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/Login.java:38-49 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/Login.java:38-49 | terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/Login.java:55-64 | terzo-anno/tecnologie-web/esami/PingPong/src/servlets/Login.java:39-50 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/servlets/Login.java:55-63 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/Login.java:41-52 | terzo-anno/tecnologie-web/esami/RicercaVia/src/servlets/Login.java:38-49 | terzo-anno/tecnologie-web/esami/StampaFile/src/servlets/Login.java:41-52 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/servlets/Login.java:55-64 | terzo-anno/tecnologie-web/esami/Tombola/src/servlets/Login.java:46-54 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/Login.java:55-63 | terzo-anno/tecnologie-web/template/es1/src/servlets/Login.java:55-64 | terzo-anno/tecnologie-web/template/es2/src/servlets/Login.java:38-47 | terzo-anno/tecnologie-web/template/es3-websocket/src/servlets/Login.java:46-54 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/Login.java` and `terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/Login.java` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/Login.java:38` 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 first that the copies are not typed on the same thing: `Utente` names `beans.Utente` in one and `classes.Utente` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, 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, `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/Login.java:33` calls `getServletContext`, `getAttribute` and `terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/Login.java:36` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 13) terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:41— terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:41-52 | terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java:41-52 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:43-54 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S2.java:43-54 | terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/TXTServlet.java:52-63 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/JSONServlet.java:53-64 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S1.java:45-56 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S2.java:42-53 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/JSONServlet.java:50-61 | terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/DataServlet.java:100-111 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/CognomeServlet.java:51-62 | terzo-anno/tecnologie-web/template/es1/src/servlets/DataServlet.java:100-111 | terzo-anno/tecnologie-web/template/es2/src/servlets/JSONServlet.java:41-52 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java` and `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:41` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:38` calls `doGet` and `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:38` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 6) terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java:28— terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java:28-39 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java:28-39 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/beans/Dati.java:28-39 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/beans/Dati.java:28-39 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/Dati.java:28-39 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/beans/Dati.java:28-39 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java` and `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 5) terzo-anno/tecnologie-web/esami/NomeFileTarget/src/beans/Dati.java:26— terzo-anno/tecnologie-web/esami/NomeFileTarget/src/beans/Dati.java:26-37 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/beans/Dati.java:26-37 | terzo-anno/tecnologie-web/esami/Tombola/src/beans/Dati.java:26-37 | terzo-anno/tecnologie-web/template/es1/src/beans/Dati.java:26-37 | terzo-anno/tecnologie-web/template/es3-websocket/src/beans/Dati.java:26-37 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/NomeFileTarget/src/beans/Dati.java` and `terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/beans/Dati.java` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/Dati.java:35— terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/Dati.java:35-46 | terzo-anno/tecnologie-web/esami/StampaFile/src/beans/Dati.java:30-41 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/Dati.java` and `terzo-anno/tecnologie-web/esami/StampaFile/src/beans/Dati.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `terzo-anno/tecnologie-web/esami/StampaFile/src/beans/Dati.java:43` calls `Utente`, `setIsProfessore`, `add` and `terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/Dati.java:48` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 16) terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:43— terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:43-53 | terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java:43-53 | terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/S1.java:54-64 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java:45-55 | terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S2.java:45-55 | terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/TXTServlet.java:54-64 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/JSONServlet.java:55-65 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S1.java:47-57 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/S2.java:44-54 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/JSONServlet.java:52-62 | terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/DataServlet.java:102-112 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/CognomeServlet.java:53-63 | terzo-anno/tecnologie-web/esami/RicercaVia/src/servlets/JSONServlet.java:60-70 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/servlets/S1.java:44-54 | terzo-anno/tecnologie-web/template/es1/src/servlets/DataServlet.java:102-112 | terzo-anno/tecnologie-web/template/es2/src/servlets/JSONServlet.java:43-53 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java` and `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `terzo-anno/tecnologie-web/esami/RicercaVia/src/servlets/JSONServlet.java:57` calls `currentTimeMillis` and `terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:41` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 8) terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/SessionListener.java:51— terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/SessionListener.java:51-62 | terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/SessionListener.java:51-62 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/SessionListener.java:51-62 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/SessionListener.java:51-62 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/SessionListener.java:51-62 | terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/SessionListener.java:51-62 | terzo-anno/tecnologie-web/esami/StampaFile/src/servlets/SessionListener.java:51-62 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/SessionListener.java:51-62 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/SessionListener.java` and `terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/SessionListener.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
Duplicated block (11 lines × 3) terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/beans/GroupsManager.java:76— terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/beans/GroupsManager.java:76-86 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java:53-63 | terzo-anno/tecnologie-web/template/es1/src/beans/GroupsManager.java:55-65 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java` and `terzo-anno/tecnologie-web/template/es1/src/beans/GroupsManager.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 4) terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/AdminServlet.java:43— terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/AdminServlet.java:43-52 | terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/AdminServlet.java:43-52 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/servlets/AdminServlet.java:43-52 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/AdminServlet.java:43-52 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/AdminServlet.java` and `terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/AdminServlet.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/AdminServlet.java:43` 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 (10 lines × 3) terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java:34— terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java:34-43 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/beans/Dati.java:34-44 | terzo-anno/tecnologie-web/esami/NomeFileTarget/src/beans/Dati.java:31-40 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java` and `terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/beans/Dati.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java:34` 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 (9 lines × 11) terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java:33— terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java:33-41 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java:33-41 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/beans/Dati.java:33-41 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/beans/Dati.java:33-41 | terzo-anno/tecnologie-web/esami/NomeFileTarget/src/beans/Dati.java:30-38 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/Dati.java:33-41 | terzo-anno/tecnologie-web/esami/StampaFile/src/beans/Dati.java:28-36 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/beans/Dati.java:30-38 | terzo-anno/tecnologie-web/esami/Tombola/src/beans/Dati.java:30-38 | terzo-anno/tecnologie-web/template/es1/src/beans/Dati.java:30-38 | terzo-anno/tecnologie-web/template/es3-websocket/src/beans/Dati.java:30-38 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java` and `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java:44` calls `Utente`, `setIsXXX`, `add` and `terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java:43` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 7) terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java:31— terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java:31-39 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java:31-39 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/beans/Dati.java:31-39 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/beans/Dati.java:31-39 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/Dati.java:31-39 | terzo-anno/tecnologie-web/esami/StampaFile/src/beans/Dati.java:26-34 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/beans/Dati.java:31-39 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java` and `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Dati.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7–9 lines × 6) terzo-anno/tecnologie-web/esami/Anagrammi/src/listener/SessionListener.java:30— terzo-anno/tecnologie-web/esami/Anagrammi/src/listener/SessionListener.java:30-38 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/SessionListener.java:51-59 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/SessionListener.java:51-59 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/SessionListener.java:51-59 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/SessionListener.java:51-57 | terzo-anno/tecnologie-web/template/es2/src/listener/SessionListener.java:30-38 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Anagrammi/src/listener/SessionListener.java` and `terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/SessionListener.java` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/Anagrammi/src/listener/SessionListener.java:30` 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 (3–9 lines × 5) terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/Login.java:63— terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/Login.java:63-65 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/AdminServlet.java:30-38 | terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/AdminServlet.java:30-38 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/servlets/AdminServlet.java:30-38 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/AdminServlet.java:30-38 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/AdminServlet.java` and `terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/AdminServlet.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/Login.java:63` 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 (10 lines × 8) terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/SessionListener.java:66— terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/SessionListener.java:66-75 | terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/SessionListener.java:66-75 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/SessionListener.java:66-75 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/SessionListener.java:66-75 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/SessionListener.java:66-75 | terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/SessionListener.java:66-75 | terzo-anno/tecnologie-web/esami/StampaFile/src/servlets/SessionListener.java:66-75 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/SessionListener.java:66-75 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/SessionListener.java` and `terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/SessionListener.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
Duplicated block (10 lines × 6) terzo-anno/tecnologie-web/esami/Anagrammi/src/listener/SessionListener.java:46— terzo-anno/tecnologie-web/esami/Anagrammi/src/listener/SessionListener.java:46-55 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/SessionListener.java:68-77 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/SessionListener.java:68-77 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/SessionListener.java:68-77 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/SessionListener.java:66-75 | terzo-anno/tecnologie-web/template/es2/src/listener/SessionListener.java:46-55 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Anagrammi/src/listener/SessionListener.java` and `terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/SessionListener.java` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
Duplicated block (6 lines × 14) terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/SessionListener.java:54— terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/SessionListener.java:54-59 | terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/SessionListener.java:54-59 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/SessionListener.java:54-59 | terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/SessionListener.java:33-38 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/SessionListener.java:54-59 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/servlets/SessionListener.java:56-61 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/SessionListener.java:54-59 | terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/servlets/SessionListener.java:54-59 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/servlets/SessionListener.java:56-61 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/servlets/SessionListener.java:56-61 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/servlets/SessionListener.java:54-59 | terzo-anno/tecnologie-web/esami/RicercaVia/src/servlets/SessionListener.java:57-62 | terzo-anno/tecnologie-web/esami/StampaFile/src/servlets/SessionListener.java:54-59 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/SessionListener.java:54-59 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/SessionListener.java` and `terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/servlets/SessionListener.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `terzo-anno/tecnologie-web/esami/ContaCaratteri/src/servlets/SessionListener.java:31` calls `SuppressWarnings` and `terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/SessionListener.java:52` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java:72— terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java:72-78 | terzo-anno/tecnologie-web/template/es1/src/beans/GroupsManager.java:74-80 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java` and `terzo-anno/tecnologie-web/template/es1/src/beans/GroupsManager.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
Duplicated block (5 lines × 4) terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java:69— terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java:69-73 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/Login.java:60-64 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/Login.java:60-64 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/Login.java:69-73 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/CalcoloFile/src/servlets/Login.java` and `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/Login.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (35 lines × 7) terzo-anno/tecnologie-web/esami/Anagrammi/src/beans/Dati.java:21— terzo-anno/tecnologie-web/esami/Anagrammi/src/beans/Dati.java:21-55 | terzo-anno/tecnologie-web/esami/ContaCaratteri/src/beans/Dati.java:19-53 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/beans/Dati.java:19-53 | terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/beans/Dati.java:22-57 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/beans/Dati.java:19-53 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/beans/Dati.java:19-53 | terzo-anno/tecnologie-web/esami/RicercaVia/src/beans/Dati.java:19-53 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Anagrammi/src/beans/Dati.java` and `terzo-anno/tecnologie-web/esami/ContaCaratteri/src/beans/Dati.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (18 lines × 8) terzo-anno/tecnologie-web/esami/Anagrammi/src/classes/Utente.java:17— terzo-anno/tecnologie-web/esami/Anagrammi/src/classes/Utente.java:17-34 | terzo-anno/tecnologie-web/esami/ContaCaratteri/src/beans/Utente.java:17-34 | terzo-anno/tecnologie-web/esami/DifferenzaMatrici/src/beans/Utente.java:17-34 | terzo-anno/tecnologie-web/esami/MatriceSimmetrica/src/beans/Utente.java:17-34 | terzo-anno/tecnologie-web/esami/MaxMinMatr/src/beans/Utente.java:17-34 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/beans/Utente.java:17-34 | terzo-anno/tecnologie-web/esami/RicercaVia/src/beans/Utente.java:17-34 | terzo-anno/tecnologie-web/template/es2/src/classes/Utente.java:17-34 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Anagrammi/src/classes/Utente.java` and `terzo-anno/tecnologie-web/esami/ContaCaratteri/src/beans/Utente.java` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (46 lines × 7) terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/beans/Utente.java:19— terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/beans/Utente.java:19-64 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Utente.java:19-64 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/beans/Utente.java:19-64 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/classes/Utente.java:19-77 | terzo-anno/tecnologie-web/esami/Tombola/src/classes/Utente.java:19-64 | terzo-anno/tecnologie-web/template/es1/src/classes/Utente.java:19-77 | terzo-anno/tecnologie-web/template/es3-websocket/src/classes/Utente.java:19-64 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/beans/Utente.java` and `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Utente.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (29 lines × 4) terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/beans/Utente.java:18— terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/beans/Utente.java:18-46 | terzo-anno/tecnologie-web/esami/NomeFileTarget/src/classes/Utente.java:19-68 | terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/Utente.java:20-68 | terzo-anno/tecnologie-web/esami/StampaFile/src/beans/Utente.java:18-56 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/beans/Utente.java` and `terzo-anno/tecnologie-web/esami/NomeFileTarget/src/classes/Utente.java` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (64 lines × 3) terzo-anno/tecnologie-web/esami/NomeFileTarget/src/listener/SessionListener.java:1— terzo-anno/tecnologie-web/esami/NomeFileTarget/src/listener/SessionListener.java:1-64 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/listener/SessionListener.java:1-64 | terzo-anno/tecnologie-web/template/es1/src/listener/SessionListener.java:1-64 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/NomeFileTarget/src/listener/SessionListener.java` and `terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/listener/SessionListener.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/NomeFileTarget/src/listener/SessionListener.java:1` 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 (59 lines × 2) terzo-anno/tecnologie-web/esami/Tombola/src/listener/SessionListener.java:1— terzo-anno/tecnologie-web/esami/Tombola/src/listener/SessionListener.java:1-59 | terzo-anno/tecnologie-web/template/es3-websocket/src/listener/SessionListener.java:1-59 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/Tombola/src/listener/SessionListener.java` and `terzo-anno/tecnologie-web/template/es3-websocket/src/listener/SessionListener.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `terzo-anno/tecnologie-web/esami/Tombola/src/listener/SessionListener.java:1` 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 (39 lines × 8) terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/beans/Utente.java:19— terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/beans/Utente.java:19-64 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Utente.java:19-64 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/beans/Utente.java:19-64 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/classes/Utente.java:19-77 | terzo-anno/tecnologie-web/esami/Tombola/src/classes/Utente.java:19-64 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/beans/Utente.java:19-57 | terzo-anno/tecnologie-web/template/es1/src/classes/Utente.java:19-77 | terzo-anno/tecnologie-web/template/es3-websocket/src/classes/Utente.java:19-64 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/beans/Utente.java` and `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/beans/Utente.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 × 11) terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/servlets/Login.java:33— terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/servlets/Login.java:33-43 | terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/Login.java:32-42 | terzo-anno/tecnologie-web/esami/ConteggioMaiuscolo/src/servlets/Login.java:32-42 | terzo-anno/tecnologie-web/esami/DispositiviIOT/src/servlets/Login.java:32-42 | terzo-anno/tecnologie-web/esami/DrinkDiscoteca/src/servlets/Login.java:33-42 | terzo-anno/tecnologie-web/esami/InfoProbabili/src/servlets/Login.java:32-42 | terzo-anno/tecnologie-web/esami/NomeFileTarget/src/servlets/Login.java:37-51 | terzo-anno/tecnologie-web/esami/TestoMinoreMille/src/servlets/Login.java:37-51 | terzo-anno/tecnologie-web/esami/Tombola/src/servlets/Login.java:32-42 | terzo-anno/tecnologie-web/template/es1/src/servlets/Login.java:37-51 | terzo-anno/tecnologie-web/template/es3-websocket/src/servlets/Login.java:32-42 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/servlets/Login.java` and `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/Login.java` 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 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/beans/Dati.java:25— terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/beans/Dati.java:25-39 | terzo-anno/tecnologie-web/esami/RicercaCognome/src/beans/Dati.java:19-33 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/beans/Dati.java` and `terzo-anno/tecnologie-web/esami/RicercaCognome/src/beans/Dati.java` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 6) terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/WebSocket.java:82— terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/WebSocket.java:82-94 | terzo-anno/tecnologie-web/esami/DispositiviIOT/src/servlets/WebSocket.java:105-117 | terzo-anno/tecnologie-web/esami/InfoProbabili/src/servlets/WebSocket.java:106-118 | terzo-anno/tecnologie-web/esami/Tombola/src/servlets/WebSocket.java:132-144 | terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/WebSocket.java:50-62 | terzo-anno/tecnologie-web/template/es3-websocket/src/servlets/WebSocket.java:85-97 — before extracting anything, compare `terzo-anno/tecnologie-web/esami/ChatNonProibita/src/servlets/WebSocket.java` and `terzo-anno/tecnologie-web/esami/UfficioPostale/src/servlets/WebSocket.java` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
No structured logging — No logging call was found in the 347 JVM, JavaScript/TypeScript production file(s) this check read across 2 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
Duplication concentrated across 3 sibling directories (26 clone groups) REDACTED:202— 26 duplicated blocks under terzo-anno/tecnologie-web/ have copies in at least two of the sibling directories esami, esami_react_Achille_Pisani, template — 25 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 26 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 9 sibling directories (22 clone groups) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/App.js:113— 22 duplicated blocks under terzo-anno/tecnologie-web/esami_react_Achille_Pisani/ have copies in at least two of the sibling directories campominato11gen2022B, corsa24giu2024, dado10set2025, lago10set2024_RIFATTO, lotto9giu2022A, memory15lug2024 (+3 more sibling(s) not listed) — 20 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 22 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 17 sibling directories (15 clone groups) terzo-anno/tecnologie-web/esami/PingPong/web/scripts/functions.js:37— 15 duplicated blocks under terzo-anno/tecnologie-web/esami/ have copies in at least two of the sibling directories ArticoloCollaborativo, CalcoloFile, CarrelloCondiviso, ChatNonProibita, Cifratura, ConteggioMaiuscolo (+11 more sibling(s) not listed) — 14 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplicated block (315 lines × 26 locations) REDACTED:202— REDACTED:202 · REDACTED:202 · REDACTED:202 · REDACTED:202 · +22 more site(s) not listed — the 26 copies are spread across 26 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 26 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (68 lines × 2 locations) terzo-anno/tecnologie-web/esami/PingPong/web/scripts/functions.js:37— terzo-anno/tecnologie-web/esami/PingPong/web/scripts/functions.js:37 · terzo-anno/tecnologie-web/esami/StampaFile/web/scripts/functions.js:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (53 matched lines × 2 locations) · ×1
Duplicated block with local edits (53 matched lines × 2 locations) terzo-anno/tecnologie-web/esami/NomeFileTarget/web/scripts/functions.js:13— terzo-anno/tecnologie-web/esami/NomeFileTarget/web/scripts/functions.js:13 · terzo-anno/tecnologie-web/template/es1/web/scripts/functions.js:12 — the two spans are one implementation copied and then locally edited — 322 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (52 lines × 26 locations) terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/utils.js:4— terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/utils.js:4 · terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/utils.js:4 · terzo-anno/tecnologie-web/esami/CalcoloFile/web/scripts/utils.js:4 · terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/utils.js:4 · +22 more site(s) not listed — the 26 copies are spread across 26 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 26 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (51 lines × 3 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/App.js:113— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/App.js:113 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/App.js:95 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/tesoro7set2022/src/App.js:91 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (50 lines × 2 locations) terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/functions.js:60— terzo-anno/tecnologie-web/esami/CarrelloCondiviso/web/scripts/functions.js:60 · terzo-anno/tecnologie-web/esami/StampaFile/web/scripts/functions.js:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (36 lines × 2 locations) terzo-anno/tecnologie-web/esami/MaxMinMatr/web/scripts/functions.js:71— terzo-anno/tecnologie-web/esami/MaxMinMatr/web/scripts/functions.js:71 · terzo-anno/tecnologie-web/esami/RicercaVia/web/scripts/functions.js:64 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (32 lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Sezione1.js:11— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Sezione1.js:11 · terzo-anno/tecnologie-web/template/es3-react/Sezione1.js:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (30 lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rigori20dic2024/src/Cella.js:21— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rigori20dic2024/src/Cella.js:21 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/tesoro7set2022/src/Cella.js:21 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (28 lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione1.js:24— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione1.js:24 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/tesoro7set2022/src/Sezione1.js:24 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (27 lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/memory15lug2024/src/Cella.js:21— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/memory15lug2024/src/Cella.js:21 · terzo-anno/tecnologie-web/template/es3-react/Cella.js:21 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (26 lines × 3 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Cella.js:11— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Cella.js:11 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rigori20dic2024/src/Cella.js:11 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/tesoro7set2022/src/Cella.js:11 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (25 lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/App.js:116— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/App.js:116 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rigori20dic2024/src/App.js:220 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (25 matched lines × 2 locations) · ×1
Duplicated block with local edits (25 matched lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/Sezione1.js:15— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/Sezione1.js:15 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rubrica19apr2024A/src/Sezione3.js:16 — the two spans are one implementation copied and then locally edited — 152 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (24 lines × 5 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione2.js:16— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione2.js:16 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Sezione2.js:16 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Sezione2.js:16 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/memory15lug2024/src/Sezione2.js:18 · +1 more site(s) not listed — the 5 copies are spread across 5 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 5 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (21 lines × 2 locations) terzo-anno/tecnologie-web/esami/TestoMinoreMille/web/scripts/functions.js:18— terzo-anno/tecnologie-web/esami/TestoMinoreMille/web/scripts/functions.js:18 · terzo-anno/tecnologie-web/template/es1/web/scripts/functions.js:20 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (20 lines × 6 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Cella.js:31— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Cella.js:31 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Cella.js:31 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/memory15lug2024/src/Cella.js:28 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rigori20dic2024/src/Cella.js:31 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (20 lines × 4 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione1.js:24— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/campominato11gen2022B/src/Sezione1.js:24 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/Sezione1.js:23 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lago10set2024_RIFATTO/src/Sezione1.js:25 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Sezione1.js:27 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (20 lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/Cella.js:43— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/Cella.js:43 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Cella.js:34 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (18 matched lines × 2 locations) · ×1
Duplicated block with local edits (18 matched lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Sezione3.js:34— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Sezione3.js:34 · terzo-anno/tecnologie-web/template/es3-react/Sezione3.js:13 — the two spans are one implementation copied and then locally edited — 117 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (17 lines × 3 locations) terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:87— terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:87 · terzo-anno/tecnologie-web/esami/MaxMinMatr/web/scripts/functions.js:103 · terzo-anno/tecnologie-web/esami/RicercaVia/web/scripts/functions.js:95 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (16 lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/Sezione2.js:13— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/dado10set2025/src/Sezione2.js:13 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/rigori20dic2024/src/Sezione2.js:30 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (15 lines × 6 locations) terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/interval.js:12— terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/web/scripts/interval.js:12 · terzo-anno/tecnologie-web/esami/DrinkDiscoteca/web/scripts/interval.js:12 · terzo-anno/tecnologie-web/esami/LavagnaCondivisa/web/scripts/interval.js:12 · terzo-anno/tecnologie-web/esami/NomeFileTarget/web/scripts/interval.js:12 · +2 more site(s) not listed — the 6 copies are spread across 6 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 6 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication· Duplicated block with local edits (15 matched lines × 2 locations) · ×1
Duplicated block with local edits (15 matched lines × 2 locations) terzo-anno/tecnologie-web/esami/Cifratura/web/scripts/functions.js:65— terzo-anno/tecnologie-web/esami/Cifratura/web/scripts/functions.js:65 · terzo-anno/tecnologie-web/esami/RicercaCognome/web/scripts/functions.js:52 — the two spans are one implementation copied and then locally edited — 75 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (15 lines × 2 locations) terzo-anno/tecnologie-web/esami/UfficioPostale/web/scripts/functions.js:19— terzo-anno/tecnologie-web/esami/UfficioPostale/web/scripts/functions.js:19 · terzo-anno/tecnologie-web/esami/UfficioPostale/web/scripts/functions.js:35 — 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.
R10 · Code Duplication· Duplicated block with local edits (14 matched lines × 2 locations) · ×1
Duplicated block with local edits (14 matched lines × 2 locations) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/corsa24giu2024/src/Sezione3.js:45— terzo-anno/tecnologie-web/esami_react_Achille_Pisani/corsa24giu2024/src/Sezione3.js:45 · terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/Sezione3.js:28 — the two spans are one implementation copied and then locally edited — 70 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (13 lines × 2 locations) terzo-anno/tecnologie-web/esami/DrinkDiscoteca/web/scripts/functions.js:16— terzo-anno/tecnologie-web/esami/DrinkDiscoteca/web/scripts/functions.js:16 · terzo-anno/tecnologie-web/esami/UfficioPostale/web/scripts/functions.js:24 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Complex function (anonymous) (cyclomatic 17, cognitive 13) terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/web/scripts/functions.js:13— (anonymous) has cyclomatic complexity 17 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function schedinaRandom (cyclomatic 13, cognitive 19) terzo-anno/tecnologie-web/esami_react_Achille_Pisani/lotto9giu2022A/src/App.js:58— schedinaRandom has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function checkText (cyclomatic 12, cognitive 11) terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/functions.js:19— checkText has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function sendMatrix (cyclomatic 11, cognitive 17) terzo-anno/tecnologie-web/esami/DifferenzaMatrici/web/scripts/functions.js:11— sendMatrix has cyclomatic complexity 11 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function checkText (cyclomatic 11, cognitive 10) terzo-anno/tecnologie-web/esami/NomeFileTarget/web/scripts/functions.js:19— checkText has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Test Coverage — 0% of 151 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
Duplicated predicate REDACTED:113— `!directory.exists() && !directory.isDirectory()` appears character-identically in 14 files — REDACTED, REDACTED, REDACTED, REDACTED. 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 REDACTED:163— `!file.getName().endsWith(".txt") && isText` appears character-identically in 2 files — REDACTED, REDACTED. 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 terzo-anno/reti-di-calcolatori/esami/esame02092024/java/RMI_Server.java:65— `!originalFile.exists() || !originalFile.isFile()` appears character-identically in 9 files — terzo-anno/reti-di-calcolatori/esami/esame02092024/java/RMI_Server.java, terzo-anno/reti-di-calcolatori/esami/esame06052019/java/RMI_Server.java, terzo-anno/reti-di-calcolatori/template/lib/java/3-rmi-file/RMI_Server.java, terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame02092024-1/java/RMI_Server.java. 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 terzo-anno/reti-di-calcolatori/esami/esame13012021/java/RMI_Server.java:69— `(char) buffer[i] < '0' || (char) buffer[i] > '9'` appears character-identically in 2 files — terzo-anno/reti-di-calcolatori/esami/esame13012021/java/RMI_Server.java, terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame13012021-2/java/RMI_Server.java. 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 REDACTED:95— `Character.isUpperCase(line.charAt(0)) && trovati >= 5` appears character-identically in 2 files — REDACTED, REDACTED. 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 REDACTED:93— `Character.isUpperCase(line.charAt(0)) && trovati >= numOccorrenze` appears character-identically in 3 files — REDACTED, REDACTED, REDACTED. 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 terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java:108— `c == 'a' || c == 'e' || c == 'i' || c == 'o' || c == 'u'` appears character-identically in 4 files — terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S1.java, terzo-anno/tecnologie-web/esami/Anagrammi/src/servlets/S2.java, terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S1.java, terzo-anno/tecnologie-web/esami/Cifratura/src/servlets/S2.java. 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 terzo-anno/reti-di-calcolatori/esami/esame02092024/java/RMI_Server.java:129— `directory.exists() && directory.isDirectory()` appears character-identically in 20 files — terzo-anno/reti-di-calcolatori/esami/esame02092024/java/RMI_Server.java, terzo-anno/reti-di-calcolatori/esami/esame06052019/java/RMI_Server.java, terzo-anno/reti-di-calcolatori/esami/esame08012024-2/java/RMI_Server.java, REDACTED. 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 REDACTED:77— `elementi[i][j].getMatricola().equals(matricola) && elementi[i][j+1].isLibera()` appears character-identically in 2 files — REDACTED, REDACTED. 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 terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/beans/GroupsManager.java:66— `group1.size() >= MAX_USERS_PER_GROUP && group2.isEmpty()` appears character-identically in 3 files — terzo-anno/tecnologie-web/esami/LavagnaCondivisa/src/beans/GroupsManager.java, terzo-anno/tecnologie-web/esami/ProfessoriDottorandi/src/beans/GroupsManager.java, terzo-anno/tecnologie-web/template/es1/src/beans/GroupsManager.java. 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 terzo-anno/reti-di-calcolatori/esami/esame02092024/java/RMI_Server.java:134— `i < files.length && arraySize < MAX_LIST_SIZE` appears character-identically in 10 files — terzo-anno/reti-di-calcolatori/esami/esame02092024/java/RMI_Server.java, terzo-anno/reti-di-calcolatori/esami/esame06052019/java/RMI_Server.java, terzo-anno/reti-di-calcolatori/template/lib/java/3-rmi-file/RMI_Server.java, terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame02092024-1/java/RMI_Server.java. 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 terzo-anno/reti-di-calcolatori/esami/esame10022021/java/RMI_Client.java:91— `i == 3 && estremiData[i].length() != 4 || (i < 3 && estremiData[i].length() > 2)` appears character-identically in 2 files — terzo-anno/reti-di-calcolatori/esami/esame10022021/java/RMI_Client.java, terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame10022021-1/java/RMI_Client.java. 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 terzo-anno/reti-di-calcolatori/esami/esame10012025/java/Elemento.java:43— `matricola.equals("L") || directory.equals("L")` appears character-identically in 2 files — terzo-anno/reti-di-calcolatori/esami/esame10012025/java/Elemento.java, terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame10012025/java/Elemento.java. 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 terzo-anno/reti-di-calcolatori/esami/esame10022021/java/RMI_Server.java:123— `o[i].giorni > 0 || !o[i].data.equals("L")` appears character-identically in 2 files — terzo-anno/reti-di-calcolatori/esami/esame10022021/java/RMI_Server.java, terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame10022021-1/java/RMI_Server.java. 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 terzo-anno/reti-di-calcolatori/esami/esame13012021/java/RMI_Server.java:130— `subfiles[j].isFile() && subfiles[j].getName().endsWith(".txt")` appears character-identically in 3 files — terzo-anno/reti-di-calcolatori/esami/esame13012021/java/RMI_Server.java, terzo-anno/reti-di-calcolatori/template/lib/java/3-rmi-file/RMI_Server.java, terzo-anno/reti-di-calcolatori/zESAMI_SISTEMATI_AchillePisani_BeatriceCasoni/esami/esame13012021-2/java/RMI_Server.java. 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 terzo-anno/tecnologie-web/esami/Anagrammi/src/beans/Dati.java:41— `utente.getUsername().equals(username) && utente.getPassword().equals(password)` appears character-identically in 25 files — terzo-anno/tecnologie-web/esami/Anagrammi/src/beans/Dati.java, terzo-anno/tecnologie-web/esami/ArticoloCollaborativo/src/beans/Dati.java, terzo-anno/tecnologie-web/esami/CalcoloFile/src/beans/Dati.java, terzo-anno/tecnologie-web/esami/CarrelloCondiviso/src/beans/Dati.java. 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 terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/functions.js:31— `(char < 'A' || char > 'Z') && (char < 'a' || char > 'z')` appears character-identically in 3 files — terzo-anno/tecnologie-web/esami/Anagrammi/web/scripts/functions.js, terzo-anno/tecnologie-web/esami/TestoMinoreMille/web/scripts/functions.js, terzo-anno/tecnologie-web/template/es1/web/scripts/functions.js. 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 REDACTED:421— `replacer && typeof replacer !== 'function' && (typeof replacer !== 'object' || typeof replacer.length !== 'number')` appears character-identically in 26 files — REDACTED, REDACTED, REDACTED, REDACTED. 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 REDACTED:276— `value && typeof value === 'object' && typeof value.toJSON === 'function'` appears character-identically in 26 files — REDACTED, REDACTED, REDACTED, REDACTED. 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.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No SAST — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
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.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/5 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types· Java packages are not null-marked everywhere · ×1
Java packages are not null-marked everywhere — 0/110 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`.
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.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
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.
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.
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.
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.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a1ea77-7142-7a9d-aaa5-010051f5e386 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 335 · Warnings: 371 · Recommendations: 26 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 17:04 UTC.
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.