Public report of facebook/hermes, published 15 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. This copy doesn't carry the survey's signed record. How a survey is checked →
facebook/hermes
Measured 15 November 2026, 06:42 UTC, at code version c319a1a
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureTestRunFailed).
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: 50,836 lines of product code in 46 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Code Health, 41
Findings by how serious they are
120 critical435 serious251 minor
34 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
15 November 2026, 06: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 ▸
46of 46 dimensions measured by tools.
782of 806 findings point to an exact file and line, so you can open each one in the code. The other 24 concern the repository as a whole, such as missing documentation.
46dimensions across 6 lenses, read from 50,836 lines of product code in 46 projects.
facebook/hermes is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 51 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Code Health, at 41, is the weakest lens and counts most in the score. The best first step is adding type checking, worth about 6 points. Fixing the test command with no tests behind it comes next, worth about 3 points. Raising Code Health to 67 would lift the score to about 59.
Fifty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Forty known security holes in the packages the code depends on can be used by attackers, and seven weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, updating the vulnerable packages and fixing the weaknesses the scanner points to would close these risks. Passing outside input through environment variables would fix the four pipeline steps that put outside input straight into a shell command, and limiting each secret to its own step would deal with the two secrets exposed to more of the pipeline than needed. The ten parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 50,836 lines, about €64,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 Code Health rose from 41 to 67, the lowest score rated Strong, the score would rise from 51 to about 59.
Code composition: what the lines of code are
Product code 75%Tests 25%
Rebuild cost: about €64,000 · Estimate
Cost to rebuild
€21,000 to €110,000, for 356 to 1,130 hours of work, about 0.4 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 51. 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: 50,836 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 finding(s) in Type Safety.
Raises the score by about 6 points · Medium effort · Type Safety
2
Resolve the 1 Test suite declares a test script but contains no test files finding(s) in Test Reliability.
Raises the score by about 3 points · Low effort · Test Reliability
3
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced.
Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
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 €64,000 to build again, about 0.4 person-years of work. Its weakest lens is Code Health, at 41 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 1 finding(s) in Type Safety. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for medium effort, because it clears the 1 Type Safety 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.
276 modules, with 359 dependencies between them. 4 loops run through 31 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 236 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.
API.hermes.cdp.tools.hermes-inspector-msggen.src.Graph uses lib.TypedLib.04-set, so a change to lib.TypedLib.04-set can break API.hermes.cdp.tools.hermes-inspector-msggen.src.Graph, while a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Graph can't break lib.TypedLib.04-set.
Position
Below the diagonal: API.hermes.cdp.tools.hermes-inspector-msggen.src.Graph uses a module listed above it, which is the healthy direction.
API.hermes.cdp.tools.hermes-inspector-msggen.src.Property uses lib.TypedLib.04-set, so a change to lib.TypedLib.04-set can break API.hermes.cdp.tools.hermes-inspector-msggen.src.Property, while a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Property can't break lib.TypedLib.04-set.
Position
Below the diagonal: API.hermes.cdp.tools.hermes-inspector-msggen.src.Property uses a module listed above it, which is the healthy direction.
hermes.parser.hermes_parser uses hermes.parser.node, so a change to hermes.parser.node can break hermes.parser.hermes_parser, while a change to hermes.parser.hermes_parser can't break hermes.parser.node.
Position
Below the diagonal: hermes.parser.hermes_parser uses a module listed above it, which is the healthy direction.
hermes_parser.generated_extension uses hermes.parser.node, so a change to hermes.parser.node can break hermes_parser.generated_extension, while a change to hermes_parser.generated_extension can't break hermes.parser.node.
Position
Below the diagonal: hermes_parser.generated_extension uses a module listed above it, which is the healthy direction.
hermes_parser.generated_extension uses hermes_estree.range, so a change to hermes_estree.range can break hermes_parser.generated_extension, while a change to hermes_parser.generated_extension can't break hermes_estree.range.
Position
Below the diagonal: hermes_parser.generated_extension uses a module listed above it, which is the healthy direction.
hermes_semantic_analysis.scope_manager uses hermes_estree.range, so a change to hermes_estree.range can break hermes_semantic_analysis.scope_manager, while a change to hermes_semantic_analysis.scope_manager can't break hermes_estree.range.
Position
Below the diagonal: hermes_semantic_analysis.scope_manager uses a module listed above it, which is the healthy direction.
juno_support.source_manager uses juno_support.atom_table, so a change to juno_support.atom_table can break juno_support.source_manager, while a change to juno_support.source_manager can't break juno_support.atom_table.
Position
Below the diagonal: juno_support.source_manager uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase uses a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Reference.
tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase uses tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Reference, so a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Reference can break tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase, while a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase can't break tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Reference.
Position
Below the diagonal: tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase uses a type in tools.hermes-parser.js.hermes-estree.src.types.
tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase uses tools.hermes-parser.js.hermes-estree.src.types, so a change to tools.hermes-parser.js.hermes-estree.src.types can break tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase, while a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase can't break tools.hermes-parser.js.hermes-estree.src.types.
Position
Below the diagonal: tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase uses a module listed above it, which is the healthy direction.
API.hermes.cdp.tools.hermes-inspector-msggen.src.Command uses lib.TypedLib.04-set, so a change to lib.TypedLib.04-set can break API.hermes.cdp.tools.hermes-inspector-msggen.src.Command, while a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Command can't break lib.TypedLib.04-set.
Position
Below the diagonal: API.hermes.cdp.tools.hermes-inspector-msggen.src.Command uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in API.hermes.cdp.tools.hermes-inspector-msggen.src.Command uses a type in API.hermes.cdp.tools.hermes-inspector-msggen.src.Property.
API.hermes.cdp.tools.hermes-inspector-msggen.src.Command uses API.hermes.cdp.tools.hermes-inspector-msggen.src.Property, so a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Property can break API.hermes.cdp.tools.hermes-inspector-msggen.src.Command, while a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Command can't break API.hermes.cdp.tools.hermes-inspector-msggen.src.Property.
Position
Below the diagonal: API.hermes.cdp.tools.hermes-inspector-msggen.src.Command uses a module listed above it, which is the healthy direction.
API.hermes.cdp.tools.hermes-inspector-msggen.src.Event uses lib.TypedLib.04-set, so a change to lib.TypedLib.04-set can break API.hermes.cdp.tools.hermes-inspector-msggen.src.Event, while a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Event can't break lib.TypedLib.04-set.
Position
Below the diagonal: API.hermes.cdp.tools.hermes-inspector-msggen.src.Event uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in API.hermes.cdp.tools.hermes-inspector-msggen.src.Event uses a type in API.hermes.cdp.tools.hermes-inspector-msggen.src.Property.
API.hermes.cdp.tools.hermes-inspector-msggen.src.Event uses API.hermes.cdp.tools.hermes-inspector-msggen.src.Property, so a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Property can break API.hermes.cdp.tools.hermes-inspector-msggen.src.Event, while a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Event can't break API.hermes.cdp.tools.hermes-inspector-msggen.src.Property.
Position
Below the diagonal: API.hermes.cdp.tools.hermes-inspector-msggen.src.Event uses a module listed above it, which is the healthy direction.
API.hermes.cdp.tools.hermes-inspector-msggen.src.Type uses lib.TypedLib.04-set, so a change to lib.TypedLib.04-set can break API.hermes.cdp.tools.hermes-inspector-msggen.src.Type, while a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Type can't break lib.TypedLib.04-set.
Position
Below the diagonal: API.hermes.cdp.tools.hermes-inspector-msggen.src.Type uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in API.hermes.cdp.tools.hermes-inspector-msggen.src.Type uses a type in API.hermes.cdp.tools.hermes-inspector-msggen.src.Property.
API.hermes.cdp.tools.hermes-inspector-msggen.src.Type uses API.hermes.cdp.tools.hermes-inspector-msggen.src.Property, so a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Property can break API.hermes.cdp.tools.hermes-inspector-msggen.src.Type, while a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Type can't break API.hermes.cdp.tools.hermes-inspector-msggen.src.Property.
Position
Below the diagonal: API.hermes.cdp.tools.hermes-inspector-msggen.src.Type uses a module listed above it, which is the healthy direction.
juno_ast.context uses juno_support.atom_table, so a change to juno_support.atom_table can break juno_ast.context, while a change to juno_ast.context can't break juno_support.atom_table.
Position
Below the diagonal: juno_ast.context uses a module listed above it, which is the healthy direction.
juno_ast.context uses juno_support.scoped_hashmap, so a change to juno_support.scoped_hashmap can break juno_ast.context, while a change to juno_ast.context can't break juno_support.scoped_hashmap.
Position
Below the diagonal: juno_ast.context uses a module listed above it, which is the healthy direction.
juno_ast.context uses juno_support.source_manager, so a change to juno_support.source_manager can break juno_ast.context, while a change to juno_ast.context can't break juno_support.source_manager.
Position
Below the diagonal: juno_ast.context uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.Variable uses a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase.
tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.Variable uses tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase, so a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase can break tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.Variable, while a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.Variable can't break tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.VariableBase.
Position
Below the diagonal: tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.Variable uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in API.hermes.cdp.tools.hermes-inspector-msggen.src uses a type in API.hermes.cdp.tools.hermes-inspector-msggen.src.Graph.
API.hermes.cdp.tools.hermes-inspector-msggen.src uses API.hermes.cdp.tools.hermes-inspector-msggen.src.Graph, so a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Graph can break API.hermes.cdp.tools.hermes-inspector-msggen.src, while a change to API.hermes.cdp.tools.hermes-inspector-msggen.src can't break API.hermes.cdp.tools.hermes-inspector-msggen.src.Graph.
Position
Below the diagonal: API.hermes.cdp.tools.hermes-inspector-msggen.src uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in API.hermes.cdp.tools.hermes-inspector-msggen.src uses a type in API.hermes.cdp.tools.hermes-inspector-msggen.src.Property.
API.hermes.cdp.tools.hermes-inspector-msggen.src uses API.hermes.cdp.tools.hermes-inspector-msggen.src.Property, so a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Property can break API.hermes.cdp.tools.hermes-inspector-msggen.src, while a change to API.hermes.cdp.tools.hermes-inspector-msggen.src can't break API.hermes.cdp.tools.hermes-inspector-msggen.src.Property.
Position
Below the diagonal: API.hermes.cdp.tools.hermes-inspector-msggen.src uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in API.hermes.cdp.tools.hermes-inspector-msggen.src uses a type in API.hermes.cdp.tools.hermes-inspector-msggen.src.Command.
API.hermes.cdp.tools.hermes-inspector-msggen.src uses API.hermes.cdp.tools.hermes-inspector-msggen.src.Command, so a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Command can break API.hermes.cdp.tools.hermes-inspector-msggen.src, while a change to API.hermes.cdp.tools.hermes-inspector-msggen.src can't break API.hermes.cdp.tools.hermes-inspector-msggen.src.Command.
Position
Below the diagonal: API.hermes.cdp.tools.hermes-inspector-msggen.src uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in API.hermes.cdp.tools.hermes-inspector-msggen.src uses a type in API.hermes.cdp.tools.hermes-inspector-msggen.src.Event.
API.hermes.cdp.tools.hermes-inspector-msggen.src uses API.hermes.cdp.tools.hermes-inspector-msggen.src.Event, so a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Event can break API.hermes.cdp.tools.hermes-inspector-msggen.src, while a change to API.hermes.cdp.tools.hermes-inspector-msggen.src can't break API.hermes.cdp.tools.hermes-inspector-msggen.src.Event.
Position
Below the diagonal: API.hermes.cdp.tools.hermes-inspector-msggen.src uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in API.hermes.cdp.tools.hermes-inspector-msggen.src uses a type in API.hermes.cdp.tools.hermes-inspector-msggen.src.Type.
API.hermes.cdp.tools.hermes-inspector-msggen.src uses API.hermes.cdp.tools.hermes-inspector-msggen.src.Type, so a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Type can break API.hermes.cdp.tools.hermes-inspector-msggen.src, while a change to API.hermes.cdp.tools.hermes-inspector-msggen.src can't break API.hermes.cdp.tools.hermes-inspector-msggen.src.Type.
Position
Below the diagonal: API.hermes.cdp.tools.hermes-inspector-msggen.src uses a module listed above it, which is the healthy direction.
juno.hparser.convert uses hermes.parser.node, so a change to hermes.parser.node can break juno.hparser.convert, while a change to juno.hparser.convert can't break hermes.parser.node.
Position
Below the diagonal: juno.hparser.convert uses a module listed above it, which is the healthy direction.
juno.hparser.convert uses hermes.parser.hermes_parser, so a change to hermes.parser.hermes_parser can break juno.hparser.convert, while a change to juno.hparser.convert can't break hermes.parser.hermes_parser.
Position
Below the diagonal: juno.hparser.convert uses a module listed above it, which is the healthy direction.
juno.hparser.convert uses juno_support.source_manager, so a change to juno_support.source_manager can break juno.hparser.convert, while a change to juno.hparser.convert can't break juno_support.source_manager.
Position
Below the diagonal: juno.hparser.convert uses a module listed above it, which is the healthy direction.
juno.hparser.convert uses juno_ast.context, so a change to juno_ast.context can break juno.hparser.convert, while a change to juno.hparser.convert can't break juno_ast.context.
Position
Below the diagonal: juno.hparser.convert uses a module listed above it, which is the healthy direction.
juno.sema.sem_context uses juno_support.atom_table, so a change to juno_support.atom_table can break juno.sema.sem_context, while a change to juno.sema.sem_context can't break juno_support.atom_table.
Position
Below the diagonal: juno.sema.sem_context uses a module listed above it, which is the healthy direction.
juno.sema.sem_context uses juno_support.source_manager, so a change to juno_support.source_manager can break juno.sema.sem_context, while a change to juno.sema.sem_context can't break juno_support.source_manager.
Position
Below the diagonal: juno.sema.sem_context uses a module listed above it, which is the healthy direction.
juno.sema.sem_context uses juno_ast.context, so a change to juno_ast.context can break juno.sema.sem_context, while a change to juno.sema.sem_context can't break juno_ast.context.
Position
Below the diagonal: juno.sema.sem_context uses a module listed above it, which is the healthy direction.
juno_ast.visitor uses juno_support.scoped_hashmap, so a change to juno_support.scoped_hashmap can break juno_ast.visitor, while a change to juno_ast.visitor can't break juno_support.scoped_hashmap.
Position
Below the diagonal: juno_ast.visitor uses a module listed above it, which is the healthy direction.
juno_ast.visitor uses juno_ast.context, so a change to juno_ast.context can break juno_ast.visitor, while a change to juno_ast.visitor can't break juno_ast.context.
Position
Below the diagonal: juno_ast.visitor uses a module listed above it, which is the healthy direction.
juno_eval.eval.runtime uses juno_ast.context, so a change to juno_ast.context can break juno_eval.eval.runtime, while a change to juno_eval.eval.runtime can't break juno_ast.context.
Position
Below the diagonal: juno_eval.eval.runtime uses a module listed above it, which is the healthy direction.
27→34 juno_eval.eval.runtime uses juno_eval.eval.jsvaluepart of a loop✕
Connections
1 pair of types, where a type in juno_eval.eval.runtime uses a type in juno_eval.eval.jsvalue.
juno_eval.eval.runtime uses juno_eval.eval.jsvalue, so a change to juno_eval.eval.jsvalue can break juno_eval.eval.runtime, while a change to juno_eval.eval.runtime can't break juno_eval.eval.jsvalue.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager uses a type in tools.hermes-parser.js.hermes-estree.src.types.
tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager uses tools.hermes-parser.js.hermes-estree.src.types, so a change to tools.hermes-parser.js.hermes-estree.src.types can break tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager, while a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager can't break tools.hermes-parser.js.hermes-estree.src.types.
Position
Below the diagonal: tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager uses a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.Variable.
tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager uses tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.Variable, so a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.Variable can break tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager, while a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager can't break tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.Variable.
Position
Below the diagonal: tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase uses a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Reference.
tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase uses tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Reference, so a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Reference can break tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase, while a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase can't break tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Reference.
Position
Below the diagonal: tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase uses a type in tools.hermes-parser.js.hermes-estree.src.types.
tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase uses tools.hermes-parser.js.hermes-estree.src.types, so a change to tools.hermes-parser.js.hermes-estree.src.types can break tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase, while a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase can't break tools.hermes-parser.js.hermes-estree.src.types.
Position
Below the diagonal: tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase uses a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.Variable.
tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase uses tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.Variable, so a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.Variable can break tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase, while a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase can't break tools.hermes-parser.js.hermes-eslint.src.scope-manager.variable.Variable.
Position
Below the diagonal: tools.hermes-parser.js.hermes-eslint.src.scope-manager.scope.ScopeBase uses a module listed above it, which is the healthy direction.
flow_native uses hermes.parser.node, so a change to hermes.parser.node can break flow_native, while a change to flow_native can't break hermes.parser.node.
Position
Below the diagonal: flow_native uses a module listed above it, which is the healthy direction.
flow_native uses juno_support.atom_table, so a change to juno_support.atom_table can break flow_native, while a change to flow_native can't break juno_support.atom_table.
Position
Below the diagonal: flow_native uses a module listed above it, which is the healthy direction.
flow_native uses juno_support.source_manager, so a change to juno_support.source_manager can break flow_native, while a change to flow_native can't break juno_support.source_manager.
Position
Below the diagonal: flow_native uses a module listed above it, which is the healthy direction.
flow_native uses juno.sema.sem_context, so a change to juno.sema.sem_context can break flow_native, while a change to flow_native can't break juno.sema.sem_context.
Position
Below the diagonal: flow_native uses a module listed above it, which is the healthy direction.
juno.hparser uses hermes.parser.node, so a change to hermes.parser.node can break juno.hparser, while a change to juno.hparser can't break hermes.parser.node.
Position
Below the diagonal: juno.hparser uses a module listed above it, which is the healthy direction.
juno.hparser uses hermes.parser.hermes_parser, so a change to hermes.parser.hermes_parser can break juno.hparser, while a change to juno.hparser can't break hermes.parser.hermes_parser.
Position
Below the diagonal: juno.hparser uses a module listed above it, which is the healthy direction.
juno.hparser uses juno_support.source_manager, so a change to juno_support.source_manager can break juno.hparser, while a change to juno.hparser can't break juno_support.source_manager.
Position
Below the diagonal: juno.hparser uses a module listed above it, which is the healthy direction.
juno.hparser uses juno_ast.context, so a change to juno_ast.context can break juno.hparser, while a change to juno.hparser can't break juno_ast.context.
Position
Below the diagonal: juno.hparser uses a module listed above it, which is the healthy direction.
juno.hparser uses juno.hparser.convert, so a change to juno.hparser.convert can break juno.hparser, while a change to juno.hparser can't break juno.hparser.convert.
Position
Below the diagonal: juno.hparser uses a module listed above it, which is the healthy direction.
juno.sema.resolver uses hermes.parser.node, so a change to hermes.parser.node can break juno.sema.resolver, while a change to juno.sema.resolver can't break hermes.parser.node.
Position
Below the diagonal: juno.sema.resolver uses a module listed above it, which is the healthy direction.
juno.sema.resolver uses juno_support.scoped_hashmap, so a change to juno_support.scoped_hashmap can break juno.sema.resolver, while a change to juno.sema.resolver can't break juno_support.scoped_hashmap.
Position
Below the diagonal: juno.sema.resolver uses a module listed above it, which is the healthy direction.
juno.sema.resolver uses juno_support.source_manager, so a change to juno_support.source_manager can break juno.sema.resolver, while a change to juno.sema.resolver can't break juno_support.source_manager.
Position
Below the diagonal: juno.sema.resolver uses a module listed above it, which is the healthy direction.
juno.sema.resolver uses juno_ast.context, so a change to juno_ast.context can break juno.sema.resolver, while a change to juno.sema.resolver can't break juno_ast.context.
Position
Below the diagonal: juno.sema.resolver uses a module listed above it, which is the healthy direction.
juno.sema.resolver uses juno.sema.sem_context, so a change to juno.sema.sem_context can break juno.sema.resolver, while a change to juno.sema.resolver can't break juno.sema.sem_context.
Position
Below the diagonal: juno.sema.resolver uses a module listed above it, which is the healthy direction.
juno.sema.resolver uses juno_ast.visitor, so a change to juno_ast.visitor can break juno.sema.resolver, while a change to juno.sema.resolver can't break juno_ast.visitor.
Position
Below the diagonal: juno.sema.resolver uses a module listed above it, which is the healthy direction.
juno_ast.validate uses juno_support.scoped_hashmap, so a change to juno_support.scoped_hashmap can break juno_ast.validate, while a change to juno_ast.validate can't break juno_support.scoped_hashmap.
Position
Below the diagonal: juno_ast.validate uses a module listed above it, which is the healthy direction.
juno_ast.validate uses juno_ast.context, so a change to juno_ast.context can break juno_ast.validate, while a change to juno_ast.validate can't break juno_ast.context.
Position
Below the diagonal: juno_ast.validate uses a module listed above it, which is the healthy direction.
juno_ast.validate uses juno_ast.visitor, so a change to juno_ast.visitor can break juno_ast.validate, while a change to juno_ast.validate can't break juno_ast.visitor.
Position
Below the diagonal: juno_ast.validate uses a module listed above it, which is the healthy direction.
juno_eval.eval.jsvalue uses juno_eval.eval.runtime, so a change to juno_eval.eval.runtime can break juno_eval.eval.jsvalue, while a change to juno_eval.eval.jsvalue can't break juno_eval.eval.runtime.
Position
Below the diagonal: juno_eval.eval.jsvalue uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in juno_pass.manager uses a type in hermes.parser.node.
The types involved
juno_pass.manager.Pass → hermes.parser.node.Node
Direction
juno_pass.manager uses hermes.parser.node, so a change to hermes.parser.node can break juno_pass.manager, while a change to juno_pass.manager can't break hermes.parser.node.
Position
Below the diagonal: juno_pass.manager uses a module listed above it, which is the healthy direction.
juno_pass.manager uses juno_ast.context, so a change to juno_ast.context can break juno_pass.manager, while a change to juno_pass.manager can't break juno_ast.context.
Position
Below the diagonal: juno_pass.manager uses a module listed above it, which is the healthy direction.
juno_pass.manager uses juno_ast.visitor, so a change to juno_ast.visitor can break juno_pass.manager, while a change to juno_pass.manager can't break juno_ast.visitor.
Position
Below the diagonal: juno_pass.manager uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer uses a type in external.asmjit.asmjit.db.exp.
tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer uses external.asmjit.asmjit.db.exp, so a change to external.asmjit.asmjit.db.exp can break tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer, while a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer can't break external.asmjit.asmjit.db.exp.
Position
Below the diagonal: tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer uses a module listed above it, which is the healthy direction.
69 pairs of types, where a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer uses a type in tools.hermes-parser.js.hermes-estree.src.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer uses tools.hermes-parser.js.hermes-estree.src.types, so a change to tools.hermes-parser.js.hermes-estree.src.types can break tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer, while a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer can't break tools.hermes-parser.js.hermes-estree.src.types.
Position
Below the diagonal: tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer uses a type in API.hermes.cdp.tools.hermes-inspector-msggen.src.Property.
tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer uses API.hermes.cdp.tools.hermes-inspector-msggen.src.Property, so a change to API.hermes.cdp.tools.hermes-inspector-msggen.src.Property can break tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer, while a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer can't break API.hermes.cdp.tools.hermes-inspector-msggen.src.Property.
Position
Below the diagonal: tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer uses a type in tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager.
tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer uses tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager, so a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager can break tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer, while a change to tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer can't break tools.hermes-parser.js.hermes-eslint.src.scope-manager.ScopeManager.
Position
Below the diagonal: tools.hermes-parser.js.hermes-eslint.src.scope-manager.referencer.Referencer uses a module listed above it, which is the healthy direction.
juno_ast.node_child uses juno_support.scoped_hashmap, so a change to juno_support.scoped_hashmap can break juno_ast.node_child, while a change to juno_ast.node_child can't break juno_support.scoped_hashmap.
Position
Below the diagonal: juno_ast.node_child uses a module listed above it, which is the healthy direction.
juno_ast.node_child uses juno_support.source_manager, so a change to juno_support.source_manager can break juno_ast.node_child, while a change to juno_ast.node_child can't break juno_support.source_manager.
Position
Below the diagonal: juno_ast.node_child uses a module listed above it, which is the healthy direction.
juno_ast.node_child uses juno_ast.context, so a change to juno_ast.context can break juno_ast.node_child, while a change to juno_ast.node_child can't break juno_ast.context.
Position
Below the diagonal: juno_ast.node_child uses a module listed above it, which is the healthy direction.
juno_ast.node_child uses juno_ast.visitor, so a change to juno_ast.visitor can break juno_ast.node_child, while a change to juno_ast.node_child can't break juno_ast.visitor.
Position
Below the diagonal: juno_ast.node_child uses a module listed above it, which is the healthy direction.
juno_ast.node_child uses juno_ast.validate, so a change to juno_ast.validate can break juno_ast.node_child, while a change to juno_ast.node_child can't break juno_ast.validate.
Position
Below the diagonal: juno_ast.node_child uses a module listed above it, which is the healthy direction.
juno_cli uses hermes.parser.hermes_parser, so a change to hermes.parser.hermes_parser can break juno_cli, while a change to juno_cli can't break hermes.parser.hermes_parser.
Position
Below the diagonal: juno_cli uses a module listed above it, which is the healthy direction.
juno_cli uses juno_support.source_manager, so a change to juno_support.source_manager can break juno_cli, while a change to juno_cli can't break juno_support.source_manager.
Position
Below the diagonal: juno_cli uses a module listed above it, which is the healthy direction.
juno_cli uses juno.sema.sem_context, so a change to juno.sema.sem_context can break juno_cli, while a change to juno_cli can't break juno.sema.sem_context.
Position
Below the diagonal: juno_cli uses a module listed above it, which is the healthy direction.
juno_ast.node_enums uses juno_ast.context, so a change to juno_ast.context can break juno_ast.node_enums, while a change to juno_ast.node_enums can't break juno_ast.context.
Position
Below the diagonal: juno_ast.node_enums uses a module listed above it, which is the healthy direction.
juno_ast.node_enums uses juno_ast.validate, so a change to juno_ast.validate can break juno_ast.node_enums, while a change to juno_ast.node_enums can't break juno_ast.validate.
Position
Below the diagonal: juno_ast.node_enums uses a module listed above it, which is the healthy direction.
juno_ast.node_enums uses juno_ast.node_child, so a change to juno_ast.node_child can break juno_ast.node_enums, while a change to juno_ast.node_enums can't break juno_ast.node_child.
Position
Below the diagonal: juno_ast.node_enums uses a module listed above it, which is the healthy direction.
juno.gen_js uses hermes.parser.node, so a change to hermes.parser.node can break juno.gen_js, while a change to juno.gen_js can't break hermes.parser.node.
Position
Below the diagonal: juno.gen_js uses a module listed above it, which is the healthy direction.
juno.gen_js uses juno_support.source_manager, so a change to juno_support.source_manager can break juno.gen_js, while a change to juno.gen_js can't break juno_support.source_manager.
Position
Below the diagonal: juno.gen_js uses a module listed above it, which is the healthy direction.
juno.gen_js uses juno_ast.node_enums, so a change to juno_ast.node_enums can break juno.gen_js, while a change to juno.gen_js can't break juno_ast.node_enums.
Position
Below the diagonal: juno.gen_js uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 41% · Weak · gated by R1, X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
83
High / Critical
A03:2025 — Software Supply Chain Failures
71
High / Critical
A02:2025 — Security Misconfiguration
2
High / Critical
Roadmap
Top priorities: Resolve the 1 finding(s) in Type Safety; Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor); Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
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.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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 — 120
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 — 435
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 — 251
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 34
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 46 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 46 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, 782 of 806 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D1 Cyclomatic Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.c, .cpp) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
D2 Cognitive Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.c, .cpp) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
D4 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 84 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .c (3,007,600 lines, 88% of production source), .cpp (370,340 lines, 11% of production source), .cc (541 lines, 0% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
D6 Cohesion (LCOM4) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 792 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 43 test source file(s) (.py, .rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 6 Maven/Gradle manifest(s) were read, stating a version for 6 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — 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 repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — 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 repository declares REDACTED, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D15 Churn × Complexity Hotspots — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A hotspot is churn × complexity. Churn was measured (147486 line(s) across the 90-day window), but no complexity could be computed for .c, .cpp, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — 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.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Project size and spread are measured over build units (a .NET project, a Maven or Gradle module, an npm, Deno or JSR package, a Go module, a Cargo crate, a Python, Composer, Bundler, RubyGems, Mix, rebar3, sbt, SwiftPM or pub package, an OTP application, an Xcode project or XcodeGen spec, or a checkout that declares no build at all) whose source a code model reads. This repository's production source is in a language no model reads, or in units whose build tool D26 does not recognise. That is a gap in this analyzer's language reach — not a finding that the repository's projects are cohesive.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D31 IaC & Container Security — 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. Checkov ran but its report could not be read (checkov produced no output — not a clean result). Every misconfiguration only checkov reports — most of its Terraform, CloudFormation, Bicep and Ansible policies — is absent from this card, so its absence here is not evidence those resources are configured correctly.
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. `API/hermes/extensions/00-header.js`, `API/hermes/extensions/99-footer.js`, `benchmarks/MiniReact/no-deps/MiniReact.js`, `benchmarks/MiniReact/no-objects/out/music.js`, `benchmarks/MiniReact/no-objects/out/simple.js`, … (+47 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.
D35 Change Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Change coupling is mined from the co-change history of production source files, but this repository's production source is .c, .cc, .cpp, .mm, which this pass does not recognise as source — only 4443 file(s) could be paired, so no coupling could be found no matter how tangled the history is. Not scored — this is a gap in the analysis run, not a finding about this repository.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
AXB2 Runtime readiness — 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. `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read REDACTED: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
AXR1 Runtime accessibility — 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. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read REDACTED: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java, Kotlin, Python, Rust, c, cpp, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin, Python, Rust, c, cpp, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
PF1 Benchmark discipline — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
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. 70 further occurrence(s) are not listed individually; the score already reflects all 110.
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. 64 further occurrence(s) are not listed individually; the score already reflects all 104.
R4 Test Coverage — 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. 149 further occurrence(s) are not listed individually; the score already reflects all 189.
R7 Dead Code — 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. 175 further occurrence(s) are not listed individually; the score already reflects all 215.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X28 Index access outside its own emptiness guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Production source was not modelled — run is Degraded — No code model read .c, .cc, .cpp, .mm, so the complexity, duplication and architecture dimensions were scored over a minority of this repository rather than its product, and dimensions that abstained did so for want of a model rather than for want of findings. The grade is NOT representative of this repository; diagnostics.md records the exact cause.
Repo exclusion declarations: 4 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.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
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.
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.
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.
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.
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.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
84 duplicated block group(s) detected. 5.9 % of the production lines (3,012 of 50,836) are in a reported copy. A further 34 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 118 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .c, .cpp, .cc (98% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
+ 71 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with gen_js.rs (2), PlatformNumberFormatterAndroid.java, antipattern_scan.py. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), codegen.rs, analyzer.rs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with atom_table.rs (2), de.rs, LocaleMatcher.java. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.3 / 10Stronggated by 4 serious findings✓ 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.
46 production modules (Gradle+Cargo+npm+CMake), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 4 module(s) off the main sequence, with abstractness counted on 19 of the 46 (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).
Off the main sequence: hermes_estree_codegen · ×4
What to do
Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Stronggated by 4 serious findings✓ 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.
28 skipped (24 with a documented reason), 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 792 tests. Measured on the JavaScript/TypeScript suite only — at least 43 test source file(s) (.py, .rs) went unread, so its test quality is unmeasured and is not in these counts.
Skipped test: Function name shadows type parameter · ×4tools/hermes-parser/js/hermes-eslint/__tests__/HermesScopeManager-test.js:1573
Resolve the 4 Skipped test finding(s) in Test Quality — start with types-include-all-nodes-test.js (3), HermesScopeManager-test.js. — One of this dimension's main actionable groups (4 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 / 10Adequategated by 1 critical finding✓ 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.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `npm install --ignore-scripts` (no lockfile) in API/hermes/cdp/tools/hermes-inspector-msggen/ (0 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in tools/hermes-parser/js/ (68 tests)): measured (0 flaky).
Test suite declares a test script but contains no test files: API/hermes/cdp/tools/hermes-inspector-msggen/
What to do
Resolve the 1 Test suite declares a test script but contains no test files finding(s) in Test Reliability. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d11_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 84 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 3 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Gradle build (build.gradle/build.gradle.kts) and REDACTED, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
✓ On the Gold path — maintain.
Detailed fixes: d14_recommendation.md.
Do you agree with this assessment?
D16 · Bus Factor9.1 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
25 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleIdentifier.java. Counted over 288 of the 2386 production source files in this repository: 2067 are under the ~2,400-byte size floor this dimension measures over, and the remaining 31 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×4
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
78 deducted task-comment markers across 50836 LoC (0.1/KLoC) → score 9.7. 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 51 TodoComment finding(s) in Explicit Debt — start with analyzer.rs (4), PlatformCollatorAndroid.java (4), PlatformDateTimeFormatterAndroid.java (4). — One of this dimension's main actionable groups (51 warning-level).
Resolve the 26 FixmeComment finding(s) in Explicit Debt — start with TestRunner.py (5), REDACTED (5), config.py (4). — One of this dimension's main actionable groups (26 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with LocaleObjectAndroid.java. — 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.
1 of 2 documentation facets pass in full; short on: F2 example. 109 document(s) read across 18 unit(s).
Documentation: no build, run or usage example · ×3tools/hermes-parser/js/hermes-estree/README.md:1
What to do
Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3). — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
No ADRs foundunsupported/juno/crates/juno_cli/Cargo.toml:8
What to do
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
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 names · ×6benchmarks/MiniReact/no-deps/MiniReact.js:57
What to do
Resolve the 61 redundant comment finding(s) in Comment Value — start with gbemu.js (7), pdfjs.js (7), test.js (4). — One of this dimension's main actionable groups (61 recommendation-level).
Detailed fixes: d24_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.
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).
83 finding(s): 0 critical, 68 high, 13 medium, 2 low. 47 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 466 file(s) — `API/hermes/AsyncDebuggerAPI.h` (line 81, line 86, line 91, …), `API/hermes/SynthTrace.h` (lines 245–246, line 779, line 781, …), `API/hermes/TracingRuntime.h` (line 24, line 27), `API/hermes/cdp/DomainState.h` (line 135), `API/hermes/extensions/00-header.js`, … (+461 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 7 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
+ 17 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 47 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (48 issue-level, 1 of them charged here).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 36 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (33), REDACTED (3). — One of this dimension's main actionable groups (36 issue-level).
Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 10 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED (2). — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d31_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.
121 of 319 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is benchmarks/bench-runner/resource/test-suites/octane/pdfjs.js. Counted over 319 of the 2386 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 111 Orphaned file finding(s) in Knowledge Freshness — start with comments.js (2), scope_manager.rs, MiniReact.js. — One of this dimension's main actionable groups (111 recommendation-level).
Resolve the 10 Orphaned knowledge finding(s) in Knowledge Freshness — start with pdfjs.js, REDACTED, analyzer.rs. — One of this dimension's main actionable groups (10 issue-level).
Resolve the 1 Further orphaned files (smaller) 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 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 6 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
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 read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
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.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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.
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 & versioning9.7 / 10Exemplary✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
2 public types in `com.facebook.hermes.helpers.internal` are marked as implementation by their own namespace, folder or name: `PackageJson` (android/build-logic/src/main/kotlin/com/facebook/hermes/helpers/internal/SerializeHermesCompilerPackageJson.kt:14, `internal`), `SerializeHermesCompilerPackageJson` (android/build-logic/src/main/kotlin/com/facebook/hermes/helpers/internal/SerializeHermesCompilerPackageJson.kt:16, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — android/build-logic/src/main/kotlin/com/facebook/hermes/helpers/internal/SerializeHermesCompilerPackageJson.kt:14
2 public types in the root namespace are marked as implementation by their own namespace, folder or name: `HermesUtilsPlugin` (android/build-logic/src/main/kotlin/com/facebook/hermes/plugins/internal/TestUtilsPlugin.kt:14, `internal`), `HermesUtils` (android/build-logic/src/main/kotlin/com/facebook/hermes/plugins/internal/TestUtilsPlugin.kt:25, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — android/build-logic/src/main/kotlin/com/facebook/hermes/plugins/internal/TestUtilsPlugin.kt:14
1 public type in `com.facebook.hermes.tasks.internal` is marked as implementation by its own namespace, folder or name: `CustomExecTask` (android/build-logic/src/main/kotlin/com/facebook/hermes/tasks/internal/CustomExecTask.kt:23, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — android/build-logic/src/main/kotlin/com/facebook/hermes/tasks/internal/CustomExecTask.kt:23
What to do
Hide `com.facebook.hermes.helpers.internal` (`PackageJson`, `SerializeHermesCompilerPackageJson`) (Kotlin: `internal`; Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide the root namespace (`HermesUtilsPlugin`, `HermesUtils`) (Kotlin: `internal`; Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `com.facebook.hermes.tasks.internal` (`CustomExecTask`) (Kotlin: `internal`; Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Do you agree with this assessment?
P2 · Observability4.6 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `.`, `unsupported/juno/crates/flow_native`, `unsupported/juno/crates/juno_cli`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 12 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
`API/hermes/cdp/tools/hermes-inspector-msggen/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — API/hermes/cdp/tools/hermes-inspector-msggen/package.json:24
What to do
Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety0.1 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
40 typed · 5642 plain JS — the untyped files are API/hermes/cdp/tools/hermes-inspector-msggen/src/Command.js, API/hermes/cdp/tools/hermes-inspector-msggen/src/Converters.js, API/hermes/cdp/tools/hermes-inspector-msggen/src/Event.js, API/hermes/cdp/tools/hermes-inspector-msggen/src/GeneratedHeader.js, API/hermes/cdp/tools/hermes-inspector-msggen/src/Graph.js, API/hermes/cdp/tools/hermes-inspector-msggen/src/HeaderWriter.js (+5636 more).
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.
external/asmjit/asmjit/db/aarch32.js:601 · external/asmjit/asmjit/db/aarch64.js:605 — 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. — external/asmjit/asmjit/db/aarch32.js:601
API/hermes/cdp/tools/hermes-inspector-msggen/src/HeaderWriter.js:20 · API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js:18 — the two spans are one implementation copied and then locally edited — 652 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. — API/hermes/cdp/tools/hermes-inspector-msggen/src/HeaderWriter.js:20
lib/InternalJavaScript/08-IteratorPrototypeDrop.js:32 · lib/InternalJavaScript/17-IteratorPrototypeTake.js:32 — the two spans are one implementation copied and then locally edited — 332 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. — lib/InternalJavaScript/08-IteratorPrototypeDrop.js:32
external/asmjit/asmjit/db/aarch32.js:433 · external/asmjit/asmjit/db/aarch64.js:436 — 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. — external/asmjit/asmjit/db/aarch32.js:433
external/asmjit/asmjit/db/aarch32.js:893 · external/asmjit/asmjit/db/aarch64.js:854 — 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. — external/asmjit/asmjit/db/aarch32.js:893
external/asmjit/asmjit/db/aarch32.js:349 · external/asmjit/asmjit/db/aarch64.js:350 — 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. — external/asmjit/asmjit/db/aarch32.js:349
external/asmjit/asmjit/db/aarch32.js:542 · external/asmjit/asmjit/db/aarch64.js:541 — 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. — external/asmjit/asmjit/db/aarch32.js:542
lib/InternalJavaScript/10-IteratorPrototypeFilter.js:32 · lib/InternalJavaScript/14-IteratorPrototypeMap.js:32 — the two spans are one implementation copied and then locally edited — 268 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. — lib/InternalJavaScript/10-IteratorPrototypeFilter.js:32
lib/InternalJavaScript/11-IteratorPrototypeFind.js:32 · lib/InternalJavaScript/16-IteratorPrototypeSome.js:32 — 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. — lib/InternalJavaScript/11-IteratorPrototypeFind.js:32
lib/TypedLib/01-array.js:390 · lib/TypedLib/01-array.js:431 — 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. — lib/TypedLib/01-array.js:390
lib/InternalJavaScript/01-Promise.js:160 · lib/InternalJavaScript/01-Promise.js:301 — 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. — lib/InternalJavaScript/01-Promise.js:160
external/asmjit/asmjit/db/aarch32.js:902 · external/asmjit/asmjit/db/aarch64.js:863 · external/asmjit/asmjit/db/x86.js:911 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — external/asmjit/asmjit/db/aarch32.js:902
tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:150 · tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:233 — 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. — tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:150
lib/TypedLib/03-map.js:26 · lib/TypedLib/04-set.js:20 — 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. — lib/TypedLib/03-map.js:26
tools/hermes-parser/js/prettier-plugin-hermes-parser/index.mjs:10 · tools/hermes-parser/js/scripts/templates/prettier-plugin-index.mjs:10 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — tools/hermes-parser/js/prettier-plugin-hermes-parser/index.mjs:10
API/hermes/cdp/tools/hermes-inspector-msggen/src/Command.js:19 · API/hermes/cdp/tools/hermes-inspector-msggen/src/Event.js:18 — 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. — API/hermes/cdp/tools/hermes-inspector-msggen/src/Command.js:19
external/asmjit/asmjit/db/aarch32.js:209 · external/asmjit/asmjit/db/aarch64.js:248 — 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. — external/asmjit/asmjit/db/aarch32.js:209
external/asmjit/asmjit/db/aarch32.js:836 · external/asmjit/asmjit/db/aarch64.js:831 — 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. — external/asmjit/asmjit/db/aarch32.js:836
tools/hermes-parser/js/hermes-eslint/src/scope-manager/referencer/Referencer.js:246 · tools/hermes-parser/js/hermes-eslint/src/scope-manager/referencer/Referencer.js:418 — 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. — tools/hermes-parser/js/hermes-eslint/src/scope-manager/referencer/Referencer.js:246
tools/hermes-parser/js/hermes-eslint/src/scope-manager/scope/ComponentScope.js:22 · tools/hermes-parser/js/hermes-eslint/src/scope-manager/scope/HookScope.js:22 — 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. — tools/hermes-parser/js/hermes-eslint/src/scope-manager/scope/ComponentScope.js:22
lib/InternalJavaScript/09-IteratorPrototypeEvery.js:32 · lib/InternalJavaScript/11-IteratorPrototypeFind.js:32 · lib/InternalJavaScript/13-IteratorPrototypeForEach.js:32 · lib/InternalJavaScript/16-IteratorPrototypeSome.js:32 — the 4 copies are spread across 4 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. — lib/InternalJavaScript/09-IteratorPrototypeEvery.js:32
lib/TypedLib/01-array.js:186 · lib/TypedLib/01-array.js:209 — 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. — lib/TypedLib/01-array.js:186
tools/hermes-parser/js/hermes-transform/src/traverse/NodeEventGenerator.js:128 · tools/hermes-parser/js/hermes-transform/src/traverse/NodeEventGenerator.js:163 — 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. — tools/hermes-parser/js/hermes-transform/src/traverse/NodeEventGenerator.js:128
external/asmjit/asmjit/db/aarch32.js:259 · external/asmjit/asmjit/db/aarch64.js:303 — 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. — external/asmjit/asmjit/db/aarch32.js:259
API/hermes/cdp/tools/hermes-inspector-msggen/src/Command.js:51 · API/hermes/cdp/tools/hermes-inspector-msggen/src/Event.js:42 — 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. — API/hermes/cdp/tools/hermes-inspector-msggen/src/Command.js:51
external/asmjit/asmjit/db/aarch32.js:6 · external/asmjit/asmjit/db/aarch64.js:6 — 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. — external/asmjit/asmjit/db/aarch32.js:6
API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js:413 · API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js:534 — 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. — API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js:413
lib/TypedLib/01-array.js:484 · lib/TypedLib/01-array.js:509 — 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. — lib/TypedLib/01-array.js:484
tools/hermes-parser/js/hermes-parser/src/estree/StripFlowTypesForBabel.js:77 · tools/hermes-parser/js/hermes-parser/src/estree/StripFlowTypesForBabel.js:99 — 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. — tools/hermes-parser/js/hermes-parser/src/estree/StripFlowTypesForBabel.js:77
tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:610 · tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:799 — 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. — tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:610
lib/InternalJavaScript/01-Promise.js:374 · lib/InternalJavaScript/01-Promise.js:493 — 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. — lib/InternalJavaScript/01-Promise.js:374
lib/InternalJavaScript/04-AsyncIterator.js:38 · lib/InternalJavaScript/04-AsyncIterator.js:325 — the two spans are one implementation copied and then locally edited — 86 tokens are still identical, in the same order in both spans, 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. — lib/InternalJavaScript/04-AsyncIterator.js:38
lib/InternalJavaScript/09-IteratorPrototypeEvery.js:32 · lib/InternalJavaScript/10-IteratorPrototypeFilter.js:32 · lib/InternalJavaScript/11-IteratorPrototypeFind.js:32 · lib/InternalJavaScript/12-IteratorPrototypeFlatMap.js:32 · +4 more site(s) not listed — the 8 copies are spread across 8 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. — lib/InternalJavaScript/09-IteratorPrototypeEvery.js:32
tools/hermes-parser/js/hermes-parser/src/HermesParserDeserializer.js:184 · tools/hermes-parser/js/hermes-parser/src/HermesParserDeserializer.js:202 — 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. — tools/hermes-parser/js/hermes-parser/src/HermesParserDeserializer.js:184
tools/hermes-parser/js/scripts/genTransformCloneTypes.js:41 · tools/hermes-parser/js/scripts/genTransformModifyTypes.js:35 — 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. — tools/hermes-parser/js/scripts/genTransformCloneTypes.js:41
external/asmjit/asmjit/db/aarch32.js:112 · external/asmjit/asmjit/db/aarch64.js:188 — 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. — external/asmjit/asmjit/db/aarch32.js:112
external/asmjit/asmjit/db/base.js:551 · external/asmjit/asmjit/db/base.js:581 — 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. — external/asmjit/asmjit/db/base.js:551
external/asmjit/asmjit/tools/tablegen-a64.js:228 · external/asmjit/asmjit/tools/tablegen-x86.js:847 — 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. — external/asmjit/asmjit/tools/tablegen-a64.js:228
lib/InternalJavaScript/01-Promise.js:206 · lib/InternalJavaScript/01-Promise.js:355 — 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. — lib/InternalJavaScript/01-Promise.js:206
lib/TypedLib/02-string.js:45 · lib/TypedLib/02-string.js:75 · lib/TypedLib/02-string.js:105 · lib/TypedLib/02-string.js:168 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — lib/TypedLib/02-string.js:45
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.
external/asmjit/asmjit/tools/tablegen.js:23 reaches into another package with a relative path (../db) — import the package by name instead. — external/asmjit/asmjit/tools/tablegen.js:23
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.
(top-level) has cyclomatic complexity 343 and cognitive complexity 342; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — test/BCGen/HBC/many_tries.js:15
transformNode has cyclomatic complexity 84 and cognitive complexity 64; 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. — tools/hermes-parser/js/hermes-parser/src/babel/TransformESTreeToBabel.js:926
makeSignatures has cyclomatic complexity 74 and cognitive complexity 212; 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. — external/asmjit/asmjit/tools/tablegen-x86.js:1574
_assignOpcode has cyclomatic complexity 54 and cognitive complexity 140; 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. — external/asmjit/asmjit/db/x86.js:573
sumPrecise has cyclomatic complexity 52 and cognitive complexity 104; 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. — lib/InternalJavaScript/20-MathPrototypeSumPrecise.js:44
(anonymous) has cyclomatic complexity 47 and cognitive complexity 45; 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. — lib/InternalJavaScript/05-IteratorHelperDependencies.js:311
transform has cyclomatic complexity 43 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 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. — tools/hermes-parser/js/hermes-parser/src/estree/StripFlowTypes.js:33
flagsOf has cyclomatic complexity 42 and cognitive complexity 87; 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. — external/asmjit/asmjit/tools/tablegen-x86.js:204
newInstFromGroup has cyclomatic complexity 38 and cognitive complexity 74; 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. — external/asmjit/asmjit/tools/tablegen-x86.js:590
_assignOperands has cyclomatic complexity 37 and cognitive complexity 107; 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. — external/asmjit/asmjit/db/aarch64.js:413
queryRwGeneric has cyclomatic complexity 36 and cognitive complexity 68; 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. — external/asmjit/asmjit/tools/tablegen-x86.js:2144
ValidateAndApplyPropertyDescriptor has cyclomatic complexity 36 and cognitive complexity 67; 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. — lib/InternalJavaScript/05-IteratorHelperDependencies.js:954
_assignOpcode has cyclomatic complexity 35 and cognitive complexity 77; 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. — external/asmjit/asmjit/db/aarch32.js:641
_assignOpcode has cyclomatic complexity 34 and cognitive complexity 76; 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. — external/asmjit/asmjit/db/aarch64.js:648
prettyPrintRec has cyclomatic complexity 34 and cognitive complexity 46; 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. — tools/hermes/evaluate-line.js:103
_assignOperands has cyclomatic complexity 33 and cognitive complexity 100; 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. — external/asmjit/asmjit/db/aarch32.js:417
constructor has cyclomatic complexity 33 and cognitive complexity 59; 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. — external/asmjit/asmjit/db/x86.js:213
defineDataProperty has cyclomatic complexity 33 and cognitive complexity 35; 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. — lib/InternalJavaScript/05-IteratorHelperDependencies.js:191
attach has cyclomatic complexity 30 and cognitive complexity 53; 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. — tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/main/comments.js:161
(top-level) has cyclomatic complexity 30 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 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. — tools/hermes-parser/js/scripts/expand-minified.js:14
throws has cyclomatic complexity 29 and cognitive complexity 61; 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. — external/node-api-tests/hermes/assert.js:137
GetIntrinsic has cyclomatic complexity 29 and cognitive complexity 41; 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. — lib/InternalJavaScript/05-IteratorHelperDependencies.js:530
browserResize has cyclomatic complexity 29 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — test/IRGen/estree_parse.js:27
evaluate has cyclomatic complexity 29 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — external/asmjit/asmjit/db/exp.js:202
parseExpression has cyclomatic complexity 28 and cognitive complexity 87; 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. — external/asmjit/asmjit/db/exp.js:455
calcImplicitMemSize has cyclomatic complexity 26 and cognitive complexity 69; 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. — external/asmjit/asmjit/tools/tablegen-x86.js:1275
rwFlagsOf has cyclomatic complexity 24 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. — external/asmjit/asmjit/tools/tablegen-x86.js:1832
tokenize has cyclomatic complexity 23 and cognitive complexity 43; 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. — external/asmjit/asmjit/db/exp.js:354
deepStrictEqual has cyclomatic complexity 22 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. — external/node-api-tests/hermes/assert.js:44
handleClassComments has cyclomatic complexity 21 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. — tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:381
(top-level) has cyclomatic complexity 21 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — test/Parser/flow/conditional-type.js:14
index has cyclomatic complexity 20 and cognitive complexity 39; 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. — external/asmjit/asmjit/tools/tablegen.js:81
attributeMode has cyclomatic complexity 20 and cognitive complexity 20; 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. — test/IRGen/estree_parse.js:496
analyzePattern has cyclomatic complexity 20 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. — tools/hermes-parser/js/hermes-parser/src/estree/TransformMatchSyntax.js:287
(anonymous) has cyclomatic complexity 20 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tools/hermes-parser/js/hermes-transform/__tests__/test_codemods/thisInExportedFunction-test.js:55
(anonymous) has cyclomatic complexity 19 and cognitive complexity 40; 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. — external/asmjit/asmjit/tools/tablegen-x86.js:1990
(top-level) has cyclomatic complexity 19 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 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. — external/flowtest/test/flow/types/conditional_types/passing.js:1
rmReplaceableCategory has cyclomatic complexity 18 and cognitive complexity 31; 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. — external/asmjit/asmjit/tools/tablegen-x86.js:2347
formatEmit has cyclomatic complexity 18 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. — external/asmjit/asmjit/tools/tablegen-x86.js:612
CallExpression has cyclomatic complexity 18 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. — tools/hermes-parser/js/hermes-transform/__tests__/test_codemods/bindThisToArrow-test.js:15
Do you agree with this assessment?
R3 · Large Files9.5 / 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.
external/asmjit/asmjit/tools/tablegen-x86.js has 2200 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — external/asmjit/asmjit/tools/tablegen-x86.js:1
lib/InternalJavaScript/05-IteratorHelperDependencies.js has 1935 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/InternalJavaScript/05-IteratorHelperDependencies.js:1
tools/hermes-parser/js/hermes-estree/src/types.js has 1920 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools/hermes-parser/js/hermes-estree/src/types.js:1
tools/hermes-parser/js/hermes-parser/src/babel/TransformESTreeToBabel.js has 1260 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools/hermes-parser/js/hermes-parser/src/babel/TransformESTreeToBabel.js:1
lib/InternalJavaScript/01-Promise.js has 1053 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/InternalJavaScript/01-Promise.js:1
tools/hermes-parser/js/hermes-parser/src/estree/TransformMatchSyntax.js has 950 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools/hermes-parser/js/hermes-parser/src/estree/TransformMatchSyntax.js:1
tools/hermes-parser/js/hermes-eslint/src/scope-manager/referencer/Referencer.js has 904 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools/hermes-parser/js/hermes-eslint/src/scope-manager/referencer/Referencer.js:1
tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js has 903 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:1
external/asmjit/asmjit/db/x86.js has 830 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — external/asmjit/asmjit/db/x86.js:1
external/asmjit/asmjit/db/aarch32.js has 816 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — external/asmjit/asmjit/db/aarch32.js:1
tools/hermes-parser/js/flow-typed/prettier.js has 813 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools/hermes-parser/js/flow-typed/prettier.js:1
tools/hermes-parser/js/hermes-parser/src/estree/TransformComponentSyntax.js has 810 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools/hermes-parser/js/hermes-parser/src/estree/TransformComponentSyntax.js:1
external/asmjit/asmjit/db/aarch64.js has 768 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — external/asmjit/asmjit/db/aarch64.js:1
tools/hermes-parser/js/flow-typed/jest.js has 751 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools/hermes-parser/js/flow-typed/jest.js:1
external/asmjit/asmjit/db/exp.js has 634 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — external/asmjit/asmjit/db/exp.js:1
lib/TypedLib/01-array.js has 559 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/TypedLib/01-array.js:1
external/asmjit/asmjit/db/base.js has 527 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — external/asmjit/asmjit/db/base.js:1
tools/hermes-parser/js/hermes-transform/src/transform/TransformContext.js has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools/hermes-parser/js/hermes-transform/src/transform/TransformContext.js:1
external/asmjit/asmjit/tools/generator-commons.js has 470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — external/asmjit/asmjit/tools/generator-commons.js:1
lib/InternalJavaScript/04-AsyncIterator.js has 461 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/InternalJavaScript/04-AsyncIterator.js:1
API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js:1
external/asmjit/asmjit/tools/tablegen.js has 452 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — external/asmjit/asmjit/tools/tablegen.js:1
tools/hermes-parser/js/hermes-eslint/src/scope-manager/scope/ScopeBase.js has 436 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools/hermes-parser/js/hermes-eslint/src/scope-manager/scope/ScopeBase.js: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 Coverage5.0 / 10Adequate✓ 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.
external/node-api-tests/js-native-api/2_function_arguments/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/2_function_arguments/test.js:2
external/node-api-tests/js-native-api/3_callbacks/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/3_callbacks/test.js:2
external/node-api-tests/js-native-api/4_object_factory/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/4_object_factory/test.js:2
external/node-api-tests/js-native-api/5_function_factory/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/5_function_factory/test.js:2
external/node-api-tests/js-native-api/6_object_wrap/nested_wrap.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/6_object_wrap/nested_wrap.js:4
external/node-api-tests/js-native-api/6_object_wrap/test-basic-finalizer.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/6_object_wrap/test-basic-finalizer.js:4
external/node-api-tests/js-native-api/6_object_wrap/test-object-wrap-ref.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/6_object_wrap/test-object-wrap-ref.js:4
external/node-api-tests/js-native-api/6_object_wrap/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/6_object_wrap/test.js:2
external/node-api-tests/js-native-api/7_factory_wrap/test.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/7_factory_wrap/test.js:4
external/node-api-tests/js-native-api/8_passing_wrapped/test.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/8_passing_wrapped/test.js:4
external/node-api-tests/js-native-api/test_array/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_array/test.js:2
external/node-api-tests/js-native-api/test_bigint/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_bigint/test.js:2
external/node-api-tests/js-native-api/test_cannot_run_js/test.js:11 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_cannot_run_js/test.js:11
external/node-api-tests/js-native-api/test_constructor/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_constructor/test.js:2
external/node-api-tests/js-native-api/test_constructor/test2.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_constructor/test2.js:2
external/node-api-tests/js-native-api/test_constructor/test_null.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_constructor/test_null.js:2
external/node-api-tests/js-native-api/test_conversions/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_conversions/test.js:2
external/node-api-tests/js-native-api/test_dataview/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_dataview/test.js:2
external/node-api-tests/js-native-api/test_date/test.js:3 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_date/test.js:3
external/node-api-tests/js-native-api/test_error/test.js:3 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_error/test.js:3
external/node-api-tests/js-native-api/test_exception/test.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_exception/test.js:4
external/node-api-tests/js-native-api/test_exception/testFinalizerException.js:3 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_exception/testFinalizerException.js:3
external/node-api-tests/js-native-api/test_finalizer/test.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_finalizer/test.js:4
external/node-api-tests/js-native-api/test_finalizer/test_fatal_finalize.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_finalizer/test_fatal_finalize.js:2
external/node-api-tests/js-native-api/test_function/test.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_function/test.js:4
external/node-api-tests/js-native-api/test_general/test.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_general/test.js:4
external/node-api-tests/js-native-api/test_general/testEnvCleanup.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_general/testEnvCleanup.js:4
external/node-api-tests/js-native-api/test_general/testFinalizer.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_general/testFinalizer.js:4
external/node-api-tests/js-native-api/test_general/testGlobals.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_general/testGlobals.js:2
external/node-api-tests/js-native-api/test_general/testInstanceOf.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_general/testInstanceOf.js:2
external/node-api-tests/js-native-api/test_general/testNapiRun.js:3 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_general/testNapiRun.js:3
external/node-api-tests/js-native-api/test_general/testNapiStatus.js:3 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_general/testNapiStatus.js:3
external/node-api-tests/js-native-api/test_general/testV8Instanceof.js:32 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_general/testV8Instanceof.js:32
external/node-api-tests/js-native-api/test_general/testV8Instanceof2.js:32 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_general/testV8Instanceof2.js:32
external/node-api-tests/js-native-api/test_handle_scope/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_handle_scope/test.js:2
external/node-api-tests/js-native-api/test_instance_data/test.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_instance_data/test.js:4
external/node-api-tests/js-native-api/test_new_target/test.js:3 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_new_target/test.js:3
external/node-api-tests/js-native-api/test_number/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_number/test.js:2
external/node-api-tests/js-native-api/test_number/test_null.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_number/test_null.js:2
external/node-api-tests/js-native-api/test_object/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — external/node-api-tests/js-native-api/test_object/test.js:2
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
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.
This repository declares test tooling, and the ✓ above records that declaration — but external/node-api-tests/js-native-api/2_function_arguments/test.js and 64 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — external/node-api-tests/js-native-api/2_function_arguments/test.js:2
Do you agree with this assessment?
R7 · Dead Code7.0 / 10Strong✓ 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 137 application, 14 tooling and 5389 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (137 application, 14 tooling, 5389 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 (×37) — lib/InternalJavaScript/05-IteratorHelperDependencies.js, tools/hermes-parser/js/flow-typed/prettier.js, tools/hermes-parser/js/flow-typed/jest.js, …
no import path from any entry point (137 application, 14 tooling, 5389 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools/emhermesc/test.js) — 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 — REDACTED
no import path from any entry point (137 application, 14 tooling, 5389 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools/dependency-extractor/test.js) — 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 — tools/dependency-extractor/DependencyExtractor.js
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.
Declared in external/node-api-cts/package.json 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.
Declared in npm/package.json 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.
Declared in 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.
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 · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/3 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 77 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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
AX6 Interface segregation — AX6 reached only 17% of this repository's production lines — c (3,405,674 lines), cpp (372,661 lines), rust (26,467 lines), python (16,815 lines), objectivec (2,559 lines), swift (309 lines), kotlin (129 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read REDACTED: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D1 Cyclomatic Complexity — cyclomatic complexity not measured — .c, .cpp exposed no member bodies
D12 Dependency Hygiene — Not scored — 6 Maven/Gradle manifest(s) were read, stating a version for 6 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D15 Churn × Complexity Hotspots — complexity unreadable for .c, .cpp — churn × complexity hotspots could not be measured
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.
D2 Cognitive Complexity — cognitive complexity not measured — .c, .cpp exposed no member bodies
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 17 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Java, Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — D26 measured no build unit over this repository's .c, .cc, .cpp, .java, .mm, .swift, .ts source. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .c, .cc, .cpp, .java, .kt, .mm, .py, .rs, .swift, .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D3 God Classes — Most of this repository's production source (.c, .cpp) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 52 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D35 Change Coupling — change coupling unreadable for .c, .cc, .cpp, .mm — no production change history could be paired for this repository's own source
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D6 Cohesion (LCOM4) — D6 reads a CS/VB/GO/SCALA/SWIFT/DART/JAVA/PY/KT/TS/TSX/MTS/CTS/JS/JSX/MJS/CJS/PHP/RB/RS/ERL/EX/EXS/FS class graph only — this repository's production source is .c, .cc, .cpp, .mm, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in API/hermes/cdp/tools/hermes-inspector-msggen/ ran and not one test passed (No tests found, exiting with code 1), so the coverage would describe the failed run, not the code. 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 only 1 of the 3 signals this lens looks for (49 value object(s))
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Python, Rust 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 — Benchmark discipline was not assessed: this repository is written in C, whose benchmark frameworks this check does not search yet. That is a gap in the analyzer's language reach, not a finding about your code.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — X1 reached only 18% of this repository's production lines — c (3,405,674 lines), cpp (372,661 lines), java (6,339 lines), objectivec (2,559 lines), swift (309 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 18% of this repository's production lines — c (3,405,674 lines), cpp (372,661 lines), rust (26,467 lines), java (6,339 lines), objectivec (2,559 lines), swift (309 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — X13 reached only 18% of this repository's production lines — c (3,405,674 lines), cpp (372,661 lines), rust (26,467 lines), java (6,339 lines), objectivec (2,559 lines), swift (309 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 17% of this repository's production lines — c (3,405,674 lines), cpp (372,661 lines), rust (26,467 lines), python (16,815 lines), objectivec (2,559 lines), swift (309 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — X17 reached only 18% of this repository's production lines — c (3,405,674 lines), cpp (372,661 lines), rust (26,467 lines), java (6,339 lines), objectivec (2,559 lines), swift (309 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X21 Side-effecting pattern guard — X21 reached only 18% of this repository's production lines — c (3,405,674 lines), cpp (372,661 lines), objectivec (2,559 lines), swift (309 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — X27 reached only 1% of this repository's production lines — c (3,405,674 lines), javascript (802,101 lines), cpp (372,661 lines), objectivec (2,559 lines), typescript (539 lines), swift (309 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X28 Index access outside its own emptiness guard — X28 reached only 18% of this repository's production lines — c (3,405,674 lines), cpp (372,661 lines), objectivec (2,559 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X29 Per-element action decided by a fixed element — X29 reached only 18% of this repository's production lines — c (3,405,674 lines), cpp (372,661 lines), python (16,815 lines), objectivec (2,559 lines), swift (309 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X3 Exception handling — X3 reached only 18% of this repository's production lines — c (3,405,674 lines), cpp (372,661 lines), rust (26,467 lines), objectivec (2,559 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X30 Support guard that admits what it rejects — X30 reached only 18% of this repository's production lines — c (3,405,674 lines), cpp (372,661 lines), objectivec (2,559 lines), swift (309 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
Orphaned knowledge benchmarks/bench-runner/resource/test-suites/octane/pdfjs.js:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge REDACTED:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge unsupported/hermes/crates/hermes_estree/src/de.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge unsupported/hermes/crates/hermes_estree/src/ser.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge lib/Platform/Intl/java/com/facebook/hermes/intl/NumberFormat.java:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge benchmarks/bench-runner/resource/test-suites/v8-v6-perf/v8-deltablue.js:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge tools/hermes-parser/js/flow-typed/jest.js:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge REDACTED:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
D11 · Test Reliability· Test suite declares a test script but contains no test files · ×1
Test suite declares a test script but contains no test files: API/hermes/cdp/tools/hermes-inspector-msggen/ — The jest suite in API/hermes/cdp/tools/hermes-inspector-msggen/ was installed and launched successfully, and the runner then found no test files to run — No tests found, exiting with code 1. The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
TodoComment utils/testsuite/es_ast.py:40— # TODO: Flow conditionally outputs "inexact" depending on whether the parent — 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 utils/testsuite/es_ast.py:51— # TODO: remember to update or remove them once we update the parser. — 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 utils/testsuite/typing_defs.py:30— # TODO(zhaogang): we can make this recursive to have nested comments on — 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 unsupported/juno/crates/juno_support/src/nullbuf.rs:27— // TODO: this is an extremely naive implementation, it can be optimized in multiple ways: — 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 unsupported/juno/crates/juno_ir/src/value_list.rs:77— // TODO: this can be implemented more efficiently in a circular 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 unsupported/juno/crates/juno_ir/src/value_list.rs:215— // TODO: this can be optimized with MaybeUninit. — 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 unsupported/juno/crates/juno/src/sourcemap.rs:17— /// TODO: Add support for other sourcemap metadata fields such as `metadata` and `sourcesContent`. — 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 unsupported/juno/crates/juno/src/sema/resolver.rs:436— // TODO: Share the global AST node and scope between calls to `visit_module` to avoid — 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 unsupported/juno/crates/juno/src/sema/resolver.rs:1240— // TODO: It can be possible to avoid setting this flag if the variable is shadowed — 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 unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:512— // TODO: revisit and maybe revert this to just visit ast.left normally — 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 unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:838— // TODO: record the pragmas — 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 unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:855— // TODO: record jsx pragma if root_name is not an FBT name — 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 unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:867— // TODO: this likely indicates a parse error, since a valid parse — 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 unsupported/hermes/crates/hermes_parser/tests/parser_test.rs:41— // TODO: hack to prevent changing lots of fixtures all at once — 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 unsupported/hermes/crates/hermes_comments/tests/test.rs:40— // TODO: hack to prevent changing lots of fixtures all at once — 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 unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:573— // TODO: deserialize with `parse_type` into a custom type — 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 tools/fuzzers/fuzzilli/profile/HermesProfile.swift:87— //TODO(edq) encode signature should be [.string, .jsTypedArray("Uint8Array")], but currently there seems to be no way to express Uint8Array as a JSType in Fuzzilli — 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 test/AST/ts2flow/nbody.ts:198— // @ts-ignore TODO: add the type declaration for print() — 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 benchmarks/nbody/fully-typed/nbody.ts:189— // @ts-ignore TODO: add the type declaration for print() — 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 lldb/Stack.py:89— # TODO: Verify the result is string type. — 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 lib/Platform/Unicode/java/com/facebook/hermes/unicode/AndroidUnicodeUtils.java:16— // TODO: use com.facebook.common.locale.Locales.getApplicationLocale() as the current locale, — 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 lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleMatcher.java:28— // TODO:: Method take String list as argument to avoid conversions between array and 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 lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleMatcher.java:29— // TODO:: AvailableLocales list always seems to be sorted. Is it guaranteed so that we can — 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 lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleMatcher.java:79— // TODO:: Not available on platforms <= 20 — 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 lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformCollatorAndroid.java:107— // TODO:: Not available on platforms <= 20 — 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.
+ 26 more in this group — see findings.md.
R4 · Test Coverage· This test file cannot be loaded · ×40
This test file cannot be loaded external/node-api-tests/js-native-api/2_function_arguments/test.js:2— external/node-api-tests/js-native-api/2_function_arguments/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/3_callbacks/test.js:2— external/node-api-tests/js-native-api/3_callbacks/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/4_object_factory/test.js:2— external/node-api-tests/js-native-api/4_object_factory/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/5_function_factory/test.js:2— external/node-api-tests/js-native-api/5_function_factory/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/6_object_wrap/nested_wrap.js:4— external/node-api-tests/js-native-api/6_object_wrap/nested_wrap.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/6_object_wrap/test-basic-finalizer.js:4— external/node-api-tests/js-native-api/6_object_wrap/test-basic-finalizer.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/6_object_wrap/test-object-wrap-ref.js:4— external/node-api-tests/js-native-api/6_object_wrap/test-object-wrap-ref.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/6_object_wrap/test.js:2— external/node-api-tests/js-native-api/6_object_wrap/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/7_factory_wrap/test.js:4— external/node-api-tests/js-native-api/7_factory_wrap/test.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/8_passing_wrapped/test.js:4— external/node-api-tests/js-native-api/8_passing_wrapped/test.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_array/test.js:2— external/node-api-tests/js-native-api/test_array/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_bigint/test.js:2— external/node-api-tests/js-native-api/test_bigint/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_cannot_run_js/test.js:11— external/node-api-tests/js-native-api/test_cannot_run_js/test.js:11 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_constructor/test.js:2— external/node-api-tests/js-native-api/test_constructor/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_constructor/test2.js:2— external/node-api-tests/js-native-api/test_constructor/test2.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_constructor/test_null.js:2— external/node-api-tests/js-native-api/test_constructor/test_null.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_conversions/test.js:2— external/node-api-tests/js-native-api/test_conversions/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_dataview/test.js:2— external/node-api-tests/js-native-api/test_dataview/test.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_date/test.js:3— external/node-api-tests/js-native-api/test_date/test.js:3 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_error/test.js:3— external/node-api-tests/js-native-api/test_error/test.js:3 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_exception/test.js:4— external/node-api-tests/js-native-api/test_exception/test.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_exception/testFinalizerException.js:3— external/node-api-tests/js-native-api/test_exception/testFinalizerException.js:3 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_finalizer/test.js:4— external/node-api-tests/js-native-api/test_finalizer/test.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_finalizer/test_fatal_finalize.js:2— external/node-api-tests/js-native-api/test_finalizer/test_fatal_finalize.js:2 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded external/node-api-tests/js-native-api/test_function/test.js:4— external/node-api-tests/js-native-api/test_function/test.js:4 imports '../../common', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
FixmeComment unsupported/juno/crates/juno/src/gen_js.rs:89— /// FIXME: This currently only returns an empty SourceMap. — 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.
FixmeComment unsupported/juno/crates/juno/src/gen_js.rs:281— // FIXME: Pass in file name 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.
FixmeComment external/llvh/utils/lit/lit/ShUtil.py:261— # FIXME: Operator precedence!! — 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.
FixmeComment REDACTED:215— # FIXME should target triple parts count here too? — 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.
FixmeComment external/llvh/utils/lit/lit/TestRunner.py:753— # FIXME: Actually, this is probably an instance of PR6753. — 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.
FixmeComment external/llvh/utils/lit/lit/TestRunner.py:815— # FIXME: Standardize on the builtin echo implementation. We can use a — 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.
FixmeComment external/llvh/utils/lit/lit/TestRunner.py:896— # FIXME: This is slow, but so is deadlock. — 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.
FixmeComment external/llvh/utils/lit/lit/TestRunner.py:975— # FIXME: There is probably still deadlock potential here. Yawn. — 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.
FixmeComment external/llvh/utils/lit/lit/TestRunner.py:1173— # FIXME: Running valgrind on sh is overkill. We probably could just — 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.
FixmeComment REDACTED:138— # FIXME: This should really only be suite in test suite config — 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.
FixmeComment REDACTED:142— # FIXME: This should really only be suite in test suite config — 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.
FixmeComment external/llvh/utils/lit/lit/discovery.py:169— # FIXME: This doesn't belong 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.
FixmeComment REDACTED:112— # FIXME: Record some information on the lit configuration used? — 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.
FixmeComment REDACTED:113— # FIXME: Record information from the individual test suites? — 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.
FixmeComment REDACTED:189— # FIXME: If Python does not exit cleanly, this directory will not be cleaned — 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.
FixmeComment REDACTED:200— # FIXME: Re-try after timeout on Windows. — 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.
FixmeComment REDACTED:224— # FIXME: I find these names very confusing, although I like the — 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.
FixmeComment external/llvh/utils/lit/lit/run.py:48— # FIXME: Find a way to capture the worker process stderr. If the user — 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.
FixmeComment external/llvh/utils/lit/lit/util.py:140— # "Too many open files". FIXME: Check if there's a better fix. — 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.
FixmeComment external/llvh/utils/lit/lit/util.py:353— # FIXME: Because of the way nested function scopes work in Python 2.x we — 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.
FixmeComment external/llvh/utils/lit/lit/llvm/config.py:47— # FIXME: lld uses the first, other projects use the second. — 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.
FixmeComment external/llvh/utils/lit/lit/llvm/config.py:195— # FIXME: Rather than just getting the version, we should have clang print — 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.
FixmeComment external/llvh/utils/lit/lit/llvm/config.py:357— # FIXME: Should we have a tool that enforces 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.
FixmeComment external/llvh/utils/lit/lit/llvm/config.py:431— # FIXME: Find nicer way to prohibit 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.
FixmeComment external/llvh/utils/lit/lit/formats/base.py:35— # FIXME: Refactor into generic test for running some command on a directory — 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.
+ 1 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×10
Duplicated block (7 lines × 2) lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformNumberFormatterAndroid.java:130— lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformNumberFormatterAndroid.java:130-136 | lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformNumberFormatterICU.java:333-339 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: `Currency` names `android.icu.util.Currency` in one and `java.util.Currency` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformNumberFormatterICU.java:332` calls `RequiresApi` and `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformNumberFormatterAndroid.java:128` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) agent-perf/tools/antipattern_scan.py:269— agent-perf/tools/antipattern_scan.py:269-276 | agent-perf/tools/sh_source_mapper.py:150-156 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `agent-perf/tools/antipattern_scan.py:269` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) agent-perf/tools/binary_size_analyzer.py:166— agent-perf/tools/binary_size_analyzer.py:166-172 | agent-perf/tools/binary_size_analyzer.py:208-214 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:256— unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:256-262 | unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:410-416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:256` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:636— unsupported/juno/crates/juno/src/gen_js.rs:636-642 | unsupported/juno/crates/juno/src/gen_js.rs:3539-3545 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) unsupported/juno/crates/juno_support/src/atom_table.rs:71— unsupported/juno/crates/juno_support/src/atom_table.rs:71-77 | unsupported/juno/crates/juno_support/src/atom_table.rs:91-97 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno_support/src/atom_table.rs:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) unsupported/juno/crates/hermes/src/parser/hermes_parser.rs:99— unsupported/juno/crates/hermes/src/parser/hermes_parser.rs:99-105 | unsupported/juno/crates/hermes/src/parser/node.rs:57-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) unsupported/hermes/crates/hermes_estree/src/de.rs:1160— unsupported/hermes/crates/hermes_estree/src/de.rs:1160-1166 | unsupported/hermes/crates/hermes_estree/src/de.rs:1186-1192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/hermes/crates/hermes_estree/src/de.rs:1160` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:1961— unsupported/juno/crates/juno/src/gen_js.rs:1961-1967 | unsupported/juno/crates/juno/src/gen_js.rs:3032-3038 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:1961` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `unsupported/juno/crates/juno/src/gen_js.rs:3030` calls `TypeParameterInstantiation` and `unsupported/juno/crates/juno/src/gen_js.rs:1960` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×6
JavaScript dependencies are not locked API/hermes/cdp/tools/hermes-inspector-msggen/package.json:24— API/hermes/cdp/tools/hermes-inspector-msggen/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/widgets/original/es5/package.json:4— benchmarks/widgets/original/es5/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/widgets/single-file/es5/package.json:2— benchmarks/widgets/single-file/es5/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked external/node-api-cts/package.json:13— external/node-api-cts/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked npm/package.json:9— npm/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked tools/hermes-parser/js/prettier-plugin-hermes-parser/package.json:16— tools/hermes-parser/js/prettier-plugin-hermes-parser/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
Duplicated block (8 lines × 2) REDACTED:161— REDACTED:161-168 | REDACTED:220-227 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:161` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) REDACTED:304— REDACTED:304-311 | REDACTED:318-325 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:304` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:730— unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:730-737 | unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:749-756 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:730` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:604— unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:604-611 | unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:651-658 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:604` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `ast` to `&hermes_estree::BreakStatement` in one and `&hermes_estree::ContinueStatement` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 2) external/llvh/utils/lit/lit/TestRunner.py:344— external/llvh/utils/lit/lit/TestRunner.py:344-351 | external/llvh/utils/lit/lit/TestRunner.py:601-608 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: `StringIO` names `StringIO` in one and `io` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `external/llvh/utils/lit/lit/TestRunner.py:595` calls `on_rm_error`, `chmod`, `S_IMODE` and `external/llvh/utils/lit/lit/TestRunner.py:342` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Skipped test: Function name shadows type parameter tools/hermes-parser/js/hermes-eslint/__tests__/HermesScopeManager-test.js:1573— Skipped — switched off by test.skip
Skipped test: was skipped due to being included in `typesThatShouldBeSkipped` tools/hermes-parser/js/__tests__/types-include-all-nodes-test.js:182— Skipped — switched off by it.skip
Skipped test: was marked to be skipped in `propertiesThatShouldBeSkipped` tools/hermes-parser/js/__tests__/types-include-all-nodes-test.js:201— Skipped — switched off by it.skip
Skipped test: has an incorrect optional flag in the hermes spec so we skip this test tools/hermes-parser/js/__tests__/types-include-all-nodes-test.js:222— Skipped — switched off by it.skip
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) unsupported/juno/crates/juno_support/src/atom_table.rs:70— unsupported/juno/crates/juno_support/src/atom_table.rs:70-84 | unsupported/juno/crates/juno_support/src/atom_table.rs:90-104 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) unsupported/hermes/crates/hermes_estree/src/de.rs:1157— unsupported/hermes/crates/hermes_estree/src/de.rs:1157-1171 | unsupported/hermes/crates/hermes_estree/src/de.rs:1180-1197 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleMatcher.java:49— lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleMatcher.java:49-66 | lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleMatcher.java:135-149 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) unsupported/juno/crates/juno_support/src/atom_table.rs:121— unsupported/juno/crates/juno_support/src/atom_table.rs:121-135 | unsupported/juno/crates/juno_support/src/atom_table.rs:161-175 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (6 lines × 2) REDACTED:142— REDACTED:142-147 | REDACTED:211-216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:142` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) external/llvh/utils/lit/lit/ProgressBar.py:276— external/llvh/utils/lit/lit/ProgressBar.py:276-281 | utils/testsuite/progress.py:302-312 — before extracting anything, compare `external/llvh/utils/lit/lit/ProgressBar.py` and `utils/testsuite/progress.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:479— unsupported/juno/crates/juno/src/gen_js.rs:479-484 | unsupported/juno/crates/juno/src/gen_js.rs:3035-3040 — 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 (6 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:647— unsupported/juno/crates/juno/src/gen_js.rs:647-652 | unsupported/juno/crates/juno/src/gen_js.rs:654-659 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) external/llvh/utils/lit/lit/util.py:397— external/llvh/utils/lit/lit/util.py:397-406 | external/llvh/utils/lit/lit/util.py:413-422 — 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 (10 lines × 2) utils/testsuite/hermes.py:231— utils/testsuite/hermes.py:231-240 | utils/testsuite/hermes.py:428-437 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `utils/testsuite/hermes.py:231` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) unsupported/juno/crates/flow_native/src/main.rs:1333— unsupported/juno/crates/flow_native/src/main.rs:1333-1342 | unsupported/juno/crates/juno_cli/src/main.rs:656-665 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) unsupported/juno/crates/juno/src/sema/resolver.rs:682— unsupported/juno/crates/juno/src/sema/resolver.rs:682-691 | unsupported/juno/crates/juno/src/sema/resolver.rs:1348-1357 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/sema/resolver.rs:682` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:1118— unsupported/juno/crates/juno/src/gen_js.rs:1118-1130 | unsupported/juno/crates/juno/src/gen_js.rs:1145-1157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:1118` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:2089— unsupported/juno/crates/juno/src/gen_js.rs:2089-2101 | unsupported/juno/crates/juno/src/gen_js.rs:2103-2115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:2089` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:2375— unsupported/juno/crates/juno/src/gen_js.rs:2375-2387 | unsupported/juno/crates/juno/src/gen_js.rs:2753-2765 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:2375` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) unsupported/juno/crates/juno/src/sema/resolver.rs:1484— unsupported/juno/crates/juno/src/sema/resolver.rs:1484-1496 | unsupported/juno/crates/juno/src/sema/resolver.rs:1538-1550 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/sema/resolver.rs:1484` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Off the main sequence: hermes_estree_codegen — hermes_estree_codegen: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: hermes_utils — hermes_utils: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: command_line — command_line: abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: juno_support — juno_support: abstractness 0.05, instability 0.14, distance 0.80 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Duplicated block (22 lines × 2 locations) external/asmjit/asmjit/db/aarch32.js:209— external/asmjit/asmjit/db/aarch32.js:209 · external/asmjit/asmjit/db/aarch64.js:248 — 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 (22 lines × 2 locations) external/asmjit/asmjit/db/aarch32.js:836— external/asmjit/asmjit/db/aarch32.js:836 · external/asmjit/asmjit/db/aarch64.js:831 — 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 (22 lines × 2 locations) tools/hermes-parser/js/hermes-eslint/src/scope-manager/referencer/Referencer.js:246— tools/hermes-parser/js/hermes-eslint/src/scope-manager/referencer/Referencer.js:246 · tools/hermes-parser/js/hermes-eslint/src/scope-manager/referencer/Referencer.js:418 — 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 (22 lines × 2 locations) tools/hermes-parser/js/hermes-eslint/src/scope-manager/scope/ComponentScope.js:22— tools/hermes-parser/js/hermes-eslint/src/scope-manager/scope/ComponentScope.js:22 · tools/hermes-parser/js/hermes-eslint/src/scope-manager/scope/HookScope.js:22 — 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 (18 lines × 2 locations) API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js:413— API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js:413 · API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js:534 — 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 (18 lines × 2 locations) lib/TypedLib/01-array.js:484— lib/TypedLib/01-array.js:484 · lib/TypedLib/01-array.js:509 — 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 (18 lines × 2 locations) tools/hermes-parser/js/hermes-parser/src/estree/StripFlowTypesForBabel.js:77— tools/hermes-parser/js/hermes-parser/src/estree/StripFlowTypesForBabel.js:77 · tools/hermes-parser/js/hermes-parser/src/estree/StripFlowTypesForBabel.js:99 — 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 (18 lines × 2 locations) tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:610— tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:610 · tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:799 — 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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×3
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×3
Edited copy of a member (13 corresponding lines) unsupported/hermes/crates/hermes_estree/src/de.rs:673— unsupported/hermes/crates/hermes_estree/src/de.rs:673-685 | unsupported/hermes/crates/hermes_estree/src/de.rs:690-704 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) lib/Platform/Intl/java/com/facebook/hermes/intl/Intl.java:85— lib/Platform/Intl/java/com/facebook/hermes/intl/Intl.java:85-97 | lib/Platform/Intl/java/com/facebook/hermes/intl/Intl.java:103-115 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:148— lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:148-160 | lib/Platform/Intl/java/com/facebook/hermes/intl/NumberFormat.java:156-171 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9 lines × 2) agent-perf/tools/generated_code_antipatterns.py:325— agent-perf/tools/generated_code_antipatterns.py:325-333 | agent-perf/tools/js_antipattern_scan.py:308-316 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:571— unsupported/juno/crates/juno/src/gen_js.rs:571-579 | unsupported/juno/crates/juno/src/gen_js.rs:590-598 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:571` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:1693— unsupported/juno/crates/juno/src/gen_js.rs:1693-1701 | unsupported/juno/crates/juno/src/gen_js.rs:2843-2851 — 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) unsupported/juno/crates/juno/src/gen_js.rs:1018— unsupported/juno/crates/juno/src/gen_js.rs:1018-1031 | unsupported/juno/crates/juno/src/gen_js.rs:1052-1065 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:1018` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:1892— unsupported/juno/crates/juno/src/gen_js.rs:1892-1905 | unsupported/juno/crates/juno/src/gen_js.rs:2706-2719 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:1892` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `unsupported/juno/crates/juno/src/gen_js.rs:1890` calls `as_str` and `unsupported/juno/crates/juno/src/gen_js.rs:2705` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:2470— unsupported/juno/crates/juno/src/gen_js.rs:2470-2483 | unsupported/juno/crates/juno/src/gen_js.rs:2532-2545 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `unsupported/juno/crates/juno/src/gen_js.rs:2546` calls `Some` and `unsupported/juno/crates/juno/src/gen_js.rs:2484` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) unsupported/juno/crates/juno/src/gen_js.rs:2415— unsupported/juno/crates/juno/src/gen_js.rs:2415-2422 | unsupported/juno/crates/juno/src/gen_js.rs:2582-2589 | unsupported/juno/crates/juno/src/gen_js.rs:3470-3477 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:2415` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) unsupported/juno/crates/juno/src/gen_js.rs:2471— unsupported/juno/crates/juno/src/gen_js.rs:2471-2478 | unsupported/juno/crates/juno/src/gen_js.rs:2533-2540 | unsupported/juno/crates/juno/src/gen_js.rs:2574-2581 — 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.
Duplicated block (8 lines × 3) unsupported/juno/crates/juno_eval/src/eval/environment_record.rs:614— unsupported/juno/crates/juno_eval/src/eval/environment_record.rs:614-621 | unsupported/juno/crates/juno_eval/src/eval/environment_record.rs:656-663 | unsupported/juno/crates/juno_eval/src/eval/environment_record.rs:729-736 — 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.
Duplicated block (17 lines × 2 locations) lib/InternalJavaScript/01-Promise.js:374— lib/InternalJavaScript/01-Promise.js:374 · lib/InternalJavaScript/01-Promise.js:493 — 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 (17 lines × 2 locations) tools/hermes-parser/js/hermes-parser/src/HermesParserDeserializer.js:184— tools/hermes-parser/js/hermes-parser/src/HermesParserDeserializer.js:184 · tools/hermes-parser/js/hermes-parser/src/HermesParserDeserializer.js:202 — 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 (17 lines × 2 locations) tools/hermes-parser/js/scripts/genTransformCloneTypes.js:41— tools/hermes-parser/js/scripts/genTransformCloneTypes.js:41 · tools/hermes-parser/js/scripts/genTransformModifyTypes.js:35 — 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 (15 lines × 2 locations) external/asmjit/asmjit/db/base.js:551— external/asmjit/asmjit/db/base.js:551 · external/asmjit/asmjit/db/base.js:581 — 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 (15 lines × 2 locations) external/asmjit/asmjit/tools/tablegen-a64.js:228— external/asmjit/asmjit/tools/tablegen-a64.js:228 · external/asmjit/asmjit/tools/tablegen-x86.js:847 — 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 (15 lines × 2 locations) lib/InternalJavaScript/01-Promise.js:206— lib/InternalJavaScript/01-Promise.js:206 · lib/InternalJavaScript/01-Promise.js:355 — 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.
Dead file (~100 LoC) lib/InternalJavaScript/06-IteratorObject.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~100 LoC) lib/InternalJavaScript/14-IteratorPrototypeMap.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~100 LoC) tools/hermes-parser/js/flow-typed/glob.js— no import path from any entry point (137 application, 14 tooling, 5389 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
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×2
Edited copy of a member (26 corresponding lines) agent-perf/tools/generated_code_antipatterns.py:315— agent-perf/tools/generated_code_antipatterns.py:315-346 | agent-perf/tools/js_antipattern_scan.py:298-323 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) agent-perf/tools/generated_code_analyzer.py:384— agent-perf/tools/generated_code_analyzer.py:384-413 | agent-perf/tools/generated_code_antipatterns.py:350-375 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:121— lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:121-142 | lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java:134-155 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformNumberFormatterICU.java:224— lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformNumberFormatterICU.java:224-245 | lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformNumberFormatterICU.java:303-330 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) unsupported/juno/crates/juno_ast/src/context.rs:450— unsupported/juno/crates/juno_ast/src/context.rs:450-461 | unsupported/juno/crates/juno_ast/src/context.rs:465-479 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) external/llvh/utils/lit/lit/util.py:397— external/llvh/utils/lit/lit/util.py:397-409 | external/llvh/utils/lit/lit/util.py:413-424 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) unsupported/juno/crates/juno_ast/src/context.rs:676— unsupported/juno/crates/juno_ast/src/context.rs:676-686 | unsupported/juno/crates/juno_ast/src/context.rs:691-703 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleObjectAndroid.java:210— lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleObjectAndroid.java:210-220 | lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleObjectICU.java:47-57 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (18 lines × 3) REDACTED:237— REDACTED:237-254 | REDACTED:260-277 | REDACTED:332-349 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 3) agent-perf/tools/annotate_disasm.py:143— agent-perf/tools/annotate_disasm.py:143-160 | agent-perf/tools/annotate_source.py:159-176 | agent-perf/tools/profile_to_json.py:139-156 — before extracting anything, compare `agent-perf/tools/annotate_disasm.py` and `agent-perf/tools/annotate_source.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `agent-perf/tools/annotate_disasm.py:143` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:583— lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:583-597 | lib/Platform/Intl/java/com/facebook/hermes/intl/NumberFormat.java:679-693 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:583` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (15 lines × 2) lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:471— lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:471-485 | lib/Platform/Intl/java/com/facebook/hermes/intl/NumberFormat.java:584-598 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:149— lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:149-153 | lib/Platform/Intl/java/com/facebook/hermes/intl/NumberFormat.java:159-163 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:149` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) external/llvh/utils/lit/lit/llvm/config.py:380— external/llvh/utils/lit/lit/llvm/config.py:380-384 | external/llvh/utils/lit/lit/llvm/config.py:468-472 — 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 (11 lines × 2) agent-perf/tools/generated_code_analyzer.py:328— agent-perf/tools/generated_code_analyzer.py:328-338 | agent-perf/tools/type_coverage_analyzer.py:194-204 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) unsupported/juno/crates/juno_pass/src/passes/strip_flow.rs:92— unsupported/juno/crates/juno_pass/src/passes/strip_flow.rs:92-102 | unsupported/juno/crates/juno_pass/src/passes/strip_flow.rs:110-120 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno_pass/src/passes/strip_flow.rs:92` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:945— unsupported/juno/crates/juno/src/gen_js.rs:945-965 | unsupported/juno/crates/juno/src/gen_js.rs:1025-1045 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:945` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (21 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:1085— unsupported/juno/crates/juno/src/gen_js.rs:1085-1105 | unsupported/juno/crates/juno/src/gen_js.rs:1531-1551 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:1085` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 3) unsupported/juno/crates/juno/src/gen_js.rs:942— unsupported/juno/crates/juno/src/gen_js.rs:942-954 | unsupported/juno/crates/juno/src/gen_js.rs:1022-1034 | unsupported/juno/crates/juno/src/gen_js.rs:1056-1068 — 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.
Duplicated block (13 lines × 3) unsupported/juno/crates/juno/src/gen_js.rs:956— unsupported/juno/crates/juno/src/gen_js.rs:956-968 | unsupported/juno/crates/juno/src/gen_js.rs:1036-1048 | unsupported/juno/crates/juno/src/gen_js.rs:1070-1082 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:956` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (37 lines × 2 locations) lib/InternalJavaScript/11-IteratorPrototypeFind.js:32— lib/InternalJavaScript/11-IteratorPrototypeFind.js:32 · lib/InternalJavaScript/16-IteratorPrototypeSome.js:32 — 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 (37 lines × 2 locations) lib/TypedLib/01-array.js:390— lib/TypedLib/01-array.js:390 · lib/TypedLib/01-array.js:431 — 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 (25 lines × 2 locations) lib/TypedLib/03-map.js:26— lib/TypedLib/03-map.js:26 · lib/TypedLib/04-set.js:20 — 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 (25 lines × 2 locations) tools/hermes-parser/js/prettier-plugin-hermes-parser/index.mjs:10— tools/hermes-parser/js/prettier-plugin-hermes-parser/index.mjs:10 · tools/hermes-parser/js/scripts/templates/prettier-plugin-index.mjs:10 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (21 lines × 2 locations) lib/TypedLib/01-array.js:186— lib/TypedLib/01-array.js:186 · lib/TypedLib/01-array.js:209 — 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 (21 lines × 2 locations) tools/hermes-parser/js/hermes-transform/src/traverse/NodeEventGenerator.js:128— tools/hermes-parser/js/hermes-transform/src/traverse/NodeEventGenerator.js:128 · tools/hermes-parser/js/hermes-transform/src/traverse/NodeEventGenerator.js:163 — 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 (19 lines × 2 locations) API/hermes/cdp/tools/hermes-inspector-msggen/src/Command.js:51— API/hermes/cdp/tools/hermes-inspector-msggen/src/Command.js:51 · API/hermes/cdp/tools/hermes-inspector-msggen/src/Event.js:42 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) external/asmjit/asmjit/db/aarch32.js:6— external/asmjit/asmjit/db/aarch32.js:6 · external/asmjit/asmjit/db/aarch64.js:6 — 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.
Dead file (~142 LoC) tools/hermes-parser/js/flow-typed/babel-parser.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~142 LoC) unsupported/juno/lit/flow_native/bitwise.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~90 LoC) lib/InternalJavaScript/15-IteratorPrototypeReduce.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~90 LoC) lib/InternalJavaScript/19-IteratorFrom.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~86 LoC) lib/InternalJavaScript/09-IteratorPrototypeEvery.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~86 LoC) lib/InternalJavaScript/16-IteratorPrototypeSome.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~61 LoC) lib/InternalJavaScript/18-IteratorPrototypeToArray.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~61 LoC) lib/TypedLib/03-map.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~59 LoC) lib/TypedLib/06-object.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~59 LoC) tools/hvm-bench/allocObj.js— no import path from any entry point (137 application, 14 tooling, 5389 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
HackComment lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleObjectAndroid.java:49— // hacky fallback!. — 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.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) external/llvh/utils/lit/lit/ProgressBar.py:90— external/llvh/utils/lit/lit/ProgressBar.py:90-135 | utils/testsuite/progress.py:97-147 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:255— unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:255-307 | unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:409-466 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:571— lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:571-597 | lib/Platform/Intl/java/com/facebook/hermes/intl/NumberFormat.java:665-693 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (47 corresponding lines) · ×1
Edited copy of a member (47 corresponding lines) unsupported/juno/crates/juno/src/gen_js.rs:3305— unsupported/juno/crates/juno/src/gen_js.rs:3305-3351 | unsupported/juno/crates/juno_support/src/json.rs:217-266 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:601— unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:601-634 | unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:636-668 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 35+ corresponding lines) · ×1
Edited copies of one member (5 members, 35+ corresponding lines) agent-perf/tools/annotate_disasm.py:133— agent-perf/tools/annotate_disasm.py:133-171 | agent-perf/tools/annotate_source.py:151-187 | agent-perf/tools/profile_to_json.py:124-168 | agent-perf/tools/regalloc_report.py:250-284 | agent-perf/tools/runtime_call_profiler.py:262-303 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) lib/Platform/Intl/java/com/facebook/hermes/intl/IntlTextUtils.java:24— lib/Platform/Intl/java/com/facebook/hermes/intl/IntlTextUtils.java:24-42 | lib/Platform/Intl/java/com/facebook/hermes/intl/IntlTextUtils.java:44-62 | lib/Platform/Intl/java/com/facebook/hermes/intl/IntlTextUtils.java:64-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:99— lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:99-117 | lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java:111-129 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleMatcher.java:68— lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleMatcher.java:68-84 | lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformCollatorAndroid.java:96-112 | lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:210-226 | lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformNumberFormatterAndroid.java:188-204 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) unsupported/juno/crates/flow_native/src/main.rs:1263— unsupported/juno/crates/flow_native/src/main.rs:1263-1272 | unsupported/juno/crates/juno_cli/src/main.rs:388-397 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) unsupported/juno/crates/flow_native/src/main.rs:646— unsupported/juno/crates/flow_native/src/main.rs:646-680 | unsupported/juno/crates/flow_native/src/main.rs:683-712 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) unsupported/juno/crates/juno_eval/src/eval/environment_record.rs:612— unsupported/juno/crates/juno_eval/src/eval/environment_record.rs:612-634 | unsupported/juno/crates/juno_eval/src/eval/environment_record.rs:654-683 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:118— unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:118-135 | unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:137-154 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) utils/testsuite/utils.py:79— utils/testsuite/utils.py:79-98 | utils/testsuite/utils.py:102-118 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) unsupported/hermes/crates/hermes_estree/src/de.rs:870— unsupported/hermes/crates/hermes_estree/src/de.rs:870-878 | unsupported/hermes/crates/hermes_estree/src/de.rs:890-899 | unsupported/hermes/crates/hermes_estree/src/de.rs:1048-1058 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:393— unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:393-410 | unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:455-470 | unsupported/hermes/crates/hermes_semantic_analysis/src/analyzer.rs:472-489 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:19— unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:19-30 | unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:33-50 | unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:54-65 | unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:68-84 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) unsupported/juno/crates/command_line/src/opt.rs:642— unsupported/juno/crates/command_line/src/opt.rs:642-649 | unsupported/juno/crates/command_line/src/opt.rs:697-704 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformCollatorAndroid.java:42— lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformCollatorAndroid.java:42-55 | lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformCollatorICU.java:47-61 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (53–54 lines × 2) lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:29— lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:29-81 | lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java:37-90 — before extracting anything, compare `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java` and `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `DateFormat` names `android.icu.text.DateFormat` in one and `java.text.DateFormat` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java:34` calls `RequiresApi` and `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:25` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21–22 lines × 2) lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java:400— lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java:400-421 | lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformNumberFormatterICU.java:404-424 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17–18 lines × 2) lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:188— lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:188-205 | lib/Platform/Intl/java/com/facebook/hermes/intl/NumberFormat.java:429-445 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:188` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java:364— lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java:364-381 | lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformNumberFormatterICU.java:351-368 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:101— lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:101-117 | lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java:113-129 — before extracting anything, compare `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java` and `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java:132` calls `RequiresApi` and `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:120` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:127— lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:127-142 | lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java:140-155 — before extracting anything, compare `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java` and `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:127` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java:157` calls `RequiresApi` and `lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:144` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 3) lib/Platform/Intl/java/com/facebook/hermes/intl/Collator.java:107— lib/Platform/Intl/java/com/facebook/hermes/intl/Collator.java:107-121 | lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:185-201 | lib/Platform/Intl/java/com/facebook/hermes/intl/NumberFormat.java:427-441 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/Platform/Intl/java/com/facebook/hermes/intl/Collator.java:107` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) lib/Platform/Intl/java/com/facebook/hermes/intl/IntlTextUtils.java:25— lib/Platform/Intl/java/com/facebook/hermes/intl/IntlTextUtils.java:25-35 | lib/Platform/Intl/java/com/facebook/hermes/intl/IntlTextUtils.java:45-55 | lib/Platform/Intl/java/com/facebook/hermes/intl/IntlTextUtils.java:65-75 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/Platform/Intl/java/com/facebook/hermes/intl/IntlTextUtils.java:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 3) lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:195— lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:195-205 | lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:209-219 | lib/Platform/Intl/java/com/facebook/hermes/intl/NumberFormat.java:436-445 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:195` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) lib/Platform/Intl/java/com/facebook/hermes/intl/Collator.java:141— lib/Platform/Intl/java/com/facebook/hermes/intl/Collator.java:141-146 | lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:246-251 | lib/Platform/Intl/java/com/facebook/hermes/intl/NumberFormat.java:455-460 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (8–9 lines × 2) lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:574— lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:574-581 | lib/Platform/Intl/java/com/facebook/hermes/intl/NumberFormat.java:669-677 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java:574` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27–31 lines × 2) external/llvh/utils/lit/lit/ProgressBar.py:247— external/llvh/utils/lit/lit/ProgressBar.py:247-273 | utils/testsuite/progress.py:269-299 — before extracting anything, compare `external/llvh/utils/lit/lit/ProgressBar.py` and `utils/testsuite/progress.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `utils/testsuite/progress.py:269` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24–27 lines × 2) external/llvh/utils/lit/lit/ProgressBar.py:110— external/llvh/utils/lit/lit/ProgressBar.py:110-133 | utils/testsuite/progress.py:119-145 — before extracting anything, compare `external/llvh/utils/lit/lit/ProgressBar.py` and `utils/testsuite/progress.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (24 lines × 2) agent-perf/tools/annotate_disasm.py:137— agent-perf/tools/annotate_disasm.py:137-160 | agent-perf/tools/annotate_source.py:153-176 — before extracting anything, compare `agent-perf/tools/annotate_disasm.py` and `agent-perf/tools/annotate_source.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `agent-perf/tools/annotate_disasm.py:137` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–22 lines × 2) external/llvh/utils/lit/lit/ProgressBar.py:225— external/llvh/utils/lit/lit/ProgressBar.py:225-244 | utils/testsuite/progress.py:245-266 — before extracting anything, compare `external/llvh/utils/lit/lit/ProgressBar.py` and `utils/testsuite/progress.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) external/llvh/utils/lit/lit/ProgressBar.py:183— external/llvh/utils/lit/lit/ProgressBar.py:183-202 | utils/testsuite/progress.py:201-220 — before extracting anything, compare `external/llvh/utils/lit/lit/ProgressBar.py` and `utils/testsuite/progress.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 5) agent-perf/tools/annotate_disasm.py:145— agent-perf/tools/annotate_disasm.py:145-161 | agent-perf/tools/annotate_source.py:161-177 | agent-perf/tools/pmu_anomalies.py:211-227 | agent-perf/tools/profile_to_json.py:141-157 | agent-perf/tools/regalloc_report.py:257-273 — before extracting anything, compare `agent-perf/tools/annotate_disasm.py` and `agent-perf/tools/annotate_source.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `agent-perf/tools/annotate_disasm.py:145` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–16 lines × 2) agent-perf/tools/antipattern_scan.py:219— agent-perf/tools/antipattern_scan.py:219-234 | agent-perf/tools/js_antipattern_scan.py:282-294 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 5) agent-perf/tools/annotate_disasm.py:151— agent-perf/tools/annotate_disasm.py:151-164 | agent-perf/tools/annotate_source.py:167-180 | agent-perf/tools/profile_to_json.py:147-160 | agent-perf/tools/regalloc_report.py:263-276 | agent-perf/tools/runtime_call_profiler.py:282-295 — before extracting anything, compare `agent-perf/tools/annotate_disasm.py` and `agent-perf/tools/annotate_source.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `agent-perf/tools/annotate_disasm.py:151` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–13 lines × 2) utils/bench_with_stats.py:366— utils/bench_with_stats.py:366-378 | utils/bench_with_stats.py:400-410 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5–6 lines × 3) agent-perf/tools/regalloc_report.py:219— agent-perf/tools/regalloc_report.py:219-224 | agent-perf/tools/regalloc_report.py:235-240 | agent-perf/tools/type_coverage_analyzer.py:248-252 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `agent-perf/tools/regalloc_report.py:219` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (38–40 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:2236— unsupported/juno/crates/juno/src/gen_js.rs:2236-2275 | unsupported/juno/crates/juno/src/gen_js.rs:3413-3450 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:2236` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (39 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:2853— unsupported/juno/crates/juno/src/gen_js.rs:2853-2891 | unsupported/juno/crates/juno/src/gen_js.rs:2913-2951 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:2853` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (38 lines × 2) unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:264— unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:264-301 | unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:420-457 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:264` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (35 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:3310— unsupported/juno/crates/juno/src/gen_js.rs:3310-3344 | unsupported/juno/crates/juno_support/src/json.rs:224-258 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:3310` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (29–30 lines × 2) unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:605— unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:605-634 | unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:640-668 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/hermes/crates/hermes_estree_codegen/src/codegen.rs:605` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–22 lines × 3) unsupported/juno/crates/juno/src/gen_js.rs:2857— unsupported/juno/crates/juno/src/gen_js.rs:2857-2878 | unsupported/juno/crates/juno/src/gen_js.rs:2917-2938 | unsupported/juno/crates/juno/src/gen_js.rs:2960-2978 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:2857` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16–21 lines × 2) unsupported/juno/crates/hermes/src/utf.rs:140— unsupported/juno/crates/hermes/src/utf.rs:140-155 | unsupported/juno/crates/hermes/src/utf.rs:166-186 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/hermes/src/utf.rs:140` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 3) unsupported/juno/crates/juno/src/gen_js.rs:2649— unsupported/juno/crates/juno/src/gen_js.rs:2649-2668 | unsupported/juno/crates/juno/src/gen_js.rs:2866-2885 | unsupported/juno/crates/juno/src/gen_js.rs:2926-2945 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:2649` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:1604— unsupported/juno/crates/juno/src/gen_js.rs:1604-1616 | unsupported/juno/crates/juno/src/gen_js.rs:2600-2611 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:1604` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) unsupported/juno/crates/juno/src/gen_js.rs:1308— unsupported/juno/crates/juno/src/gen_js.rs:1308-1319 | unsupported/juno/crates/juno/src/gen_js.rs:1662-1673 | unsupported/juno/crates/juno/src/gen_js.rs:1704-1715 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `unsupported/juno/crates/juno/src/gen_js.rs:1703` calls `visit`, `Some` and `unsupported/juno/crates/juno/src/gen_js.rs:1661` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 4) unsupported/juno/crates/juno/src/gen_js.rs:2649— unsupported/juno/crates/juno/src/gen_js.rs:2649-2661 | unsupported/juno/crates/juno/src/gen_js.rs:2866-2878 | unsupported/juno/crates/juno/src/gen_js.rs:2926-2938 | unsupported/juno/crates/juno/src/gen_js.rs:2969-2978 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:2649` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–10 lines × 2) unsupported/juno/crates/juno_ast/src/context.rs:451— unsupported/juno/crates/juno_ast/src/context.rs:451-460 | unsupported/juno/crates/juno_ast/src/context.rs:466-474 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (4–6 lines × 3) unsupported/hermes/crates/hermes_estree/src/de.rs:680— unsupported/hermes/crates/hermes_estree/src/de.rs:680-685 | unsupported/hermes/crates/hermes_estree/src/de.rs:699-704 | unsupported/hermes/crates/hermes_estree/src/de.rs:746-749 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/hermes/crates/hermes_estree/src/de.rs:680` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `unsupported/hermes/crates/hermes_estree/src/de.rs:678` calls `U64`, `visit_u64`, `I8` and `unsupported/hermes/crates/hermes_estree/src/de.rs:746` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) unsupported/juno/crates/juno/src/gen_js.rs:2347— unsupported/juno/crates/juno/src/gen_js.rs:2347-2358 | unsupported/juno/crates/juno/src/gen_js.rs:2362-2373 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:2347` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 7) unsupported/juno/crates/juno/src/gen_js.rs:1604— unsupported/juno/crates/juno/src/gen_js.rs:1604-1609 | unsupported/juno/crates/juno/src/gen_js.rs:1831-1839 | unsupported/juno/crates/juno/src/gen_js.rs:2415-2420 | unsupported/juno/crates/juno/src/gen_js.rs:2582-2587 | unsupported/juno/crates/juno/src/gen_js.rs:2591-2596 | unsupported/juno/crates/juno/src/gen_js.rs:2600-2605 | unsupported/juno/crates/juno/src/gen_js.rs:3470-3475 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/juno/crates/juno/src/gen_js.rs:1604` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `unsupported/juno/crates/juno/src/gen_js.rs:3467` calls `visit`, `Some`, `space` and `unsupported/juno/crates/juno/src/gen_js.rs:1830` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) unsupported/hermes/crates/hermes_estree/src/de.rs:871— unsupported/hermes/crates/hermes_estree/src/de.rs:871-875 | unsupported/hermes/crates/hermes_estree/src/de.rs:891-895 | unsupported/hermes/crates/hermes_estree/src/de.rs:1049-1053 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `unsupported/hermes/crates/hermes_estree/src/de.rs:871` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `unsupported/hermes/crates/hermes_estree/src/de.rs:896` calls `Seq`, `visit_content_seq` and `unsupported/hermes/crates/hermes_estree/src/de.rs:876` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in API/hermes/cdp/tools/hermes-inspector-msggen/ ran and not one test passed (No tests found, exiting with code 1), so the coverage would describe the failed run, not the code. 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.
Duplicated block (174 lines × 2 locations) external/asmjit/asmjit/db/aarch32.js:601— external/asmjit/asmjit/db/aarch32.js:601 · external/asmjit/asmjit/db/aarch64.js:605 — 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 (116 matched lines × 2 locations) · ×1
Duplicated block with local edits (116 matched lines × 2 locations) API/hermes/cdp/tools/hermes-inspector-msggen/src/HeaderWriter.js:20— API/hermes/cdp/tools/hermes-inspector-msggen/src/HeaderWriter.js:20 · API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js:18 — the two spans are one implementation copied and then locally edited — 652 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 (64 matched lines × 2 locations) · ×1
Duplicated block with local edits (64 matched lines × 2 locations) lib/InternalJavaScript/08-IteratorPrototypeDrop.js:32— lib/InternalJavaScript/08-IteratorPrototypeDrop.js:32 · lib/InternalJavaScript/17-IteratorPrototypeTake.js:32 — the two spans are one implementation copied and then locally edited — 332 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 (60 lines × 2 locations) external/asmjit/asmjit/db/aarch32.js:433— external/asmjit/asmjit/db/aarch32.js:433 · external/asmjit/asmjit/db/aarch64.js:436 — 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 (54 lines × 2 locations) external/asmjit/asmjit/db/aarch32.js:893— external/asmjit/asmjit/db/aarch32.js:893 · external/asmjit/asmjit/db/aarch64.js:854 — 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 (50 lines × 2 locations) external/asmjit/asmjit/db/aarch32.js:349— external/asmjit/asmjit/db/aarch32.js:349 · external/asmjit/asmjit/db/aarch64.js:350 — 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 (49 lines × 2 locations) external/asmjit/asmjit/db/aarch32.js:542— external/asmjit/asmjit/db/aarch32.js:542 · external/asmjit/asmjit/db/aarch64.js:541 — 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 (46 matched lines × 2 locations) · ×1
Duplicated block with local edits (46 matched lines × 2 locations) lib/InternalJavaScript/10-IteratorPrototypeFilter.js:32— lib/InternalJavaScript/10-IteratorPrototypeFilter.js:32 · lib/InternalJavaScript/14-IteratorPrototypeMap.js:32 — the two spans are one implementation copied and then locally edited — 268 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 (35 lines × 2 locations) lib/InternalJavaScript/01-Promise.js:160— lib/InternalJavaScript/01-Promise.js:160 · lib/InternalJavaScript/01-Promise.js:301 — 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 (32 lines × 3 locations) external/asmjit/asmjit/db/aarch32.js:902— external/asmjit/asmjit/db/aarch32.js:902 · external/asmjit/asmjit/db/aarch64.js:863 · external/asmjit/asmjit/db/x86.js:911 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (30 lines × 2 locations) tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:150— tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:150 · tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:233 — 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 (24 lines × 2 locations) API/hermes/cdp/tools/hermes-inspector-msggen/src/Command.js:19— API/hermes/cdp/tools/hermes-inspector-msggen/src/Command.js:19 · API/hermes/cdp/tools/hermes-inspector-msggen/src/Event.js:18 — 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 (21 lines × 4 locations) lib/InternalJavaScript/09-IteratorPrototypeEvery.js:32— lib/InternalJavaScript/09-IteratorPrototypeEvery.js:32 · lib/InternalJavaScript/11-IteratorPrototypeFind.js:32 · lib/InternalJavaScript/13-IteratorPrototypeForEach.js:32 · lib/InternalJavaScript/16-IteratorPrototypeSome.js:32 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (20 lines × 2 locations) external/asmjit/asmjit/db/aarch32.js:259— external/asmjit/asmjit/db/aarch32.js:259 · external/asmjit/asmjit/db/aarch64.js:303 — 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 (17 matched lines × 2 locations) · ×1
Duplicated block with local edits (17 matched lines × 2 locations) lib/InternalJavaScript/04-AsyncIterator.js:38— lib/InternalJavaScript/04-AsyncIterator.js:38 · lib/InternalJavaScript/04-AsyncIterator.js:325 — the two spans are one implementation copied and then locally edited — 86 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (17 lines × 8 locations) lib/InternalJavaScript/09-IteratorPrototypeEvery.js:32— lib/InternalJavaScript/09-IteratorPrototypeEvery.js:32 · lib/InternalJavaScript/10-IteratorPrototypeFilter.js:32 · lib/InternalJavaScript/11-IteratorPrototypeFind.js:32 · lib/InternalJavaScript/12-IteratorPrototypeFlatMap.js:32 · +4 more site(s) not listed — the 8 copies are spread across 8 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 (16 lines × 2 locations) external/asmjit/asmjit/db/aarch32.js:112— external/asmjit/asmjit/db/aarch32.js:112 · external/asmjit/asmjit/db/aarch64.js:188 — 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 (15 lines × 4 locations) lib/TypedLib/02-string.js:45— lib/TypedLib/02-string.js:45 · lib/TypedLib/02-string.js:75 · lib/TypedLib/02-string.js:105 · lib/TypedLib/02-string.js:168 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Boundary violation [package:relative-cross-package] external/asmjit/asmjit/tools/tablegen.js:23— external/asmjit/asmjit/tools/tablegen.js:23 reaches into another package with a relative path (../db) — import the package by name instead.
Complex function (top-level) (cyclomatic 343, cognitive 342) test/BCGen/HBC/many_tries.js:15— (top-level) has cyclomatic complexity 343 and cognitive complexity 342; 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 transformNode (cyclomatic 84, cognitive 64) tools/hermes-parser/js/hermes-parser/src/babel/TransformESTreeToBabel.js:926— transformNode has cyclomatic complexity 84 and cognitive complexity 64; 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 makeSignatures (cyclomatic 74, cognitive 212) external/asmjit/asmjit/tools/tablegen-x86.js:1574— makeSignatures has cyclomatic complexity 74 and cognitive complexity 212; 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 _assignOpcode (cyclomatic 54, cognitive 140) external/asmjit/asmjit/db/x86.js:573— _assignOpcode has cyclomatic complexity 54 and cognitive complexity 140; 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 sumPrecise (cyclomatic 52, cognitive 104) lib/InternalJavaScript/20-MathPrototypeSumPrecise.js:44— sumPrecise has cyclomatic complexity 52 and cognitive complexity 104; 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 47, cognitive 45) lib/InternalJavaScript/05-IteratorHelperDependencies.js:311— (anonymous) has cyclomatic complexity 47 and cognitive complexity 45; 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 transform (cyclomatic 43, cognitive 26) tools/hermes-parser/js/hermes-parser/src/estree/StripFlowTypes.js:33— transform has cyclomatic complexity 43 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 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 flagsOf (cyclomatic 42, cognitive 87) external/asmjit/asmjit/tools/tablegen-x86.js:204— flagsOf has cyclomatic complexity 42 and cognitive complexity 87; 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 newInstFromGroup (cyclomatic 38, cognitive 74) external/asmjit/asmjit/tools/tablegen-x86.js:590— newInstFromGroup has cyclomatic complexity 38 and cognitive complexity 74; 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 _assignOperands (cyclomatic 37, cognitive 107) external/asmjit/asmjit/db/aarch64.js:413— _assignOperands has cyclomatic complexity 37 and cognitive complexity 107; 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 queryRwGeneric (cyclomatic 36, cognitive 68) external/asmjit/asmjit/tools/tablegen-x86.js:2144— queryRwGeneric has cyclomatic complexity 36 and cognitive complexity 68; 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 ValidateAndApplyPropertyDescriptor (cyclomatic 36, cognitive 67) lib/InternalJavaScript/05-IteratorHelperDependencies.js:954— ValidateAndApplyPropertyDescriptor has cyclomatic complexity 36 and cognitive complexity 67; 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 _assignOpcode (cyclomatic 35, cognitive 77) external/asmjit/asmjit/db/aarch32.js:641— _assignOpcode has cyclomatic complexity 35 and cognitive complexity 77; 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 _assignOpcode (cyclomatic 34, cognitive 76) external/asmjit/asmjit/db/aarch64.js:648— _assignOpcode has cyclomatic complexity 34 and cognitive complexity 76; 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 prettyPrintRec (cyclomatic 34, cognitive 46) tools/hermes/evaluate-line.js:103— prettyPrintRec has cyclomatic complexity 34 and cognitive complexity 46; 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 _assignOperands (cyclomatic 33, cognitive 100) external/asmjit/asmjit/db/aarch32.js:417— _assignOperands has cyclomatic complexity 33 and cognitive complexity 100; 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 constructor (cyclomatic 33, cognitive 59) external/asmjit/asmjit/db/x86.js:213— constructor has cyclomatic complexity 33 and cognitive complexity 59; 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 defineDataProperty (cyclomatic 33, cognitive 35) lib/InternalJavaScript/05-IteratorHelperDependencies.js:191— defineDataProperty has cyclomatic complexity 33 and cognitive complexity 35; 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 attach (cyclomatic 30, cognitive 53) tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/main/comments.js:161— attach has cyclomatic complexity 30 and cognitive complexity 53; 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 (top-level) (cyclomatic 30, cognitive 28) tools/hermes-parser/js/scripts/expand-minified.js:14— (top-level) has cyclomatic complexity 30 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 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 throws (cyclomatic 29, cognitive 61) external/node-api-tests/hermes/assert.js:137— throws has cyclomatic complexity 29 and cognitive complexity 61; 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 GetIntrinsic (cyclomatic 29, cognitive 41) lib/InternalJavaScript/05-IteratorHelperDependencies.js:530— GetIntrinsic has cyclomatic complexity 29 and cognitive complexity 41; 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 browserResize (cyclomatic 29, cognitive 28) test/IRGen/estree_parse.js:27— browserResize has cyclomatic complexity 29 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 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 evaluate (cyclomatic 29, cognitive 19) external/asmjit/asmjit/db/exp.js:202— evaluate has cyclomatic complexity 29 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 parseExpression (cyclomatic 28, cognitive 87) external/asmjit/asmjit/db/exp.js:455— parseExpression has cyclomatic complexity 28 and cognitive complexity 87; 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 calcImplicitMemSize (cyclomatic 26, cognitive 69) external/asmjit/asmjit/tools/tablegen-x86.js:1275— calcImplicitMemSize has cyclomatic complexity 26 and cognitive complexity 69; 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 rwFlagsOf (cyclomatic 24, cognitive 13) external/asmjit/asmjit/tools/tablegen-x86.js:1832— rwFlagsOf has cyclomatic complexity 24 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 tokenize (cyclomatic 23, cognitive 43) external/asmjit/asmjit/db/exp.js:354— tokenize has cyclomatic complexity 23 and cognitive complexity 43; 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 deepStrictEqual (cyclomatic 22, cognitive 33) external/node-api-tests/hermes/assert.js:44— deepStrictEqual has cyclomatic complexity 22 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 handleClassComments (cyclomatic 21, cognitive 27) tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:381— handleClassComments has cyclomatic complexity 21 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 (top-level) (cyclomatic 21, cognitive 20) test/Parser/flow/conditional-type.js:14— (top-level) has cyclomatic complexity 21 and cognitive complexity 20; 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.
R2 · Cyclomatic Complexity· Complex function index (cyclomatic 20, cognitive 39) · ×1
Complex function index (cyclomatic 20, cognitive 39) external/asmjit/asmjit/tools/tablegen.js:81— index has cyclomatic complexity 20 and cognitive complexity 39; 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 attributeMode (cyclomatic 20, cognitive 20) test/IRGen/estree_parse.js:496— attributeMode has cyclomatic complexity 20 and cognitive complexity 20; 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 analyzePattern (cyclomatic 20, cognitive 16) tools/hermes-parser/js/hermes-parser/src/estree/TransformMatchSyntax.js:287— analyzePattern has cyclomatic complexity 20 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 (anonymous) (cyclomatic 20, cognitive 11) tools/hermes-parser/js/hermes-transform/__tests__/test_codemods/thisInExportedFunction-test.js:55— (anonymous) has cyclomatic complexity 20 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 19, cognitive 40) external/asmjit/asmjit/tools/tablegen-x86.js:1990— (anonymous) has cyclomatic complexity 19 and cognitive complexity 40; 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 (top-level) (cyclomatic 19, cognitive 18) external/flowtest/test/flow/types/conditional_types/passing.js:1— (top-level) has cyclomatic complexity 19 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 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 rmReplaceableCategory (cyclomatic 18, cognitive 31) external/asmjit/asmjit/tools/tablegen-x86.js:2347— rmReplaceableCategory has cyclomatic complexity 18 and cognitive complexity 31; 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 formatEmit (cyclomatic 18, cognitive 30) external/asmjit/asmjit/tools/tablegen-x86.js:612— formatEmit has cyclomatic complexity 18 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 CallExpression (cyclomatic 18, cognitive 16) tools/hermes-parser/js/hermes-transform/__tests__/test_codemods/bindThisToArrow-test.js:15— CallExpression has cyclomatic complexity 18 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.
R3 · Large Files· external/asmjit/asmjit/tools/tablegen-x86.js · ×1
external/asmjit/asmjit/tools/tablegen-x86.js: 2200 lines of code external/asmjit/asmjit/tools/tablegen-x86.js:1— external/asmjit/asmjit/tools/tablegen-x86.js has 2200 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· lib/InternalJavaScript/05-IteratorHelperDependencies.js · ×1
lib/InternalJavaScript/05-IteratorHelperDependencies.js: 1935 lines of code lib/InternalJavaScript/05-IteratorHelperDependencies.js:1— lib/InternalJavaScript/05-IteratorHelperDependencies.js has 1935 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· tools/hermes-parser/js/hermes-estree/src/types.js · ×1
tools/hermes-parser/js/hermes-estree/src/types.js: 1920 lines of code tools/hermes-parser/js/hermes-estree/src/types.js:1— tools/hermes-parser/js/hermes-estree/src/types.js has 1920 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· tools/hermes-parser/js/hermes-parser/src/babel/TransformESTreeToBabel.js · ×1
tools/hermes-parser/js/hermes-parser/src/babel/TransformESTreeToBabel.js: 1260 lines of code tools/hermes-parser/js/hermes-parser/src/babel/TransformESTreeToBabel.js:1— tools/hermes-parser/js/hermes-parser/src/babel/TransformESTreeToBabel.js has 1260 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· lib/InternalJavaScript/01-Promise.js · ×1
lib/InternalJavaScript/01-Promise.js: 1053 lines of code lib/InternalJavaScript/01-Promise.js:1— lib/InternalJavaScript/01-Promise.js has 1053 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· tools/hermes-parser/js/hermes-parser/src/estree/TransformMatchSyntax.js · ×1
tools/hermes-parser/js/hermes-parser/src/estree/TransformMatchSyntax.js: 950 lines of code tools/hermes-parser/js/hermes-parser/src/estree/TransformMatchSyntax.js:1— tools/hermes-parser/js/hermes-parser/src/estree/TransformMatchSyntax.js has 950 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· tools/hermes-parser/js/hermes-eslint/src/scope-manager/referencer/Referencer.js · ×1
tools/hermes-parser/js/hermes-eslint/src/scope-manager/referencer/Referencer.js: 904 lines of code tools/hermes-parser/js/hermes-eslint/src/scope-manager/referencer/Referencer.js:1— tools/hermes-parser/js/hermes-eslint/src/scope-manager/referencer/Referencer.js has 904 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· tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js · ×1
tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js: 903 lines of code tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js:1— tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/language-js/comments.js has 903 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· external/asmjit/asmjit/db/x86.js · ×1
external/asmjit/asmjit/db/x86.js: 830 lines of code external/asmjit/asmjit/db/x86.js:1— external/asmjit/asmjit/db/x86.js has 830 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· external/asmjit/asmjit/db/aarch32.js · ×1
external/asmjit/asmjit/db/aarch32.js: 816 lines of code external/asmjit/asmjit/db/aarch32.js:1— external/asmjit/asmjit/db/aarch32.js has 816 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· tools/hermes-parser/js/flow-typed/prettier.js · ×1
tools/hermes-parser/js/flow-typed/prettier.js: 813 lines of code tools/hermes-parser/js/flow-typed/prettier.js:1— tools/hermes-parser/js/flow-typed/prettier.js has 813 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· tools/hermes-parser/js/hermes-parser/src/estree/TransformComponentSyntax.js · ×1
tools/hermes-parser/js/hermes-parser/src/estree/TransformComponentSyntax.js: 810 lines of code tools/hermes-parser/js/hermes-parser/src/estree/TransformComponentSyntax.js:1— tools/hermes-parser/js/hermes-parser/src/estree/TransformComponentSyntax.js has 810 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· external/asmjit/asmjit/db/aarch64.js · ×1
external/asmjit/asmjit/db/aarch64.js: 768 lines of code external/asmjit/asmjit/db/aarch64.js:1— external/asmjit/asmjit/db/aarch64.js has 768 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· tools/hermes-parser/js/flow-typed/jest.js · ×1
tools/hermes-parser/js/flow-typed/jest.js: 751 lines of code tools/hermes-parser/js/flow-typed/jest.js:1— tools/hermes-parser/js/flow-typed/jest.js has 751 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· external/asmjit/asmjit/db/exp.js · ×1
external/asmjit/asmjit/db/exp.js: 634 lines of code external/asmjit/asmjit/db/exp.js:1— external/asmjit/asmjit/db/exp.js has 634 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
lib/TypedLib/01-array.js: 559 lines of code lib/TypedLib/01-array.js:1— lib/TypedLib/01-array.js has 559 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· external/asmjit/asmjit/db/base.js · ×1
external/asmjit/asmjit/db/base.js: 527 lines of code external/asmjit/asmjit/db/base.js:1— external/asmjit/asmjit/db/base.js has 527 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· tools/hermes-parser/js/hermes-transform/src/transform/TransformContext.js · ×1
tools/hermes-parser/js/hermes-transform/src/transform/TransformContext.js: 521 lines of code tools/hermes-parser/js/hermes-transform/src/transform/TransformContext.js:1— tools/hermes-parser/js/hermes-transform/src/transform/TransformContext.js has 521 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· external/asmjit/asmjit/tools/generator-commons.js · ×1
external/asmjit/asmjit/tools/generator-commons.js: 470 lines of code external/asmjit/asmjit/tools/generator-commons.js:1— external/asmjit/asmjit/tools/generator-commons.js has 470 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· lib/InternalJavaScript/04-AsyncIterator.js · ×1
lib/InternalJavaScript/04-AsyncIterator.js: 461 lines of code lib/InternalJavaScript/04-AsyncIterator.js:1— lib/InternalJavaScript/04-AsyncIterator.js has 461 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· API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js · ×1
API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js: 459 lines of code API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js:1— API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.js has 459 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· external/asmjit/asmjit/tools/tablegen.js · ×1
external/asmjit/asmjit/tools/tablegen.js: 452 lines of code external/asmjit/asmjit/tools/tablegen.js:1— external/asmjit/asmjit/tools/tablegen.js has 452 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· tools/hermes-parser/js/hermes-eslint/src/scope-manager/scope/ScopeBase.js · ×1
tools/hermes-parser/js/hermes-eslint/src/scope-manager/scope/ScopeBase.js: 436 lines of code tools/hermes-parser/js/hermes-eslint/src/scope-manager/scope/ScopeBase.js:1— tools/hermes-parser/js/hermes-eslint/src/scope-manager/scope/ScopeBase.js has 436 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· The declared test suite includes a file that cannot be loaded · ×1
The declared test suite includes a file that cannot be loaded external/node-api-tests/js-native-api/2_function_arguments/test.js:2— This repository declares test tooling, and the ✓ above records that declaration — but external/node-api-tests/js-native-api/2_function_arguments/test.js and 64 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
Dead file (~2194 LoC) lib/InternalJavaScript/05-IteratorHelperDependencies.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~881 LoC) tools/hermes-parser/js/flow-typed/prettier.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~775 LoC) tools/hermes-parser/js/flow-typed/jest.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~593 LoC) lib/TypedLib/01-array.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~482 LoC) lib/InternalJavaScript/04-AsyncIterator.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~310 LoC) tools/hermes/evaluate-line.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~236 LoC) lib/InternalJavaScript/20-MathPrototypeSumPrecise.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~230 LoC) lib/TypedLib/02-string.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~198 LoC) utils/es5objects.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~177 LoC) lib/InternalJavaScript/02-AsyncFn.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~153 LoC) tools/hermes-parser/js/flow-typed/node.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~141 LoC) lib/InternalJavaScript/12-IteratorPrototypeFlatMap.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~125 LoC) REDACTED— no import path from any entry point (137 application, 14 tooling, 5389 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools/emhermesc/test.js) — 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 (~120 LoC) lib/InternalJavaScript/08-IteratorPrototypeDrop.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~117 LoC) lib/InternalJavaScript/21-IteratorConcat.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~116 LoC) lib/InternalJavaScript/17-IteratorPrototypeTake.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~103 LoC) lib/InternalJavaScript/10-IteratorPrototypeFilter.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~87 LoC) lib/InternalJavaScript/11-IteratorPrototypeFind.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~83 LoC) tools/hermes-parser/js/flow-typed/espree.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~81 LoC) unsupported/juno/lit/juno/reduce_conditional.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~79 LoC) lib/InternalJavaScript/13-IteratorPrototypeForEach.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~78 LoC) tools/dependency-extractor/DependencyExtractor.js— no import path from any entry point (137 application, 14 tooling, 5389 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools/dependency-extractor/test.js) — 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 (~77 LoC) tools/hermes-parser/js/flow-typed/babel-code-frame.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~63 LoC) lib/InternalJavaScript/07-IteratorHelperPrototype.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~60 LoC) unsupported/juno/lit/flow_native/mod.js— no import path from any entry point (137 application, 14 tooling, 5389 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 (~57 LoC) tools/hvm-bench/allocArray.js— no import path from any entry point (137 application, 14 tooling, 5389 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 'node-api-headers' — Declared in external/node-api-cts/package.json 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 'request' — Declared in npm/package.json 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 'flow-bin' — Declared in 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.
Orphaned file unsupported/hermes/crates/hermes_semantic_analysis/src/scope_manager.rs: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 benchmarks/MiniReact/original/MiniReact.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 lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformNumberFormatterICU.java: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 agent-perf/benchmarks/macro/app_startup.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 benchmarks/bench-runner/categories.py: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 benchmarks/bench-runner/resource/test-suites/v8-v6-perf/v8-richards.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 API/hermes/cdp/tools/hermes-inspector-msggen/src/ImplementationWriter.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 agent-perf/tools/generated_code_analyzer.py: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 agent-perf/tools/generated_code_antipatterns.py: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 tools/hermes-parser/js/hermes-eslint/src/scope-manager/scope/ScopeBase.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 agent-perf/tools/js_antipattern_scan.py: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 tools/hermes-parser/js/hermes-transform/src/transform/comments/prettier/main/comments.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 benchmarks/bench-runner/resource/test-suites/octane/navier-stokes.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 tools/hermes-parser/js/hermes-eslint/src/scope-manager/referencer/TypeVisitor.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 lib/Platform/Intl/java/com/facebook/hermes/intl/Collator.java: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 tools/hermes-parser/js/hermes-transform/src/traverse/NodeEventGenerator.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 benchmarks/build-helpers/flow-bundler/src/transforms/transformJSX.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 agent-perf/tools/antipattern_scan.py: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 lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleObjectAndroid.java: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 benchmarks/bench-runner/resource/test-suites/v8-v6-perf/v8-splay.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 benchmarks/build-helpers/flow-bundler/src/TransformModule.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 tools/hermes-parser/js/hermes-transform/src/transform/comments/comments.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 benchmarks/build-helpers/flow-bundler/src/ModuleGraph.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 lib/Platform/Intl/java/com/facebook/hermes/intl/IPlatformDateTimeFormatter.java: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 agent-perf/tools/type_coverage_analyzer.py: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.
redundant comment benchmarks/bench-runner/resource/test-suites/octane/gbemu.js:1400— "Did we boot to the GBC boot ROM?" repeats the code it sits on: 3 of its 3 words (boot, gbc, rom) are already in `this.usedGBCBootROM = false;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/bench-runner/resource/test-suites/octane/gbemu.js:1546— "Actual scan line..." repeats the code it sits on: 3 of its 3 words (actual, scan, line) are already in `this.actualScanLine = 0;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/bench-runner/resource/test-suites/octane/gbemu.js:1550— "Post-Halt clocking." repeats the code it sits on: 3 of its 3 words (post, halt, clocking) are already in `this.haltPostClocks = 0;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/bench-runner/resource/test-suites/octane/pdfjs.js:3843— "Recursively get other XRefs 'XRefStm', if any" repeats the code it sits on: 4 of its 5 words (get, refs, ref, stm) are already in `obj = dict.get('XRefStm');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/bench-runner/resource/test-suites/octane/pdfjs.js:13607— "switch" only labels the closing brace of the switch. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/bench-runner/resource/test-suites/octane/pdfjs.js:15236— "usLastCharIndex" repeats the code it sits on: 3 of its 3 words (last, char, index) are already in `string16(lastCharIndex || properties.lastChar) +`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/build-helpers/flow-bundler/src/ModuleGraph.js:340— "Resolve export names" repeats the code it sits on: 3 of its 3 words (resolve, export, names) are already in `resolveExportNames(moduleGraphNode, moduleInfo);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/build-helpers/flow-bundler/src/ModuleGraph.js:357— "Pop module from stack" repeats the code it sits on: 3 of its 3 words (pop, module, stack) are already in `moduleStack.pop();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/box2d.js:189— "Computes the geometric mean of a set of numbers." repeats the code it sits on: 4 of its 5 words (geometric, mean, set, numbers) are already in `BenchmarkSuite.GeometricMean = function(numbers)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:189— "Computes the geometric mean of a set of numbers." repeats the code it sits on: 4 of its 5 words (geometric, mean, set, numbers) are already in `BenchmarkSuite.GeometricMean = function(numbers)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/deltablue.js:189— "Computes the geometric mean of a set of numbers." repeats the code it sits on: 4 of its 5 words (geometric, mean, set, numbers) are already in `BenchmarkSuite.GeometricMean = function(numbers)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/earley-boyer.js:189— "Computes the geometric mean of a set of numbers." repeats the code it sits on: 4 of its 5 words (geometric, mean, set, numbers) are already in `BenchmarkSuite.GeometricMean = function(numbers)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/gbemu.js:189— "Computes the geometric mean of a set of numbers." repeats the code it sits on: 4 of its 5 words (geometric, mean, set, numbers) are already in `BenchmarkSuite.GeometricMean = function(numbers)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/gbemu.js:1803— "Did we boot to the GBC boot ROM?" repeats the code it sits on: 3 of its 3 words (boot, gbc, rom) are already in `this.usedGBCBootROM = false;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/gbemu.js:1949— "Actual scan line..." repeats the code it sits on: 3 of its 3 words (actual, scan, line) are already in `this.actualScanLine = 0;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/gbemu.js:1953— "Post-Halt clocking." repeats the code it sits on: 3 of its 3 words (post, halt, clocking) are already in `this.haltPostClocks = 0;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/mandreel.js:189— "Computes the geometric mean of a set of numbers." repeats the code it sits on: 4 of its 5 words (geometric, mean, set, numbers) are already in `BenchmarkSuite.GeometricMean = function(numbers)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/mandreel.js:2141— "Call mandreel app init funtion (__init())" repeats the code it sits on: 4 of its 5 words (call, mandreel, app, init) are already in `mandreelAppInit();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/mandreel.js:3135— "element.requestFullScreen" repeats the code it sits on: 4 of its 4 words (element, request, full, screen) are already in `if(!elementPrototype.requestFullScreen)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/mandreel_latency.js:189— "Computes the geometric mean of a set of numbers." repeats the code it sits on: 4 of its 5 words (geometric, mean, set, numbers) are already in `BenchmarkSuite.GeometricMean = function(numbers)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/mandreel_latency.js:2148— "Call mandreel app init funtion (__init())" repeats the code it sits on: 4 of its 5 words (call, mandreel, app, init) are already in `mandreelAppInit();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/mandreel_latency.js:3142— "element.requestFullScreen" repeats the code it sits on: 4 of its 4 words (element, request, full, screen) are already in `if(!elementPrototype.requestFullScreen)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/navier-stokes.js:189— "Computes the geometric mean of a set of numbers." repeats the code it sits on: 4 of its 5 words (geometric, mean, set, numbers) are already in `BenchmarkSuite.GeometricMean = function(numbers)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/pdfjs.js:189— "Computes the geometric mean of a set of numbers." repeats the code it sits on: 4 of its 5 words (geometric, mean, set, numbers) are already in `BenchmarkSuite.GeometricMean = function(numbers)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment benchmarks/octane/pdfjs.js:4238— "Recursively get other XRefs 'XRefStm', if any" repeats the code it sits on: 4 of its 5 words (get, refs, ref, stm) are already in `obj = dict.get('XRefStm');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Duplicated predicate lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:203— `!JSObjects.isUndefined(timeZone) && !JSObjects.isNull(timeZone)` appears character-identically in 2 files — lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java, lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java:113— `(c >= 'A' && c <= 'Z') || (c >= 'a' && c <= 'z')` appears character-identically in 2 files — lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterAndroid.java, lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformDateTimeFormatterICU.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/Platform/Intl/java/com/facebook/hermes/intl/Collator.java:252— `Build.VERSION.SDK_INT >= Build.VERSION_CODES.N && matcher.equals("best fit")` appears character-identically in 3 files — lib/Platform/Intl/java/com/facebook/hermes/intl/Collator.java, lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java, lib/Platform/Intl/java/com/facebook/hermes/intl/NumberFormat.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/InternalJavaScript/01-Promise.js:58— `!!x && (typeof x === 'function' || typeof x === 'object')` appears character-identically in 2 files — lib/InternalJavaScript/01-Promise.js, lib/InternalJavaScript/05-IteratorHelperDependencies.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate external/asmjit/asmjit/db/aarch32.js:586— `!op.hasMemModes() && (op.offset || op.index)` appears character-identically in 2 files — external/asmjit/asmjit/db/aarch32.js, external/asmjit/asmjit/db/aarch64.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate API/hermes/cdp/tools/hermes-inspector-msggen/src/Command.js:28— `ignoreExperimental && obj.experimental && !includeExperimental.has(domain + '.' + obj.name)` appears character-identically in 2 files — API/hermes/cdp/tools/hermes-inspector-msggen/src/Command.js, API/hermes/cdp/tools/hermes-inspector-msggen/src/Event.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate external/asmjit/asmjit/db/aarch32.js:277— `this.restrict && this.restrict.startsWith("*")` appears character-identically in 2 files — external/asmjit/asmjit/db/aarch32.js, external/asmjit/asmjit/db/aarch64.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lldb/HermesValueFormatter.py:172— `evaluation_result.GetError() and evaluation_result.GetError().Fail()` appears character-identically in 2 files — lldb/HermesValueFormatter.py, lldb/Stack.py. 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 external/llvh/utils/lit/lit/ProgressBar.py:226— `self.term.CLEAR_EOL and self.term.UP and self.term.BOL` appears character-identically in 2 files — external/llvh/utils/lit/lit/ProgressBar.py, utils/testsuite/progress.py. 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.
Silent fallback default in catch REDACTED:170— `sortIndex` (in `sort_by_incremental_cache`) swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch benchmarks/bench-runner/resource/test-suites/octane/gbemu.js:1313— `Resize.generateFloatBuffer` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch benchmarks/bench-runner/resource/test-suites/octane/gbemu.js:1322— `Resize.generateUint8Buffer` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch benchmarks/octane/gbemu.js:1714— `Resize.generateFloatBuffer` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch benchmarks/octane/gbemu.js:1723— `Resize.generateUint8Buffer` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch test/Sema/flow/implicit-return-error.js:30— `f4` swallows every exception into `return 1` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch test/jit/x86-64/fastarrays.js:107— `catchLd` swallows every exception into `return "oob"` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch tools/hcdp/hcdp.js:91— `fileExists` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 9 significant file(s) lose their only recent owner: benchmarks/build-helpers/flow-bundler/src/fork/TransformESTreeToBabel.js, benchmarks/MiniReact/no-objects/src/packages/react/index.js, lib/TypedLib/01-array.js, benchmarks/widgets/simple-classes/widgets.js, benchmarks/MiniReact/no-objects/src/packages/@radix-ui/react-primitive/index.js, lib/TypedLib/02-string.js, benchmarks/MiniReact/no-objects/src/app/simple/App.js, benchmarks/micros/lazy-string-growth-gen.js (+1 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 5 significant file(s) lose their only recent owner: agent-perf/tools/runtime_call_profiler.py, agent-perf/tools/pmu_anomalies.py, agent-perf/tools/annotate_source.py, agent-perf/tools/annotate_disasm.py, agent-perf/tools/profile_to_json.py. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 4 significant file(s) lose their only recent owner: lib/Platform/Intl/java/com/facebook/hermes/intl/LocaleIdentifier.java, lib/Platform/Intl/java/com/facebook/hermes/intl/DateTimeFormat.java, lib/Platform/Intl/java/com/facebook/hermes/intl/UnicodeExtensionKeys.java, lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformCollatorAndroid.java. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 3 significant file(s) lose their only recent owner: utils/testsuite/cli.py, utils/testsuite/utils.py, tools/synth/fix_trace.py. Pair on, review, or document these before any departure.
Documentation: no build, run or usage example tools/hermes-parser/js/hermes-estree/README.md:1— `hermes-estree` is a published package (`REDACTED` without `"private": true`) and neither `tools/hermes-parser/js/hermes-estree/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example tools/hermes-parser/js/hermes-parser/README.md:1— `hermes-parser` is a published package (`REDACTED` without `"private": true`) and neither `tools/hermes-parser/js/hermes-parser/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example tools/hermes-parser/js/hermes-transform/README.md:1— `hermes-transform` is a published package (`REDACTED` without `"private": true`) and neither `tools/hermes-parser/js/hermes-transform/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
P10 · Library API & versioning· Implementation type on the public API · ×3
Implementation type on the public API android/build-logic/src/main/kotlin/com/facebook/hermes/helpers/internal/SerializeHermesCompilerPackageJson.kt:14— 2 public types in `com.facebook.hermes.helpers.internal` are marked as implementation by their own namespace, folder or name: `PackageJson` (android/build-logic/src/main/kotlin/com/facebook/hermes/helpers/internal/SerializeHermesCompilerPackageJson.kt:14, `internal`), `SerializeHermesCompilerPackageJson` (android/build-logic/src/main/kotlin/com/facebook/hermes/helpers/internal/SerializeHermesCompilerPackageJson.kt:16, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API android/build-logic/src/main/kotlin/com/facebook/hermes/plugins/internal/TestUtilsPlugin.kt:14— 2 public types in the root namespace are marked as implementation by their own namespace, folder or name: `HermesUtilsPlugin` (android/build-logic/src/main/kotlin/com/facebook/hermes/plugins/internal/TestUtilsPlugin.kt:14, `internal`), `HermesUtils` (android/build-logic/src/main/kotlin/com/facebook/hermes/plugins/internal/TestUtilsPlugin.kt:25, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API android/build-logic/src/main/kotlin/com/facebook/hermes/tasks/internal/CustomExecTask.kt:23— 1 public type in `com.facebook.hermes.tasks.internal` is marked as implementation by its own namespace, folder or name: `CustomExecTask` (android/build-logic/src/main/kotlin/com/facebook/hermes/tasks/internal/CustomExecTask.kt:23, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Silent fallback default on parse failure agent-perf/tools/antipattern_scan.py:74— `scan_file` returns `[]` when `(OSError, UnicodeDecodeError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure agent-perf/tools/generated_code_antipatterns.py:58— `scan_generated_c` returns `[]` when `(OSError, UnicodeDecodeError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure agent-perf/tools/js_antipattern_scan.py:53— `scan_js_file` returns `[]` when `(OSError, UnicodeDecodeError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (25 single-owned of 288 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 288 of the 2386 production source files in this repository met that bar). They are anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: unsupported/juno/crates/hermes/src/parser/hermes_parser.rs, lib/Platform/Unicode/java/com/facebook/hermes/unicode/AndroidUnicodeUtils.java, benchmarks/micros/typed-array-sort.js.
No ADRs found unsupported/juno/crates/juno_cli/Cargo.toml:8— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `unsupported/juno/crates/juno_cli/Cargo.toml` makes this repository a deployable product (line 8).
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 111 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: unsupported/hermes/crates/hermes_semantic_analysis/src/scope_manager.rs, benchmarks/MiniReact/original/MiniReact.js, lib/Platform/Intl/java/com/facebook/hermes/intl/PlatformNumberFormatterICU.java, agent-perf/benchmarks/macro/app_startup.js, benchmarks/bench-runner/categories.py, benchmarks/bench-runner/resource/test-suites/v8-v6-perf/v8-richards.js, agent-perf/tools/generated_code_analyzer.py, agent-perf/tools/generated_code_antipatterns.py (and 103 more) (121 orphaned of 319 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 319 of the 2386 production source files in this repository met that bar). 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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 1/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `.`, `unsupported/juno/crates/flow_native`, `unsupported/juno/crates/juno_cli`.
No SAST REDACTED:4— No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 12 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation API/hermes/cdp/tools/hermes-inspector-msggen/package.json:24— `API/hermes/cdp/tools/hermes-inspector-msggen/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
X5 · Nullable reference types· Java packages are not null-marked everywhere · ×1
Java packages are not null-marked everywhere — 0/3 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
Skipped (documented): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/InsertStatement-test.js:27— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/InsertStatement-test.js:73— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/InsertStatement-test.js:86— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/InsertStatement-test.js:104— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/InsertStatement-test.js:140— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/InsertStatement-test.js:159— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/InsertStatement-test.js:194— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/InsertStatement-test.js:216— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/RemoveStatement-test.js:26— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/RemoveStatement-test.js:56— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/RemoveStatement-test.js:69— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/RemoveStatement-test.js:87— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/RemoveStatement-test.js:123— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/RemoveStatement-test.js:142— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/RemoveStatement-test.js:177— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/RemoveStatement-test.js:199— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/ReplaceStatementWithMany-test.js:27— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/ReplaceStatementWithMany-test.js:71— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/ReplaceStatementWithMany-test.js:84— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/ReplaceStatementWithMany-test.js:102— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/ReplaceStatementWithMany-test.js:138— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/ReplaceStatementWithMany-test.js:157— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/ReplaceStatementWithMany-test.js:192— 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): (unnamed test) tools/hermes-parser/js/hermes-transform/__tests__/transform/mutations/ReplaceStatementWithMany-test.js:214— 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 benchmarks/MiniReact/no-deps/MiniReact.js:57— 3 of 63 documented parameters and 3 of 1627 summaries in `.` only repeat the member or parameter name (e.g. "The current root" for `workInProgressRoot`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tools/hermes-parser/js/hermes-eslint/src/scope-manager/ScopeManager.js:57— 0 of 5 documented parameters and 2 of 77 summaries in `hermes-eslint` only repeat the member or parameter name (e.g. "All scopes" for `scopes`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tools/hermes-parser/js/hermes-estree/src/types.js:2036— 0 of 0 documented parameters and 2 of 11 summaries in `hermes-estree` only repeat the member or parameter name (e.g. "Match patterns *" for `MatchPattern`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tools/hermes-parser/js/hermes-parser/src/transform/SimpleTransform.js:24— 6 of 15 documented parameters and 1 of 60 summaries in `hermes-parser` only repeat the member or parameter name (e.g. "Transform callback" for `TransformCallback`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tools/hermes-parser/js/flow-typed/babel-parser.js:71— 0 of 13 documented parameters and 1 of 140 summaries in `hermes-parser-packages` only repeat the member or parameter name (e.g. "Source filename." for `sourceFilename`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tools/hermes-parser/js/hermes-transform/src/transform/TransformContext.js:203— 0 of 24 documented parameters and 1 of 69 summaries in `hermes-transform` only repeat the member or parameter name (e.g. "Removes the specified comments" for `removeComments`). 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.
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 52 file(s) — `API/hermes/extensions/00-header.js`, `API/hermes/extensions/99-footer.js`, `benchmarks/MiniReact/no-deps/MiniReact.js`, `benchmarks/MiniReact/no-objects/out/music.js`, `benchmarks/MiniReact/no-objects/out/simple.js`, … (+47 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1ddf1-2b85-7174-b6e8-fa5db18cd65a · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 120 · Warnings: 435 · Recommendations: 221 · Info: 30 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 15-11-2026 @ 06: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.