Public report of ReactiveX/rxjs, 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, 03:43 UTC · Survey ID cd_f330f3855ee24bc3b501fa4ae1ebe347
ReactiveX/rxjs
Measured 17 November 2026, 03:42 UTC, at code version 54796b3
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureNoCollector).
CAI scoreAt risk
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,610 lines of product code in 5 projects, tests not counted · Estimated rebuild effort: about 1.1 person-years · Weakest lens: Accessibility, 40.2
Findings by how serious they are
98 critical324 serious4911 minor
6 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, 03:42 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.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
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 ▸
71of 71 dimensions measured by tools.
5313of 5333 findings point to an exact file and line, so you can open each one in the code. The other 20 concern the repository as a whole, such as missing documentation.
71dimensions across 7 lenses, read from 22,610 lines of product code in 5 projects.
ReactiveX/rxjs is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because it has controls that only work with a mouse. It scores 55.9 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 40.2, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the password or key in the code, worth about 2.7 points. Making the controls keyboard-usable would lift Accessibility itself, worth about 5.3 points. Raising Accessibility to 70 would lift the score to about 68.2.
Seventy-six known security holes in the packages the code depends on can be used by attackers. Two automatic updates take new releases before a bad one can be spotted, and two weaknesses in the code could be used by an attacker. Updating the vulnerable packages, setting a waiting period for automatic updates and fixing the weaknesses the scanner points to would close these risks. The eight labels or groups of fields with no name need connecting to their fields or naming.
The product code is 22,610 lines, about €150,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 Accessibility rose from 40.2 to 70, the lowest score rated Strong, the score would rise from 55.9 to about 68.2.
Code composition: what the lines of code are
Product code 15%Tests 85%
Rebuild cost: about €150,000 · Estimate
Cost to rebuild
€51,000 to €260,000, for 846 to 2,685 hours of work, about 1.1 person-years for 1 to 2 engineers
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.8 at a score of 56. 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,610 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 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 2.7 points · Low effort · Secret Scanning
2
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 5.3 points · Medium effort · Keyboard semantics
3
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with navigation.service.spec.ts.
Raises the score by about 2.1 points · Low effort · Test Quality
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 €150,000 to build again, about 1.1 person-years of work. Its weakest lens is Accessibility, at 40.2 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 2.7 points for low effort, because it clears the 1 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
255 modules, with 194 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; 215 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.
apps.rxjs_dev.src.app.custom-elements.api.api_service uses apps.rxjs_dev.src.app.shared.logger_service, so a change to apps.rxjs_dev.src.app.shared.logger_service can break apps.rxjs_dev.src.app.custom-elements.api.api_service, while a change to apps.rxjs_dev.src.app.custom-elements.api.api_service can't break apps.rxjs_dev.src.app.shared.logger_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.api.api_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.code.pretty-printer_service uses a type in apps.rxjs_dev.src.app.shared.logger_service.
apps.rxjs_dev.src.app.custom-elements.code.pretty-printer_service uses apps.rxjs_dev.src.app.shared.logger_service, so a change to apps.rxjs_dev.src.app.shared.logger_service can break apps.rxjs_dev.src.app.custom-elements.code.pretty-printer_service, while a change to apps.rxjs_dev.src.app.custom-elements.code.pretty-printer_service can't break apps.rxjs_dev.src.app.shared.logger_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.code.pretty-printer_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.custom-elements.code.pretty-printer_service uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.custom-elements.code.pretty-printer_service, while a change to apps.rxjs_dev.src.app.custom-elements.code.pretty-printer_service can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.code.pretty-printer_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.custom-elements.elements-loader uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.custom-elements.elements-loader, while a change to apps.rxjs_dev.src.app.custom-elements.elements-loader can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.elements-loader uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service uses a type in apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.interfaces.
apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service uses apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.interfaces, so a change to apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.interfaces can break apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service, while a change to apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service can't break apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.interfaces.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service uses a type in packages.observable-polyfill.src.
apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service, while a change to apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.search.search_service uses apps.rxjs_dev.src.app.search.interfaces, so a change to apps.rxjs_dev.src.app.search.interfaces can break apps.rxjs_dev.src.app.search.search_service, while a change to apps.rxjs_dev.src.app.search.search_service can't break apps.rxjs_dev.src.app.search.interfaces.
Position
Below the diagonal: apps.rxjs_dev.src.app.search.search_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.search.search_service uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.search.search_service, while a change to apps.rxjs_dev.src.app.search.search_service can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.search.search_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.sw-updates.sw-updates_service uses apps.rxjs_dev.src.app.shared.logger_service, so a change to apps.rxjs_dev.src.app.shared.logger_service can break apps.rxjs_dev.src.app.sw-updates.sw-updates_service, while a change to apps.rxjs_dev.src.app.sw-updates.sw-updates_service can't break apps.rxjs_dev.src.app.shared.logger_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.sw-updates.sw-updates_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.sw-updates.sw-updates_service uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.sw-updates.sw-updates_service, while a change to apps.rxjs_dev.src.app.sw-updates.sw-updates_service can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.sw-updates.sw-updates_service uses a module listed above it, which is the healthy direction.
packages.migrate.src uses packages.migrate.src.skill-install, so a change to packages.migrate.src.skill-install can break packages.migrate.src, while a change to packages.migrate.src can't break packages.migrate.src.skill-install.
Position
Below the diagonal: packages.migrate.src uses a module listed above it, which is the healthy direction.
packages.migrate.src uses packages.migrate.src.types, so a change to packages.migrate.src.types can break packages.migrate.src, while a change to packages.migrate.src can't break packages.migrate.src.types.
Position
Below the diagonal: packages.migrate.src uses a module listed above it, which is the healthy direction.
packages.rxjs.src.connectable uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break packages.rxjs.src.connectable, while a change to packages.rxjs.src.connectable can't break packages.observable-polyfill.src.
Position
Below the diagonal: packages.rxjs.src.connectable uses a module listed above it, which is the healthy direction.
packages.rxjs.src.connectable uses packages.rxjs.src.util.types, so a change to packages.rxjs.src.util.types can break packages.rxjs.src.connectable, while a change to packages.rxjs.src.connectable can't break packages.rxjs.src.util.types.
Position
Below the diagonal: packages.rxjs.src.connectable uses a module listed above it, which is the healthy direction.
packages.rxjs.src.per-subscription-subject-base uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break packages.rxjs.src.per-subscription-subject-base, while a change to packages.rxjs.src.per-subscription-subject-base can't break packages.observable-polyfill.src.
Position
Below the diagonal: packages.rxjs.src.per-subscription-subject-base uses a module listed above it, which is the healthy direction.
packages.rxjs.src.per-subscription-subject-base uses packages.rxjs.src.util.types, so a change to packages.rxjs.src.util.types can break packages.rxjs.src.per-subscription-subject-base, while a change to packages.rxjs.src.per-subscription-subject-base can't break packages.rxjs.src.util.types.
Position
Below the diagonal: packages.rxjs.src.per-subscription-subject-base uses a module listed above it, which is the healthy direction.
packages.rxjs.src.subject uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break packages.rxjs.src.subject, while a change to packages.rxjs.src.subject can't break packages.observable-polyfill.src.
Position
Below the diagonal: packages.rxjs.src.subject uses a module listed above it, which is the healthy direction.
packages.rxjs.src.subject uses packages.rxjs.src.util.types, so a change to packages.rxjs.src.util.types can break packages.rxjs.src.subject, while a change to packages.rxjs.src.subject can't break packages.rxjs.src.util.types.
Position
Below the diagonal: packages.rxjs.src.subject uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.custom-elements.code.code_component uses apps.rxjs_dev.src.app.shared.logger_service, so a change to apps.rxjs_dev.src.app.shared.logger_service can break apps.rxjs_dev.src.app.custom-elements.code.code_component, while a change to apps.rxjs_dev.src.app.custom-elements.code.code_component can't break apps.rxjs_dev.src.app.shared.logger_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.code.code_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.code.code_component uses a type in apps.rxjs_dev.src.app.custom-elements.code.pretty-printer_service.
apps.rxjs_dev.src.app.custom-elements.code.code_component uses apps.rxjs_dev.src.app.custom-elements.code.pretty-printer_service, so a change to apps.rxjs_dev.src.app.custom-elements.code.pretty-printer_service can break apps.rxjs_dev.src.app.custom-elements.code.code_component, while a change to apps.rxjs_dev.src.app.custom-elements.code.code_component can't break apps.rxjs_dev.src.app.custom-elements.code.pretty-printer_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.code.code_component uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service uses a type in apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.interfaces.
apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service uses apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.interfaces, so a change to apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.interfaces can break apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service, while a change to apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service can't break apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.interfaces.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service uses a type in packages.observable-polyfill.src.
apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service, while a change to apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service uses a type in apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service.
apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service uses apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service, so a change to apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service can break apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service, while a change to apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service can't break apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree-data_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.shared.location_service uses apps.rxjs_dev.src.app.sw-updates.sw-updates_service, so a change to apps.rxjs_dev.src.app.sw-updates.sw-updates_service can break apps.rxjs_dev.src.app.shared.location_service, while a change to apps.rxjs_dev.src.app.shared.location_service can't break apps.rxjs_dev.src.app.sw-updates.sw-updates_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.shared.location_service uses a module listed above it, which is the healthy direction.
packages.rxjs.src.multicast uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break packages.rxjs.src.multicast, while a change to packages.rxjs.src.multicast can't break packages.observable-polyfill.src.
Position
Below the diagonal: packages.rxjs.src.multicast uses a module listed above it, which is the healthy direction.
packages.rxjs.src.multicast uses packages.rxjs.src.util.types, so a change to packages.rxjs.src.util.types can break packages.rxjs.src.multicast, while a change to packages.rxjs.src.multicast can't break packages.rxjs.src.util.types.
Position
Below the diagonal: packages.rxjs.src.multicast uses a module listed above it, which is the healthy direction.
packages.rxjs.src.multicast uses packages.rxjs.src.connectable, so a change to packages.rxjs.src.connectable can break packages.rxjs.src.multicast, while a change to packages.rxjs.src.multicast can't break packages.rxjs.src.connectable.
Position
Below the diagonal: packages.rxjs.src.multicast uses a module listed above it, which is the healthy direction.
packages.rxjs.src.ref-count uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break packages.rxjs.src.ref-count, while a change to packages.rxjs.src.ref-count can't break packages.observable-polyfill.src.
Position
Below the diagonal: packages.rxjs.src.ref-count uses a module listed above it, which is the healthy direction.
packages.rxjs.src.ref-count uses packages.rxjs.src.connectable, so a change to packages.rxjs.src.connectable can break packages.rxjs.src.ref-count, while a change to packages.rxjs.src.ref-count can't break packages.rxjs.src.connectable.
Position
Below the diagonal: packages.rxjs.src.ref-count uses a module listed above it, which is the healthy direction.
packages.rxjs.src.replay-subject uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break packages.rxjs.src.replay-subject, while a change to packages.rxjs.src.replay-subject can't break packages.observable-polyfill.src.
Position
Below the diagonal: packages.rxjs.src.replay-subject uses a module listed above it, which is the healthy direction.
packages.rxjs.src.replay-subject uses packages.rxjs.src.per-subscription-subject-base, so a change to packages.rxjs.src.per-subscription-subject-base can break packages.rxjs.src.replay-subject, while a change to packages.rxjs.src.replay-subject can't break packages.rxjs.src.per-subscription-subject-base.
Position
Below the diagonal: packages.rxjs.src.replay-subject uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.custom-elements.api.api-list_component uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.custom-elements.api.api-list_component, while a change to apps.rxjs_dev.src.app.custom-elements.api.api-list_component can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.api.api-list_component uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in apps.rxjs_dev.src.app.custom-elements.api.api-list_component uses a type in apps.rxjs_dev.src.app.custom-elements.api.api_service.
apps.rxjs_dev.src.app.custom-elements.api.api-list_component uses apps.rxjs_dev.src.app.custom-elements.api.api_service, so a change to apps.rxjs_dev.src.app.custom-elements.api.api_service can break apps.rxjs_dev.src.app.custom-elements.api.api-list_component, while a change to apps.rxjs_dev.src.app.custom-elements.api.api-list_component can't break apps.rxjs_dev.src.app.custom-elements.api.api_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.api.api-list_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.api.api-list_component uses a type in apps.rxjs_dev.src.app.shared.location_service.
apps.rxjs_dev.src.app.custom-elements.api.api-list_component uses apps.rxjs_dev.src.app.shared.location_service, so a change to apps.rxjs_dev.src.app.shared.location_service can break apps.rxjs_dev.src.app.custom-elements.api.api-list_component, while a change to apps.rxjs_dev.src.app.custom-elements.api.api-list_component can't break apps.rxjs_dev.src.app.shared.location_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.api.api-list_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.contributor.contributor-list_component uses a type in apps.rxjs_dev.src.app.custom-elements.contributor.contributors_model.
apps.rxjs_dev.src.app.custom-elements.contributor.contributor-list_component uses apps.rxjs_dev.src.app.custom-elements.contributor.contributors_model, so a change to apps.rxjs_dev.src.app.custom-elements.contributor.contributors_model can break apps.rxjs_dev.src.app.custom-elements.contributor.contributor-list_component, while a change to apps.rxjs_dev.src.app.custom-elements.contributor.contributor-list_component can't break apps.rxjs_dev.src.app.custom-elements.contributor.contributors_model.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.contributor.contributor-list_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.contributor.contributor-list_component uses a type in apps.rxjs_dev.src.app.shared.location_service.
apps.rxjs_dev.src.app.custom-elements.contributor.contributor-list_component uses apps.rxjs_dev.src.app.shared.location_service, so a change to apps.rxjs_dev.src.app.shared.location_service can break apps.rxjs_dev.src.app.custom-elements.contributor.contributor-list_component, while a change to apps.rxjs_dev.src.app.custom-elements.contributor.contributor-list_component can't break apps.rxjs_dev.src.app.shared.location_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.contributor.contributor-list_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component uses a type in apps.rxjs_dev.src.app.shared.scroll_service.
apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component uses apps.rxjs_dev.src.app.shared.scroll_service, so a change to apps.rxjs_dev.src.app.shared.scroll_service can break apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component, while a change to apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component can't break apps.rxjs_dev.src.app.shared.scroll_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component uses a type in packages.observable-polyfill.src.
apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component, while a change to apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component uses a type in apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service.
apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component uses apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service, so a change to apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service can break apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component, while a change to apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component can't break apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.operator-decision-tree.operator-decision-tree_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component uses a type in apps.rxjs_dev.src.app.search.interfaces.
apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component uses apps.rxjs_dev.src.app.search.interfaces, so a change to apps.rxjs_dev.src.app.search.interfaces can break apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component, while a change to apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component can't break apps.rxjs_dev.src.app.search.interfaces.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component uses a type in packages.observable-polyfill.src.
apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component, while a change to apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component uses a type in apps.rxjs_dev.src.app.search.search_service.
apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component uses apps.rxjs_dev.src.app.search.search_service, so a change to apps.rxjs_dev.src.app.search.search_service can break apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component, while a change to apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component can't break apps.rxjs_dev.src.app.search.search_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component uses a type in apps.rxjs_dev.src.app.shared.location_service.
apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component uses apps.rxjs_dev.src.app.shared.location_service, so a change to apps.rxjs_dev.src.app.shared.location_service can break apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component, while a change to apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component can't break apps.rxjs_dev.src.app.shared.location_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.custom-elements.search.file-not-found-search_component uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.documents.document_service uses apps.rxjs_dev.src.app.documents.document-contents, so a change to apps.rxjs_dev.src.app.documents.document-contents can break apps.rxjs_dev.src.app.documents.document_service, while a change to apps.rxjs_dev.src.app.documents.document_service can't break apps.rxjs_dev.src.app.documents.document-contents.
Position
Below the diagonal: apps.rxjs_dev.src.app.documents.document_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.documents.document_service uses apps.rxjs_dev.src.app.shared.logger_service, so a change to apps.rxjs_dev.src.app.shared.logger_service can break apps.rxjs_dev.src.app.documents.document_service, while a change to apps.rxjs_dev.src.app.documents.document_service can't break apps.rxjs_dev.src.app.shared.logger_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.documents.document_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.documents.document_service uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.documents.document_service, while a change to apps.rxjs_dev.src.app.documents.document_service can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.documents.document_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.documents.document_service uses apps.rxjs_dev.src.app.shared.location_service, so a change to apps.rxjs_dev.src.app.shared.location_service can break apps.rxjs_dev.src.app.documents.document_service, while a change to apps.rxjs_dev.src.app.documents.document_service can't break apps.rxjs_dev.src.app.shared.location_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.documents.document_service uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in apps.rxjs_dev.src.app.navigation.navigation_service uses a type in apps.rxjs_dev.src.app.navigation.navigation_model.
apps.rxjs_dev.src.app.navigation.navigation_service uses apps.rxjs_dev.src.app.navigation.navigation_model, so a change to apps.rxjs_dev.src.app.navigation.navigation_model can break apps.rxjs_dev.src.app.navigation.navigation_service, while a change to apps.rxjs_dev.src.app.navigation.navigation_service can't break apps.rxjs_dev.src.app.navigation.navigation_model.
Position
Below the diagonal: apps.rxjs_dev.src.app.navigation.navigation_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.navigation.navigation_service uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.navigation.navigation_service, while a change to apps.rxjs_dev.src.app.navigation.navigation_service can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.navigation.navigation_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.navigation.navigation_service uses apps.rxjs_dev.src.app.shared.location_service, so a change to apps.rxjs_dev.src.app.shared.location_service can break apps.rxjs_dev.src.app.navigation.navigation_service, while a change to apps.rxjs_dev.src.app.navigation.navigation_service can't break apps.rxjs_dev.src.app.shared.location_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.navigation.navigation_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.shared.scroll-spy_service uses apps.rxjs_dev.src.app.shared.scroll_service, so a change to apps.rxjs_dev.src.app.shared.scroll_service can break apps.rxjs_dev.src.app.shared.scroll-spy_service, while a change to apps.rxjs_dev.src.app.shared.scroll-spy_service can't break apps.rxjs_dev.src.app.shared.scroll_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.shared.scroll-spy_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.shared.scroll-spy_service uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.shared.scroll-spy_service, while a change to apps.rxjs_dev.src.app.shared.scroll-spy_service can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.shared.scroll-spy_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.shared.scroll-spy_service uses packages.rxjs.src.replay-subject, so a change to packages.rxjs.src.replay-subject can break apps.rxjs_dev.src.app.shared.scroll-spy_service, while a change to apps.rxjs_dev.src.app.shared.scroll-spy_service can't break packages.rxjs.src.replay-subject.
Position
Below the diagonal: apps.rxjs_dev.src.app.shared.scroll-spy_service uses a module listed above it, which is the healthy direction.
48 pairs of types, where a type in packages.rxjs.src uses a type in packages.observable-polyfill.src. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
packages.rxjs.src uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break packages.rxjs.src, while a change to packages.rxjs.src can't break packages.observable-polyfill.src.
Position
Below the diagonal: packages.rxjs.src uses a module listed above it, which is the healthy direction.
packages.rxjs.src uses packages.rxjs.src.util.types, so a change to packages.rxjs.src.util.types can break packages.rxjs.src, while a change to packages.rxjs.src can't break packages.rxjs.src.util.types.
Position
Below the diagonal: packages.rxjs.src uses a module listed above it, which is the healthy direction.
packages.rxjs.src uses packages.rxjs.src.connectable, so a change to packages.rxjs.src.connectable can break packages.rxjs.src, while a change to packages.rxjs.src can't break packages.rxjs.src.connectable.
Position
Below the diagonal: packages.rxjs.src uses a module listed above it, which is the healthy direction.
packages.rxjs.src uses packages.rxjs.src.ref-count, so a change to packages.rxjs.src.ref-count can break packages.rxjs.src, while a change to packages.rxjs.src can't break packages.rxjs.src.ref-count.
Position
Below the diagonal: packages.rxjs.src uses a module listed above it, which is the healthy direction.
packages.rxjs.src uses packages.rxjs.src.replay-subject, so a change to packages.rxjs.src.replay-subject can break packages.rxjs.src, while a change to packages.rxjs.src can't break packages.rxjs.src.replay-subject.
Position
Below the diagonal: packages.rxjs.src uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.shared.toc_service uses apps.rxjs_dev.src.app.shared.scroll-spy_service, so a change to apps.rxjs_dev.src.app.shared.scroll-spy_service can break apps.rxjs_dev.src.app.shared.toc_service, while a change to apps.rxjs_dev.src.app.shared.toc_service can't break apps.rxjs_dev.src.app.shared.scroll-spy_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.shared.toc_service uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.app_component uses apps.rxjs_dev.src.app.documents.document-contents, so a change to apps.rxjs_dev.src.app.documents.document-contents can break apps.rxjs_dev.src.app.app_component, while a change to apps.rxjs_dev.src.app.app_component can't break apps.rxjs_dev.src.app.documents.document-contents.
Position
Below the diagonal: apps.rxjs_dev.src.app.app_component uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.app_component uses apps.rxjs_dev.src.app.navigation.navigation_model, so a change to apps.rxjs_dev.src.app.navigation.navigation_model can break apps.rxjs_dev.src.app.app_component, while a change to apps.rxjs_dev.src.app.app_component can't break apps.rxjs_dev.src.app.navigation.navigation_model.
Position
Below the diagonal: apps.rxjs_dev.src.app.app_component uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.app_component uses apps.rxjs_dev.src.app.search.interfaces, so a change to apps.rxjs_dev.src.app.search.interfaces can break apps.rxjs_dev.src.app.app_component, while a change to apps.rxjs_dev.src.app.app_component can't break apps.rxjs_dev.src.app.search.interfaces.
Position
Below the diagonal: apps.rxjs_dev.src.app.app_component uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.app_component uses apps.rxjs_dev.src.app.shared.scroll_service, so a change to apps.rxjs_dev.src.app.shared.scroll_service can break apps.rxjs_dev.src.app.app_component, while a change to apps.rxjs_dev.src.app.app_component can't break apps.rxjs_dev.src.app.shared.scroll_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.app_component uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.app_component uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.app_component, while a change to apps.rxjs_dev.src.app.app_component can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.app_component uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.app_component uses apps.rxjs_dev.src.app.search.search_service, so a change to apps.rxjs_dev.src.app.search.search_service can break apps.rxjs_dev.src.app.app_component, while a change to apps.rxjs_dev.src.app.app_component can't break apps.rxjs_dev.src.app.search.search_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.app_component uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.app_component uses apps.rxjs_dev.src.app.shared.location_service, so a change to apps.rxjs_dev.src.app.shared.location_service can break apps.rxjs_dev.src.app.app_component, while a change to apps.rxjs_dev.src.app.app_component can't break apps.rxjs_dev.src.app.shared.location_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.app_component uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.app_component uses apps.rxjs_dev.src.app.documents.document_service, so a change to apps.rxjs_dev.src.app.documents.document_service can break apps.rxjs_dev.src.app.app_component, while a change to apps.rxjs_dev.src.app.app_component can't break apps.rxjs_dev.src.app.documents.document_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.app_component uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.app_component uses apps.rxjs_dev.src.app.navigation.navigation_service, so a change to apps.rxjs_dev.src.app.navigation.navigation_service can break apps.rxjs_dev.src.app.app_component, while a change to apps.rxjs_dev.src.app.app_component can't break apps.rxjs_dev.src.app.navigation.navigation_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.app_component uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.app_component uses apps.rxjs_dev.src.app.shared.toc_service, so a change to apps.rxjs_dev.src.app.shared.toc_service can break apps.rxjs_dev.src.app.app_component, while a change to apps.rxjs_dev.src.app.app_component can't break apps.rxjs_dev.src.app.shared.toc_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.app_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component uses a type in apps.rxjs_dev.src.app.documents.document-contents.
apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component uses apps.rxjs_dev.src.app.documents.document-contents, so a change to apps.rxjs_dev.src.app.documents.document-contents can break apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component, while a change to apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component can't break apps.rxjs_dev.src.app.documents.document-contents.
Position
Below the diagonal: apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component uses a type in apps.rxjs_dev.src.app.shared.logger_service.
apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component uses apps.rxjs_dev.src.app.shared.logger_service, so a change to apps.rxjs_dev.src.app.shared.logger_service can break apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component, while a change to apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component can't break apps.rxjs_dev.src.app.shared.logger_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component, while a change to apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component uses a type in apps.rxjs_dev.src.app.custom-elements.elements-loader.
apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component uses apps.rxjs_dev.src.app.custom-elements.elements-loader, so a change to apps.rxjs_dev.src.app.custom-elements.elements-loader can break apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component, while a change to apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component can't break apps.rxjs_dev.src.app.custom-elements.elements-loader.
Position
Below the diagonal: apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component uses apps.rxjs_dev.src.app.shared.toc_service, so a change to apps.rxjs_dev.src.app.shared.toc_service can break apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component, while a change to apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component can't break apps.rxjs_dev.src.app.shared.toc_service.
Position
Below the diagonal: apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.testing.doc-viewer-utils uses apps.rxjs_dev.src.app.documents.document-contents, so a change to apps.rxjs_dev.src.app.documents.document-contents can break apps.rxjs_dev.src.testing.doc-viewer-utils, while a change to apps.rxjs_dev.src.testing.doc-viewer-utils can't break apps.rxjs_dev.src.app.documents.document-contents.
Position
Below the diagonal: apps.rxjs_dev.src.testing.doc-viewer-utils uses a module listed above it, which is the healthy direction.
apps.rxjs_dev.src.testing.doc-viewer-utils uses packages.observable-polyfill.src, so a change to packages.observable-polyfill.src can break apps.rxjs_dev.src.testing.doc-viewer-utils, while a change to apps.rxjs_dev.src.testing.doc-viewer-utils can't break packages.observable-polyfill.src.
Position
Below the diagonal: apps.rxjs_dev.src.testing.doc-viewer-utils uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in apps.rxjs_dev.src.testing.doc-viewer-utils uses a type in apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component.
apps.rxjs_dev.src.testing.doc-viewer-utils uses apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component, so a change to apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component can break apps.rxjs_dev.src.testing.doc-viewer-utils, while a change to apps.rxjs_dev.src.testing.doc-viewer-utils can't break apps.rxjs_dev.src.app.layout.doc-viewer.doc-viewer_component.
Position
Below the diagonal: apps.rxjs_dev.src.testing.doc-viewer-utils uses a module listed above it, which is the healthy direction.
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
A03:2025 — Software Supply Chain Failures
295
High / Critical
A05:2025 — Injection
7
High / Critical
A07:2025 — Authentication Failures
3
High / Critical
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; 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; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
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.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Test Quality: No assertions: should fetch a document for the initial location
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 — 98
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 — 324
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 — 4911
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 6
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 71 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 71 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, 5313 of 5333 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.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 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 an ADMISSION gap, not an environment fault: it declares a published package (packages/observable-polyfill/REDACTED), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published REDACTED's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
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.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `apps/rxjs.dev/tools/transforms/templates/data-module.template.js`, `packages/migrate/src/capabilities.ts`, `packages/migrate/src/skill-install.ts`, `packages/observable-polyfill/src/index.ts`, `packages/rxjs/src/animation-frames.ts`, … (+92 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
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.
M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
R2 Cyclomatic Complexity — 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. 35 further occurrence(s) are not listed individually; the score already reflects all 75.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 6 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
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.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
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.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 12 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with semantics.migrateTestSchedulerSemantics (cyclomatic 47), group-by.groupByOperator (cyclomatic 34), generateKeywords.generateKeywordsProcessor.$process (cyclomatic 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 12 together lifts Cyclomatic Complexity from 7.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 20 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 25 bodies over 15 down to 15 or less in Cognitive Complexity — start with semantics.migrateTestSchedulerSemantics (cognitive 49), generateKeywordsProcessor.$process (cognitive 44), generateKeywords.generateKeywordsProcessor.$process (cognitive 43). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 25 together lifts Cognitive Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.2 / 10Stronggated by 5 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 3 FunctionTooLong finding(s) in God Classes — start with semantics.ts, group-by.ts, generateKeywords.js. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 FileTooLong finding(s) in God Classes — start with index.ts, semantics.ts. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
5 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 4 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
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.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with live-example.component.ts, navigation.service.ts. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Adequategated by 1 critical finding✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
3 skipped (3 with a documented reason), 4580 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 6572 tests (2 harness-style project(s) excluded from the assertion penalty).
Assertions commented out: navigationViews observable should completeapps/rxjs.dev/src/app/navigation/navigation.service.spec.ts:32
No assertions: matches exact timestamped observable messages · ×25packages/test/src/index.spec.ts:24
No direct assertions: requires a host with a native Observable implementation · ×4554packages/rxjs/test/ported/native-unavailable.spec.ts:4
Skipped (documented): should do WHAT(?) if the request fails · ×3apps/rxjs.dev/src/app/navigation/navigation.service.spec.ts:57
What to do
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with navigation.service.spec.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 4554 No direct assertions finding(s) in Test Quality — start with share.spec.ts (244), multicasting-deprecations.spec.ts (96), zip-all.spec.ts (94). — One of this dimension's main actionable groups (4554 recommendation-level).
Resolve the 25 No assertions finding(s) in Test Quality — start with index.spec.ts (12), visual-testing.e2e-spec.ts (5), document.service.spec.ts (3). — One of this dimension's main actionable groups (25 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
19 outdated direct production npm dependency(ies) of 21 graded, 0 pinning defect(s), across 10 REDACTED (5 of them the product) and 5 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 6 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Resolve the 68 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (68). — One of this dimension's main actionable groups (68 recommendation-level).
Resolve the 12 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED (12). — One of this dimension's main actionable groups (12 recommendation-level).
Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 114 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 114 package(s) this repository's committed lockfile installs for a consumer — its 21 production, optional and peer dependency(ies), across 5 product REDACTED manifest(s), and everything those install in turn. Its 119 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 3 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. No third-party code was found shipping without a manifest entry (vendored or copied-in directories, licence comments preserved in committed bundles, bundled module paths, compiled wasm modules). This repository publishes itself under Apache-2.0 / MIT, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 9 Hotspot finding(s) in Churn × Complexity Hotspots — start with generate-port-manifest.mjs, group-by.ts, generate-failure-tracker.mjs. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor4.8 / 10Weak✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
42 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/observable-polyfill/src/index.ts. Counted over 82 of the 342 production source files in this repository: 252 are under the ~2,400-byte size floor this dimension measures over, and the remaining 8 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
14 deducted task-comment markers across 17710 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 13 TodoComment finding(s) in Explicit Debt — start with api.service.ts (3), share-replay.spec.ts (2), location.service.ts (2). — One of this dimension's main actionable groups (13 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with api-list.component.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
53 domain type(s) cross context boundaries across 4 contexts; they are measured and withheld (not published, not scored). Contexts: migrate, observable-polyfill, rxjs, rxjs.dev.
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.
doc comments repeat the namesapps/rxjs.dev/src/app/sw-updates/sw-updates.service.ts:10
What to do
Resolve the 7 redundant comment finding(s) in Comment Value — start with index.js (2), app.component.ts, live-example.component.ts. — One of this dimension's main actionable groups (7 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D26 · Project Cohesion2.6 / 10Weak✓ Tool-verified
What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.
2 of 5 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×2apps/rxjs.dev/REDACTED:1
What to do
Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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).
7 finding(s): 0 critical, 4 high, 3 medium, 0 low. semgrep hit a parse error in 125 file(s) — `apps/rxjs.dev/tools/transforms/templates/api/base.template.html` (lines 1–3), `apps/rxjs.dev/tools/transforms/templates/api/deprecation.template.html` (line 1, line 18), `apps/rxjs.dev/tools/transforms/templates/api/includes/directive-overview.html` (line 1), `apps/rxjs.dev/tools/transforms/templates/api/includes/info-bar.html` (line 1), `apps/rxjs.dev/tools/transforms/templates/api/lib/memberHelpers.html` (lines 1–13, lines 14–15, lines 16–17, …), … (+120 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 64 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (62), REDACTED (2). — One of this dimension's main actionable groups (64 issue-level).
Resolve the 10 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_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.
28 of 90 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is apps/rxjs.dev/src/app/app.component.ts. Counted over 90 of the 342 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 28 Orphaned file finding(s) in Knowledge Freshness — start with index.js (4), app.component.ts, doc-viewer.component.ts. — One of this dimension's main actionable groups (28 recommendation-level).
Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No dependency in any ecosystem this repository declares is published as malicious. 177 advisory suppression(s) declared in REDACTED, 177 stale.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives3.5 / 10Weak✓ 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. — apps/rxjs.dev/src/app/custom-elements/announcement-bar/announcement-bar.component.ts:50
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 & labels5.2 / 10Adequate✓ 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. — apps/rxjs.dev/src/app/layout/doc-viewer/dt.component.ts:9
This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×8) — apps/rxjs.dev/tools/transforms/templates/api/base.template.html:24, apps/rxjs.dev/tools/transforms/templates/api/base.template.html:25, apps/rxjs.dev/tools/transforms/templates/api/base.template.html:26, …
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.
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.
An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. — apps/rxjs.dev/content/marketing/index.html:32
A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×3) — apps/rxjs.dev/tools/transforms/templates/api/deprecation.template.html:5, apps/rxjs.dev/tools/transforms/templates/api/function.template.html:22, apps/rxjs.dev/tools/transforms/templates/api/lib/paramList.html:16
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — apps/rxjs.dev/tools/transforms/templates/overview-dump.template.html:1
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — apps/rxjs.dev/tools/transforms/templates/overview-dump.template.html:1
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — apps/rxjs.dev/tools/transforms/templates/overview-dump.template.html: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 interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. — apps/rxjs.dev/src/app/custom-elements/contributor/contributor-list.component.ts:11
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — apps/rxjs.dev/src/app/custom-elements/contributor/contributor.component.ts:39, apps/rxjs.dev/src/app/layout/notification/notification.component.ts:12
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
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.
`&:hover` sets color: #2B85E7 on background-color: #edf0f2 — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — apps/rxjs.dev/src/styles/2-modules/_resources.scss:135, apps/rxjs.dev/src/styles/2-modules/_resources.scss:148
`mat-sidenav .doc-version select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/rxjs.dev/src/styles/1-layouts/_sidenav.scss:183
`aio-search-box.search-container input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — apps/rxjs.dev/src/styles/1-layouts/_top-menu.scss:170
`code-tabs mat-tab-body-content .fadeIn` moves (`animation: opacity 2s ease-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/rxjs.dev/src/styles/2-modules/_code.scss:66
`aio-contributor div.contributor-card` moves (`transition: transform ease 500ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/rxjs.dev/src/styles/2-modules/_contributor.scss:105
`.aio-notification-animating mat-sidenav.mat-sidenav.sidenav` moves (`transition: top 250ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/rxjs.dev/src/styles/2-modules/_notification.scss:104
`.heading-children.expanded` moves (`transition: visibility 500ms, opacity 500ms, max-height 500ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/rxjs.dev/src/styles/1-layouts/_sidenav.scss:112
`.heading-children.collapsed` moves (`transition: visibility 275ms, opacity 275ms, max-height 280ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/rxjs.dev/src/styles/1-layouts/_sidenav.scss:121
`.hamburger.mat-button:not(.starting)` moves (`transition-property: color, margin`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/rxjs.dev/src/styles/1-layouts/_top-menu.scss:68
`aio-search-box.search-container input` moves (`transition: width 0.4s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/rxjs.dev/src/styles/1-layouts/_top-menu.scss:174
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. — apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js:2
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — packages/rxjs/test/ported/native-unavailable.spec.ts:3
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
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.
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.
1 ADR-shaped document(s) detected by content — `docs/rxjs-next/DECISIONS.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
What to do
Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
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.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
README.md names RxJS 8, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:28
README.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:110
docs/RELEASE_PROCESS.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/RELEASE_PROCESS.md:88
docs/rxjs-next/ARCHITECTURE.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/rxjs-next/ARCHITECTURE.md:38
docs/rxjs-next/DECISIONS.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/rxjs-next/DECISIONS.md:1135
docs/rxjs-next/PROJECT_CHARTER.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/rxjs-next/PROJECT_CHARTER.md:19
docs/rxjs-next/PROJECT_CHARTER.md names RxJS 8, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/rxjs-next/PROJECT_CHARTER.md:20
docs/rxjs-next/WHY_SYMBOL_OPERATORS.md names RxJS 5, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/rxjs-next/WHY_SYMBOL_OPERATORS.md:55
What to do
Reconcile the README with reality: README.md names RxJS 8, but the manifest declares `rxjs` ^7.5.1; README.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1; docs/RELEASE_PROCESS.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1; docs/rxjs-next/ARCHITECTURE.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1; docs/rxjs-next/DECISIONS.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1.
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.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability5.5 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/migrate`.
`apps/rxjs.dev/src/assets/js/devtools-welcome.js` reports through `console.*` at line 10 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/rxjs.dev/src/assets/js/devtools-welcome.js:10
`apps/rxjs.dev/src/assets/js/devtools-welcome.js` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/rxjs.dev/src/assets/js/devtools-welcome.js:12
`apps/rxjs.dev/src/app/shared/logger.service.ts` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/rxjs.dev/src/app/shared/logger.service.ts:12
`apps/rxjs.dev/src/app/shared/logger.service.ts` reports through `console.*` at line 21 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/rxjs.dev/src/app/shared/logger.service.ts:21
`apps/rxjs.dev/src/app/search/search.worker.ts` reports through `console.*` at line 170 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/rxjs.dev/src/app/search/search.worker.ts:170
`apps/rxjs.dev/src/app/custom-elements/code/code-example.component.ts` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/rxjs.dev/src/app/custom-elements/code/code-example.component.ts:12
`apps/rxjs.dev/src/app/custom-elements/code/pretty-printer.service.ts` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/rxjs.dev/src/app/custom-elements/code/pretty-printer.service.ts:56
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
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.
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
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 · 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 Safety7.8 / 10Strong✓ 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.
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.
6 duplicated blocks under packages/ have copies in at least two of the sibling directories observable-polyfill, rxjs — 1 of them are reported below, and 5 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 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 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 6 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. — packages/observable-polyfill/src/index.ts:873
packages/rxjs/src/buffer-toggle.ts:16 · packages/rxjs/src/window-toggle.ts:18 — the two spans are one implementation copied and then locally edited — 460 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. — packages/rxjs/src/buffer-toggle.ts:16
packages/rxjs/src/buffer-time.ts:13 · packages/rxjs/src/window-time.ts:15 — the two spans are one implementation copied and then locally edited — 387 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. — packages/rxjs/src/buffer-time.ts:13
packages/rxjs/src/last.ts:5 · packages/rxjs/src/single.ts:7 — the two spans are one implementation copied and then locally edited — 336 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. — packages/rxjs/src/last.ts:5
packages/rxjs/src/first.ts:35 · packages/rxjs/src/last.ts:29 — the two spans are one implementation copied and then locally edited — 248 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. — packages/rxjs/src/first.ts:35
packages/rxjs/src/testing/index.ts:27 · packages/rxjs/src/testing/index.ts:83 — all 2 copies are in the same file, 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. — packages/rxjs/src/testing/index.ts:27
packages/rxjs/src/merge-scan.ts:50 · packages/rxjs/src/switch-scan.ts:31 — the two spans are one implementation copied and then locally edited — 146 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. — packages/rxjs/src/merge-scan.ts:50
packages/rxjs/src/finalize.ts:12 · packages/rxjs/src/tap.ts:46 — the two spans are one implementation copied and then locally edited — 114 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. — packages/rxjs/src/finalize.ts:12
packages/rxjs/src/async-subject.ts:29 · packages/rxjs/src/per-subscription-subject-base.ts:84 — the two spans are one implementation copied and then locally edited — 113 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. — packages/rxjs/src/async-subject.ts:29
apps/rxjs.dev/tools/transforms/authors-package/guide-package.js:17 · apps/rxjs.dev/tools/transforms/authors-package/tutorial-package.js:17 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — apps/rxjs.dev/tools/transforms/authors-package/guide-package.js:17
packages/rxjs/src/catch-error.ts:37 · packages/rxjs/src/retry-when.ts:42 — the two spans are one implementation copied and then locally edited — 92 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. — packages/rxjs/src/catch-error.ts:37
packages/rxjs/src/combine-latest-all.ts:20 · packages/rxjs/src/zip-all.ts:14 — the two spans are one implementation copied and then locally edited — 266 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. — packages/rxjs/src/combine-latest-all.ts:20
packages/rxjs/src/util/observable-async-generators.ts:47 · packages/rxjs/src/util/observable-async-generators.ts:191 — all 2 copies are in the same file, 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. — packages/rxjs/src/util/observable-async-generators.ts:47
packages/rxjs/src/skip-until.ts:4 · packages/rxjs/src/take-until.ts:4 — the two spans are one implementation copied and then locally edited — 142 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. — packages/rxjs/src/skip-until.ts:4
packages/rxjs/src/every.ts:19 · packages/rxjs/src/find-index.ts:14 — 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. — packages/rxjs/src/every.ts:19
packages/rxjs/src/exhaust-map.ts:4 · packages/rxjs/src/switch-map.ts:4 — the two spans are one implementation copied and then locally edited — 139 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. — packages/rxjs/src/exhaust-map.ts:4
packages/rxjs/src/util/observable-async-generators.ts:28 · packages/rxjs/src/util/observable-async-generators.ts:98 · packages/rxjs/src/util/observable-async-generators.ts:169 · packages/rxjs/src/util/observable-async-generators.ts:232 — all 4 copies are in the same file, 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. — packages/rxjs/src/util/observable-async-generators.ts:28
packages/observable-polyfill/src/index.ts:1045 · packages/observable-polyfill/src/index.ts:1071 — all 2 copies are in the same file, 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. — packages/observable-polyfill/src/index.ts:1045
packages/migrate/src/schemas.ts:133 · packages/migrate/src/schemas.ts:152 — 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. Check what actually differs between the copies before collapsing them: every one of them is an argument to a `object(…)` call, so where these calls are a MATRIX of cases — one per input, differing precisely in the case each one pins — the repetition is the enumeration and extracting the shared part would delete cases rather than de-duplicate anything. — packages/migrate/src/schemas.ts:133
packages/rxjs/src/delay.ts:4 · packages/rxjs/src/take-last.ts:4 — the two spans are one implementation copied and then locally edited — 93 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. — packages/rxjs/src/delay.ts:4
packages/observable-polyfill/src/index.ts:235 · packages/rxjs/src/per-subscription-subject-base.ts:138 — the two spans are one implementation copied and then locally edited — 62 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. — packages/observable-polyfill/src/index.ts:235
packages/rxjs/src/concat.ts:4 · packages/rxjs/src/on-error-resume-next.ts:7 · packages/rxjs/src/race.ts:6 — the 3 copies are spread across 3 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. — packages/rxjs/src/concat.ts:4
packages/rxjs/src/skip-last.ts:4 · packages/rxjs/src/take-last.ts:4 — the two spans are one implementation copied and then locally edited — 113 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. — packages/rxjs/src/skip-last.ts:4
packages/migrate/src/node.ts:205 · packages/migrate/src/skill-install.ts:355 — 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. — packages/migrate/src/node.ts:205
packages/migrate/src/semantics.ts:387 · packages/migrate/src/semantics.ts:407 — 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. — packages/migrate/src/semantics.ts:387
packages/rxjs/src/window-toggle.ts:182 · packages/rxjs/src/window-when.ts:163 — 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. — packages/rxjs/src/window-toggle.ts:182
packages/observable-polyfill/src/index.ts:645 · packages/observable-polyfill/src/index.ts:671 — all 2 copies are in the same file, 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. — packages/observable-polyfill/src/index.ts:645
packages/observable-polyfill/src/index.ts:1031 · packages/observable-polyfill/src/index.ts:1057 · packages/observable-polyfill/src/index.ts:1083 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — packages/observable-polyfill/src/index.ts:1031
packages/rxjs/src/buffer.ts:64 · packages/rxjs/src/throttle.ts:58 — the two spans are one implementation copied and then locally edited — 85 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. — packages/rxjs/src/buffer.ts:64
apps/rxjs.dev/src/app/custom-elements/code/code-example.component.ts:34 · apps/rxjs.dev/src/app/custom-elements/code/code.component.ts:81 — the two spans are one implementation copied and then locally edited — 58 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. — apps/rxjs.dev/src/app/custom-elements/code/code-example.component.ts:34
packages/migrate/src/semantics.ts:696 · packages/migrate/src/semantics.ts:708 — all 2 copies are in the same file, 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. — packages/migrate/src/semantics.ts:696
packages/rxjs/src/util/observable-async-generators.ts:15 · packages/rxjs/src/util/observable-async-generators.ts:221 — all 2 copies are in the same file, 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. — packages/rxjs/src/util/observable-async-generators.ts:15
packages/rxjs/src/util/observable-async-generators.ts:130 · packages/rxjs/src/util/observable-async-generators.ts:204 — all 2 copies are in the same file, 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. — packages/rxjs/src/util/observable-async-generators.ts:130
packages/migrate/src/mocha-chai-vitest.ts:149 · packages/migrate/src/semantics.ts:388 · packages/migrate/src/semantics.ts:408 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/migrate/src/mocha-chai-vitest.ts:149
packages/migrate/src/mocha-chai-vitest.ts:166 · packages/migrate/src/mocha-chai-vitest.ts:186 — all 2 copies are in the same file, 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. — packages/migrate/src/mocha-chai-vitest.ts:166
packages/rxjs/src/delay.ts:4 · packages/rxjs/src/repeat.ts:4 — the two spans are one implementation copied and then locally edited — 67 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. — packages/rxjs/src/delay.ts:4
packages/rxjs/src/every.ts:27 · packages/rxjs/src/find-index.ts:22 · packages/rxjs/src/is-empty.ts:16 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. 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. — packages/rxjs/src/every.ts:27
packages/rxjs/src/expand.ts:39 · packages/rxjs/src/merge-scan.ts:33 — 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. — packages/rxjs/src/expand.ts:39
packages/rxjs/src/retry.ts:56 · packages/rxjs/src/throttle.ts:61 — the two spans are one implementation copied and then locally edited — 52 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. — packages/rxjs/src/retry.ts:56
packages/migrate/src/mocha-chai-vitest.ts:116 · packages/migrate/src/semantics.ts:831 — 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. — packages/migrate/src/mocha-chai-vitest.ts:116
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 · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
apps/rxjs.dev/src/app/app.component.ts:16 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/app.component.ts:16
apps/rxjs.dev/src/app/custom-elements/announcement-bar/announcement-bar.component.ts:3 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/custom-elements/announcement-bar/announcement-bar.component.ts:3
apps/rxjs.dev/src/app/custom-elements/api/api-list.component.ts:17 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/custom-elements/api/api-list.component.ts:17
apps/rxjs.dev/src/app/custom-elements/api/api.service.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/custom-elements/api/api.service.ts:5
apps/rxjs.dev/src/app/custom-elements/code/code.component.ts:6 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/custom-elements/code/code.component.ts:6
apps/rxjs.dev/src/app/custom-elements/code/pretty-printer.service.ts:4 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/custom-elements/code/pretty-printer.service.ts:4
apps/rxjs.dev/src/app/custom-elements/contributor/contributor.service.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/custom-elements/contributor/contributor.service.ts:5
apps/rxjs.dev/src/app/custom-elements/operator-decision-tree/operator-decision-tree.service.ts:3 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/custom-elements/operator-decision-tree/operator-decision-tree.service.ts:3
apps/rxjs.dev/src/app/custom-elements/resource/resource.service.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/custom-elements/resource/resource.service.ts:5
apps/rxjs.dev/src/app/custom-elements/search/file-not-found-search.component.ts:3 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/custom-elements/search/file-not-found-search.component.ts:3
apps/rxjs.dev/src/app/custom-elements/toc/toc.component.ts:3 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/custom-elements/toc/toc.component.ts:3
apps/rxjs.dev/src/app/documents/document.service.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/documents/document.service.ts:5
apps/rxjs.dev/src/app/layout/doc-viewer/doc-viewer.component.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/layout/doc-viewer/doc-viewer.component.ts:5
apps/rxjs.dev/src/app/navigation/navigation.service.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/navigation/navigation.service.ts:5
apps/rxjs.dev/src/app/search/search-box/search-box.component.ts:4 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/search/search-box/search-box.component.ts:4
apps/rxjs.dev/src/app/search/search.service.ts:9 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/search/search.service.ts:9
apps/rxjs.dev/src/app/shared/location.service.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/shared/location.service.ts:5
apps/rxjs.dev/src/app/shared/scroll-spy.service.ts:4 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/shared/scroll-spy.service.ts:4
apps/rxjs.dev/src/app/shared/scroll.service.ts:4 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/shared/scroll.service.ts:4
apps/rxjs.dev/src/app/sw-updates/sw-updates.service.ts:4 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/app/sw-updates/sw-updates.service.ts:4
apps/rxjs.dev/src/testing/location.service.ts:2 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — apps/rxjs.dev/src/testing/location.service.ts:2
apps/rxjs.dev/tools/stackblitz/rxjs.version.js:6 reaches into another package with a relative path (../../../../packages/rxjs/REDACTED) — import the package by name instead. — apps/rxjs.dev/tools/stackblitz/rxjs.version.js:6
apps/rxjs.dev/tools/transforms/helpers/test-package.js:18 imports dgeni/lib/mocks/log, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/rxjs.dev/tools/transforms/helpers/test-package.js:18
packages/migrate/test/contracts/accepted-contracts.spec.ts:5 reaches past another workspace package's public entry into its internals with a relative path (../../../rxjs/src/behavior-subject.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/migrate/test/contracts/accepted-contracts.spec.ts:5
packages/migrate/test/contracts/accepted-contracts.spec.ts:6 reaches past another workspace package's public entry into its internals with a relative path (../../../rxjs/src/cold-observable.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/migrate/test/contracts/accepted-contracts.spec.ts:6
packages/migrate/test/contracts/accepted-contracts.spec.ts:7 reaches past another workspace package's public entry into its internals with a relative path (../../../rxjs/src/map.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/migrate/test/contracts/accepted-contracts.spec.ts:7
packages/migrate/test/contracts/accepted-contracts.spec.ts:8 reaches past another workspace package's public entry into its internals with a relative path (../../../rxjs/src/replay-subject.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/migrate/test/contracts/accepted-contracts.spec.ts:8
packages/migrate/test/contracts/accepted-contracts.spec.ts:9 reaches past another workspace package's public entry into its internals with a relative path (../../../rxjs/src/share.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/migrate/test/contracts/accepted-contracts.spec.ts:9
packages/migrate/test/mechanical/behavior.spec.ts:2 reaches past another workspace package's public entry into its internals with a relative path (../../../rxjs/src/cold-observable.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/migrate/test/mechanical/behavior.spec.ts:2
packages/migrate/test/mechanical/behavior.spec.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../../../rxjs/src/buffer.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/migrate/test/mechanical/behavior.spec.ts:3
packages/migrate/test/mechanical/behavior.spec.ts:4 reaches past another workspace package's public entry into its internals with a relative path (../../../rxjs/src/map.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/migrate/test/mechanical/behavior.spec.ts:4
packages/migrate/test/mechanical/behavior.spec.ts:5 reaches past another workspace package's public entry into its internals with a relative path (../../../rxjs/src/merge-map.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/migrate/test/mechanical/behavior.spec.ts:5
packages/rxjs/test/ported/setup.ts:4 reaches past another workspace package's public entry into its internals with a relative path (../../../observable-polyfill/src/index.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/rxjs/test/ported/setup.ts:4
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
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.
visit has cyclomatic complexity 117 and cognitive complexity 178; 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. — packages/rxjs/test/ported/tools/generate-port-manifest.mjs:7832
visitStatements has cyclomatic complexity 52 and cognitive complexity 78; 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. — packages/rxjs/test/ported/tools/generate-port-manifest.mjs:3021
isReference has cyclomatic complexity 35 and cognitive complexity 14; 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. — packages/rxjs/test/ported/tools/generate-port-manifest.mjs:8850
deepEqual has cyclomatic complexity 33 and cognitive complexity 38; 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. — packages/test/src/assertions.ts:306
visit has cyclomatic complexity 32 and cognitive complexity 32; 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. — packages/migrate/src/semantics.ts:120
auditReport has cyclomatic complexity 31 and cognitive complexity 55; 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. — packages/observable-polyfill/test/wpt/lib/report.mjs:176
validateCatalog has cyclomatic complexity 30 and cognitive complexity 55; 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. — packages/rxjs/test/ported/tools/generate-unsupported-surface-doc.mjs:35
collectNestedCases has cyclomatic complexity 29 and cognitive complexity 60; 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. — packages/rxjs/test/ported/tools/generate-port-manifest.mjs:2901
baselineFromAuditReport has cyclomatic complexity 25 and cognitive complexity 23; 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. — packages/rxjs/test/ported/tools/mode-audit-baseline.mjs:3
getDynamicVariants has cyclomatic complexity 24 and cognitive complexity 38; 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. — packages/rxjs/test/ported/tools/generate-port-manifest.mjs:7367
verifyVendoredImport has cyclomatic complexity 24 and cognitive complexity 34; 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. — packages/observable-polyfill/test/wpt/lib/provenance.mjs:64
mergeLedger has cyclomatic complexity 23 and cognitive complexity 29; 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. — packages/rxjs/test/ported/tools/generate-failure-tracker.mjs:204
analyzeTestSource has cyclomatic complexity 22 and cognitive complexity 32; 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. — packages/migrate/src/analyze.ts:14
(anonymous) has cyclomatic complexity 22 and cognitive complexity 30; 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. — packages/migrate/src/semantics.ts:266
validateOsvExceptions has cyclomatic complexity 22 and cognitive complexity 29; 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. — scripts/security/check-osv-exceptions.mjs:21
visit has cyclomatic complexity 21 and cognitive complexity 33; 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. — packages/rxjs/test/ported/tools/generate-port-manifest.mjs:7623
parseMarbles has cyclomatic complexity 20 and cognitive complexity 27; 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. — packages/test/src/marble-parser.ts:50
(anonymous) has cyclomatic complexity 19 and cognitive complexity 24; 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. — packages/observable-polyfill/src/index.ts:136
$process has cyclomatic complexity 18 and cognitive complexity 28; 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. — apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js:25
parseSubscriptionMarbles has cyclomatic complexity 18 and cognitive complexity 25; 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. — packages/test/src/marble-parser.ts:154
getLinkInfoImpl has cyclomatic complexity 18 and cognitive complexity 18; 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. — apps/rxjs.dev/tools/transforms/links-package/services/getLinkInfo.js:18
migrateTestSchedulerSemantics has cyclomatic complexity 18 and cognitive complexity 18; 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. — packages/migrate/src/semantics.ts:17
validateReport has cyclomatic complexity 18 and cognitive complexity 18; 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. — packages/rxjs/test/ported/tools/generate-failure-tracker.mjs:140
evaluateObservedAuthority has cyclomatic complexity 17 and cognitive complexity 26; 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. — packages/migrate/test/agent/evaluation.ts:682
auditReleaseMatrix has cyclomatic complexity 17 and cognitive complexity 23; 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. — scripts/check-release-coherence.mjs:69
parseArguments has cyclomatic complexity 17 and cognitive complexity 16; 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. — packages/migrate/src/cli.ts:120
getModeAwareObservableTarget 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. — packages/rxjs/test/ported/tools/generate-port-manifest.mjs:7751
summarizeGroup has cyclomatic complexity 16 and cognitive complexity 29; 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. — packages/rxjs/test/ported/tools/generate-failure-tracker.mjs:551
auditPackageDocs has cyclomatic complexity 16 and cognitive complexity 29; 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. — scripts/check-package-docs.mjs:15
validate has cyclomatic complexity 16 and cognitive complexity 24; 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. — packages/rxjs/test/ported/tools/generate-migration-evidence-ledger.mjs:290
assessAvailability has cyclomatic complexity 16 and cognitive complexity 24; 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. — packages/rxjs/test/ported/tools/generate-port-manifest.mjs:8775
(anonymous) has cyclomatic complexity 16 and cognitive complexity 15; 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. — packages/rxjs/src/sequence-equal.ts:31
verifyBrowser has cyclomatic complexity 16 and cognitive complexity 14; 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. — packages/observable-polyfill/test/wpt/lib/browser.mjs:405
visit has cyclomatic complexity 15 and cognitive complexity 26; 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. — packages/migrate/src/mocha-chai-vitest.ts:59
evaluateManifestReadiness has cyclomatic complexity 15 and cognitive complexity 24; 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. — packages/migrate/test/agent/evaluation.ts:547
verifyArtifacts has cyclomatic complexity 15 and cognitive complexity 23; 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. — packages/migrate/test/agent/qualification-record.ts:337
requestRotation has cyclomatic complexity 15 and cognitive complexity 18; 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. — packages/rxjs/src/window-when.ts:46
compareEvaluation has cyclomatic complexity 15 and cognitive complexity 15; 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. — packages/migrate/test/agent/qualification-record.ts:294
auditEsmDistribution has cyclomatic complexity 15 and cognitive complexity 15; 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. — scripts/check-release-coherence.mjs:178
readImports has cyclomatic complexity 14 and cognitive complexity 22; 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. — packages/rxjs/test/ported/tools/generate-port-manifest.mjs:8711
Do you agree with this assessment?
R3 · Large Files9.7 / 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.
packages/observable-polyfill/src/index.ts has 1302 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/observable-polyfill/src/index.ts:1
packages/migrate/src/semantics.ts has 798 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/migrate/src/semantics.ts:1
apps/rxjs.dev/src/app/app.component.ts has 424 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/rxjs.dev/src/app/app.component.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage9.1 / 10Exemplary✓ 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.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×29) — packages/rxjs/src/testing/index.ts:1, apps/rxjs.dev/tools/transforms/angular-api-package/index.js:1, apps/rxjs.dev/tools/transforms/angular-api-package/processors/mergeDecoratorDocs.js:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
the root package is TypeScript, but a type error in it cannot fail anything this repository runs: its `test:release:adoption` script (`node scripts/qualify-prerelease.mjs`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles. — REDACTED:24
The package in `apps/rxjs.dev` declares the lint script `lint` (`pnpm run docs-lint && ng lint && pnpm run tools-lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `apps/rxjs.dev` (or the workspace's task runner). — apps/rxjs.dev/REDACTED:16
The package in `packages/observable-polyfill` declares the lint script `lint` (`eslint ./src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/observable-polyfill` (or the workspace's task runner). — packages/observable-polyfill/REDACTED:21
The package in `packages/rxjs` declares the lint script `lint` (`eslint ./src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/rxjs` (or the workspace's task runner). — packages/rxjs/REDACTED:25
The package in `packages/test` declares the lint script `lint` (`eslint ./src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/test` (or the workspace's task runner). — packages/test/REDACTED:21
Do you agree with this assessment?
R7 · Dead Code9.9 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 90 application, 40 tooling and 638 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (90 application, 40 tooling, 638 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×10) — packages/rxjs/src/testing/scheduled-observable.ts, apps/rxjs.dev/tools/transforms/authors-package/api-package.js, packages/rxjs/src/skip-while.ts, …
no import path from any entry point (90 application, 40 tooling, 638 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/rxjs.dev/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/rxjs.dev/src/testing/search.service.ts
Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used. — packages/rxjs/src/testing/index.ts:193
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. — apps/rxjs.dev/tools/transforms/angular-base-package/post-processors/autolink-headings.js:1
Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2) — REDACTED:34, REDACTED:38
Only test files import it (first: apps/rxjs.dev/tests/e2e/visual-testing.e2e-spec.ts:3) — move it to devDependencies. — apps/rxjs.dev/REDACTED:60
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
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 · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `firebase.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — apps/rxjs.dev/firebase.json:1
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
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 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.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. 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 `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
`debug` at line 28 is called with an argument built by `duplicateDocs.map((doc : Document) => doc.name)` (line 29), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — apps/rxjs.dev/tools/transforms/angular-api-package/processors/markAliases.ts:28
What to do
Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped4.1 / 10Weak✓ 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.
`formattedCode` 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. — apps/rxjs.dev/src/app/custom-elements/code/code.component.ts:160
`this.selector` 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. — apps/rxjs.dev/src/app/custom-elements/lazy-custom-element.component.ts:24
`initialDocViewerContent` 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. — apps/rxjs.dev/src/app/layout/doc-viewer/doc-viewer.component.ts:73
`doc.contents||''` 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. — apps/rxjs.dev/src/app/layout/doc-viewer/doc-viewer.component.ts:144
`icon.svgSource` 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. — apps/rxjs.dev/src/app/shared/custom-icon-registry.ts:56
`heading.innerHTML` 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. — apps/rxjs.dev/src/app/shared/toc.service.ts:54
`div.innerHTML.trim()` is text this program did not author, and it is written into the text of an element through Angular's `bypassSecurityTrustHtml` 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. — apps/rxjs.dev/src/app/shared/toc.service.ts:72
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.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
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. (×5) — packages/rxjs/src/connectable.ts:155, packages/migrate/src/skill-cli.ts:63, packages/migrate/src/skill-install.ts:261, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — packages/observable-polyfill/src/index.ts:1206
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
16/17 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~2.8 `!` null assertions per 1k TypeScript source lines — 55 assertion(s) across the 19786 source line(s) of the 243 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/observable-polyfill/src/index.ts (13), apps/rxjs.dev/src/app/custom-elements/elements-loader.ts (3), packages/rxjs/src/combine.ts (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 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 — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
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 — 55 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.
AX1 Captive dependencies — Not applicable: Angular's root injector cannot see a component-level provider, so a root service asking for one fails with NullInjectorError instead of capturing it.
AX2 Stateful singletons — Not applicable: 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).
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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): REDACTED has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. The cause is in the repository, not in our sandbox: REDACTED has no "start" script, so `npm run start` could not start the app. Nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
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.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
D27 Navigability — symbol resolution incomplete — navigability not assessed
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 97 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
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.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
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
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, 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.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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
X2 Cancellation propagation — 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
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
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 — 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
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· <label> that labels no control · ×8
<label> that labels no control apps/rxjs.dev/tools/transforms/templates/api/base.template.html:24— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control apps/rxjs.dev/tools/transforms/templates/api/base.template.html:25— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control apps/rxjs.dev/tools/transforms/templates/api/base.template.html:26— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control apps/rxjs.dev/tools/transforms/templates/api/base.template.html:27— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control apps/rxjs.dev/tools/transforms/templates/api/base.template.html:28— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control apps/rxjs.dev/tools/transforms/templates/api/base.template.html:29— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control apps/rxjs.dev/tools/transforms/templates/api/lib/memberHelpers.html:151— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control apps/rxjs.dev/tools/transforms/templates/overview-dump.template.html:4— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
D30 · Dependency Vulnerabilities· High vulnerability · ×2
REDACTED
REDACTED
AC1 · Text alternatives· <img> without a text alternative · ×1
<img> without a text alternative apps/rxjs.dev/src/app/custom-elements/announcement-bar/announcement-bar.component.ts:50— 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 apps/rxjs.dev/src/app/layout/doc-viewer/dt.component.ts:9— 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 apps/rxjs.dev/tools/transforms/templates/overview-dump.template.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> apps/rxjs.dev/tools/transforms/templates/overview-dump.template.html:1— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×1
Click handler on a non-interactive <div> apps/rxjs.dev/src/app/custom-elements/contributor/contributor.component.ts:39— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×1
Click handler on a non-interactive <span> apps/rxjs.dev/src/app/layout/notification/notification.component.ts:12— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Assertions commented out: navigationViews observable should complete apps/rxjs.dev/src/app/navigation/navigation.service.spec.ts:32— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Unlisted import 'hast-util-has-property' apps/rxjs.dev/tools/transforms/angular-base-package/post-processors/autolink-headings.js:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/app.component.ts:16— apps/rxjs.dev/src/app/app.component.ts:16 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/custom-elements/announcement-bar/announcement-bar.component.ts:3— apps/rxjs.dev/src/app/custom-elements/announcement-bar/announcement-bar.component.ts:3 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/custom-elements/api/api-list.component.ts:17— apps/rxjs.dev/src/app/custom-elements/api/api-list.component.ts:17 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/custom-elements/api/api.service.ts:5— apps/rxjs.dev/src/app/custom-elements/api/api.service.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/custom-elements/code/code.component.ts:6— apps/rxjs.dev/src/app/custom-elements/code/code.component.ts:6 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/custom-elements/code/pretty-printer.service.ts:4— apps/rxjs.dev/src/app/custom-elements/code/pretty-printer.service.ts:4 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/custom-elements/contributor/contributor.service.ts:5— apps/rxjs.dev/src/app/custom-elements/contributor/contributor.service.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/custom-elements/operator-decision-tree/operator-decision-tree.service.ts:3— apps/rxjs.dev/src/app/custom-elements/operator-decision-tree/operator-decision-tree.service.ts:3 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/custom-elements/resource/resource.service.ts:5— apps/rxjs.dev/src/app/custom-elements/resource/resource.service.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/custom-elements/search/file-not-found-search.component.ts:3— apps/rxjs.dev/src/app/custom-elements/search/file-not-found-search.component.ts:3 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/custom-elements/toc/toc.component.ts:3— apps/rxjs.dev/src/app/custom-elements/toc/toc.component.ts:3 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/documents/document.service.ts:5— apps/rxjs.dev/src/app/documents/document.service.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/layout/doc-viewer/doc-viewer.component.ts:5— apps/rxjs.dev/src/app/layout/doc-viewer/doc-viewer.component.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/navigation/navigation.service.ts:5— apps/rxjs.dev/src/app/navigation/navigation.service.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/search/search-box/search-box.component.ts:4— apps/rxjs.dev/src/app/search/search-box/search-box.component.ts:4 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/search/search.service.ts:9— apps/rxjs.dev/src/app/search/search.service.ts:9 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/shared/location.service.ts:5— apps/rxjs.dev/src/app/shared/location.service.ts:5 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/shared/scroll-spy.service.ts:4— apps/rxjs.dev/src/app/shared/scroll-spy.service.ts:4 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/shared/scroll.service.ts:4— apps/rxjs.dev/src/app/shared/scroll.service.ts:4 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/app/sw-updates/sw-updates.service.ts:4— apps/rxjs.dev/src/app/sw-updates/sw-updates.service.ts:4 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:deep-import] apps/rxjs.dev/src/testing/location.service.ts:2— apps/rxjs.dev/src/testing/location.service.ts:2 imports rxjs/operators, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:relative-cross-package] apps/rxjs.dev/tools/stackblitz/rxjs.version.js:6— apps/rxjs.dev/tools/stackblitz/rxjs.version.js:6 reaches into another package with a relative path (../../../../packages/rxjs/REDACTED) — import the package by name instead.
Boundary violation [package:third-party-deep-import] apps/rxjs.dev/tools/transforms/helpers/test-package.js:18— apps/rxjs.dev/tools/transforms/helpers/test-package.js:18 imports dgeni/lib/mocks/log, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:test-cross-package-internals] packages/migrate/test/contracts/accepted-contracts.spec.ts:5— packages/migrate/test/contracts/accepted-contracts.spec.ts:5 reaches past another workspace package's public entry into its internals with a relative path (../../../rxjs/src/behavior-subject.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/migrate/test/contracts/accepted-contracts.spec.ts:6— packages/migrate/test/contracts/accepted-contracts.spec.ts:6 reaches past another workspace package's public entry into its internals with a relative path (../../../rxjs/src/cold-observable.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
+ 8 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×29
No test reaches this file packages/rxjs/src/testing/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular-api-package/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular-api-package/processors/mergeDecoratorDocs.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/scripts/test-pwa-score.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/rxjs/src/testing/scheduled-observable.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular.io-package/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/authors-package/watchr.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular.io-package/processors/processNavigationMap.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/authors-package/api-package.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular-api-package/post-processors/embedMarbleDiagrams.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/rxjs-decision-tree-generator/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/rxjs/src/skip-while.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular-api-package/processors/extractDecoratedClasses.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/rxjs/src/default-if-empty.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular-api-package/processors/generateDeprecationsListDoc.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular.io-package/processors/createOverviewDump.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular-api-package/processors/filterContainedDocs.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/test.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular-api-package/tag-defs/internal.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular-api-package/processors/checkOperator.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular-api-package/processors/convertPrivateClassesToInterfaces.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular.io-package/processors/cleanGeneratedFiles.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/rxjs.dev/tools/transforms/angular-api-package/tag-defs/throws.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/rxjs/src/never.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/rxjs/src/empty.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
+ 4 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×27
No assertions: matches exact timestamped observable messages packages/test/src/index.spec.ts:24— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: uses independent timelines for cold test observables packages/test/src/index.spec.ts:35— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shares one active producer for platform test observables packages/test/src/index.spec.ts:55— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: creates a subject-like hot observable on an absolute timeline packages/test/src/index.spec.ts:65— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: attaches a time-zero observation before a hot time-zero notification packages/test/src/index.spec.ts:86— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: supports toEqual comparisons packages/test/src/index.spec.ts:208— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: observes from frame zero when only unsubscription is marked packages/test/src/index.spec.ts:214— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: treats the unsubscription frame as an exclusive observation boundary packages/test/src/index.spec.ts:223— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: aborts an observation before a hot notification at the same frame packages/test/src/index.spec.ts:235— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: supports grouped values, errors, and observable metastreams packages/test/src/index.spec.ts:244— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: restarts a platform source after the final observer leaves packages/test/src/index.spec.ts:256— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: supports negative hot time with a caret zero point packages/test/src/index.spec.ts:266— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: maps values packages/migrate/test/fixtures/mocha-chai-map.ts:12— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shows the landing page apps/rxjs.dev/tests/e2e/visual-testing.e2e-spec.ts:7— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shows the overview page apps/rxjs.dev/tests/e2e/visual-testing.e2e-spec.ts:14— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shows the API page apps/rxjs.dev/tests/e2e/visual-testing.e2e-spec.ts:21— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shows the migration page apps/rxjs.dev/tests/e2e/visual-testing.e2e-spec.ts:28— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shows the team page apps/rxjs.dev/tests/e2e/visual-testing.e2e-spec.ts:35— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should return an observable apps/rxjs.dev/src/app/layout/doc-viewer/doc-viewer.component.spec.ts:604— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should fetch a document for the initial location apps/rxjs.dev/src/app/documents/document.service.spec.ts:41— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should map the "empty" location to the correct document request apps/rxjs.dev/src/app/documents/document.service.spec.ts:175— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should map the "folder" locations to the correct document request apps/rxjs.dev/src/app/documents/document.service.spec.ts:182— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should not immediately connect to the server apps/rxjs.dev/src/app/custom-elements/api/api.service.spec.ts:30— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should connect to the server w/ expected URL apps/rxjs.dev/src/app/custom-elements/api/api.service.spec.ts:91— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should make a single request to the server apps/rxjs.dev/src/app/custom-elements/announcement-bar/announcement-bar.component.spec.ts:40— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
TodoComment packages/rxjs/test/ported/platform/operators/share-replay.spec.ts:267— // TODO: revisit once https://github.com/ReactiveX/rxjs/issues/5523 is fixed
TodoComment packages/rxjs/test/ported/cold/operators/share-replay.spec.ts:232— // TODO: revisit once https://github.com/ReactiveX/rxjs/issues/5523 is fixed
TodoComment apps/rxjs.dev/tools/transforms/rxjs-decision-tree-generator/src/lib/fixtures.ts:45— // TODO consider using the real API list — 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 apps/rxjs.dev/src/app/shared/location.service.ts:38— // TODO: ignore if url-without-hash-or-search matches current location? — 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 apps/rxjs.dev/src/app/shared/location.service.ts:123— // TODO: should we also allow an explicit `_self` target to opt-out? — 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 apps/rxjs.dev/src/app/layout/doc-viewer/doc-viewer.component.ts:22— // TODO(robwormald): shadow DOM and emulated don't work here (?!) — 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 apps/rxjs.dev/src/app/custom-elements/custom-elements.module.ts:20— // TODO(andrewjs): Provide first-class support for providing this. — 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 apps/rxjs.dev/src/app/custom-elements/element-registry.ts:5— // TODO(andrewjs): This is a hack, Angular should have first-class support for preparing a module — 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 apps/rxjs.dev/src/app/custom-elements/contributor/contributor.service.ts:9— // TODO(andrewjs): Look into changing this so that we don't import the service just to get the const — 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 apps/rxjs.dev/src/app/custom-elements/api/api-list.component.ts:96— // TODO: may need to debounce as the original did — 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 apps/rxjs.dev/src/app/custom-elements/api/api.service.ts:45— // TODO: get URL for fetchSections by configuration? — 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 apps/rxjs.dev/src/app/custom-elements/api/api.service.ts:73— // TODO: get URL by configuration? — 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 apps/rxjs.dev/src/app/custom-elements/api/api.service.ts:83— // TODO: handle error — 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.
Hotspot: packages/rxjs/test/ported/tools/generate-port-manifest.mjs packages/rxjs/test/ported/tools/generate-port-manifest.mjs:7832— packages/rxjs/test/ported/tools/generate-port-manifest.mjs changed 51 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 117 in visit at line 7832. 8 of those changes were fix/bug commits, and the other 43 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-07..2026-08-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-07 15:15:50 -05:00' --until='2026-08-05 15:15:50 -05:00' --full-history --no-merges -- packages/rxjs/test/ported/tools/generate-port-manifest.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/rxjs/src/group-by.ts packages/rxjs/src/group-by.ts:80— packages/rxjs/src/group-by.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in group-by.groupByOperator at line 80. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-07..2026-08-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-07 15:15:50 -05:00' --until='2026-08-05 15:15:50 -05:00' --full-history --no-merges -- packages/rxjs/src/group-by.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/rxjs/test/ported/tools/generate-failure-tracker.mjs packages/rxjs/test/ported/tools/generate-failure-tracker.mjs:204— packages/rxjs/test/ported/tools/generate-failure-tracker.mjs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in mergeLedger at line 204. 2 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-07..2026-08-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-07 15:15:50 -05:00' --until='2026-08-05 15:15:50 -05:00' --full-history --no-merges -- packages/rxjs/test/ported/tools/generate-failure-tracker.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: scripts/check-release-coherence.mjs scripts/check-release-coherence.mjs:69— scripts/check-release-coherence.mjs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in check-release-coherence.auditReleaseMatrix at line 69. 2 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-07..2026-08-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-07 15:15:50 -05:00' --until='2026-08-05 15:15:50 -05:00' --full-history --no-merges -- scripts/check-release-coherence.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/rxjs/src/zip.ts packages/rxjs/src/zip.ts:27— packages/rxjs/src/zip.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in zip.zip at line 27. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-07..2026-08-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-07 15:15:50 -05:00' --until='2026-08-05 15:15:50 -05:00' --full-history --no-merges -- packages/rxjs/src/zip.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/migrate/src/semantics.ts packages/migrate/src/semantics.ts:17— packages/migrate/src/semantics.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in semantics.migrateTestSchedulerSemantics at line 17. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-07..2026-08-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-07 15:15:50 -05:00' --until='2026-08-05 15:15:50 -05:00' --full-history --no-merges -- packages/migrate/src/semantics.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/rxjs/src/sequence-equal.ts packages/rxjs/src/sequence-equal.ts:31— packages/rxjs/src/sequence-equal.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in (anonymous) at line 31. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-07..2026-08-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-07 15:15:50 -05:00' --until='2026-08-05 15:15:50 -05:00' --full-history --no-merges -- packages/rxjs/src/sequence-equal.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/migrate/src/analyze.ts packages/migrate/src/analyze.ts:14— packages/migrate/src/analyze.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in analyze.analyzeTestSource at line 14. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-07..2026-08-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-07 15:15:50 -05:00' --until='2026-08-05 15:15:50 -05:00' --full-history --no-merges -- packages/migrate/src/analyze.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/rxjs/test/ported/tools/generate-migration-evidence-ledger.mjs packages/rxjs/test/ported/tools/generate-migration-evidence-ledger.mjs:290— packages/rxjs/test/ported/tools/generate-migration-evidence-ledger.mjs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in validate at line 290. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-07..2026-08-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-07 15:15:50 -05:00' --until='2026-08-05 15:15:50 -05:00' --full-history --no-merges -- packages/rxjs/test/ported/tools/generate-migration-evidence-ledger.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×7
Animation without a prefers-reduced-motion guard apps/rxjs.dev/src/styles/2-modules/_code.scss:66— `code-tabs mat-tab-body-content .fadeIn` moves (`animation: opacity 2s ease-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard apps/rxjs.dev/src/styles/2-modules/_contributor.scss:105— `aio-contributor div.contributor-card` moves (`transition: transform ease 500ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard apps/rxjs.dev/src/styles/2-modules/_notification.scss:104— `.aio-notification-animating mat-sidenav.mat-sidenav.sidenav` moves (`transition: top 250ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard apps/rxjs.dev/src/styles/1-layouts/_sidenav.scss:112— `.heading-children.expanded` moves (`transition: visibility 500ms, opacity 500ms, max-height 500ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard apps/rxjs.dev/src/styles/1-layouts/_sidenav.scss:121— `.heading-children.collapsed` moves (`transition: visibility 275ms, opacity 275ms, max-height 280ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard apps/rxjs.dev/src/styles/1-layouts/_top-menu.scss:68— `.hamburger.mat-button:not(.starting)` moves (`transition-property: color, margin`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard apps/rxjs.dev/src/styles/1-layouts/_top-menu.scss:174— `aio-search-box.search-container input` moves (`transition: width 0.4s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Deprecated: eyes.selenium apps/rxjs.dev/REDACTED:60— eyes.selenium 3.9.1, declared in apps/rxjs.dev/REDACTED, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint apps/rxjs.dev/REDACTED:95— eslint 8.56.0, declared in apps/rxjs.dev/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: image-size apps/rxjs.dev/REDACTED:108— image-size 0.7.5, declared in apps/rxjs.dev/REDACTED, is marked deprecated by its publisher: "Please migrate to image-size@2.x". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: protractor apps/rxjs.dev/REDACTED:124— protractor 7.0.0, declared in apps/rxjs.dev/REDACTED, is marked deprecated by its publisher: "We have news to share - Protractor is deprecated and will reach end-of-life by Summer 2023. To learn more and find out about other options please refer to this post on the Angular blog. Thank you for using and contributing to Protractor. https://goo.gle/state-of-e2e-in-angular". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: rimraf apps/rxjs.dev/REDACTED:128— rimraf 2.7.1, declared in apps/rxjs.dev/REDACTED, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: svgo apps/rxjs.dev/REDACTED:132— svgo 1.3.2, declared in apps/rxjs.dev/REDACTED, is marked deprecated by its publisher: "This SVGO version is no longer supported. Upgrade to v2.x.x.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint REDACTED:40— eslint 8.57.1, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×7
Untrusted text written into markup unescaped apps/rxjs.dev/src/app/custom-elements/code/code.component.ts:160— `formattedCode` 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 apps/rxjs.dev/src/app/custom-elements/lazy-custom-element.component.ts:24— `this.selector` 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 apps/rxjs.dev/src/app/layout/doc-viewer/doc-viewer.component.ts:73— `initialDocViewerContent` 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 apps/rxjs.dev/src/app/layout/doc-viewer/doc-viewer.component.ts:144— `doc.contents||''` 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 apps/rxjs.dev/src/app/shared/custom-icon-registry.ts:56— `icon.svgSource` 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 apps/rxjs.dev/src/app/shared/toc.service.ts:54— `heading.innerHTML` 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 apps/rxjs.dev/src/app/shared/toc.service.ts:72— `div.innerHTML.trim()` is text this program did not author, and it is written into the text of an element through Angular's `bypassSecurityTrustHtml` 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.
Swallowed exception (empty catch) packages/rxjs/src/connectable.ts:155— 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) packages/observable-polyfill/src/index.ts:1206— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/migrate/src/skill-cli.ts:63— 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) packages/migrate/src/skill-install.ts:261— 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) apps/rxjs.dev/src/app/shared/location.service.ts:77— 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) apps/rxjs.dev/src/app/shared/reporting-error-handler.ts:39— 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.
R6 · Tooling· This package's lint script runs in no CI job · ×4
This package's lint script runs in no CI job apps/rxjs.dev/REDACTED:16— The package in `apps/rxjs.dev` declares the lint script `lint` (`pnpm run docs-lint && ng lint && pnpm run tools-lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `apps/rxjs.dev` (or the workspace's task runner).
This package's lint script runs in no CI job packages/observable-polyfill/REDACTED:21— The package in `packages/observable-polyfill` declares the lint script `lint` (`eslint ./src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/observable-polyfill` (or the workspace's task runner).
This package's lint script runs in no CI job packages/rxjs/REDACTED:25— The package in `packages/rxjs` declares the lint script `lint` (`eslint ./src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/rxjs` (or the workspace's task runner).
This package's lint script runs in no CI job packages/test/REDACTED:21— The package in `packages/test` declares the lint script `lint` (`eslint ./src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/test` (or the workspace's task runner).
AC3 · Page structure· Data table has no header cells · ×3
Data table has no header cells apps/rxjs.dev/tools/transforms/templates/api/deprecation.template.html:5— A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
Data table has no header cells apps/rxjs.dev/tools/transforms/templates/api/function.template.html:22— A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
Data table has no header cells apps/rxjs.dev/tools/transforms/templates/api/lib/paramList.html:16— A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
FunctionTooLong: semantics.migrateTestSchedulerSemantics packages/migrate/src/semantics.ts:17— FunctionTooLong — migrateTestSchedulerSemantics runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: group-by.groupByOperator packages/rxjs/src/group-by.ts:80— FunctionTooLong — groupByOperator runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: generateKeywords.generateKeywordsProcessor apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js:11— FunctionTooLong — generateKeywordsProcessor runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (14 lines × 2 locations) packages/migrate/src/node.ts:205— packages/migrate/src/node.ts:205 · packages/migrate/src/skill-install.ts:355 — 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 (14 lines × 2 locations) packages/migrate/src/semantics.ts:387— packages/migrate/src/semantics.ts:387 · packages/migrate/src/semantics.ts:407 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2 locations) packages/rxjs/src/window-toggle.ts:182— packages/rxjs/src/window-toggle.ts:182 · packages/rxjs/src/window-when.ts:163 — 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 (12 lines × 2 locations) packages/migrate/src/semantics.ts:696— packages/migrate/src/semantics.ts:696 · packages/migrate/src/semantics.ts:708 — all 2 copies are in the same file, 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 (12 lines × 2 locations) packages/rxjs/src/util/observable-async-generators.ts:15— packages/rxjs/src/util/observable-async-generators.ts:15 · packages/rxjs/src/util/observable-async-generators.ts:221 — all 2 copies are in the same file, 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 (12 lines × 2 locations) packages/rxjs/src/util/observable-async-generators.ts:130— packages/rxjs/src/util/observable-async-generators.ts:130 · packages/rxjs/src/util/observable-async-generators.ts:204 — all 2 copies are in the same file, 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.
Low contrast colour pair in CSS (3.3:1) apps/rxjs.dev/src/styles/2-modules/_resources.scss:135— `&:hover` sets color: #2B85E7 on background-color: #edf0f2 — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.3:1) apps/rxjs.dev/src/styles/2-modules/_resources.scss:148— `&:hover` sets color: #2B85E7 on background-color: #edf0f2 — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×2
Focus outline removed in CSS without a :focus replacement apps/rxjs.dev/src/styles/1-layouts/_sidenav.scss:183— `mat-sidenav .doc-version select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement apps/rxjs.dev/src/styles/1-layouts/_top-menu.scss:170— `aio-search-box.search-container input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
FileTooLong: src/index.ts packages/observable-polyfill/src/index.ts— FileTooLong — 914 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 414 over it, 1.83× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/semantics.ts packages/migrate/src/semantics.ts— FileTooLong — 645 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 145 over it, 1.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Low cohesion: LiveExampleComponent (LCOM4 7) apps/rxjs.dev/src/app/custom-elements/live-example/live-example.component.ts:52— LiveExampleComponent's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NavigationService (LCOM4 4) apps/rxjs.dev/src/app/navigation/navigation.service.ts:16— NavigationService's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
R10 · Code Duplication· Duplicated block with local edits (15 matched lines × 2 locations) · ×2
Duplicated block with local edits (15 matched lines × 2 locations) packages/observable-polyfill/src/index.ts:235— packages/observable-polyfill/src/index.ts:235 · packages/rxjs/src/per-subscription-subject-base.ts:138 — the two spans are one implementation copied and then locally edited — 62 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 (15 matched lines × 2 locations) packages/rxjs/src/skip-last.ts:4— packages/rxjs/src/skip-last.ts:4 · packages/rxjs/src/take-last.ts:4 — the two spans are one implementation copied and then locally edited — 113 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 (11 lines × 3 locations) packages/migrate/src/mocha-chai-vitest.ts:149— packages/migrate/src/mocha-chai-vitest.ts:149 · packages/migrate/src/semantics.ts:388 · packages/migrate/src/semantics.ts:408 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (11 lines × 3 locations) packages/rxjs/src/every.ts:27— packages/rxjs/src/every.ts:27 · packages/rxjs/src/find-index.ts:22 · packages/rxjs/src/is-empty.ts:16 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. 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 (11 lines × 2 locations) packages/migrate/src/mocha-chai-vitest.ts:166— packages/migrate/src/mocha-chai-vitest.ts:166 · packages/migrate/src/mocha-chai-vitest.ts:186 — all 2 copies are in the same file, 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 (11 lines × 2 locations) packages/rxjs/src/expand.ts:39— packages/rxjs/src/expand.ts:39 · packages/rxjs/src/merge-scan.ts:33 — 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 (11 matched lines × 2 locations) · ×2
Duplicated block with local edits (11 matched lines × 2 locations) packages/rxjs/src/delay.ts:4— packages/rxjs/src/delay.ts:4 · packages/rxjs/src/repeat.ts:4 — the two spans are one implementation copied and then locally edited — 67 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 (11 matched lines × 2 locations) packages/rxjs/src/retry.ts:56— packages/rxjs/src/retry.ts:56 · packages/rxjs/src/throttle.ts:61 — the two spans are one implementation copied and then locally edited — 52 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.
Empty <h1> heading apps/rxjs.dev/content/marketing/index.html:32— An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark apps/rxjs.dev/tools/transforms/templates/overview-dump.template.html:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC4 · Keyboard semantics· Anchor without href · ×1
Anchor without href apps/rxjs.dev/src/app/custom-elements/contributor/contributor-list.component.ts:11— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
semantics.migrateTestSchedulerSemantics (cyclomatic 47) packages/migrate/src/semantics.ts:17— semantics.migrateTestSchedulerSemantics has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 14 of the 47 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 120, 215). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/migrate/src/semantics.ts holds 2 of the 12 methods over the threshold — including the worst — and 39 of the 122 points over it (32%), 2.1× the next-largest file (packages/rxjs/src/group-by.ts at 19). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
group-by.groupByOperator (cyclomatic 34) packages/rxjs/src/group-by.ts:80— group-by.groupByOperator has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 2 of the 34 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 241, 155, 200, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
generateKeywords.generateKeywordsProcessor.$process (cyclomatic 31) apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js:25— generateKeywords.generateKeywordsProcessor.$process has cyclomatic complexity 31 (threshold 15). Of this number, 18 points are the body's own statements and 13 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
generateKeywordsProcessor.$process (cyclomatic 31) apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js:25— generateKeywordsProcessor.$process has cyclomatic complexity 31 (threshold 15). Of this number, 18 points are the body's own statements and 13 belong to 11 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
mocha-chai-vitest.migrateMochaChaiToVitest (cyclomatic 26) packages/migrate/src/mocha-chai-vitest.ts:13— mocha-chai-vitest.migrateMochaChaiToVitest has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 10 of the 26 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 59, 114). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
semantics.collectUnsafeOperatorLocals::visit (cyclomatic 22) packages/migrate/src/semantics.ts:266— semantics.collectUnsafeOperatorLocals::visit has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/migrate/src/semantics.ts holds 2 of the 12 methods over the threshold — including the worst — and 39 of the 122 points over it (32%), 2.1× the next-largest file (packages/rxjs/src/group-by.ts at 19). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
schemas.assessMigrationContractReadiness (cyclomatic 21) packages/migrate/src/schemas.ts:238— schemas.assessMigrationContractReadiness has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 271, 260, 266, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
zip.zip (cyclomatic 20) packages/rxjs/src/zip.ts:27— zip.zip has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 46, 37, 47, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
getLinkInfo.getLinkInfo::getLinkInfoImpl (cyclomatic 18) apps/rxjs.dev/tools/transforms/links-package/services/getLinkInfo.js:18— getLinkInfo.getLinkInfo::getLinkInfoImpl has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
analyze.analyzeTestSource (cyclomatic 18) packages/migrate/src/analyze.ts:14— analyze.analyzeTestSource has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
auto-link-code.autoLinkCode (cyclomatic 17) apps/rxjs.dev/tools/transforms/angular-base-package/post-processors/auto-link-code.js:23— auto-link-code.autoLinkCode has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 6 function items inside it that branch (foundValidDoc, isValidCodeElement, a function literal at line 40, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
cli.parseArguments (cyclomatic 17) packages/migrate/src/cli.ts:120— cli.parseArguments has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HackComment apps/rxjs.dev/src/app/custom-elements/api/api-list.component.ts:150— // Hack: can't bind to query because input cursor always forced to end-of-line. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
semantics.migrateTestSchedulerSemantics (cognitive 49) packages/migrate/src/semantics.ts:17— semantics.migrateTestSchedulerSemantics has cognitive complexity 49 (threshold 15). Drivers by points: if/else 23 (30 pts), ternaries 6 (10 pts), boolean chains 9 (nesting depth added 11). Most of this is not in the body itself: 15 of the 49 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 120, 215). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: packages/migrate/src/semantics.ts holds 5 of the 25 methods over the threshold — including the worst — and 59 of the 221 points over it (27%), 2× the next-largest file (apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js at 29). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
generateKeywordsProcessor.$process (cognitive 44) apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js:25— generateKeywordsProcessor.$process has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (26 pts), loops 5 (11 pts), boolean chains 7 (nesting depth added 16). Of this number, 28 points are the body's own statements and 16 belong to 11 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generateKeywords.generateKeywordsProcessor.$process (cognitive 43) apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js:25— generateKeywords.generateKeywordsProcessor.$process has cognitive complexity 43 (threshold 15). Drivers by points: if/else 16 (26 pts), loops 5 (11 pts), boolean chains 6 (nesting depth added 16). Of this number, 27 points are the body's own statements and 16 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
group-by.groupByOperator (cognitive 38) packages/rxjs/src/group-by.ts:80— group-by.groupByOperator has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (23 pts), error handling 5 (6 pts), boolean chains 5, loops 3, ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 241, 155, 183, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
mocha-chai-vitest.migrateMochaChaiToVitest (cognitive 37) packages/migrate/src/mocha-chai-vitest.ts:13— mocha-chai-vitest.migrateMochaChaiToVitest has cognitive complexity 37 (threshold 15). Drivers by points: if/else 16 (25 pts), loops 2 (5 pts), boolean chains 4, ternaries 3 (nesting depth added 12). Most of this is not in the body itself: 9 of the 37 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 59, 114). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
semantics.collectUnsafeOperatorLocals::visit (cognitive 30) packages/migrate/src/semantics.ts:266— semantics.collectUnsafeOperatorLocals::visit has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 3 (7 pts), boolean chains 6 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: packages/migrate/src/semantics.ts holds 5 of the 25 methods over the threshold — including the worst — and 59 of the 221 points over it (27%), 2× the next-largest file (apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js at 29). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
analyze.analyzeTestSource (cognitive 28) packages/migrate/src/analyze.ts:14— analyze.analyzeTestSource has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 3 (8 pts), boolean chains 4 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
schemas.migrationContractManifestSchema (cognitive 23) packages/migrate/src/schemas.ts:192— schemas.migrationContractManifestSchema has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 4 (7 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
schemas.assessMigrationContractReadiness (cognitive 21) packages/migrate/src/schemas.ts:238— schemas.assessMigrationContractReadiness has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11, boolean chains 5, ternaries 4 (5 pts) (nesting depth added 1). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 271, 260, 266, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
fork-join.forkJoinImpl (cognitive 21) packages/rxjs/src/fork-join.ts:40— fork-join.forkJoinImpl has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 2 (4 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 10). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 76, 46, 69). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
zip.zip (cognitive 21) packages/rxjs/src/zip.ts:27— zip.zip has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (7 pts), ternaries 4 (5 pts), loops 2 (nesting depth added 3). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 46, 37, 47, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
semantics.collectTestSchedulerIdentifiers::visit (cognitive 20) packages/migrate/src/semantics.ts:351— semantics.collectTestSchedulerIdentifiers::visit has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 2 (6 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: packages/migrate/src/semantics.ts holds 5 of the 25 methods over the threshold — including the worst — and 59 of the 221 points over it (27%), 2× the next-largest file (apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js at 29). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parseAttributes (cognitive 19) apps/rxjs.dev/tools/transforms/helpers/utils.js:18— parseAttributes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (8 pts), loops 5 (7 pts), boolean chains 4 (nesting depth added 3). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 6 function items inside it that branch (takeValue, takeAttribute, skipSpace, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
mocha-chai-vitest.collectFrameworkImports (cognitive 18) packages/migrate/src/mocha-chai-vitest.ts:375— mocha-chai-vitest.collectFrameworkImports has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
semantics.convertPipeline (cognitive 18) packages/migrate/src/semantics.ts:532— semantics.convertPipeline has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: packages/migrate/src/semantics.ts holds 5 of the 25 methods over the threshold — including the worst — and 59 of the 221 points over it (27%), 2× the next-largest file (apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js at 29). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
getLinkInfo::getLinkInfoImpl (cognitive 18) apps/rxjs.dev/tools/transforms/links-package/services/getLinkInfo.js:18— getLinkInfo::getLinkInfoImpl has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
auto-link-code.autoLinkCode (cognitive 17) apps/rxjs.dev/tools/transforms/angular-base-package/post-processors/auto-link-code.js:23— auto-link-code.autoLinkCode has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, ternaries 1 (nesting depth added 1). None of this is in the body itself: all 17 points belong to 6 function items inside it that branch (foundValidDoc, a function literal at line 40, isValidCodeElement, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
semantics.collectOperatorLocals (cognitive 17) packages/migrate/src/semantics.ts:244— semantics.collectOperatorLocals has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: packages/migrate/src/semantics.ts holds 5 of the 25 methods over the threshold — including the worst — and 59 of the 221 points over it (27%), 2× the next-largest file (apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js at 29). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
index.abortWithObservableAlgorithms (cognitive 17) packages/observable-polyfill/src/index.ts:64— index.abortWithObservableAlgorithms has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 1 (4 pts), loops 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
race.raceImpl (cognitive 17) packages/rxjs/src/race.ts:21— race.raceImpl has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 7). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 31, 27, 55, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
renderMarkdown.rgxFindMatchPos (cognitive 16) REDACTED:162— renderMarkdown.rgxFindMatchPos has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
add-image-dimensions.addImageDimensions.addImageDimensionsImpl.<returned closure> (cognitive 16) apps/rxjs.dev/tools/transforms/angular-base-package/post-processors/add-image-dimensions.js:15— add-image-dimensions.addImageDimensions.addImageDimensionsImpl.<returned closure> has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 8). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 16). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
cli.parseArguments (cognitive 16) packages/migrate/src/cli.ts:120— cli.parseArguments has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
skill-cli.parseSkillArguments (cognitive 16) packages/migrate/src/skill-cli.ts:70— skill-cli.parseSkillArguments has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
addImageDimensions (cognitive 16) apps/rxjs.dev/tools/transforms/angular-base-package/post-processors/add-image-dimensions.js:13— addImageDimensions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 8). None of this is in the body itself: all 16 points belong to 3 function items inside it that branch (a function literal at line 16, addImageDimensionsImpl, a function literal at line 15). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
Duplication concentrated across 2 sibling directories (6 clone groups) packages/observable-polyfill/src/index.ts:873— 6 duplicated blocks under packages/ have copies in at least two of the sibling directories observable-polyfill, rxjs — 1 of them are reported below, and 5 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 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 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 6 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.
R10 · Code Duplication· Duplicated block with local edits (86 matched lines × 2 locations) · ×1
Duplicated block with local edits (86 matched lines × 2 locations) packages/rxjs/src/buffer-toggle.ts:16— packages/rxjs/src/buffer-toggle.ts:16 · packages/rxjs/src/window-toggle.ts:18 — the two spans are one implementation copied and then locally edited — 460 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.
R10 · Code Duplication· Duplicated block with local edits (60 matched lines × 2 locations) · ×1
Duplicated block with local edits (60 matched lines × 2 locations) packages/rxjs/src/buffer-time.ts:13— packages/rxjs/src/buffer-time.ts:13 · packages/rxjs/src/window-time.ts:15 — the two spans are one implementation copied and then locally edited — 387 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.
R10 · Code Duplication· Duplicated block with local edits (41 matched lines × 2 locations) · ×1
Duplicated block with local edits (41 matched lines × 2 locations) packages/rxjs/src/last.ts:5— packages/rxjs/src/last.ts:5 · packages/rxjs/src/single.ts:7 — the two spans are one implementation copied and then locally edited — 336 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.
R10 · Code Duplication· Duplicated block with local edits (40 matched lines × 2 locations) · ×1
Duplicated block with local edits (40 matched lines × 2 locations) packages/rxjs/src/first.ts:35— packages/rxjs/src/first.ts:35 · packages/rxjs/src/last.ts:29 — the two spans are one implementation copied and then locally edited — 248 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 (38 lines × 2 locations) packages/rxjs/src/testing/index.ts:27— packages/rxjs/src/testing/index.ts:27 · packages/rxjs/src/testing/index.ts:83 — all 2 copies are in the same file, 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 (35 matched lines × 2 locations) · ×1
Duplicated block with local edits (35 matched lines × 2 locations) packages/rxjs/src/merge-scan.ts:50— packages/rxjs/src/merge-scan.ts:50 · packages/rxjs/src/switch-scan.ts:31 — the two spans are one implementation copied and then locally edited — 146 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.
R10 · Code Duplication· Duplicated block with local edits (31 matched lines × 2 locations) · ×1
Duplicated block with local edits (31 matched lines × 2 locations) packages/rxjs/src/finalize.ts:12— packages/rxjs/src/finalize.ts:12 · packages/rxjs/src/tap.ts:46 — the two spans are one implementation copied and then locally edited — 114 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.
R10 · Code Duplication· Duplicated block with local edits (30 matched lines × 2 locations) · ×1
Duplicated block with local edits (30 matched lines × 2 locations) packages/rxjs/src/async-subject.ts:29— packages/rxjs/src/async-subject.ts:29 · packages/rxjs/src/per-subscription-subject-base.ts:84 — the two spans are one implementation copied and then locally edited — 113 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 (28 lines × 2 locations) apps/rxjs.dev/tools/transforms/authors-package/guide-package.js:17— apps/rxjs.dev/tools/transforms/authors-package/guide-package.js:17 · apps/rxjs.dev/tools/transforms/authors-package/tutorial-package.js:17 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (27 matched lines × 2 locations) · ×1
Duplicated block with local edits (27 matched lines × 2 locations) packages/rxjs/src/catch-error.ts:37— packages/rxjs/src/catch-error.ts:37 · packages/rxjs/src/retry-when.ts:42 — the two spans are one implementation copied and then locally edited — 92 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.
R10 · Code Duplication· Duplicated block with local edits (22 matched lines × 2 locations) · ×1
Duplicated block with local edits (22 matched lines × 2 locations) packages/rxjs/src/combine-latest-all.ts:20— packages/rxjs/src/combine-latest-all.ts:20 · packages/rxjs/src/zip-all.ts:14 — the two spans are one implementation copied and then locally edited — 266 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 (21 lines × 2 locations) packages/rxjs/src/util/observable-async-generators.ts:47— packages/rxjs/src/util/observable-async-generators.ts:47 · packages/rxjs/src/util/observable-async-generators.ts:191 — all 2 copies are in the same file, 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 (20 matched lines × 2 locations) · ×1
Duplicated block with local edits (20 matched lines × 2 locations) packages/rxjs/src/skip-until.ts:4— packages/rxjs/src/skip-until.ts:4 · packages/rxjs/src/take-until.ts:4 — the two spans are one implementation copied and then locally edited — 142 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 (18 lines × 2 locations) packages/rxjs/src/every.ts:19— packages/rxjs/src/every.ts:19 · packages/rxjs/src/find-index.ts:14 — 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) packages/rxjs/src/exhaust-map.ts:4— packages/rxjs/src/exhaust-map.ts:4 · packages/rxjs/src/switch-map.ts:4 — the two spans are one implementation copied and then locally edited — 139 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 (18 lines × 4 locations) packages/rxjs/src/util/observable-async-generators.ts:28— packages/rxjs/src/util/observable-async-generators.ts:28 · packages/rxjs/src/util/observable-async-generators.ts:98 · packages/rxjs/src/util/observable-async-generators.ts:169 · packages/rxjs/src/util/observable-async-generators.ts:232 — all 4 copies are in the same file, 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 (17 lines × 2 locations) packages/observable-polyfill/src/index.ts:1045— packages/observable-polyfill/src/index.ts:1045 · packages/observable-polyfill/src/index.ts:1071 — all 2 copies are in the same file, 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 (16 lines × 2 locations) packages/migrate/src/schemas.ts:133— packages/migrate/src/schemas.ts:133 · packages/migrate/src/schemas.ts:152 — 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. Check what actually differs between the copies before collapsing them: every one of them is an argument to a `object(…)` call, so where these calls are a MATRIX of cases — one per input, differing precisely in the case each one pins — the repetition is the enumeration and extracting the shared part would delete cases rather than de-duplicate anything.
R10 · Code Duplication· Duplicated block with local edits (16 matched lines × 2 locations) · ×1
Duplicated block with local edits (16 matched lines × 2 locations) packages/rxjs/src/delay.ts:4— packages/rxjs/src/delay.ts:4 · packages/rxjs/src/take-last.ts:4 — the two spans are one implementation copied and then locally edited — 93 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 × 3 locations) packages/rxjs/src/concat.ts:4— packages/rxjs/src/concat.ts:4 · packages/rxjs/src/on-error-resume-next.ts:7 · packages/rxjs/src/race.ts:6 — the 3 copies are spread across 3 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 (13 lines × 2 locations) packages/observable-polyfill/src/index.ts:645— packages/observable-polyfill/src/index.ts:645 · packages/observable-polyfill/src/index.ts:671 — all 2 copies are in the same file, 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 (13 lines × 3 locations) packages/observable-polyfill/src/index.ts:1031— packages/observable-polyfill/src/index.ts:1031 · packages/observable-polyfill/src/index.ts:1057 · packages/observable-polyfill/src/index.ts:1083 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R10 · Code Duplication· Duplicated block with local edits (13 matched lines × 2 locations) · ×1
Duplicated block with local edits (13 matched lines × 2 locations) packages/rxjs/src/buffer.ts:64— packages/rxjs/src/buffer.ts:64 · packages/rxjs/src/throttle.ts:58 — the two spans are one implementation copied and then locally edited — 85 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.
R10 · Code Duplication· Duplicated block with local edits (12 matched lines × 2 locations) · ×1
Duplicated block with local edits (12 matched lines × 2 locations) apps/rxjs.dev/src/app/custom-elements/code/code-example.component.ts:34— apps/rxjs.dev/src/app/custom-elements/code/code-example.component.ts:34 · apps/rxjs.dev/src/app/custom-elements/code/code.component.ts:81 — the two spans are one implementation copied and then locally edited — 58 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 (10 lines × 2 locations) packages/migrate/src/mocha-chai-vitest.ts:116— packages/migrate/src/mocha-chai-vitest.ts:116 · packages/migrate/src/semantics.ts:831 — 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.
Complex function visit (cyclomatic 117, cognitive 178) packages/rxjs/test/ported/tools/generate-port-manifest.mjs:7832— visit has cyclomatic complexity 117 and cognitive complexity 178; 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 visitStatements (cyclomatic 52, cognitive 78) packages/rxjs/test/ported/tools/generate-port-manifest.mjs:3021— visitStatements has cyclomatic complexity 52 and cognitive complexity 78; 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 isReference (cyclomatic 35, cognitive 14) packages/rxjs/test/ported/tools/generate-port-manifest.mjs:8850— isReference has cyclomatic complexity 35 and cognitive complexity 14; 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 deepEqual (cyclomatic 33, cognitive 38) packages/test/src/assertions.ts:306— deepEqual has cyclomatic complexity 33 and cognitive complexity 38; 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 visit (cyclomatic 32, cognitive 32) packages/migrate/src/semantics.ts:120— visit has cyclomatic complexity 32 and cognitive complexity 32; 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 auditReport (cyclomatic 31, cognitive 55) packages/observable-polyfill/test/wpt/lib/report.mjs:176— auditReport has cyclomatic complexity 31 and cognitive complexity 55; 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 validateCatalog (cyclomatic 30, cognitive 55) packages/rxjs/test/ported/tools/generate-unsupported-surface-doc.mjs:35— validateCatalog has cyclomatic complexity 30 and cognitive complexity 55; 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 collectNestedCases (cyclomatic 29, cognitive 60) packages/rxjs/test/ported/tools/generate-port-manifest.mjs:2901— collectNestedCases has cyclomatic complexity 29 and cognitive complexity 60; 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 baselineFromAuditReport (cyclomatic 25, cognitive 23) packages/rxjs/test/ported/tools/mode-audit-baseline.mjs:3— baselineFromAuditReport has cyclomatic complexity 25 and cognitive complexity 23; 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 getDynamicVariants (cyclomatic 24, cognitive 38) packages/rxjs/test/ported/tools/generate-port-manifest.mjs:7367— getDynamicVariants has cyclomatic complexity 24 and cognitive complexity 38; 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 verifyVendoredImport (cyclomatic 24, cognitive 34) packages/observable-polyfill/test/wpt/lib/provenance.mjs:64— verifyVendoredImport has cyclomatic complexity 24 and cognitive complexity 34; 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 mergeLedger (cyclomatic 23, cognitive 29) packages/rxjs/test/ported/tools/generate-failure-tracker.mjs:204— mergeLedger has cyclomatic complexity 23 and cognitive complexity 29; 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 analyzeTestSource (cyclomatic 22, cognitive 32) packages/migrate/src/analyze.ts:14— analyzeTestSource has cyclomatic complexity 22 and cognitive complexity 32; 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 (anonymous) (cyclomatic 22, cognitive 30) packages/migrate/src/semantics.ts:266— (anonymous) has cyclomatic complexity 22 and cognitive complexity 30; 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 validateOsvExceptions (cyclomatic 22, cognitive 29) scripts/security/check-osv-exceptions.mjs:21— validateOsvExceptions has cyclomatic complexity 22 and cognitive complexity 29; 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 visit (cyclomatic 21, cognitive 33) packages/rxjs/test/ported/tools/generate-port-manifest.mjs:7623— visit has cyclomatic complexity 21 and cognitive complexity 33; 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 parseMarbles (cyclomatic 20, cognitive 27) packages/test/src/marble-parser.ts:50— parseMarbles has cyclomatic complexity 20 and cognitive complexity 27; 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 (anonymous) (cyclomatic 19, cognitive 24) packages/observable-polyfill/src/index.ts:136— (anonymous) has cyclomatic complexity 19 and cognitive complexity 24; 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 $process (cyclomatic 18, cognitive 28) apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js:25— $process has cyclomatic complexity 18 and cognitive complexity 28; 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 parseSubscriptionMarbles (cyclomatic 18, cognitive 25) packages/test/src/marble-parser.ts:154— parseSubscriptionMarbles has cyclomatic complexity 18 and cognitive complexity 25; 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 getLinkInfoImpl (cyclomatic 18, cognitive 18) apps/rxjs.dev/tools/transforms/links-package/services/getLinkInfo.js:18— getLinkInfoImpl has cyclomatic complexity 18 and cognitive complexity 18; 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 migrateTestSchedulerSemantics (cyclomatic 18, cognitive 18) packages/migrate/src/semantics.ts:17— migrateTestSchedulerSemantics has cyclomatic complexity 18 and cognitive complexity 18; 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 validateReport (cyclomatic 18, cognitive 18) packages/rxjs/test/ported/tools/generate-failure-tracker.mjs:140— validateReport has cyclomatic complexity 18 and cognitive complexity 18; 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 evaluateObservedAuthority (cyclomatic 17, cognitive 26) packages/migrate/test/agent/evaluation.ts:682— evaluateObservedAuthority has cyclomatic complexity 17 and cognitive complexity 26; 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 auditReleaseMatrix (cyclomatic 17, cognitive 23) scripts/check-release-coherence.mjs:69— auditReleaseMatrix has cyclomatic complexity 17 and cognitive complexity 23; 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 parseArguments (cyclomatic 17, cognitive 16) packages/migrate/src/cli.ts:120— parseArguments has cyclomatic complexity 17 and cognitive complexity 16; 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 getModeAwareObservableTarget (cyclomatic 17, cognitive 13) packages/rxjs/test/ported/tools/generate-port-manifest.mjs:7751— getModeAwareObservableTarget 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 summarizeGroup (cyclomatic 16, cognitive 29) packages/rxjs/test/ported/tools/generate-failure-tracker.mjs:551— summarizeGroup has cyclomatic complexity 16 and cognitive complexity 29; 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 auditPackageDocs (cyclomatic 16, cognitive 29) scripts/check-package-docs.mjs:15— auditPackageDocs has cyclomatic complexity 16 and cognitive complexity 29; 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 validate (cyclomatic 16, cognitive 24) packages/rxjs/test/ported/tools/generate-migration-evidence-ledger.mjs:290— validate has cyclomatic complexity 16 and cognitive complexity 24; 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 assessAvailability (cyclomatic 16, cognitive 24) packages/rxjs/test/ported/tools/generate-port-manifest.mjs:8775— assessAvailability has cyclomatic complexity 16 and cognitive complexity 24; 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 (anonymous) (cyclomatic 16, cognitive 15) packages/rxjs/src/sequence-equal.ts:31— (anonymous) has cyclomatic complexity 16 and cognitive complexity 15; 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 verifyBrowser (cyclomatic 16, cognitive 14) packages/observable-polyfill/test/wpt/lib/browser.mjs:405— verifyBrowser has cyclomatic complexity 16 and cognitive complexity 14; 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 visit (cyclomatic 15, cognitive 26) packages/migrate/src/mocha-chai-vitest.ts:59— visit has cyclomatic complexity 15 and cognitive complexity 26; 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 evaluateManifestReadiness (cyclomatic 15, cognitive 24) packages/migrate/test/agent/evaluation.ts:547— evaluateManifestReadiness has cyclomatic complexity 15 and cognitive complexity 24; 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 verifyArtifacts (cyclomatic 15, cognitive 23) packages/migrate/test/agent/qualification-record.ts:337— verifyArtifacts has cyclomatic complexity 15 and cognitive complexity 23; 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 requestRotation (cyclomatic 15, cognitive 18) packages/rxjs/src/window-when.ts:46— requestRotation has cyclomatic complexity 15 and cognitive complexity 18; 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 compareEvaluation (cyclomatic 15, cognitive 15) packages/migrate/test/agent/qualification-record.ts:294— compareEvaluation has cyclomatic complexity 15 and cognitive complexity 15; 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 auditEsmDistribution (cyclomatic 15, cognitive 15) scripts/check-release-coherence.mjs:178— auditEsmDistribution has cyclomatic complexity 15 and cognitive complexity 15; 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 readImports (cyclomatic 14, cognitive 22) packages/rxjs/test/ported/tools/generate-port-manifest.mjs:8711— readImports has cyclomatic complexity 14 and cognitive complexity 22; 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.
R3 · Large Files· packages/observable-polyfill/src/index.ts · ×1
packages/observable-polyfill/src/index.ts: 1302 lines of code packages/observable-polyfill/src/index.ts:1— packages/observable-polyfill/src/index.ts has 1302 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/migrate/src/semantics.ts · ×1
packages/migrate/src/semantics.ts: 798 lines of code packages/migrate/src/semantics.ts:1— packages/migrate/src/semantics.ts has 798 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/rxjs.dev/src/app/app.component.ts · ×1
apps/rxjs.dev/src/app/app.component.ts: 424 lines of code apps/rxjs.dev/src/app/app.component.ts:1— apps/rxjs.dev/src/app/app.component.ts has 424 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· Type errors in this package cannot fail any build or CI step · ×1
Type errors in this package cannot fail any build or CI step REDACTED:24— the root package is TypeScript, but a type error in it cannot fail anything this repository runs: its `test:release:adoption` script (`node scripts/qualify-prerelease.mjs`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles.
Dead file (~103 LoC) packages/rxjs/src/testing/scheduled-observable.ts— no import path from any entry point (90 application, 40 tooling, 638 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~50 LoC) apps/rxjs.dev/tools/transforms/authors-package/api-package.js— no import path from any entry point (90 application, 40 tooling, 638 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~32 LoC) packages/rxjs/src/skip-while.ts— no import path from any entry point (90 application, 40 tooling, 638 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~28 LoC) packages/rxjs/src/default-if-empty.ts— no import path from any entry point (90 application, 40 tooling, 638 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~27 LoC) packages/migrate/src/skill.ts— no import path from any entry point (90 application, 40 tooling, 638 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~21 LoC) scripts/copy-common-package-files.js— no import path from any entry point (90 application, 40 tooling, 638 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~20 LoC) apps/rxjs.dev/src/test.ts— no import path from any entry point (90 application, 40 tooling, 638 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~9 LoC) apps/rxjs.dev/src/testing/search.service.ts— no import path from any entry point (90 application, 40 tooling, 638 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/rxjs.dev/src/test.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~7 LoC) packages/rxjs/src/never.ts— no import path from any entry point (90 application, 40 tooling, 638 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~5 LoC) packages/rxjs/src/empty.ts— no import path from any entry point (90 application, 40 tooling, 638 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~3 LoC) apps/rxjs.dev/tools/transforms/templates/data-module.template.js— no import path from any entry point (90 application, 40 tooling, 638 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency '@nx/js' REDACTED:34— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'cz-conventional-changelog' REDACTED:38— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
No direct assertions: requires a host with a native Observable implementation packages/rxjs/test/ported/native-unavailable.spec.ts:4— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should create observable from a next Notification packages/rxjs/test/ported/platform/notification.spec.ts:7— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should create observable from a complete Notification packages/rxjs/test/ported/platform/notification.spec.ts:14— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should create observable from a error Notification packages/rxjs/test/ported/platform/notification.spec.ts:20— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should handle subject never emits packages/rxjs/test/ported/platform/subject.spec.ts:6— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should handle subject completes without emits packages/rxjs/test/ported/platform/subject.spec.ts:12— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should handle subject throws packages/rxjs/test/ported/platform/subject.spec.ts:19— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should handle subject emits packages/rxjs/test/ported/platform/subject.spec.ts:26— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should replay the previous value when subscribed packages/rxjs/test/ported/platform/subjects/behavior-subject.spec.ts:9— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should emit complete when subscribed after completed packages/rxjs/test/ported/platform/subjects/behavior-subject.spec.ts:38— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should replay 2 previous values when subscribed packages/rxjs/test/ported/platform/subjects/replay-subject.spec.ts:9— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should replay 2 last values for when subscribed after completed packages/rxjs/test/ported/platform/subjects/replay-subject.spec.ts:38— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should act like the async scheduler if delay > 0 packages/rxjs/test/ported/platform/schedulers/animation-frame-scheduler.spec.ts:8— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should cancel animationFrame actions when delay > 0 packages/rxjs/test/ported/platform/schedulers/animation-frame-scheduler.spec.ts:17— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should act like the async scheduler if delay > 0 packages/rxjs/test/ported/platform/schedulers/asap-scheduler.spec.ts:8— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should cancel asap actions when delay > 0 packages/rxjs/test/ported/platform/schedulers/asap-scheduler.spec.ts:17— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should act like the async scheduler if delay > 0 packages/rxjs/test/ported/platform/schedulers/queue-scheduler.spec.ts:8— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should parse a subscription marble string into a subscriptionLog packages/rxjs/test/ported/platform/schedulers/test-scheduler.spec.ts:207— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should parse a subscription marble string with a synchronous unsubscription packages/rxjs/test/ported/platform/schedulers/test-scheduler.spec.ts:229— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should ignore whitespace when runMode=true packages/rxjs/test/ported/platform/schedulers/test-scheduler.spec.ts:236— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should support time progression syntax when runMode=true packages/rxjs/test/ported/platform/schedulers/test-scheduler.spec.ts:243— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should handle empty packages/rxjs/test/ported/platform/schedulers/test-scheduler.spec.ts:389— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should handle never packages/rxjs/test/ported/platform/schedulers/test-scheduler.spec.ts:394— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should accept an unsubscription marble diagram packages/rxjs/test/ported/platform/schedulers/test-scheduler.spec.ts:401— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should accept a subscription marble diagram packages/rxjs/test/ported/platform/schedulers/test-scheduler.spec.ts:409— No conventional assertion call was detected, and 4403 of 5441 tests in `packages/rxjs` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
Deprecated: @babel/plugin-proposal-async-generator-functions REDACTED:893— @babel/plugin-proposal-async-generator-functions 7.16.4 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-async-generator-functions REDACTED:900— @babel/plugin-proposal-async-generator-functions 7.20.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-class-properties REDACTED:907— @babel/plugin-proposal-class-properties 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-class-static-block REDACTED:914— @babel/plugin-proposal-class-static-block 7.21.0 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-static-block instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-dynamic-import REDACTED:927— @babel/plugin-proposal-dynamic-import 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-dynamic-import instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-export-namespace-from REDACTED:934— @babel/plugin-proposal-export-namespace-from 7.18.9 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-json-strings REDACTED:941— @babel/plugin-proposal-json-strings 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-json-strings instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-logical-assignment-operators REDACTED:948— @babel/plugin-proposal-logical-assignment-operators 7.20.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-logical-assignment-operators instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:955— @babel/plugin-proposal-nullish-coalescing-operator 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:962— @babel/plugin-proposal-numeric-separator 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-object-rest-spread REDACTED:969— @babel/plugin-proposal-object-rest-spread 7.20.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-optional-catch-binding REDACTED:976— @babel/plugin-proposal-optional-catch-binding 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:983— @babel/plugin-proposal-optional-chaining 7.21.0 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-private-methods REDACTED:990— @babel/plugin-proposal-private-methods 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-private-property-in-object REDACTED:1003— @babel/plugin-proposal-private-property-in-object 7.21.11 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-unicode-property-regex REDACTED:1010— @babel/plugin-proposal-unicode-property-regex 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-unicode-property-regex instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/config-array REDACTED:1779— @humanwhocodes/config-array 0.11.13 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/config-array REDACTED:1784— @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema REDACTED:1793— @humanwhocodes/object-schema 2.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema REDACTED:1797— @humanwhocodes/object-schema 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @npmcli/move-file REDACTED:1918— @npmcli/move-file 1.1.2 is resolved in REDACTED and is marked deprecated by its publisher: "This functionality has been moved to @npmcli/fs". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @npmcli/move-file REDACTED:1923— @npmcli/move-file 2.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "This functionality has been moved to @npmcli/fs". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @types/vfile-message REDACTED:2479— @types/vfile-message 2.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @ungap/structured-clone REDACTED:2639— @ungap/structured-clone 1.2.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @xmldom/xmldom REDACTED:2765— @xmldom/xmldom 0.8.10 is resolved in REDACTED and is marked deprecated by its publisher: "this version has critical issues, please update to the latest version". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Orphaned file apps/rxjs.dev/src/app/app.component.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/app/layout/doc-viewer/doc-viewer.component.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/app/shared/scroll-spy.service.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/app/shared/scroll.service.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/app/custom-elements/code/code.component.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/app/custom-elements/live-example/live-example.component.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/app/app.module.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/tools/transforms/angular-base-package/post-processors/auto-link-code.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/tools/transforms/angular-api-package/index.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/app/search/search.worker.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/tools/transforms/angular-base-package/index.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/tools/transforms/angular-api-package/processors/mergeDecoratorDocs.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/app/shared/location.service.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/app/shared/toc.service.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/testing/doc-viewer-utils.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/app/documents/document.service.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/app/custom-elements/element-registry.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/.eslintrc.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/tools/transforms/angular.io-package/index.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/tools/transforms/angular-api-package/processors/matchUpDirectiveDecorators.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/app/custom-elements/announcement-bar/announcement-bar.component.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/src/app/custom-elements/code/code-tabs.component.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/rxjs.dev/tools/firebase-test-utils/FirebaseGlob.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Outdated (npm): @angular/animations apps/rxjs.dev/REDACTED:45— @angular/animations is pinned at 13.4.0; registry.npmjs.org publishes 22.2.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @angular/cdk apps/rxjs.dev/REDACTED:46— @angular/cdk is pinned at 13.3.9; registry.npmjs.org publishes 22.2.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @angular/common apps/rxjs.dev/REDACTED:47— @angular/common is pinned at 13.4.0; registry.npmjs.org publishes 22.2.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @angular/compiler apps/rxjs.dev/REDACTED:48— @angular/compiler is pinned at 13.4.0; registry.npmjs.org publishes 22.2.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @angular/core apps/rxjs.dev/REDACTED:49— @angular/core is pinned at 13.4.0; registry.npmjs.org publishes 22.2.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @angular/elements apps/rxjs.dev/REDACTED:50— @angular/elements is pinned at 13.4.0; registry.npmjs.org publishes 22.2.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @angular/forms apps/rxjs.dev/REDACTED:51— @angular/forms is pinned at 13.4.0; registry.npmjs.org publishes 22.2.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @angular/material apps/rxjs.dev/REDACTED:52— @angular/material is pinned at 13.3.9; registry.npmjs.org publishes 22.2.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @angular/platform-browser apps/rxjs.dev/REDACTED:53— @angular/platform-browser is pinned at 13.4.0; registry.npmjs.org publishes 22.2.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @angular/platform-browser-dynamic apps/rxjs.dev/REDACTED:54— @angular/platform-browser-dynamic is pinned at 13.4.0; registry.npmjs.org publishes 22.2.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @angular/router apps/rxjs.dev/REDACTED:55— @angular/router is pinned at 13.4.0; registry.npmjs.org publishes 22.2.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @angular/service-worker apps/rxjs.dev/REDACTED:56— @angular/service-worker is pinned at 13.4.0; registry.npmjs.org publishes 22.2.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
README/code drift README.md:28— README.md names RxJS 8, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:110— README.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/RELEASE_PROCESS.md:88— docs/RELEASE_PROCESS.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/rxjs-next/ARCHITECTURE.md:38— docs/rxjs-next/ARCHITECTURE.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/rxjs-next/DECISIONS.md:1135— docs/rxjs-next/DECISIONS.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/rxjs-next/PROJECT_CHARTER.md:19— docs/rxjs-next/PROJECT_CHARTER.md names RxJS 9, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/rxjs-next/PROJECT_CHARTER.md:20— docs/rxjs-next/PROJECT_CHARTER.md names RxJS 8, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/rxjs-next/WHY_SYMBOL_OPERATORS.md:55— docs/rxjs-next/WHY_SYMBOL_OPERATORS.md names RxJS 5, but the manifest declares `rxjs` ^7.5.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Duplicated predicate packages/migrate/src/mocha-chai-vitest.ts:393— `!bindings || !ts.isNamedImports(bindings)` appears character-identically in 2 files — packages/migrate/src/mocha-chai-vitest.ts, packages/migrate/src/semantics.ts. 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 packages/migrate/src/mocha-chai-vitest.ts:148— `!clause || !bindings || !ts.isNamedImports(bindings)` appears character-identically in 2 files — packages/migrate/src/mocha-chai-vitest.ts, packages/migrate/src/semantics.ts. 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 packages/migrate/src/mocha-chai-vitest.ts:384— `!ts.isImportDeclaration(statement) || !ts.isStringLiteral(statement.moduleSpecifier)` appears character-identically in 2 files — packages/migrate/src/mocha-chai-vitest.ts, packages/migrate/src/semantics.ts. 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 packages/rxjs/src/connectable.ts:90— `currentConnection && !currentConnection.closed` appears character-identically in 2 files — packages/rxjs/src/connectable.ts, packages/rxjs/src/ref-count.ts. 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 packages/migrate/src/node.ts:236— `error instanceof Error && 'code' in error && error.code === 'ENOENT'` appears character-identically in 2 files — packages/migrate/src/node.ts, packages/migrate/src/skill-install.ts. 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 packages/migrate/src/mocha-chai-vitest.ts:60— `ts.isImportDeclaration(node) && ts.isStringLiteral(node.moduleSpecifier)` appears character-identically in 2 files — packages/migrate/src/mocha-chai-vitest.ts, packages/migrate/src/semantics.ts. 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 packages/rxjs/src/combine-latest.ts:51— `typeof configOrProject === 'object' && configOrProject !== null` appears character-identically in 2 files — packages/rxjs/src/combine-latest.ts, packages/rxjs/src/zip.ts. 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 scripts/check-release-coherence.mjs:198— `typeof target !== 'string' || !target.startsWith('./dist/esm/')` appears character-identically in 2 files — scripts/check-release-coherence.mjs, scripts/finalize-esm-package.mjs. 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.
redundant comment apps/rxjs.dev/src/app/app.component.ts:237— "Find the current version - either title matches the current deployment mode or its title matches the major version of the current version info" repeats the code it sits on: 8 of its 9 words (find, current, version, title, deployment, mode, major, info) are already in `this.currentDocVersion = this.docVersions.find(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/rxjs.dev/src/app/custom-elements/live-example/live-example.component.ts:148— "EmbeddedStackblitzComponent ///" repeats the code it sits on: 3 of its 3 words (embedded, stackblitz, component) are already in `@Component({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/rxjs.dev/src/app/search/search.service.ts:28— "Wait for the initDelay or the first search" repeats the code it sits on: 4 of its 5 words (init, delay, first, search) are already in `const ready = (this.ready = race<any>(timer(initDelay), this.searchesSubject.asObservable().pipe(first())).pipe(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/rxjs.dev/src/app/search/search.worker.ts:164— "Map the hits into info about each page to be returned as results" repeats the code it sits on: 5 of its 6 words (map, hits, page, returned, results) are already in `return results.map((hit) => pageMap[hit.ref]);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/rxjs.dev/tools/transforms/angular-api-package/index.js:79— "Load up all the tag definitions in the tag-defs folder" repeats the code it sits on: 4 of its 5 words (tag, definitions, defs, folder) are already in `parseTagsProcessor.tagDefinitions =`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment apps/rxjs.dev/tools/transforms/angular-api-package/index.js:86— "Only split the description on the API docs" repeats the code it sits on: 4 of its 5 words (split, description, api, docs) are already in `splitDescription.docTypes = API_DOC_TYPES;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:84— "Create matchers for each block" repeats the code it sits on: 3 of its 3 words (create, matchers, block) are already in `const anyBlockMatcher = new RegExp('^' + createOpenMatcher(`(${plainBlocks.join('|')})`));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
P2 · Observability· Console output used as the logging channel · ×7
Console output used as the logging channel apps/rxjs.dev/src/assets/js/devtools-welcome.js:10— `apps/rxjs.dev/src/assets/js/devtools-welcome.js` reports through `console.*` at line 10 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/rxjs.dev/src/assets/js/devtools-welcome.js:12— `apps/rxjs.dev/src/assets/js/devtools-welcome.js` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/rxjs.dev/src/app/shared/logger.service.ts:12— `apps/rxjs.dev/src/app/shared/logger.service.ts` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/rxjs.dev/src/app/shared/logger.service.ts:21— `apps/rxjs.dev/src/app/shared/logger.service.ts` reports through `console.*` at line 21 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/rxjs.dev/src/app/search/search.worker.ts:170— `apps/rxjs.dev/src/app/search/search.worker.ts` reports through `console.*` at line 170 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/rxjs.dev/src/app/custom-elements/code/code-example.component.ts:12— `apps/rxjs.dev/src/app/custom-elements/code/code-example.component.ts` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel apps/rxjs.dev/src/app/custom-elements/code/pretty-printer.service.ts:56— `apps/rxjs.dev/src/app/custom-elements/code/pretty-printer.service.ts` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×2
Projects may be oversized for their cohesion apps/rxjs.dev/REDACTED:1— `apps/rxjs.dev` (8885 LoC, 229 module-visible types across 62 directories) overshoots its size bounds. 2 of 5 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 2.6/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion packages/rxjs/REDACTED:1— `packages/rxjs` (7529 LoC, 197 module-visible types across 3 directories) overshoots its size bounds. 2 of 5 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 2.6/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 42 significant file(s) lose their only recent owner: packages/observable-polyfill/src/index.ts, packages/migrate/src/semantics.ts, packages/migrate/src/schemas.ts, packages/migrate/src/node.ts, packages/rxjs/src/group-by.ts, packages/migrate/src/types.ts, packages/migrate/src/cli.ts, packages/rxjs/src/pluck.ts (+34 more). Pair on, review, or document these before any departure.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D30 · Dependency Vulnerabilities· Stale vulnerability suppression · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 28 of 90 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 90 of the 342 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: apps/rxjs.dev/src/app/app.component.ts, apps/rxjs.dev/src/app/layout/doc-viewer/doc-viewer.component.ts, apps/rxjs.dev/src/app/shared/scroll-spy.service.ts, apps/rxjs.dev/src/app/shared/scroll.service.ts, apps/rxjs.dev/src/app/custom-elements/code/code.component.ts, REDACTED, apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js, apps/rxjs.dev/src/app/custom-elements/live-example/live-example.component.ts (and 20 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Blanket warning suppression apps/rxjs.dev/tools/transforms/angular-base-package/processors/generateKeywords.js:2— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Disabled test packages/rxjs/test/ported/native-unavailable.spec.ts:3— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
M2 · Architecture documentation· ADRs not easily discoverable · ×1
ADRs not easily discoverable — 1 ADR-shaped document(s) detected by content — `docs/rxjs-next/DECISIONS.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
Logging is not universal — Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/migrate`.
P3 · Security & performance tooling· Dependabot does not watch npm · ×1
Dependabot does not watch npm REDACTED:2— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
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.)
R7 · Dead Code· Unused private method '#flushTimers' · ×1
Unused private method '#flushTimers' packages/rxjs/src/testing/index.ts:193— Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used.
R8 · Dependency Hygiene· Test-only dependency 'eyes.selenium' in production deps · ×1
Test-only dependency 'eyes.selenium' in production deps apps/rxjs.dev/REDACTED:60— Only test files import it (first: apps/rxjs.dev/tests/e2e/visual-testing.e2e-spec.ts:3) — move it to devDependencies.
No security response headers detected apps/rxjs.dev/firebase.json:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `firebase.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×1
Diagnostic log message is built whether or not it is wanted apps/rxjs.dev/tools/transforms/angular-api-package/processors/markAliases.ts:28— `debug` at line 28 is called with an argument built by `duplicateDocs.map((doc : Document) => doc.name)` (line 29), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 16/17 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) override strict null checking — ~2.8 `!` null assertions per 1k TypeScript source lines — 55 assertion(s) across the 19786 source line(s) of the 243 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/observable-polyfill/src/index.ts (13), apps/rxjs.dev/src/app/custom-elements/elements-loader.ts (3), packages/rxjs/src/combine.ts (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Outdated (npm): @stackblitz/sdk — @stackblitz/sdk is pinned at 1.9.0; registry.npmjs.org publishes 1.11.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): core-js — core-js is pinned at 3.33.3; registry.npmjs.org publishes 3.51.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): rxjs — rxjs is pinned at 7.8.1; registry.npmjs.org publishes 7.8.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): tslib — tslib is pinned at 2.6.2; registry.npmjs.org publishes 2.9.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): typescript — typescript is pinned at 5.7.3; registry.npmjs.org publishes 7.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): zod — zod is pinned at 3.25.76; registry.npmjs.org publishes 4.6.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): zone.js — zone.js is pinned at 0.11.8; registry.npmjs.org publishes 0.16.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Skipped (documented): should do WHAT(?) if the request fails apps/rxjs.dev/src/app/navigation/navigation.service.spec.ts:57— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): should do WHAT(?) if the request fails apps/rxjs.dev/src/app/custom-elements/resource/resource.service.spec.ts:85— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): should do WHAT(?) if the request fails apps/rxjs.dev/src/app/custom-elements/contributor/contributor.service.spec.ts:63— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
doc comments repeat the names apps/rxjs.dev/src/app/sw-updates/sw-updates.service.ts:10— 0 of 28 documented parameters and 1 of 113 summaries in `rxjs.dev` only repeat the member or parameter name (e.g. "SwUpdatesService" for `SwUpdatesService`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 97 file(s) — `apps/rxjs.dev/tools/transforms/templates/data-module.template.js`, `packages/migrate/src/capabilities.ts`, `packages/migrate/src/skill-install.ts`, `packages/observable-polyfill/src/index.ts`, `packages/rxjs/src/animation-frames.ts`, … (+92 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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.
Run 01a1e798-e8a2-770b-a4e8-e7f23defc0e5 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 98 · Warnings: 324 · Recommendations: 4900 · Info: 11 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 03:42 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.