Executive summary
firecrawl/anydoc meets our standard for a preview release, though it has pipeline tools referenced by a changeable name. It scores 70 out of 100 and is rated Strong, and all 64 of its critical findings are security problems in the build pipeline and in the packages it uses.
Security and Compliance, at 64, is the weakest lens and counts most in the score. The best first step is fixing the runtime or framework that no longer gets security updates, worth about 3 points. Pinning the build's installs would lift Security and Compliance itself, worth about 2 points. Raising Security and Compliance to 68 would lift the score to about 72.
Fifty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four pipeline steps install packages that can change without warning, and one known security hole in a package the code depends on can be used by attackers. Pinning each tool to an exact version, pinning what the pipeline installs and updating the vulnerable packages would close these risks.
The product code is 25,854 lines, about €38,000 to rebuild.
If Security and Compliance rose from 64 to 68, the lowest score rated Strong, the score would rise from 70 to about 72.
New since the last survey: 15 findings
- Code Duplication · Edited copies of one member (3 members, 26+ corresponding lines) node/src/document.rs
- Code Duplication · Edited copies of one member (3 members, 27+ corresponding lines) node/src/document.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) src/formats/epub/mod.rs
- Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) node/src/document.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) node/src/document.rs
- Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) node/src/document.rs
- Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) src/formats/docx/content.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/formats/rtf/mod.rs
- Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) node/src/document.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/formats/docx/styles.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) src/render/markdown/escape.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) node/src/document.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/package/xml.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) node/src/document.rs
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 9 findings
- Secret Scanning · Leaked secret: hardcoded-credential REDACTED
- Churn × Complexity Hotspots · Hotspot: src/formats/docx/content.rs src/formats/docx/content.rs
- Churn × Complexity Hotspots · Hotspot: src/formats/rtf/mod.rs src/formats/rtf/mod.rs
- Churn × Complexity Hotspots · Hotspot: src/formats/odf/text.rs src/formats/odf/text.rs
- Churn × Complexity Hotspots · Hotspot: src/shared/html.rs src/shared/html.rs
- Churn × Complexity Hotspots · Hotspot: src/shared/header.rs src/shared/header.rs
- Churn × Complexity Hotspots · Hotspot: src/formats/rtf/lexer.rs src/formats/rtf/lexer.rs
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0367 REDACTED
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €38,000 · Estimate
| Cost to rebuild | €13,000 to €63,000, for 210 to 666 hours of work, about 0.3 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 | ×1.0 at a score of 70. 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: 25,854 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. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 anydoc | 2 anydoc.error | 3 anydoc.model.inline | 4 anydoc.model.link | 5 anydoc.model.style | 6 anydoc.package.xml | 7 anydoc.formats.doc.sprm | 8 anydoc.model.block | 9 anydoc.package.archive | 10 anydoc.shared.delta | 11 anydoc.formats.sheet.controls | 12 anydoc.model | 13 anydoc.model.list | 14 anydoc.model.table | 15 anydoc.package.relationships | 16 anydoc.shared.blockstyle | 17 anydoc.formats.doc.stsh | 18 anydoc.formats.pptx.cascade | 19 anydoc.formats.rtf.table | 20 anydoc.shared.assets | 21 anydoc.shared.list | 22 anydoc.shared.numbering | 23 anydoc.formats.doc.lists | 24 anydoc.formats.odf.styles | 25 anydoc.formats.ppt | 26 anydoc.formats.pptx | 27 anydoc.formats.rtf.tables | 28 anydoc.shared.html | 29 anydoc.formats.docx.numbering | 30 anydoc.formats.epub | 31 anydoc.formats.docx.styles | 32 anydoc.formats.docx.content | 33 anydoc.formats.sheet.xlsx | 34 anydoc.formats.odf | 35 anydoc.formats.odf.table | 36 anydoc.formats.odf.text | 37 anydoc.render.markdown | 38 anydoc.render.markdown.inline | 39 anydoc.formats.rtf | 40 anydoc.formats.doc |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 anydoc | ||||||||||||||||||||||||||||||||||||||||
| 2 anydoc.error | ||||||||||||||||||||||||||||||||||||||||
| 3 anydoc.model.inline | ||||||||||||||||||||||||||||||||||||||||
| 4 anydoc.model.link | ||||||||||||||||||||||||||||||||||||||||
| 5 anydoc.model.style | ||||||||||||||||||||||||||||||||||||||||
| 6 anydoc.package.xml | ||||||||||||||||||||||||||||||||||||||||
| 7 anydoc.formats.doc.sprm | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 anydoc.model.block | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 anydoc.package.archive | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 anydoc.shared.delta | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 anydoc.formats.sheet.controls | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 anydoc.model | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 anydoc.model.list | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 anydoc.model.table | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 anydoc.package.relationships | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 anydoc.shared.blockstyle | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 anydoc.formats.doc.stsh | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 18 anydoc.formats.pptx.cascade | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 anydoc.formats.rtf.table | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 20 anydoc.shared.assets | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 anydoc.shared.list | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 anydoc.shared.numbering | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 anydoc.formats.doc.lists | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 anydoc.formats.odf.styles | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 25 anydoc.formats.ppt | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 anydoc.formats.pptx | 1 | 1 | 1 | 1 | 1 | 2 | 3 | 5 | 1 | |||||||||||||||||||||||||||||||
| 27 anydoc.formats.rtf.tables | 1 | 3 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 28 anydoc.shared.html | 1 | 1 | 2 | 2 | 3 | 2 | ||||||||||||||||||||||||||||||||||
| 29 anydoc.formats.docx.numbering | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 anydoc.formats.epub | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 31 anydoc.formats.docx.styles | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 anydoc.formats.docx.content | 1 | 1 | 1 | 4 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 4 | ||||||||||||||||||||||||||
| 33 anydoc.formats.sheet.xlsx | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 34 anydoc.formats.odf | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 anydoc.formats.odf.table | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 anydoc.formats.odf.text | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 37 anydoc.render.markdown | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 anydoc.render.markdown.inline | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 anydoc.formats.rtf | 2 | 1 | 1 | 1 | 3 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||
| 40 anydoc.formats.doc | 2 | 2 | 3 | 2 | 1 | 1 | 1 | 1 | 3 | 1 |
7→5 anydoc.formats.doc.sprm uses anydoc.model.style✕
- Connections
- 1 pair of types, where a type in anydoc.formats.doc.sprm uses a type in anydoc.model.style.
- The types involved
anydoc.formats.doc.sprm.sprm$module→anydoc.model.style.Style
- Direction
- anydoc.formats.doc.sprm uses anydoc.model.style, so a change to anydoc.model.style can break anydoc.formats.doc.sprm, while a change to anydoc.formats.doc.sprm can't break anydoc.model.style.
- Position
- Below the diagonal: anydoc.formats.doc.sprm uses a module listed above it, which is the healthy direction.
8→3 anydoc.model.block uses anydoc.model.inline✕
- Connections
- 1 pair of types, where a type in anydoc.model.block uses a type in anydoc.model.inline.
- The types involved
anydoc.model.block.Block→anydoc.model.inline.Inline
- Direction
- anydoc.model.block uses anydoc.model.inline, so a change to anydoc.model.inline can break anydoc.model.block, while a change to anydoc.model.block can't break anydoc.model.inline.
- Position
- Below the diagonal: anydoc.model.block uses a module listed above it, which is the healthy direction.
9→2 anydoc.package.archive uses anydoc.error✕
- Connections
- 1 pair of types, where a type in anydoc.package.archive uses a type in anydoc.error.
- The types involved
anydoc.package.archive.archive$module→anydoc.error.ConvertError
- Direction
- anydoc.package.archive uses anydoc.error, so a change to anydoc.error can break anydoc.package.archive, while a change to anydoc.package.archive can't break anydoc.error.
- Position
- Below the diagonal: anydoc.package.archive uses a module listed above it, which is the healthy direction.
10→5 anydoc.shared.delta uses anydoc.model.style✕
- Connections
- 2 pairs of types, where a type in anydoc.shared.delta uses a type in anydoc.model.style.
- The types involved
anydoc.shared.delta.StyleDelta→anydoc.model.style.Styleanydoc.shared.delta.delta$module→anydoc.model.style.Style
- Direction
- anydoc.shared.delta uses anydoc.model.style, so a change to anydoc.model.style can break anydoc.shared.delta, while a change to anydoc.shared.delta can't break anydoc.model.style.
- Position
- Below the diagonal: anydoc.shared.delta uses a module listed above it, which is the healthy direction.
11→3 anydoc.formats.sheet.controls uses anydoc.model.inline✕
- Connections
- 1 pair of types, where a type in anydoc.formats.sheet.controls uses a type in anydoc.model.inline.
- The types involved
anydoc.formats.sheet.controls.controls$module→anydoc.model.inline.Inline
- Direction
- anydoc.formats.sheet.controls uses anydoc.model.inline, so a change to anydoc.model.inline can break anydoc.formats.sheet.controls, while a change to anydoc.formats.sheet.controls can't break anydoc.model.inline.
- Position
- Below the diagonal: anydoc.formats.sheet.controls uses a module listed above it, which is the healthy direction.
11→6 anydoc.formats.sheet.controls uses anydoc.package.xml✕
- Connections
- 1 pair of types, where a type in anydoc.formats.sheet.controls uses a type in anydoc.package.xml.
- The types involved
anydoc.formats.sheet.controls.controls$module→anydoc.package.xml.Element
- Direction
- anydoc.formats.sheet.controls uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.formats.sheet.controls, while a change to anydoc.formats.sheet.controls can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.formats.sheet.controls uses a module listed above it, which is the healthy direction.
11→9 anydoc.formats.sheet.controls uses anydoc.package.archive✕
- Connections
- 1 pair of types, where a type in anydoc.formats.sheet.controls uses a type in anydoc.package.archive.
- The types involved
anydoc.formats.sheet.controls.controls$module→anydoc.package.archive.Package
- Direction
- anydoc.formats.sheet.controls uses anydoc.package.archive, so a change to anydoc.package.archive can break anydoc.formats.sheet.controls, while a change to anydoc.formats.sheet.controls can't break anydoc.package.archive.
- Position
- Below the diagonal: anydoc.formats.sheet.controls uses a module listed above it, which is the healthy direction.
12→8 anydoc.model uses anydoc.model.block✕
- Connections
- 2 pairs of types, where a type in anydoc.model uses a type in anydoc.model.block.
- The types involved
anydoc.model.Document→anydoc.model.block.Blockanydoc.model.Note→anydoc.model.block.Block
- Direction
- anydoc.model uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.model, while a change to anydoc.model can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.model uses a module listed above it, which is the healthy direction.
13→8 anydoc.model.list uses anydoc.model.block✕
- Connections
- 1 pair of types, where a type in anydoc.model.list uses a type in anydoc.model.block.
- The types involved
anydoc.model.list.ListItem→anydoc.model.block.Block
- Direction
- anydoc.model.list uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.model.list, while a change to anydoc.model.list can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.model.list uses a module listed above it, which is the healthy direction.
14→3 anydoc.model.table uses anydoc.model.inline✕
- Connections
- 1 pair of types, where a type in anydoc.model.table uses a type in anydoc.model.inline.
- The types involved
anydoc.model.table.Cell→anydoc.model.inline.Inline
- Direction
- anydoc.model.table uses anydoc.model.inline, so a change to anydoc.model.inline can break anydoc.model.table, while a change to anydoc.model.table can't break anydoc.model.inline.
- Position
- Below the diagonal: anydoc.model.table uses a module listed above it, which is the healthy direction.
14→8 anydoc.model.table uses anydoc.model.block✕
- Connections
- 1 pair of types, where a type in anydoc.model.table uses a type in anydoc.model.block.
- The types involved
anydoc.model.table.Cell→anydoc.model.block.Block
- Direction
- anydoc.model.table uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.model.table, while a change to anydoc.model.table can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.model.table uses a module listed above it, which is the healthy direction.
15→9 anydoc.package.relationships uses anydoc.package.archive✕
- Connections
- 1 pair of types, where a type in anydoc.package.relationships uses a type in anydoc.package.archive.
- The types involved
anydoc.package.relationships.relationships$module→anydoc.package.archive.Package
- Direction
- anydoc.package.relationships uses anydoc.package.archive, so a change to anydoc.package.archive can break anydoc.package.relationships, while a change to anydoc.package.relationships can't break anydoc.package.archive.
- Position
- Below the diagonal: anydoc.package.relationships uses a module listed above it, which is the healthy direction.
16→3 anydoc.shared.blockstyle uses anydoc.model.inline✕
- Connections
- 1 pair of types, where a type in anydoc.shared.blockstyle uses a type in anydoc.model.inline.
- The types involved
anydoc.shared.blockstyle.StyledRun→anydoc.model.inline.Inline
- Direction
- anydoc.shared.blockstyle uses anydoc.model.inline, so a change to anydoc.model.inline can break anydoc.shared.blockstyle, while a change to anydoc.shared.blockstyle can't break anydoc.model.inline.
- Position
- Below the diagonal: anydoc.shared.blockstyle uses a module listed above it, which is the healthy direction.
16→8 anydoc.shared.blockstyle uses anydoc.model.block✕
- Connections
- 1 pair of types, where a type in anydoc.shared.blockstyle uses a type in anydoc.model.block.
- The types involved
anydoc.shared.blockstyle.StyledRun→anydoc.model.block.Block
- Direction
- anydoc.shared.blockstyle uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.shared.blockstyle, while a change to anydoc.shared.blockstyle can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.shared.blockstyle uses a module listed above it, which is the healthy direction.
17→5 anydoc.formats.doc.stsh uses anydoc.model.style✕
- Connections
- 1 pair of types, where a type in anydoc.formats.doc.stsh uses a type in anydoc.model.style.
- The types involved
anydoc.formats.doc.stsh.ResolvedStyle→anydoc.model.style.Style
- Direction
- anydoc.formats.doc.stsh uses anydoc.model.style, so a change to anydoc.model.style can break anydoc.formats.doc.stsh, while a change to anydoc.formats.doc.stsh can't break anydoc.model.style.
- Position
- Below the diagonal: anydoc.formats.doc.stsh uses a module listed above it, which is the healthy direction.
17→7 anydoc.formats.doc.stsh uses anydoc.formats.doc.sprm✕
- Connections
- 1 pair of types, where a type in anydoc.formats.doc.stsh uses a type in anydoc.formats.doc.sprm.
- The types involved
anydoc.formats.doc.stsh.ResolvedStyle→anydoc.formats.doc.sprm.PapDelta
- Direction
- anydoc.formats.doc.stsh uses anydoc.formats.doc.sprm, so a change to anydoc.formats.doc.sprm can break anydoc.formats.doc.stsh, while a change to anydoc.formats.doc.stsh can't break anydoc.formats.doc.sprm.
- Position
- Below the diagonal: anydoc.formats.doc.stsh uses a module listed above it, which is the healthy direction.
17→16 anydoc.formats.doc.stsh uses anydoc.shared.blockstyle✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.doc.stsh uses a type in anydoc.shared.blockstyle.
- The types involved
anydoc.formats.doc.stsh.ResolvedStyle→anydoc.shared.blockstyle.BlockStyleanydoc.formats.doc.stsh.Std→anydoc.shared.blockstyle.BlockStyle
- Direction
- anydoc.formats.doc.stsh uses anydoc.shared.blockstyle, so a change to anydoc.shared.blockstyle can break anydoc.formats.doc.stsh, while a change to anydoc.formats.doc.stsh can't break anydoc.shared.blockstyle.
- Position
- Below the diagonal: anydoc.formats.doc.stsh uses a module listed above it, which is the healthy direction.
18→6 anydoc.formats.pptx.cascade uses anydoc.package.xml✕
- Connections
- 1 pair of types, where a type in anydoc.formats.pptx.cascade uses a type in anydoc.package.xml.
- The types involved
anydoc.formats.pptx.cascade.cascade$module→anydoc.package.xml.Element
- Direction
- anydoc.formats.pptx.cascade uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.formats.pptx.cascade, while a change to anydoc.formats.pptx.cascade can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.formats.pptx.cascade uses a module listed above it, which is the healthy direction.
18→10 anydoc.formats.pptx.cascade uses anydoc.shared.delta✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.pptx.cascade uses a type in anydoc.shared.delta.
- The types involved
anydoc.formats.pptx.cascade.TextProps→anydoc.shared.delta.StyleDeltaanydoc.formats.pptx.cascade.cascade$module→anydoc.shared.delta.StyleDelta
- Direction
- anydoc.formats.pptx.cascade uses anydoc.shared.delta, so a change to anydoc.shared.delta can break anydoc.formats.pptx.cascade, while a change to anydoc.formats.pptx.cascade can't break anydoc.shared.delta.
- Position
- Below the diagonal: anydoc.formats.pptx.cascade uses a module listed above it, which is the healthy direction.
18→13 anydoc.formats.pptx.cascade uses anydoc.model.list✕
- Connections
- 1 pair of types, where a type in anydoc.formats.pptx.cascade uses a type in anydoc.model.list.
- The types involved
anydoc.formats.pptx.cascade.NumWrap→anydoc.model.list.MarkerKind
- Direction
- anydoc.formats.pptx.cascade uses anydoc.model.list, so a change to anydoc.model.list can break anydoc.formats.pptx.cascade, while a change to anydoc.formats.pptx.cascade can't break anydoc.model.list.
- Position
- Below the diagonal: anydoc.formats.pptx.cascade uses a module listed above it, which is the healthy direction.
19→3 anydoc.formats.rtf.table uses anydoc.model.inline✕
- Connections
- 1 pair of types, where a type in anydoc.formats.rtf.table uses a type in anydoc.model.inline.
- The types involved
anydoc.formats.rtf.table.TableState→anydoc.model.inline.Inline
- Direction
- anydoc.formats.rtf.table uses anydoc.model.inline, so a change to anydoc.model.inline can break anydoc.formats.rtf.table, while a change to anydoc.formats.rtf.table can't break anydoc.model.inline.
- Position
- Below the diagonal: anydoc.formats.rtf.table uses a module listed above it, which is the healthy direction.
19→8 anydoc.formats.rtf.table uses anydoc.model.block✕
- Connections
- 1 pair of types, where a type in anydoc.formats.rtf.table uses a type in anydoc.model.block.
- The types involved
anydoc.formats.rtf.table.TableState→anydoc.model.block.Block
- Direction
- anydoc.formats.rtf.table uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.formats.rtf.table, while a change to anydoc.formats.rtf.table can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.formats.rtf.table uses a module listed above it, which is the healthy direction.
19→16 anydoc.formats.rtf.table uses anydoc.shared.blockstyle✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.rtf.table uses a type in anydoc.shared.blockstyle.
- The types involved
anydoc.formats.rtf.table.TableState→anydoc.shared.blockstyle.BlockStyleanydoc.formats.rtf.table.TableState→anydoc.shared.blockstyle.StyledRun
- Direction
- anydoc.formats.rtf.table uses anydoc.shared.blockstyle, so a change to anydoc.shared.blockstyle can break anydoc.formats.rtf.table, while a change to anydoc.formats.rtf.table can't break anydoc.shared.blockstyle.
- Position
- Below the diagonal: anydoc.formats.rtf.table uses a module listed above it, which is the healthy direction.
20→9 anydoc.shared.assets uses anydoc.package.archive✕
- Connections
- 1 pair of types, where a type in anydoc.shared.assets uses a type in anydoc.package.archive.
- The types involved
anydoc.shared.assets.assets$module→anydoc.package.archive.Package
- Direction
- anydoc.shared.assets uses anydoc.package.archive, so a change to anydoc.package.archive can break anydoc.shared.assets, while a change to anydoc.shared.assets can't break anydoc.package.archive.
- Position
- Below the diagonal: anydoc.shared.assets uses a module listed above it, which is the healthy direction.
20→15 anydoc.shared.assets uses anydoc.package.relationships✕
- Connections
- 1 pair of types, where a type in anydoc.shared.assets uses a type in anydoc.package.relationships.
- The types involved
anydoc.shared.assets.assets$module→anydoc.package.relationships.Relationships
- Direction
- anydoc.shared.assets uses anydoc.package.relationships, so a change to anydoc.package.relationships can break anydoc.shared.assets, while a change to anydoc.shared.assets can't break anydoc.package.relationships.
- Position
- Below the diagonal: anydoc.shared.assets uses a module listed above it, which is the healthy direction.
21→8 anydoc.shared.list uses anydoc.model.block✕
- Connections
- 2 pairs of types, where a type in anydoc.shared.list uses a type in anydoc.model.block.
- The types involved
anydoc.shared.list.ListEntry→anydoc.model.block.Blockanydoc.shared.list.list$module→anydoc.model.block.Block
- Direction
- anydoc.shared.list uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.shared.list, while a change to anydoc.shared.list can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.shared.list uses a module listed above it, which is the healthy direction.
21→13 anydoc.shared.list uses anydoc.model.list✕
- Connections
- 1 pair of types, where a type in anydoc.shared.list uses a type in anydoc.model.list.
- The types involved
anydoc.shared.list.ListKey→anydoc.model.list.MarkerKind
- Direction
- anydoc.shared.list uses anydoc.model.list, so a change to anydoc.model.list can break anydoc.shared.list, while a change to anydoc.shared.list can't break anydoc.model.list.
- Position
- Below the diagonal: anydoc.shared.list uses a module listed above it, which is the healthy direction.
22→13 anydoc.shared.numbering uses anydoc.model.list✕
- Connections
- 1 pair of types, where a type in anydoc.shared.numbering uses a type in anydoc.model.list.
- The types involved
anydoc.shared.numbering.numbering$module→anydoc.model.list.MarkerKind
- Direction
- anydoc.shared.numbering uses anydoc.model.list, so a change to anydoc.model.list can break anydoc.shared.numbering, while a change to anydoc.shared.numbering can't break anydoc.model.list.
- Position
- Below the diagonal: anydoc.shared.numbering uses a module listed above it, which is the healthy direction.
23→13 anydoc.formats.doc.lists uses anydoc.model.list✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.doc.lists uses a type in anydoc.model.list.
- The types involved
anydoc.formats.doc.lists.LevelDef→anydoc.model.list.MarkerKindanydoc.formats.doc.lists.lists$module→anydoc.model.list.MarkerKind
- Direction
- anydoc.formats.doc.lists uses anydoc.model.list, so a change to anydoc.model.list can break anydoc.formats.doc.lists, while a change to anydoc.formats.doc.lists can't break anydoc.model.list.
- Position
- Below the diagonal: anydoc.formats.doc.lists uses a module listed above it, which is the healthy direction.
23→22 anydoc.formats.doc.lists uses anydoc.shared.numbering✕
- Connections
- 1 pair of types, where a type in anydoc.formats.doc.lists uses a type in anydoc.shared.numbering.
- The types involved
anydoc.formats.doc.lists.LevelDef→anydoc.shared.numbering.NumberPattern
- Direction
- anydoc.formats.doc.lists uses anydoc.shared.numbering, so a change to anydoc.shared.numbering can break anydoc.formats.doc.lists, while a change to anydoc.formats.doc.lists can't break anydoc.shared.numbering.
- Position
- Below the diagonal: anydoc.formats.doc.lists uses a module listed above it, which is the healthy direction.
24→6 anydoc.formats.odf.styles uses anydoc.package.xml✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.odf.styles uses a type in anydoc.package.xml.
- The types involved
anydoc.formats.odf.styles.OdfStyles→anydoc.package.xml.Elementanydoc.formats.odf.styles.styles$module→anydoc.package.xml.Element
- Direction
- anydoc.formats.odf.styles uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.formats.odf.styles, while a change to anydoc.formats.odf.styles can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.formats.odf.styles uses a module listed above it, which is the healthy direction.
24→10 anydoc.formats.odf.styles uses anydoc.shared.delta✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.styles uses a type in anydoc.shared.delta.
- The types involved
anydoc.formats.odf.styles.styles$module→anydoc.shared.delta.StyleDelta
- Direction
- anydoc.formats.odf.styles uses anydoc.shared.delta, so a change to anydoc.shared.delta can break anydoc.formats.odf.styles, while a change to anydoc.formats.odf.styles can't break anydoc.shared.delta.
- Position
- Below the diagonal: anydoc.formats.odf.styles uses a module listed above it, which is the healthy direction.
24→13 anydoc.formats.odf.styles uses anydoc.model.list✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.styles uses a type in anydoc.model.list.
- The types involved
anydoc.formats.odf.styles.ListLevel→anydoc.model.list.MarkerKind
- Direction
- anydoc.formats.odf.styles uses anydoc.model.list, so a change to anydoc.model.list can break anydoc.formats.odf.styles, while a change to anydoc.formats.odf.styles can't break anydoc.model.list.
- Position
- Below the diagonal: anydoc.formats.odf.styles uses a module listed above it, which is the healthy direction.
24→16 anydoc.formats.odf.styles uses anydoc.shared.blockstyle✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.styles uses a type in anydoc.shared.blockstyle.
- The types involved
anydoc.formats.odf.styles.OdfStyles→anydoc.shared.blockstyle.BlockStyle
- Direction
- anydoc.formats.odf.styles uses anydoc.shared.blockstyle, so a change to anydoc.shared.blockstyle can break anydoc.formats.odf.styles, while a change to anydoc.formats.odf.styles can't break anydoc.shared.blockstyle.
- Position
- Below the diagonal: anydoc.formats.odf.styles uses a module listed above it, which is the healthy direction.
24→22 anydoc.formats.odf.styles uses anydoc.shared.numbering✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.styles uses a type in anydoc.shared.numbering.
- The types involved
anydoc.formats.odf.styles.ListLevel→anydoc.shared.numbering.NumberPattern
- Direction
- anydoc.formats.odf.styles uses anydoc.shared.numbering, so a change to anydoc.shared.numbering can break anydoc.formats.odf.styles, while a change to anydoc.formats.odf.styles can't break anydoc.shared.numbering.
- Position
- Below the diagonal: anydoc.formats.odf.styles uses a module listed above it, which is the healthy direction.
25→8 anydoc.formats.ppt uses anydoc.model.block✕
- Connections
- 1 pair of types, where a type in anydoc.formats.ppt uses a type in anydoc.model.block.
- The types involved
anydoc.formats.ppt.Extractor→anydoc.model.block.Block
- Direction
- anydoc.formats.ppt uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.formats.ppt, while a change to anydoc.formats.ppt can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.formats.ppt uses a module listed above it, which is the healthy direction.
25→21 anydoc.formats.ppt uses anydoc.shared.list✕
- Connections
- 1 pair of types, where a type in anydoc.formats.ppt uses a type in anydoc.shared.list.
- The types involved
anydoc.formats.ppt.Extractor→anydoc.shared.list.ListEntry
- Direction
- anydoc.formats.ppt uses anydoc.shared.list, so a change to anydoc.shared.list can break anydoc.formats.ppt, while a change to anydoc.formats.ppt can't break anydoc.shared.list.
- Position
- Below the diagonal: anydoc.formats.ppt uses a module listed above it, which is the healthy direction.
26→3 anydoc.formats.pptx uses anydoc.model.inline✕
- Connections
- 1 pair of types, where a type in anydoc.formats.pptx uses a type in anydoc.model.inline.
- The types involved
anydoc.formats.pptx.pptx$module→anydoc.model.inline.Inline
- Direction
- anydoc.formats.pptx uses anydoc.model.inline, so a change to anydoc.model.inline can break anydoc.formats.pptx, while a change to anydoc.formats.pptx can't break anydoc.model.inline.
- Position
- Below the diagonal: anydoc.formats.pptx uses a module listed above it, which is the healthy direction.
26→4 anydoc.formats.pptx uses anydoc.model.link✕
- Connections
- 1 pair of types, where a type in anydoc.formats.pptx uses a type in anydoc.model.link.
- The types involved
anydoc.formats.pptx.SlideCtx→anydoc.model.link.LinkTarget
- Direction
- anydoc.formats.pptx uses anydoc.model.link, so a change to anydoc.model.link can break anydoc.formats.pptx, while a change to anydoc.formats.pptx can't break anydoc.model.link.
- Position
- Below the diagonal: anydoc.formats.pptx uses a module listed above it, which is the healthy direction.
26→5 anydoc.formats.pptx uses anydoc.model.style✕
- Connections
- 1 pair of types, where a type in anydoc.formats.pptx uses a type in anydoc.model.style.
- The types involved
anydoc.formats.pptx.pptx$module→anydoc.model.style.Style
- Direction
- anydoc.formats.pptx uses anydoc.model.style, so a change to anydoc.model.style can break anydoc.formats.pptx, while a change to anydoc.formats.pptx can't break anydoc.model.style.
- Position
- Below the diagonal: anydoc.formats.pptx uses a module listed above it, which is the healthy direction.
26→6 anydoc.formats.pptx uses anydoc.package.xml✕
- Connections
- 1 pair of types, where a type in anydoc.formats.pptx uses a type in anydoc.package.xml.
- The types involved
anydoc.formats.pptx.pptx$module→anydoc.package.xml.Element
- Direction
- anydoc.formats.pptx uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.formats.pptx, while a change to anydoc.formats.pptx can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.formats.pptx uses a module listed above it, which is the healthy direction.
26→8 anydoc.formats.pptx uses anydoc.model.block✕
- Connections
- 1 pair of types, where a type in anydoc.formats.pptx uses a type in anydoc.model.block.
- The types involved
anydoc.formats.pptx.pptx$module→anydoc.model.block.Block
- Direction
- anydoc.formats.pptx uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.formats.pptx, while a change to anydoc.formats.pptx can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.formats.pptx uses a module listed above it, which is the healthy direction.
26→9 anydoc.formats.pptx uses anydoc.package.archive✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.pptx uses a type in anydoc.package.archive.
- The types involved
anydoc.formats.pptx.SlideCtx→anydoc.package.archive.Packageanydoc.formats.pptx.pptx$module→anydoc.package.archive.Package
- Direction
- anydoc.formats.pptx uses anydoc.package.archive, so a change to anydoc.package.archive can break anydoc.formats.pptx, while a change to anydoc.formats.pptx can't break anydoc.package.archive.
- Position
- Below the diagonal: anydoc.formats.pptx uses a module listed above it, which is the healthy direction.
26→15 anydoc.formats.pptx uses anydoc.package.relationships✕
- Connections
- 3 pairs of types, where a type in anydoc.formats.pptx uses a type in anydoc.package.relationships.
- The types involved
anydoc.formats.pptx.SlideCtx→anydoc.package.relationships.Relationshipanydoc.formats.pptx.SlideCtx→anydoc.package.relationships.Relationshipsanydoc.formats.pptx.pptx$module→anydoc.package.relationships.Relationships
- Direction
- anydoc.formats.pptx uses anydoc.package.relationships, so a change to anydoc.package.relationships can break anydoc.formats.pptx, while a change to anydoc.formats.pptx can't break anydoc.package.relationships.
- Position
- Below the diagonal: anydoc.formats.pptx uses a module listed above it, which is the healthy direction.
26→18 anydoc.formats.pptx uses anydoc.formats.pptx.cascade✕
- Connections
- 5 pairs of types, where a type in anydoc.formats.pptx uses a type in anydoc.formats.pptx.cascade.
- The types involved
anydoc.formats.pptx.LayoutInfo→anydoc.formats.pptx.cascade.Placeholderanydoc.formats.pptx.MasterInfo→anydoc.formats.pptx.cascade.LevelStyleanydoc.formats.pptx.MasterInfo→anydoc.formats.pptx.cascade.Placeholderanydoc.formats.pptx.SlideCtx→anydoc.formats.pptx.cascade.LevelStyleanydoc.formats.pptx.SlideCtx→anydoc.formats.pptx.cascade.TextProps
- Direction
- anydoc.formats.pptx uses anydoc.formats.pptx.cascade, so a change to anydoc.formats.pptx.cascade can break anydoc.formats.pptx, while a change to anydoc.formats.pptx can't break anydoc.formats.pptx.cascade.
- Position
- Below the diagonal: anydoc.formats.pptx uses a module listed above it, which is the healthy direction.
26→20 anydoc.formats.pptx uses anydoc.shared.assets✕
- Connections
- 1 pair of types, where a type in anydoc.formats.pptx uses a type in anydoc.shared.assets.
- The types involved
anydoc.formats.pptx.SlideCtx→anydoc.shared.assets.AssetSink
- Direction
- anydoc.formats.pptx uses anydoc.shared.assets, so a change to anydoc.shared.assets can break anydoc.formats.pptx, while a change to anydoc.formats.pptx can't break anydoc.shared.assets.
- Position
- Below the diagonal: anydoc.formats.pptx uses a module listed above it, which is the healthy direction.
27→10 anydoc.formats.rtf.tables uses anydoc.shared.delta✕
- Connections
- 1 pair of types, where a type in anydoc.formats.rtf.tables uses a type in anydoc.shared.delta.
- The types involved
anydoc.formats.rtf.tables.StyleDef→anydoc.shared.delta.StyleDelta
- Direction
- anydoc.formats.rtf.tables uses anydoc.shared.delta, so a change to anydoc.shared.delta can break anydoc.formats.rtf.tables, while a change to anydoc.formats.rtf.tables can't break anydoc.shared.delta.
- Position
- Below the diagonal: anydoc.formats.rtf.tables uses a module listed above it, which is the healthy direction.
27→13 anydoc.formats.rtf.tables uses anydoc.model.list✕
- Connections
- 3 pairs of types, where a type in anydoc.formats.rtf.tables uses a type in anydoc.model.list.
- The types involved
anydoc.formats.rtf.tables.LevelTextCollector→anydoc.model.list.MarkerKindanydoc.formats.rtf.tables.ListLevelDef→anydoc.model.list.MarkerKindanydoc.formats.rtf.tables.tables$module→anydoc.model.list.MarkerKind
- Direction
- anydoc.formats.rtf.tables uses anydoc.model.list, so a change to anydoc.model.list can break anydoc.formats.rtf.tables, while a change to anydoc.formats.rtf.tables can't break anydoc.model.list.
- Position
- Below the diagonal: anydoc.formats.rtf.tables uses a module listed above it, which is the healthy direction.
27→16 anydoc.formats.rtf.tables uses anydoc.shared.blockstyle✕
- Connections
- 1 pair of types, where a type in anydoc.formats.rtf.tables uses a type in anydoc.shared.blockstyle.
- The types involved
anydoc.formats.rtf.tables.StyleDef→anydoc.shared.blockstyle.BlockStyle
- Direction
- anydoc.formats.rtf.tables uses anydoc.shared.blockstyle, so a change to anydoc.shared.blockstyle can break anydoc.formats.rtf.tables, while a change to anydoc.formats.rtf.tables can't break anydoc.shared.blockstyle.
- Position
- Below the diagonal: anydoc.formats.rtf.tables uses a module listed above it, which is the healthy direction.
27→22 anydoc.formats.rtf.tables uses anydoc.shared.numbering✕
- Connections
- 3 pairs of types, where a type in anydoc.formats.rtf.tables uses a type in anydoc.shared.numbering.
- The types involved
anydoc.formats.rtf.tables.LevelTextCollector→anydoc.shared.numbering.NumberPatternanydoc.formats.rtf.tables.ListLevelDef→anydoc.shared.numbering.NumberPatternanydoc.formats.rtf.tables.tables$module→anydoc.shared.numbering.NumberText
- Direction
- anydoc.formats.rtf.tables uses anydoc.shared.numbering, so a change to anydoc.shared.numbering can break anydoc.formats.rtf.tables, while a change to anydoc.formats.rtf.tables can't break anydoc.shared.numbering.
- Position
- Below the diagonal: anydoc.formats.rtf.tables uses a module listed above it, which is the healthy direction.
28→3 anydoc.shared.html uses anydoc.model.inline✕
- Connections
- 1 pair of types, where a type in anydoc.shared.html uses a type in anydoc.model.inline.
- The types involved
anydoc.shared.html.Builder→anydoc.model.inline.Inline
- Direction
- anydoc.shared.html uses anydoc.model.inline, so a change to anydoc.model.inline can break anydoc.shared.html, while a change to anydoc.shared.html can't break anydoc.model.inline.
- Position
- Below the diagonal: anydoc.shared.html uses a module listed above it, which is the healthy direction.
28→4 anydoc.shared.html uses anydoc.model.link✕
- Connections
- 1 pair of types, where a type in anydoc.shared.html uses a type in anydoc.model.link.
- The types involved
anydoc.shared.html.HtmlCtx→anydoc.model.link.LinkTarget
- Direction
- anydoc.shared.html uses anydoc.model.link, so a change to anydoc.model.link can break anydoc.shared.html, while a change to anydoc.shared.html can't break anydoc.model.link.
- Position
- Below the diagonal: anydoc.shared.html uses a module listed above it, which is the healthy direction.
28→6 anydoc.shared.html uses anydoc.package.xml✕
- Connections
- 2 pairs of types, where a type in anydoc.shared.html uses a type in anydoc.package.xml.
- The types involved
anydoc.shared.html.Builder→anydoc.package.xml.Elementanydoc.shared.html.html$module→anydoc.package.xml.Element
- Direction
- anydoc.shared.html uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.shared.html, while a change to anydoc.shared.html can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.shared.html uses a module listed above it, which is the healthy direction.
28→8 anydoc.shared.html uses anydoc.model.block✕
- Connections
- 2 pairs of types, where a type in anydoc.shared.html uses a type in anydoc.model.block.
- The types involved
anydoc.shared.html.Builder→anydoc.model.block.Blockanydoc.shared.html.html$module→anydoc.model.block.Block
- Direction
- anydoc.shared.html uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.shared.html, while a change to anydoc.shared.html can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.shared.html uses a module listed above it, which is the healthy direction.
28→10 anydoc.shared.html uses anydoc.shared.delta✕
- Connections
- 3 pairs of types, where a type in anydoc.shared.html uses a type in anydoc.shared.delta.
- The types involved
anydoc.shared.html.Builder→anydoc.shared.delta.StyleDeltaanydoc.shared.html.StyleProps→anydoc.shared.delta.StyleDeltaanydoc.shared.html.html$module→anydoc.shared.delta.StyleDelta
- Direction
- anydoc.shared.html uses anydoc.shared.delta, so a change to anydoc.shared.delta can break anydoc.shared.html, while a change to anydoc.shared.html can't break anydoc.shared.delta.
- Position
- Below the diagonal: anydoc.shared.html uses a module listed above it, which is the healthy direction.
28→17 anydoc.shared.html uses anydoc.formats.doc.stsh✕
- Connections
- 2 pairs of types, where a type in anydoc.shared.html uses a type in anydoc.formats.doc.stsh.
- The types involved
anydoc.shared.html.Builder→anydoc.formats.doc.stsh.Stylesheetanydoc.shared.html.html$module→anydoc.formats.doc.stsh.Stylesheet
- Direction
- anydoc.shared.html uses anydoc.formats.doc.stsh, so a change to anydoc.formats.doc.stsh can break anydoc.shared.html, while a change to anydoc.shared.html can't break anydoc.formats.doc.stsh.
- Position
- Below the diagonal: anydoc.shared.html uses a module listed above it, which is the healthy direction.
29→6 anydoc.formats.docx.numbering uses anydoc.package.xml✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.numbering uses a type in anydoc.package.xml.
- The types involved
anydoc.formats.docx.numbering.numbering$module→anydoc.package.xml.Element
- Direction
- anydoc.formats.docx.numbering uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.formats.docx.numbering, while a change to anydoc.formats.docx.numbering can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.formats.docx.numbering uses a module listed above it, which is the healthy direction.
29→13 anydoc.formats.docx.numbering uses anydoc.model.list✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.numbering uses a type in anydoc.model.list.
- The types involved
anydoc.formats.docx.numbering.LevelDef→anydoc.model.list.MarkerKind
- Direction
- anydoc.formats.docx.numbering uses anydoc.model.list, so a change to anydoc.model.list can break anydoc.formats.docx.numbering, while a change to anydoc.formats.docx.numbering can't break anydoc.model.list.
- Position
- Below the diagonal: anydoc.formats.docx.numbering uses a module listed above it, which is the healthy direction.
29→22 anydoc.formats.docx.numbering uses anydoc.shared.numbering✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.numbering uses a type in anydoc.shared.numbering.
- The types involved
anydoc.formats.docx.numbering.LevelDef→anydoc.shared.numbering.NumberPattern
- Direction
- anydoc.formats.docx.numbering uses anydoc.shared.numbering, so a change to anydoc.shared.numbering can break anydoc.formats.docx.numbering, while a change to anydoc.formats.docx.numbering can't break anydoc.shared.numbering.
- Position
- Below the diagonal: anydoc.formats.docx.numbering uses a module listed above it, which is the healthy direction.
29→23 anydoc.formats.docx.numbering uses anydoc.formats.doc.lists✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.numbering uses a type in anydoc.formats.doc.lists.
- The types involved
anydoc.formats.docx.numbering.numbering$module→anydoc.formats.doc.lists.LevelDef
- Direction
- anydoc.formats.docx.numbering uses anydoc.formats.doc.lists, so a change to anydoc.formats.doc.lists can break anydoc.formats.docx.numbering, while a change to anydoc.formats.docx.numbering can't break anydoc.formats.doc.lists.
- Position
- Below the diagonal: anydoc.formats.docx.numbering uses a module listed above it, which is the healthy direction.
30→4 anydoc.formats.epub uses anydoc.model.link✕
- Connections
- 1 pair of types, where a type in anydoc.formats.epub uses a type in anydoc.model.link.
- The types involved
anydoc.formats.epub.ChapterCtx→anydoc.model.link.LinkTarget
- Direction
- anydoc.formats.epub uses anydoc.model.link, so a change to anydoc.model.link can break anydoc.formats.epub, while a change to anydoc.formats.epub can't break anydoc.model.link.
- Position
- Below the diagonal: anydoc.formats.epub uses a module listed above it, which is the healthy direction.
30→6 anydoc.formats.epub uses anydoc.package.xml✕
- Connections
- 1 pair of types, where a type in anydoc.formats.epub uses a type in anydoc.package.xml.
- The types involved
anydoc.formats.epub.epub$module→anydoc.package.xml.Element
- Direction
- anydoc.formats.epub uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.formats.epub, while a change to anydoc.formats.epub can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.formats.epub uses a module listed above it, which is the healthy direction.
30→9 anydoc.formats.epub uses anydoc.package.archive✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.epub uses a type in anydoc.package.archive.
- The types involved
anydoc.formats.epub.ChapterCtx→anydoc.package.archive.Packageanydoc.formats.epub.epub$module→anydoc.package.archive.Package
- Direction
- anydoc.formats.epub uses anydoc.package.archive, so a change to anydoc.package.archive can break anydoc.formats.epub, while a change to anydoc.formats.epub can't break anydoc.package.archive.
- Position
- Below the diagonal: anydoc.formats.epub uses a module listed above it, which is the healthy direction.
30→20 anydoc.formats.epub uses anydoc.shared.assets✕
- Connections
- 1 pair of types, where a type in anydoc.formats.epub uses a type in anydoc.shared.assets.
- The types involved
anydoc.formats.epub.ChapterCtx→anydoc.shared.assets.AssetSink
- Direction
- anydoc.formats.epub uses anydoc.shared.assets, so a change to anydoc.shared.assets can break anydoc.formats.epub, while a change to anydoc.formats.epub can't break anydoc.shared.assets.
- Position
- Below the diagonal: anydoc.formats.epub uses a module listed above it, which is the healthy direction.
30→28 anydoc.formats.epub uses anydoc.shared.html✕
- Connections
- 1 pair of types, where a type in anydoc.formats.epub uses a type in anydoc.shared.html.
- The types involved
anydoc.formats.epub.ChapterCtx→anydoc.shared.html.HtmlCtx
- Direction
- anydoc.formats.epub uses anydoc.shared.html, so a change to anydoc.shared.html can break anydoc.formats.epub, while a change to anydoc.formats.epub can't break anydoc.shared.html.
- Position
- Below the diagonal: anydoc.formats.epub uses a module listed above it, which is the healthy direction.
31→5 anydoc.formats.docx.styles uses anydoc.model.style✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.docx.styles uses a type in anydoc.model.style.
- The types involved
anydoc.formats.docx.styles.Styles→anydoc.model.style.Styleanydoc.formats.docx.styles.Toggles→anydoc.model.style.Style
- Direction
- anydoc.formats.docx.styles uses anydoc.model.style, so a change to anydoc.model.style can break anydoc.formats.docx.styles, while a change to anydoc.formats.docx.styles can't break anydoc.model.style.
- Position
- Below the diagonal: anydoc.formats.docx.styles uses a module listed above it, which is the healthy direction.
31→6 anydoc.formats.docx.styles uses anydoc.package.xml✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.docx.styles uses a type in anydoc.package.xml.
- The types involved
anydoc.formats.docx.styles.Styles→anydoc.package.xml.Elementanydoc.formats.docx.styles.styles$module→anydoc.package.xml.Element
- Direction
- anydoc.formats.docx.styles uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.formats.docx.styles, while a change to anydoc.formats.docx.styles can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.formats.docx.styles uses a module listed above it, which is the healthy direction.
31→10 anydoc.formats.docx.styles uses anydoc.shared.delta✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.styles uses a type in anydoc.shared.delta.
- The types involved
anydoc.formats.docx.styles.styles$module→anydoc.shared.delta.StyleDelta
- Direction
- anydoc.formats.docx.styles uses anydoc.shared.delta, so a change to anydoc.shared.delta can break anydoc.formats.docx.styles, while a change to anydoc.formats.docx.styles can't break anydoc.shared.delta.
- Position
- Below the diagonal: anydoc.formats.docx.styles uses a module listed above it, which is the healthy direction.
31→29 anydoc.formats.docx.styles uses anydoc.formats.docx.numbering✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.styles uses a type in anydoc.formats.docx.numbering.
- The types involved
anydoc.formats.docx.styles.Styles→anydoc.formats.docx.numbering.Instance
- Direction
- anydoc.formats.docx.styles uses anydoc.formats.docx.numbering, so a change to anydoc.formats.docx.numbering can break anydoc.formats.docx.styles, while a change to anydoc.formats.docx.styles can't break anydoc.formats.docx.numbering.
- Position
- Below the diagonal: anydoc.formats.docx.styles uses a module listed above it, which is the healthy direction.
32→3 anydoc.formats.docx.content uses anydoc.model.inline✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.content uses a type in anydoc.model.inline.
- The types involved
anydoc.formats.docx.content.InlineWalker→anydoc.model.inline.Inline
- Direction
- anydoc.formats.docx.content uses anydoc.model.inline, so a change to anydoc.model.inline can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.model.inline.
- Position
- Below the diagonal: anydoc.formats.docx.content uses a module listed above it, which is the healthy direction.
32→4 anydoc.formats.docx.content uses anydoc.model.link✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.content uses a type in anydoc.model.link.
- The types involved
anydoc.formats.docx.content.InlineWalker→anydoc.model.link.LinkTarget
- Direction
- anydoc.formats.docx.content uses anydoc.model.link, so a change to anydoc.model.link can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.model.link.
- Position
- Below the diagonal: anydoc.formats.docx.content uses a module listed above it, which is the healthy direction.
32→5 anydoc.formats.docx.content uses anydoc.model.style✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.content uses a type in anydoc.model.style.
- The types involved
anydoc.formats.docx.content.InlineWalker→anydoc.model.style.Style
- Direction
- anydoc.formats.docx.content uses anydoc.model.style, so a change to anydoc.model.style can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.model.style.
- Position
- Below the diagonal: anydoc.formats.docx.content uses a module listed above it, which is the healthy direction.
32→6 anydoc.formats.docx.content uses anydoc.package.xml✕
- Connections
- 4 pairs of types, where a type in anydoc.formats.docx.content uses a type in anydoc.package.xml.
- The types involved
anydoc.formats.docx.content.Ctx→anydoc.package.xml.Elementanydoc.formats.docx.content.InlineWalker→anydoc.package.xml.Elementanydoc.formats.docx.content.TcInfo→anydoc.package.xml.Elementanydoc.formats.docx.content.content$module→anydoc.package.xml.Element
- Direction
- anydoc.formats.docx.content uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.formats.docx.content uses a module listed above it, which is the healthy direction.
32→8 anydoc.formats.docx.content uses anydoc.model.block✕
- Connections
- 3 pairs of types, where a type in anydoc.formats.docx.content uses a type in anydoc.model.block.
- The types involved
anydoc.formats.docx.content.InlineWalker→anydoc.model.block.Blockanydoc.formats.docx.content.Runs→anydoc.model.block.Blockanydoc.formats.docx.content.content$module→anydoc.model.block.Block
- Direction
- anydoc.formats.docx.content uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.formats.docx.content uses a module listed above it, which is the healthy direction.
32→9 anydoc.formats.docx.content uses anydoc.package.archive✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.content uses a type in anydoc.package.archive.
- The types involved
anydoc.formats.docx.content.Ctx→anydoc.package.archive.Package
- Direction
- anydoc.formats.docx.content uses anydoc.package.archive, so a change to anydoc.package.archive can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.package.archive.
- Position
- Below the diagonal: anydoc.formats.docx.content uses a module listed above it, which is the healthy direction.
32→15 anydoc.formats.docx.content uses anydoc.package.relationships✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.content uses a type in anydoc.package.relationships.
- The types involved
anydoc.formats.docx.content.Ctx→anydoc.package.relationships.Relationships
- Direction
- anydoc.formats.docx.content uses anydoc.package.relationships, so a change to anydoc.package.relationships can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.package.relationships.
- Position
- Below the diagonal: anydoc.formats.docx.content uses a module listed above it, which is the healthy direction.
32→16 anydoc.formats.docx.content uses anydoc.shared.blockstyle✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.content uses a type in anydoc.shared.blockstyle.
- The types involved
anydoc.formats.docx.content.Runs→anydoc.shared.blockstyle.StyledRun
- Direction
- anydoc.formats.docx.content uses anydoc.shared.blockstyle, so a change to anydoc.shared.blockstyle can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.shared.blockstyle.
- Position
- Below the diagonal: anydoc.formats.docx.content uses a module listed above it, which is the healthy direction.
32→20 anydoc.formats.docx.content uses anydoc.shared.assets✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.content uses a type in anydoc.shared.assets.
- The types involved
anydoc.formats.docx.content.Ctx→anydoc.shared.assets.AssetSink
- Direction
- anydoc.formats.docx.content uses anydoc.shared.assets, so a change to anydoc.shared.assets can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.shared.assets.
- Position
- Below the diagonal: anydoc.formats.docx.content uses a module listed above it, which is the healthy direction.
32→21 anydoc.formats.docx.content uses anydoc.shared.list✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.content uses a type in anydoc.shared.list.
- The types involved
anydoc.formats.docx.content.Runs→anydoc.shared.list.ListEntry
- Direction
- anydoc.formats.docx.content uses anydoc.shared.list, so a change to anydoc.shared.list can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.shared.list.
- Position
- Below the diagonal: anydoc.formats.docx.content uses a module listed above it, which is the healthy direction.
32→29 anydoc.formats.docx.content uses anydoc.formats.docx.numbering✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.content uses a type in anydoc.formats.docx.numbering.
- The types involved
anydoc.formats.docx.content.Ctx→anydoc.formats.docx.numbering.Numbering
- Direction
- anydoc.formats.docx.content uses anydoc.formats.docx.numbering, so a change to anydoc.formats.docx.numbering can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.formats.docx.numbering.
- Position
- Below the diagonal: anydoc.formats.docx.content uses a module listed above it, which is the healthy direction.
32→31 anydoc.formats.docx.content uses anydoc.formats.docx.styles✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.content uses a type in anydoc.formats.docx.styles.
- The types involved
anydoc.formats.docx.content.Ctx→anydoc.formats.docx.styles.Styles
- Direction
- anydoc.formats.docx.content uses anydoc.formats.docx.styles, so a change to anydoc.formats.docx.styles can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.formats.docx.styles.
- Position
- Below the diagonal: anydoc.formats.docx.content uses a module listed above it, which is the healthy direction.
32→39 anydoc.formats.docx.content uses anydoc.formats.rtf part of a loop✕
- Connections
- 1 pair of types, where a type in anydoc.formats.docx.content uses a type in anydoc.formats.rtf.
- The types involved
anydoc.formats.docx.content.InlineWalker→anydoc.formats.rtf.FieldFrame
- Direction
- anydoc.formats.docx.content uses anydoc.formats.rtf, so a change to anydoc.formats.rtf can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.formats.rtf.
- 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.
32→40 anydoc.formats.docx.content uses anydoc.formats.doc part of a loop✕
- Connections
- 4 pairs of types, where a type in anydoc.formats.docx.content uses a type in anydoc.formats.doc.
- The types involved
anydoc.formats.docx.content.Ctx→anydoc.formats.doc.Countersanydoc.formats.docx.content.InlineWalker→anydoc.formats.doc.Pieceanydoc.formats.docx.content.content$module→anydoc.formats.doc.Pieceanydoc.formats.docx.content.content$module→anydoc.formats.doc.Runs
- Direction
- anydoc.formats.docx.content uses anydoc.formats.doc, so a change to anydoc.formats.doc can break anydoc.formats.docx.content, while a change to anydoc.formats.docx.content can't break anydoc.formats.doc.
- 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.
33→6 anydoc.formats.sheet.xlsx uses anydoc.package.xml✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.sheet.xlsx uses a type in anydoc.package.xml.
- The types involved
anydoc.formats.sheet.xlsx.Styles→anydoc.package.xml.Elementanydoc.formats.sheet.xlsx.xlsx$module→anydoc.package.xml.Element
- Direction
- anydoc.formats.sheet.xlsx uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.formats.sheet.xlsx, while a change to anydoc.formats.sheet.xlsx can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.formats.sheet.xlsx uses a module listed above it, which is the healthy direction.
33→9 anydoc.formats.sheet.xlsx uses anydoc.package.archive✕
- Connections
- 1 pair of types, where a type in anydoc.formats.sheet.xlsx uses a type in anydoc.package.archive.
- The types involved
anydoc.formats.sheet.xlsx.xlsx$module→anydoc.package.archive.Package
- Direction
- anydoc.formats.sheet.xlsx uses anydoc.package.archive, so a change to anydoc.package.archive can break anydoc.formats.sheet.xlsx, while a change to anydoc.formats.sheet.xlsx can't break anydoc.package.archive.
- Position
- Below the diagonal: anydoc.formats.sheet.xlsx uses a module listed above it, which is the healthy direction.
33→15 anydoc.formats.sheet.xlsx uses anydoc.package.relationships✕
- Connections
- 1 pair of types, where a type in anydoc.formats.sheet.xlsx uses a type in anydoc.package.relationships.
- The types involved
anydoc.formats.sheet.xlsx.xlsx$module→anydoc.package.relationships.Relationships
- Direction
- anydoc.formats.sheet.xlsx uses anydoc.package.relationships, so a change to anydoc.package.relationships can break anydoc.formats.sheet.xlsx, while a change to anydoc.formats.sheet.xlsx can't break anydoc.package.relationships.
- Position
- Below the diagonal: anydoc.formats.sheet.xlsx uses a module listed above it, which is the healthy direction.
33→31 anydoc.formats.sheet.xlsx uses anydoc.formats.docx.styles✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.sheet.xlsx uses a type in anydoc.formats.docx.styles.
- The types involved
anydoc.formats.sheet.xlsx.Styles→anydoc.formats.docx.styles.Stylesanydoc.formats.sheet.xlsx.xlsx$module→anydoc.formats.docx.styles.Styles
- Direction
- anydoc.formats.sheet.xlsx uses anydoc.formats.docx.styles, so a change to anydoc.formats.docx.styles can break anydoc.formats.sheet.xlsx, while a change to anydoc.formats.sheet.xlsx can't break anydoc.formats.docx.styles.
- Position
- Below the diagonal: anydoc.formats.sheet.xlsx uses a module listed above it, which is the healthy direction.
34→6 anydoc.formats.odf uses anydoc.package.xml✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf uses a type in anydoc.package.xml.
- The types involved
anydoc.formats.odf.odf$module→anydoc.package.xml.Element
- Direction
- anydoc.formats.odf uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.formats.odf, while a change to anydoc.formats.odf can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.formats.odf uses a module listed above it, which is the healthy direction.
34→8 anydoc.formats.odf uses anydoc.model.block✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf uses a type in anydoc.model.block.
- The types involved
anydoc.formats.odf.odf$module→anydoc.model.block.Block
- Direction
- anydoc.formats.odf uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.formats.odf, while a change to anydoc.formats.odf can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.formats.odf uses a module listed above it, which is the healthy direction.
34→9 anydoc.formats.odf uses anydoc.package.archive✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf uses a type in anydoc.package.archive.
- The types involved
anydoc.formats.odf.odf$module→anydoc.package.archive.Package
- Direction
- anydoc.formats.odf uses anydoc.package.archive, so a change to anydoc.package.archive can break anydoc.formats.odf, while a change to anydoc.formats.odf can't break anydoc.package.archive.
- Position
- Below the diagonal: anydoc.formats.odf uses a module listed above it, which is the healthy direction.
34→32 anydoc.formats.odf uses anydoc.formats.docx.content✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf uses a type in anydoc.formats.docx.content.
- The types involved
anydoc.formats.odf.odf$module→anydoc.formats.docx.content.Ctx
- Direction
- anydoc.formats.odf uses anydoc.formats.docx.content, so a change to anydoc.formats.docx.content can break anydoc.formats.odf, while a change to anydoc.formats.odf can't break anydoc.formats.docx.content.
- Position
- Below the diagonal: anydoc.formats.odf uses a module listed above it, which is the healthy direction.
35→6 anydoc.formats.odf.table uses anydoc.package.xml✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.table uses a type in anydoc.package.xml.
- The types involved
anydoc.formats.odf.table.table$module→anydoc.package.xml.Element
- Direction
- anydoc.formats.odf.table uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.formats.odf.table, while a change to anydoc.formats.odf.table can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.formats.odf.table uses a module listed above it, which is the healthy direction.
35→8 anydoc.formats.odf.table uses anydoc.model.block✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.table uses a type in anydoc.model.block.
- The types involved
anydoc.formats.odf.table.table$module→anydoc.model.block.Block
- Direction
- anydoc.formats.odf.table uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.formats.odf.table, while a change to anydoc.formats.odf.table can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.formats.odf.table uses a module listed above it, which is the healthy direction.
35→14 anydoc.formats.odf.table uses anydoc.model.table✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.table uses a type in anydoc.model.table.
- The types involved
anydoc.formats.odf.table.TableState→anydoc.model.table.GridBuilder
- Direction
- anydoc.formats.odf.table uses anydoc.model.table, so a change to anydoc.model.table can break anydoc.formats.odf.table, while a change to anydoc.formats.odf.table can't break anydoc.model.table.
- Position
- Below the diagonal: anydoc.formats.odf.table uses a module listed above it, which is the healthy direction.
35→32 anydoc.formats.odf.table uses anydoc.formats.docx.content✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.table uses a type in anydoc.formats.docx.content.
- The types involved
anydoc.formats.odf.table.table$module→anydoc.formats.docx.content.Ctx
- Direction
- anydoc.formats.odf.table uses anydoc.formats.docx.content, so a change to anydoc.formats.docx.content can break anydoc.formats.odf.table, while a change to anydoc.formats.odf.table can't break anydoc.formats.docx.content.
- Position
- Below the diagonal: anydoc.formats.odf.table uses a module listed above it, which is the healthy direction.
36→3 anydoc.formats.odf.text uses anydoc.model.inline✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.text uses a type in anydoc.model.inline.
- The types involved
anydoc.formats.odf.text.text$module→anydoc.model.inline.Inline
- Direction
- anydoc.formats.odf.text uses anydoc.model.inline, so a change to anydoc.model.inline can break anydoc.formats.odf.text, while a change to anydoc.formats.odf.text can't break anydoc.model.inline.
- Position
- Below the diagonal: anydoc.formats.odf.text uses a module listed above it, which is the healthy direction.
36→4 anydoc.formats.odf.text uses anydoc.model.link✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.text uses a type in anydoc.model.link.
- The types involved
anydoc.formats.odf.text.text$module→anydoc.model.link.LinkTarget
- Direction
- anydoc.formats.odf.text uses anydoc.model.link, so a change to anydoc.model.link can break anydoc.formats.odf.text, while a change to anydoc.formats.odf.text can't break anydoc.model.link.
- Position
- Below the diagonal: anydoc.formats.odf.text uses a module listed above it, which is the healthy direction.
36→6 anydoc.formats.odf.text uses anydoc.package.xml✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.text uses a type in anydoc.package.xml.
- The types involved
anydoc.formats.odf.text.text$module→anydoc.package.xml.Element
- Direction
- anydoc.formats.odf.text uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.formats.odf.text, while a change to anydoc.formats.odf.text can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.formats.odf.text uses a module listed above it, which is the healthy direction.
36→8 anydoc.formats.odf.text uses anydoc.model.block✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.text uses a type in anydoc.model.block.
- The types involved
anydoc.formats.odf.text.text$module→anydoc.model.block.Block
- Direction
- anydoc.formats.odf.text uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.formats.odf.text, while a change to anydoc.formats.odf.text can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.formats.odf.text uses a module listed above it, which is the healthy direction.
36→9 anydoc.formats.odf.text uses anydoc.package.archive✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.text uses a type in anydoc.package.archive.
- The types involved
anydoc.formats.odf.text.Ctx→anydoc.package.archive.Package
- Direction
- anydoc.formats.odf.text uses anydoc.package.archive, so a change to anydoc.package.archive can break anydoc.formats.odf.text, while a change to anydoc.formats.odf.text can't break anydoc.package.archive.
- Position
- Below the diagonal: anydoc.formats.odf.text uses a module listed above it, which is the healthy direction.
36→10 anydoc.formats.odf.text uses anydoc.shared.delta✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.text uses a type in anydoc.shared.delta.
- The types involved
anydoc.formats.odf.text.text$module→anydoc.shared.delta.StyleDelta
- Direction
- anydoc.formats.odf.text uses anydoc.shared.delta, so a change to anydoc.shared.delta can break anydoc.formats.odf.text, while a change to anydoc.formats.odf.text can't break anydoc.shared.delta.
- Position
- Below the diagonal: anydoc.formats.odf.text uses a module listed above it, which is the healthy direction.
36→12 anydoc.formats.odf.text uses anydoc.model✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.text uses a type in anydoc.model.
- The types involved
anydoc.formats.odf.text.Ctx→anydoc.model.Note
- Direction
- anydoc.formats.odf.text uses anydoc.model, so a change to anydoc.model can break anydoc.formats.odf.text, while a change to anydoc.formats.odf.text can't break anydoc.model.
- Position
- Below the diagonal: anydoc.formats.odf.text uses a module listed above it, which is the healthy direction.
36→16 anydoc.formats.odf.text uses anydoc.shared.blockstyle✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.text uses a type in anydoc.shared.blockstyle.
- The types involved
anydoc.formats.odf.text.text$module→anydoc.shared.blockstyle.StyledRun
- Direction
- anydoc.formats.odf.text uses anydoc.shared.blockstyle, so a change to anydoc.shared.blockstyle can break anydoc.formats.odf.text, while a change to anydoc.formats.odf.text can't break anydoc.shared.blockstyle.
- Position
- Below the diagonal: anydoc.formats.odf.text uses a module listed above it, which is the healthy direction.
36→20 anydoc.formats.odf.text uses anydoc.shared.assets✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.text uses a type in anydoc.shared.assets.
- The types involved
anydoc.formats.odf.text.Ctx→anydoc.shared.assets.AssetSink
- Direction
- anydoc.formats.odf.text uses anydoc.shared.assets, so a change to anydoc.shared.assets can break anydoc.formats.odf.text, while a change to anydoc.formats.odf.text can't break anydoc.shared.assets.
- Position
- Below the diagonal: anydoc.formats.odf.text uses a module listed above it, which is the healthy direction.
36→24 anydoc.formats.odf.text uses anydoc.formats.odf.styles✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.text uses a type in anydoc.formats.odf.styles.
- The types involved
anydoc.formats.odf.text.Ctx→anydoc.formats.odf.styles.OdfStyles
- Direction
- anydoc.formats.odf.text uses anydoc.formats.odf.styles, so a change to anydoc.formats.odf.styles can break anydoc.formats.odf.text, while a change to anydoc.formats.odf.text can't break anydoc.formats.odf.styles.
- Position
- Below the diagonal: anydoc.formats.odf.text uses a module listed above it, which is the healthy direction.
36→32 anydoc.formats.odf.text uses anydoc.formats.docx.content✕
- Connections
- 1 pair of types, where a type in anydoc.formats.odf.text uses a type in anydoc.formats.docx.content.
- The types involved
anydoc.formats.odf.text.text$module→anydoc.formats.docx.content.Ctx
- Direction
- anydoc.formats.odf.text uses anydoc.formats.docx.content, so a change to anydoc.formats.docx.content can break anydoc.formats.odf.text, while a change to anydoc.formats.odf.text can't break anydoc.formats.docx.content.
- Position
- Below the diagonal: anydoc.formats.odf.text uses a module listed above it, which is the healthy direction.
37→8 anydoc.render.markdown uses anydoc.model.block✕
- Connections
- 1 pair of types, where a type in anydoc.render.markdown uses a type in anydoc.model.block.
- The types involved
anydoc.render.markdown.markdown$module→anydoc.model.block.Block
- Direction
- anydoc.render.markdown uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.render.markdown, while a change to anydoc.render.markdown can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.render.markdown uses a module listed above it, which is the healthy direction.
37→12 anydoc.render.markdown uses anydoc.model✕
- Connections
- 1 pair of types, where a type in anydoc.render.markdown uses a type in anydoc.model.
- The types involved
anydoc.render.markdown.markdown$module→anydoc.model.Document
- Direction
- anydoc.render.markdown uses anydoc.model, so a change to anydoc.model can break anydoc.render.markdown, while a change to anydoc.render.markdown can't break anydoc.model.
- Position
- Below the diagonal: anydoc.render.markdown uses a module listed above it, which is the healthy direction.
37→13 anydoc.render.markdown uses anydoc.model.list✕
- Connections
- 1 pair of types, where a type in anydoc.render.markdown uses a type in anydoc.model.list.
- The types involved
anydoc.render.markdown.markdown$module→anydoc.model.list.List
- Direction
- anydoc.render.markdown uses anydoc.model.list, so a change to anydoc.model.list can break anydoc.render.markdown, while a change to anydoc.render.markdown can't break anydoc.model.list.
- Position
- Below the diagonal: anydoc.render.markdown uses a module listed above it, which is the healthy direction.
37→32 anydoc.render.markdown uses anydoc.formats.docx.content✕
- Connections
- 1 pair of types, where a type in anydoc.render.markdown uses a type in anydoc.formats.docx.content.
- The types involved
anydoc.render.markdown.markdown$module→anydoc.formats.docx.content.Ctx
- Direction
- anydoc.render.markdown uses anydoc.formats.docx.content, so a change to anydoc.formats.docx.content can break anydoc.render.markdown, while a change to anydoc.render.markdown can't break anydoc.formats.docx.content.
- Position
- Below the diagonal: anydoc.render.markdown uses a module listed above it, which is the healthy direction.
38→4 anydoc.render.markdown.inline uses anydoc.model.link✕
- Connections
- 2 pairs of types, where a type in anydoc.render.markdown.inline uses a type in anydoc.model.link.
- The types involved
anydoc.render.markdown.inline.inline$module→anydoc.model.link.ImageSourceanydoc.render.markdown.inline.inline$module→anydoc.model.link.LinkTarget
- Direction
- anydoc.render.markdown.inline uses anydoc.model.link, so a change to anydoc.model.link can break anydoc.render.markdown.inline, while a change to anydoc.render.markdown.inline can't break anydoc.model.link.
- Position
- Below the diagonal: anydoc.render.markdown.inline uses a module listed above it, which is the healthy direction.
38→5 anydoc.render.markdown.inline uses anydoc.model.style✕
- Connections
- 1 pair of types, where a type in anydoc.render.markdown.inline uses a type in anydoc.model.style.
- The types involved
anydoc.render.markdown.inline.inline$module→anydoc.model.style.Style
- Direction
- anydoc.render.markdown.inline uses anydoc.model.style, so a change to anydoc.model.style can break anydoc.render.markdown.inline, while a change to anydoc.render.markdown.inline can't break anydoc.model.style.
- Position
- Below the diagonal: anydoc.render.markdown.inline uses a module listed above it, which is the healthy direction.
38→32 anydoc.render.markdown.inline uses anydoc.formats.docx.content✕
- Connections
- 1 pair of types, where a type in anydoc.render.markdown.inline uses a type in anydoc.formats.docx.content.
- The types involved
anydoc.render.markdown.inline.inline$module→anydoc.formats.docx.content.Ctx
- Direction
- anydoc.render.markdown.inline uses anydoc.formats.docx.content, so a change to anydoc.formats.docx.content can break anydoc.render.markdown.inline, while a change to anydoc.render.markdown.inline can't break anydoc.formats.docx.content.
- Position
- Below the diagonal: anydoc.render.markdown.inline uses a module listed above it, which is the healthy direction.
39→3 anydoc.formats.rtf uses anydoc.model.inline✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.rtf uses a type in anydoc.model.inline.
- The types involved
anydoc.formats.rtf.Destinations→anydoc.model.inline.Inlineanydoc.formats.rtf.Parser→anydoc.model.inline.Inline
- Direction
- anydoc.formats.rtf uses anydoc.model.inline, so a change to anydoc.model.inline can break anydoc.formats.rtf, while a change to anydoc.formats.rtf can't break anydoc.model.inline.
- Position
- Below the diagonal: anydoc.formats.rtf uses a module listed above it, which is the healthy direction.
39→5 anydoc.formats.rtf uses anydoc.model.style✕
- Connections
- 1 pair of types, where a type in anydoc.formats.rtf uses a type in anydoc.model.style.
- The types involved
anydoc.formats.rtf.CharState→anydoc.model.style.Style
- Direction
- anydoc.formats.rtf uses anydoc.model.style, so a change to anydoc.model.style can break anydoc.formats.rtf, while a change to anydoc.formats.rtf can't break anydoc.model.style.
- Position
- Below the diagonal: anydoc.formats.rtf uses a module listed above it, which is the healthy direction.
39→6 anydoc.formats.rtf uses anydoc.package.xml✕
- Connections
- 1 pair of types, where a type in anydoc.formats.rtf uses a type in anydoc.package.xml.
- The types involved
anydoc.formats.rtf.rtf$module→anydoc.package.xml.Element
- Direction
- anydoc.formats.rtf uses anydoc.package.xml, so a change to anydoc.package.xml can break anydoc.formats.rtf, while a change to anydoc.formats.rtf can't break anydoc.package.xml.
- Position
- Below the diagonal: anydoc.formats.rtf uses a module listed above it, which is the healthy direction.
39→8 anydoc.formats.rtf uses anydoc.model.block✕
- Connections
- 1 pair of types, where a type in anydoc.formats.rtf uses a type in anydoc.model.block.
- The types involved
anydoc.formats.rtf.Parser→anydoc.model.block.Block
- Direction
- anydoc.formats.rtf uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.formats.rtf, while a change to anydoc.formats.rtf can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.formats.rtf uses a module listed above it, which is the healthy direction.
39→12 anydoc.formats.rtf uses anydoc.model✕
- Connections
- 3 pairs of types, where a type in anydoc.formats.rtf uses a type in anydoc.model.
- The types involved
anydoc.formats.rtf.CharState→anydoc.model.NoteKindanydoc.formats.rtf.Destinations→anydoc.model.Noteanydoc.formats.rtf.NoteFrame→anydoc.model.NoteKind
- Direction
- anydoc.formats.rtf uses anydoc.model, so a change to anydoc.model can break anydoc.formats.rtf, while a change to anydoc.formats.rtf can't break anydoc.model.
- Position
- Below the diagonal: anydoc.formats.rtf uses a module listed above it, which is the healthy direction.
39→13 anydoc.formats.rtf uses anydoc.model.list✕
- Connections
- 1 pair of types, where a type in anydoc.formats.rtf uses a type in anydoc.model.list.
- The types involved
anydoc.formats.rtf.CharState→anydoc.model.list.MarkerKind
- Direction
- anydoc.formats.rtf uses anydoc.model.list, so a change to anydoc.model.list can break anydoc.formats.rtf, while a change to anydoc.formats.rtf can't break anydoc.model.list.
- Position
- Below the diagonal: anydoc.formats.rtf uses a module listed above it, which is the healthy direction.
39→16 anydoc.formats.rtf uses anydoc.shared.blockstyle✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.rtf uses a type in anydoc.shared.blockstyle.
- The types involved
anydoc.formats.rtf.CharState→anydoc.shared.blockstyle.BlockStyleanydoc.formats.rtf.Parser→anydoc.shared.blockstyle.StyledRun
- Direction
- anydoc.formats.rtf uses anydoc.shared.blockstyle, so a change to anydoc.shared.blockstyle can break anydoc.formats.rtf, while a change to anydoc.formats.rtf can't break anydoc.shared.blockstyle.
- Position
- Below the diagonal: anydoc.formats.rtf uses a module listed above it, which is the healthy direction.
39→20 anydoc.formats.rtf uses anydoc.shared.assets✕
- Connections
- 1 pair of types, where a type in anydoc.formats.rtf uses a type in anydoc.shared.assets.
- The types involved
anydoc.formats.rtf.Parser→anydoc.shared.assets.AssetSink
- Direction
- anydoc.formats.rtf uses anydoc.shared.assets, so a change to anydoc.shared.assets can break anydoc.formats.rtf, while a change to anydoc.formats.rtf can't break anydoc.shared.assets.
- Position
- Below the diagonal: anydoc.formats.rtf uses a module listed above it, which is the healthy direction.
39→21 anydoc.formats.rtf uses anydoc.shared.list✕
- Connections
- 1 pair of types, where a type in anydoc.formats.rtf uses a type in anydoc.shared.list.
- The types involved
anydoc.formats.rtf.Parser→anydoc.shared.list.ListEntry
- Direction
- anydoc.formats.rtf uses anydoc.shared.list, so a change to anydoc.shared.list can break anydoc.formats.rtf, while a change to anydoc.formats.rtf can't break anydoc.shared.list.
- Position
- Below the diagonal: anydoc.formats.rtf uses a module listed above it, which is the healthy direction.
39→27 anydoc.formats.rtf uses anydoc.formats.rtf.tables✕
- Connections
- 1 pair of types, where a type in anydoc.formats.rtf uses a type in anydoc.formats.rtf.tables.
- The types involved
anydoc.formats.rtf.Parser→anydoc.formats.rtf.tables.Prelude
- Direction
- anydoc.formats.rtf uses anydoc.formats.rtf.tables, so a change to anydoc.formats.rtf.tables can break anydoc.formats.rtf, while a change to anydoc.formats.rtf can't break anydoc.formats.rtf.tables.
- Position
- Below the diagonal: anydoc.formats.rtf uses a module listed above it, which is the healthy direction.
39→35 anydoc.formats.rtf uses anydoc.formats.odf.table✕
- Connections
- 1 pair of types, where a type in anydoc.formats.rtf uses a type in anydoc.formats.odf.table.
- The types involved
anydoc.formats.rtf.Parser→anydoc.formats.odf.table.TableState
- Direction
- anydoc.formats.rtf uses anydoc.formats.odf.table, so a change to anydoc.formats.odf.table can break anydoc.formats.rtf, while a change to anydoc.formats.rtf can't break anydoc.formats.odf.table.
- Position
- Below the diagonal: anydoc.formats.rtf uses a module listed above it, which is the healthy direction.
39→40 anydoc.formats.rtf uses anydoc.formats.doc part of a loop✕
- Connections
- 1 pair of types, where a type in anydoc.formats.rtf uses a type in anydoc.formats.doc.
- The types involved
anydoc.formats.rtf.Parser→anydoc.formats.doc.Counters
- Direction
- anydoc.formats.rtf uses anydoc.formats.doc, so a change to anydoc.formats.doc can break anydoc.formats.rtf, while a change to anydoc.formats.rtf can't break anydoc.formats.doc.
- 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.
40→3 anydoc.formats.doc uses anydoc.model.inline✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.doc uses a type in anydoc.model.inline.
- The types involved
anydoc.formats.doc.Assembler→anydoc.model.inline.Inlineanydoc.formats.doc.ParaBuilder→anydoc.model.inline.Inline
- Direction
- anydoc.formats.doc uses anydoc.model.inline, so a change to anydoc.model.inline can break anydoc.formats.doc, while a change to anydoc.formats.doc can't break anydoc.model.inline.
- Position
- Below the diagonal: anydoc.formats.doc uses a module listed above it, which is the healthy direction.
40→5 anydoc.formats.doc uses anydoc.model.style✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.doc uses a type in anydoc.model.style.
- The types involved
anydoc.formats.doc.Assembler→anydoc.model.style.Styleanydoc.formats.doc.ParaBuilder→anydoc.model.style.Style
- Direction
- anydoc.formats.doc uses anydoc.model.style, so a change to anydoc.model.style can break anydoc.formats.doc, while a change to anydoc.formats.doc can't break anydoc.model.style.
- Position
- Below the diagonal: anydoc.formats.doc uses a module listed above it, which is the healthy direction.
40→7 anydoc.formats.doc uses anydoc.formats.doc.sprm✕
- Connections
- 3 pairs of types, where a type in anydoc.formats.doc uses a type in anydoc.formats.doc.sprm.
- The types involved
anydoc.formats.doc.DocRow→anydoc.formats.doc.sprm.Tapanydoc.formats.doc.EffectivePap→anydoc.formats.doc.sprm.PapDeltaanydoc.formats.doc.RunProps→anydoc.formats.doc.sprm.PapDelta
- Direction
- anydoc.formats.doc uses anydoc.formats.doc.sprm, so a change to anydoc.formats.doc.sprm can break anydoc.formats.doc, while a change to anydoc.formats.doc can't break anydoc.formats.doc.sprm.
- Position
- Below the diagonal: anydoc.formats.doc uses a module listed above it, which is the healthy direction.
40→8 anydoc.formats.doc uses anydoc.model.block✕
- Connections
- 2 pairs of types, where a type in anydoc.formats.doc uses a type in anydoc.model.block.
- The types involved
anydoc.formats.doc.Assembler→anydoc.model.block.Blockanydoc.formats.doc.DocRow→anydoc.model.block.Block
- Direction
- anydoc.formats.doc uses anydoc.model.block, so a change to anydoc.model.block can break anydoc.formats.doc, while a change to anydoc.formats.doc can't break anydoc.model.block.
- Position
- Below the diagonal: anydoc.formats.doc uses a module listed above it, which is the healthy direction.
40→16 anydoc.formats.doc uses anydoc.shared.blockstyle✕
- Connections
- 1 pair of types, where a type in anydoc.formats.doc uses a type in anydoc.shared.blockstyle.
- The types involved
anydoc.formats.doc.Assembler→anydoc.shared.blockstyle.StyledRun
- Direction
- anydoc.formats.doc uses anydoc.shared.blockstyle, so a change to anydoc.shared.blockstyle can break anydoc.formats.doc, while a change to anydoc.formats.doc can't break anydoc.shared.blockstyle.
- Position
- Below the diagonal: anydoc.formats.doc uses a module listed above it, which is the healthy direction.
40→17 anydoc.formats.doc uses anydoc.formats.doc.stsh✕
- Connections
- 1 pair of types, where a type in anydoc.formats.doc uses a type in anydoc.formats.doc.stsh.
- The types involved
anydoc.formats.doc.Assembler→anydoc.formats.doc.stsh.Stylesheet
- Direction
- anydoc.formats.doc uses anydoc.formats.doc.stsh, so a change to anydoc.formats.doc.stsh can break anydoc.formats.doc, while a change to anydoc.formats.doc can't break anydoc.formats.doc.stsh.
- Position
- Below the diagonal: anydoc.formats.doc uses a module listed above it, which is the healthy direction.
40→20 anydoc.formats.doc uses anydoc.shared.assets✕
- Connections
- 1 pair of types, where a type in anydoc.formats.doc uses a type in anydoc.shared.assets.
- The types involved
anydoc.formats.doc.Assembler→anydoc.shared.assets.AssetSink
- Direction
- anydoc.formats.doc uses anydoc.shared.assets, so a change to anydoc.shared.assets can break anydoc.formats.doc, while a change to anydoc.formats.doc can't break anydoc.shared.assets.
- Position
- Below the diagonal: anydoc.formats.doc uses a module listed above it, which is the healthy direction.
40→21 anydoc.formats.doc uses anydoc.shared.list✕
- Connections
- 1 pair of types, where a type in anydoc.formats.doc uses a type in anydoc.shared.list.
- The types involved
anydoc.formats.doc.Assembler→anydoc.shared.list.ListEntry
- Direction
- anydoc.formats.doc uses anydoc.shared.list, so a change to anydoc.shared.list can break anydoc.formats.doc, while a change to anydoc.formats.doc can't break anydoc.shared.list.
- Position
- Below the diagonal: anydoc.formats.doc uses a module listed above it, which is the healthy direction.
40→23 anydoc.formats.doc uses anydoc.formats.doc.lists✕
- Connections
- 3 pairs of types, where a type in anydoc.formats.doc uses a type in anydoc.formats.doc.lists.
- The types involved
anydoc.formats.doc.Assembler→anydoc.formats.doc.lists.Listsanydoc.formats.doc.Counters→anydoc.formats.doc.lists.ListDefanydoc.formats.doc.doc$module→anydoc.formats.doc.lists.ListDef
- Direction
- anydoc.formats.doc uses anydoc.formats.doc.lists, so a change to anydoc.formats.doc.lists can break anydoc.formats.doc, while a change to anydoc.formats.doc can't break anydoc.formats.doc.lists.
- Position
- Below the diagonal: anydoc.formats.doc uses a module listed above it, which is the healthy direction.
40→39 anydoc.formats.doc uses anydoc.formats.rtf✕
- Connections
- 1 pair of types, where a type in anydoc.formats.doc uses a type in anydoc.formats.rtf.
- The types involved
anydoc.formats.doc.ParaBuilder→anydoc.formats.rtf.FieldFrame
- Direction
- anydoc.formats.doc uses anydoc.formats.rtf, so a change to anydoc.formats.rtf can break anydoc.formats.doc, while a change to anydoc.formats.doc can't break anydoc.formats.rtf.
- Position
- Below the diagonal: anydoc.formats.doc uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 65 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | High / Critical |
Roadmap
Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json; Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json. | +2.5 pts | Low | Platform End-of-Life |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). | +2.3 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.5 pts | Low | Dependency Vulnerabilities |
| 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. | +2.7 pts | Medium | Architecture documentation |
| Enable Dependabot/Renovate or a dependency-review gate. | +1.4 pts | Medium | Security & performance tooling |
| 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. | +1.4 pts | Medium | Deployment & Rollback |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +0.6 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium advisory (unsound): REDACTED |
| src/formats/sheet/xls.rs | 7.0 | Near-clean | Cyclomatic Complexity: anydoc::formats::sheet::xls::read_sheet (cyclomatic 68) |
| src/formats/docx/content.rs | 7.0 | Near-clean | Cyclomatic Complexity: InlineWalker::walk_run_content (cyclomatic 23) |
| node/src/document.rs | 7.0 | Near-clean | Code Duplication: Edited copies of one member (3 members, 26+ corresponding lines) |
| src/formats/sheet/numfmt.rs | 7.0 | Near-clean | Cyclomatic Complexity: anydoc::formats::sheet::numfmt::resolve_number (cyclomatic 34) |
| src/formats/rtf/mod.rs | 7.0 | Near-clean | Cyclomatic Complexity: Parser::text_control (cyclomatic 27) |
| src/shared/html.rs | 7.0 | Near-clean | Cyclomatic Complexity: Builder::walk_elem (cyclomatic 23) |
| src/formats/pptx/mod.rs | 7.0 | Near-clean | Cyclomatic Complexity: anydoc::formats::pptx::parse (cyclomatic 21) |
| src/render/markdown/inline.rs | 7.0 | Near-clean | Cyclomatic Complexity: anydoc::render::markdown::inline::normalize (cyclomatic 21) |
| src/formats/sheet/xlsx.rs | 7.1 | Near-clean | Cyclomatic Complexity: anydoc::formats::sheet::xlsx::build_table (cyclomatic 30) |
| src/formats/rtf/tables.rs | 7.1 | Near-clean | Cyclomatic Complexity: anydoc::formats::rtf::tables::parse_overrides (cyclomatic 28) |
| src/formats/doc/mod.rs | 7.1 | Near-clean | Cyclomatic Complexity: Assembler::build_blocks (cyclomatic 23) |
| src/formats/odf/text.rs | 7.1 | Near-clean | Cyclomatic Complexity: anydoc::formats::odf::text::parse_list (cyclomatic 19) |
| src/formats/doc/lists.rs | 7.1 | Near-clean | Cyclomatic Complexity: anydoc::formats::doc::lists::parse_plf_lfo (cyclomatic 18) |
| src/formats/sheet/xlsb.rs | 7.1 | Near-clean | Cyclomatic Complexity: anydoc::formats::sheet::xlsb::read_sheet (cyclomatic 17) |
| src/formats/ppt/mod.rs | 7.2 | Near-clean | Cyclomatic Complexity: Extractor::flush_shape (cyclomatic 23) |
| src/formats/ppt/styletext.rs | 7.2 | Near-clean | Cyclomatic Complexity: anydoc::formats::ppt::styletext::parse_pf_exception (cyclomatic 19) |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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.9, the weighted average across measured dimensions.
What we checked — 46 dimensions across the health lenses
- 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, 243 of 262 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- 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.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- 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 Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python 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 package.json, 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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (9 contributor(s) across 135 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 8 hold 1.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- 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 Python, Rust 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 Python, Rust 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.
- 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.
- 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.
- 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.
- X5 Nullable reference types — 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python, Rust 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.
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
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
Dimensions
D1 · Cyclomatic Complexity
46 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was anydoc::formats::sheet::xls::read_sheet at 68. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being anydoc::shared::math::tex::symbol at 222 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 6 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with anydoc::formats::sheet::xls::read_sheet (cyclomatic 68), anydoc::render::markdown::escape::escape_text (cyclomatic 47), anydoc::shared::math::mathml::walk_elem (cyclomatic 40). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cyclomatic Complexity from 4.3 to about 6.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
82 method(s) exceeded the cognitive complexity threshold of 15; the worst was anydoc::formats::sheet::xls::read_sheet at 123.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with anydoc::formats::sheet::xls::read_sheet (cognitive 123). — Refactoring it lifts Cognitive Complexity from 2.0 to about 3.2/10.
D3 · God Classes
10 god class(es) detected.
What to do
- Resolve the 5 FileTooLong finding(s) in God Classes — start with mod.rs (2), content.rs, xls.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 FunctionTooLong finding(s) in God Classes — start with xls.rs, tex.rs, mod.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
16 duplicated block group(s) detected. 3.3 % of the production lines (851 of 25,854) are in a reported copy. A further 14 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with mod.rs (2), inline.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with mod.rs, xml.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with styles.rs, document.rs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
6 production modules (Cargo+npm+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 4 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 38 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 2 measured tier(s). JavaScript/TypeScript (node:test via `npm ci --ignore-scripts` in node/ (1 tests)): measured (0 flaky); Rust (repository root, 43 test files): measured (0 flaky).
D12 · Dependency Hygiene
9 outdated, 0 yanked direct Cargo dependencies. 17 of 18 direct crates were graded against crates.io (0 not published there, 1 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 178 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. 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 Python pyproject.toml/requirements.txt (pip/uv/Poetry) and package.json, 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.
D15 · Churn × Complexity Hotspots
Top hotspots: src/render/markdown/escape.rs (5×47=235); src/render/markdown/inline.rs (6×21=126); node/cli.js (3×25=75)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with escape.rs, inline.rs, cli.js. — One of this dimension's main actionable groups (4 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 25854 LoC (0.0/KLoC) → score 10.0. 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 6 document(s) read across 3 unit(s).
D26 · Project Cohesion
1 of 4 build units (Cargo, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
65 finding(s): 0 critical, 63 high, 1 medium, 1 low. 59 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 59 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (59 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 1 high, 2 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 68 of the 96 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- 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 — start with REDACTED. — 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 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 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.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
AC5 · ARIA correctness
AC6 · Visual & motion safety
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `node`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- `bench/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`. — bench/package.json:4
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
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.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X2 · Cancellation propagation
X21 · Side-effecting pattern guard
X30 · Support guard that admits what it rejects
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 85% | Adequate — gated by D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 94% | Exemplary | Solid. |
| Maturity | 72% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 68% | Strong | Solid. |
| Security | 64% | Adequate | Largest drag on the score — prioritise here. |
| Accessibility | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — Not applicable: 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 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.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. 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. 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 — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~2852 lines of test source are present (.py, .rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read html yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, 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"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .py, .rs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no 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 node:test suite in node/ ran and not one test passed (const error = new Error(), so the coverage report describes 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 (11 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 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 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 — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface: 80 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 7% of this repository's production lines — rust (24,763 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 3% of this repository's production lines — rust (24,763 lines), python (1,091 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — X3 reached only 7% of this repository's production lines — rust (24,763 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.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 64 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 177 finding(s)
- anydoc::formats::sheet::xls::read_sheet (cognitive 123) src/formats/sheet/xls.rs:489
- anydoc::formats::sheet::numfmt::resolve_number (cognitive 48) src/formats/sheet/numfmt.rs:599
- anydoc::formats::sheet::xlsx::build_table (cognitive 47) src/formats/sheet/xlsx.rs:391
- anydoc::formats::odf::walk_shapes (cognitive 45) src/formats/odf/mod.rs:89
- anydoc::formats::doc::lists::parse_plf_lfo (cognitive 42) src/formats/doc/lists.rs:193
- anydoc::formats::docx::content::parse_table (cognitive 42) src/formats/docx/content.rs:763
- anydoc::formats::odf::text::walk_inlines (cognitive 41) src/formats/odf/text.rs:312
- anydoc::render::markdown::escape::escape_text (cognitive 40) src/render/markdown/escape.rs:141
- anydoc::formats::rtf::tables::parse_stylesheet (cognitive 39) src/formats/rtf/tables.rs:164
- anydoc::shared::grid::build_edge_table (cognitive 39) src/shared/grid.rs:37
- anydoc::formats::pptx::parse (cognitive 38) src/formats/pptx/mod.rs:53
- anydoc::formats::doc::parse_fkp_page (cognitive 36) src/formats/doc/mod.rs:465
- anydoc::formats::rtf::tables::parse_listtable (cognitive 35) src/formats/rtf/tables.rs:248
- anydoc::formats::rtf::tables::parse_overrides (cognitive 35) src/formats/rtf/tables.rs:328
- anydoc::shared::math::mathml::walk_elem (cognitive 34) src/shared/math/mathml.rs:48
- anydoc::formats::sheet::xlsx::read_sheet (cognitive 33) src/formats/sheet/xlsx.rs:248
- anydoc::render::markdown::inline::normalize (cognitive 33) src/render/markdown/inline.rs:29
- anydoc::formats::odf::text::parse_list (cognitive 32) src/formats/odf/text.rs:142
- anydoc::shared::list::build_lists (cognitive 32) src/shared/list.rs:48
- anydoc::formats::doc::extract_text (cognitive 31) src/formats/doc/mod.rs:331
- anydoc::shared::header::resolve_header_rows (cognitive 31) src/shared/header.rs:39
- anydoc::formats::sheet::xlsb::read_sheet (cognitive 30) src/formats/sheet/xlsb.rs:217
- anydoc::render::markdown::table::cell_block_text (cognitive 30) src/render/markdown/table.rs:103
- anydoc::render::markdown::render_block (cognitive 29) src/render/markdown/mod.rs:160
- anydoc::formats::sheet::numfmt::emit (cognitive 28) src/formats/sheet/numfmt.rs:831
- anydoc::formats::sheet::xls::read_sheet (cyclomatic 68) src/formats/sheet/xls.rs:489
- anydoc::render::markdown::escape::escape_text (cyclomatic 47) src/render/markdown/escape.rs:141
- anydoc::shared::math::mathml::walk_elem (cyclomatic 40) src/shared/math/mathml.rs:48
- anydoc::formats::sheet::numfmt::resolve_number (cyclomatic 34) src/formats/sheet/numfmt.rs:599
- anydoc::shared::math::tex::fold_alnum (cyclomatic 33) src/shared/math/tex.rs:235
- anydoc::formats::sheet::numfmt::parse_section (cyclomatic 32) src/formats/sheet/numfmt.rs:379
- anydoc::formats::sheet::xlsx::build_table (cyclomatic 30) src/formats/sheet/xlsx.rs:391
- anydoc::formats::rtf::tables::parse_overrides (cyclomatic 28) src/formats/rtf/tables.rs:328
- anydoc::shared::math::omml::walk_elem (cyclomatic 28) src/shared/math/omml.rs:42
- anydoc::formats::doc::sprm::apply_pap_sprms (cyclomatic 24) src/formats/doc/sprm.rs:153
- anydoc::formats::rtf::tables::parse_stylesheet (cyclomatic 24) src/formats/rtf/tables.rs:164
- anydoc::formats::rtf::tables::parse_listtable (cyclomatic 24) src/formats/rtf/tables.rs:248
- anydoc::formats::odf::walk_shapes (cyclomatic 21) src/formats/odf/mod.rs:89
- anydoc::formats::pptx::parse (cyclomatic 21) src/formats/pptx/mod.rs:53
- anydoc::formats::sheet::numfmt::emit (cyclomatic 21) src/formats/sheet/numfmt.rs:831
- anydoc::formats::sheet::numfmt::render_fraction (cyclomatic 21) src/formats/sheet/numfmt.rs:934
- anydoc::formats::sheet::xls::read_globals (cyclomatic 21) src/formats/sheet/xls.rs:355
- anydoc::render::markdown::render_block (cyclomatic 21) src/render/markdown/mod.rs:160
- anydoc::render::markdown::inline::normalize (cyclomatic 21) src/render/markdown/inline.rs:29
- anydoc::render::markdown::table::cell_block_text (cyclomatic 21) src/render/markdown/table.rs:103
- anydoc::shared::header::resolve_header_rows (cyclomatic 20) src/shared/header.rs:39
- anydoc::formats::odf::text::parse_list (cyclomatic 19) src/formats/odf/text.rs:142
- anydoc::formats::odf::text::walk_inlines (cyclomatic 19) src/formats/odf/text.rs:312
- anydoc::formats::ppt::styletext::parse_pf_exception (cyclomatic 19) src/formats/ppt/styletext.rs:86
- anydoc::formats::sheet::xlsx::read_sheet (cyclomatic 19) src/formats/sheet/xlsx.rs:248
- FileTooLong: rtf/mod.rs src/formats/rtf/mod.rs
- FileTooLong: doc/mod.rs src/formats/doc/mod.rs
- FileTooLong: docx/content.rs src/formats/docx/content.rs
- FileTooLong: sheet/xls.rs src/formats/sheet/xls.rs
- FileTooLong: shared/html.rs src/shared/html.rs
- Parser::text_control (cyclomatic 27) src/formats/rtf/mod.rs:765
- Parser::table_control (cyclomatic 23) src/formats/rtf/mod.rs:845
- Parser::run (cyclomatic 21) src/formats/rtf/mod.rs:650
- Parser::object_control (cyclomatic 21) src/formats/rtf/mod.rs:935
- Hotspot: src/render/markdown/escape.rs src/render/markdown/escape.rs:141
- Hotspot: src/render/markdown/inline.rs src/render/markdown/inline.rs:29
- Hotspot: node/cli.js node/cli.js:69
- Hotspot: src/render/markdown/table.rs src/render/markdown/table.rs:103
- FunctionTooLong: anydoc::formats::sheet::xls::read_sheet src/formats/sheet/xls.rs:489
- FunctionTooLong: anydoc::shared::math::tex::symbol src/shared/math/tex.rs:314
- FunctionTooLong: anydoc::formats::pptx::parse src/formats/pptx/mod.rs:53
- FunctionTooLong: anydoc::shared::math::mathml::walk_elem src/shared/math/mathml.rs:48
- Builder::walk_elem (cyclomatic 23) src/shared/html.rs:360
- Builder::parse_list (cyclomatic 19) src/shared/html.rs:536
- Builder::parse_table (cyclomatic 19) src/shared/html.rs:612
- InlineWalker::walk_run_content (cognitive 33) src/formats/docx/content.rs:482
- InlineWalker::walk (cognitive 32) src/formats/docx/content.rs:381
- InlineWalker::walk_drawing (cognitive 23) src/formats/docx/content.rs:550
- Builder::parse_table (cognitive 29) src/shared/html.rs:612
- Builder::walk_elem (cognitive 28) src/shared/html.rs:360
- Builder::parse_list (cognitive 24) src/shared/html.rs:536
- Duplicated block (9 lines × 2) src/formats/odf/mod.rs:166
- Duplicated block (9 lines × 2) src/render/markdown/inline.rs:382
- Duplicated block (9 lines × 2) src/formats/pptx/mod.rs:418
- InlineWalker::walk_run_content (cyclomatic 23) src/formats/docx/content.rs:482
- InlineWalker::walk (cyclomatic 20) src/formats/docx/content.rs:381
- Parser::run (cognitive 37) src/formats/rtf/mod.rs:650
- Parser::table_control (cognitive 17) src/formats/rtf/mod.rs:845
- GridBuilder::finish (cognitive 18) src/model/table.rs:234
- GridBuilder::place (cognitive 16) src/model/table.rs:169
- Edited copy of a member (9 corresponding lines) src/formats/rtf/mod.rs:124
- Edited copy of a member (9 corresponding lines) src/package/xml.rs:168
- Edited copy of a member (10 corresponding lines) src/formats/docx/styles.rs:134
- Edited copy of a member (10 corresponding lines) node/src/document.rs:425
- Edited copy of a member (8 corresponding lines) src/render/markdown/escape.rs:293
- Edited copy of a member (8 corresponding lines) node/src/document.rs:451
- Duplicated block (11 lines × 2) src/formats/doc/lists.rs:261
- Duplicated block (11 lines × 2) src/formats/sheet/xls.rs:373
- Duplicated block (8 lines × 2) node/src/document.rs:345
- Duplicated block (8 lines × 2) src/formats/doc/lists.rs:31
- Duplicated block (7 lines × 2) node/src/document.rs:299
- Duplicated block (7 lines × 2) node/src/document.rs:462
- cli.parseArgs (cyclomatic 25) node/cli.js:69
- Assembler::build_blocks (cyclomatic 23) src/formats/doc/mod.rs:694
- Extractor::flush_shape (cyclomatic 23) src/formats/ppt/mod.rs:509
- Extractor::flush_shape (cognitive 46) src/formats/ppt/mod.rs:509
- OdfStyles::collect (cognitive 29) src/formats/odf/styles.rs:88
- Assembler::build_blocks (cognitive 28) src/formats/doc/mod.rs:694
- Stylesheet::add (cognitive 27) src/shared/html.rs:90
- cli.parseArgs (cognitive 24) node/cli.js:69
- Lexer::control (cognitive 22) src/formats/rtf/lexer.rs:47
- main (cognitive 20) node/cli.js:151
- REDACTED
- ClassTooLong: Parser src/formats/rtf/mod.rs:608
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copies of one member (3 members, 26+ corresponding lines) node/src/document.rs:152
- Edited copies of one member (3 members, 27+ corresponding lines) node/src/document.rs:66
- Edited copy of a member (19 corresponding lines) src/formats/epub/mod.rs:180
- Edited copies of one member (3 members, 13+ corresponding lines) node/src/document.rs:250
- Edited copy of a member (14 corresponding lines) node/src/document.rs:344
- Edited copies of one member (3 members, 16+ corresponding lines) node/src/document.rs:379
- Edited copies of one member (4 members, 13+ corresponding lines) src/formats/docx/content.rs:646
- Edited copies of one member (3 members, 8+ corresponding lines) node/src/document.rs:218
- Duplicated block (20 lines × 2) src/formats/ppt/styletext.rs:95
- Duplicated block (16 lines × 2) src/formats/sheet/xlsb.rs:66
- Duplicated block (14 lines × 2) src/formats/sheet/xlsb.rs:97
- Duplicated block (11–12 lines × 2) src/formats/sheet/xls.rs:574
- Duplicated block (13 lines × 3) node/src/document.rs:50
- Duplicated block (14 lines × 3) node/src/document.rs:135
- Duplicated block (6 lines × 2) src/formats/sheet/xlsb.rs:374
- End-of-life runtime: Node.js 20 node/package.json:39
- Off the main sequence: anydoc
- Coverage not measured — JavaScript/TypeScript suite
Minor — 12 finding(s)
- Duplicated predicate node/test.mjs:50
- Duplicated predicate src/formats/sheet/xlsb.rs:106
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No dependency-update automation bench/package.json:4
- Silent fallback default on parse failure REDACTED:177
Minor — 9 finding(s)
- Outdated: encoding_rs
- Outdated: flate2
- Outdated: js-sys
- Outdated: log
- Outdated: napi
- Outdated: napi-build
- Outdated: napi-derive
- Outdated: pdf-inspector
- Outdated: wasm-bindgen
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9df71e4329bc4dca8c0e9dcdc9183154/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9df71e4329bc4dca8c0e9dcdc9183154/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 65 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 3 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |