Executive summary
rust-lang/mdBook falls short of our standard for a preview release, held back most by its Security and Compliance lens, the code's security and compliance. It scores 47 out of 100 and is rated Adequate, and 13 of its 76 critical findings are security problems in the build pipeline.
Security and Compliance, at 38, is the weakest lens and counts most in the score. The best first step is pinning the third-party scripts, worth about 8 points. Recording design decisions comes next, worth about 3 points. Raising Security and Compliance to 68 would lift the score to about 54.
Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two pipeline steps install packages that can change without warning. Pinning each tool to an exact version and pinning what the pipeline installs would close both risks. The control that only works with a mouse needs to work with the keyboard, or to become a real button.
The product code is 12,399 lines, about β¬15,000 to rebuild.
If Security and Compliance rose from 38 to 68, the lowest score rated Strong, the score would rise from 47 to about 54.
New since the last survey: 48 findings
- Cognitive Complexity Β· mdbook_core::utils::fs::copy_files_except_ignored (cognitive 31) crates/mdbook-core/src/utils/fs.rs
- God Classes Β· MethodTooLong: HtmlHandlebars.render crates/mdbook-html/src/html_handlebars/hbs_renderer.rs
- God Classes Β· FileTooLong: html_handlebars/hbs_renderer.rs crates/mdbook-html/src/html_handlebars/hbs_renderer.rs
- Code Duplication Β· Edited copy of a member (21 corresponding lines) crates/mdbook-core/src/utils/html.rs
- Code Duplication Β· Edited copy of a member (17 corresponding lines) crates/mdbook-driver/src/builtin_preprocessors/links.rs
- Code Duplication Β· Edited copy of a member (17 corresponding lines) crates/mdbook-driver/src/mdbook.rs
- Code Duplication Β· Duplicated block (5 lines × 2) crates/mdbook-html/src/html_handlebars/hbs_renderer.rs
- Code Coverage Β· Low coverage: crates/mdbook-compare/src/main.rs crates/mdbook-compare/src/main.rs
- Code Coverage Β· Low coverage: crates/mdbook-driver/src/builtin_renderers/markdown_renderer.rs crates/mdbook-driver/src/builtin_renderers/markdown_renderer.rs
- Code Coverage Β· Low coverage: crates/xtask/src/changelog.rs crates/xtask/src/changelog.rs
- Code Coverage Β· Low coverage: crates/xtask/src/main.rs crates/xtask/src/main.rs
- Code Coverage Β· Low coverage: guide/guide-helper/src/lib.rs guide/guide-helper/src/lib.rs
- Code Coverage Β· Low coverage: guide/guide-helper/src/main.rs guide/guide-helper/src/main.rs
- Code Coverage Β· Low coverage: src/cmd/clean.rs src/cmd/clean.rs
- Code Coverage Β· Low coverage: src/cmd/init.rs src/cmd/init.rs
- Code Coverage Β· Low coverage: src/cmd/serve.rs src/cmd/serve.rs
- Code Coverage Β· Low coverage: src/cmd/watch.rs src/cmd/watch.rs
- Code Coverage Β· Low coverage: src/cmd/watch/native.rs src/cmd/watch/native.rs
- Code Coverage Β· Low coverage: src/main.rs src/main.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.build::no_reserved_filename tests/testsuite/build.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.includes::multiline_include tests/testsuite/includes.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.index::index_rewrite tests/testsuite/index.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.index::readme_to_index tests/testsuite/index.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.playground::disabled_playground tests/testsuite/playground.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.print::chapter_no_h1 tests/testsuite/print.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.print::noindex tests/testsuite/print.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.redirects::redirects_are_emitted_correctly tests/testsuite/redirects.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.renderer::backends_receive_render_context_via_stdin tests/testsuite/renderer.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.renderer::failing_command tests/testsuite/renderer.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.rendering::canonical_url_site_root tests/testsuite/rendering.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.rendering::code_block_in_list tests/testsuite/rendering.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.rendering::edit_url_template_explicit_src tests/testsuite/rendering.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.rendering::first_chapter_is_copied_as_index_even_if_not_first_elem tests/testsuite/rendering.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.rendering::heading_with_unbalanced_html tests/testsuite/rendering.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.rendering::language_rust_playground tests/testsuite/rendering.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.rendering::unbalanced_html_tags tests/testsuite/rendering.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.test::test_individual_chapter tests/testsuite/test.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.theme::custom_fonts_css tests/testsuite/theme.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.theme::empty_fonts_css tests/testsuite/theme.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.theme::theme_fonts_copied tests/testsuite/theme.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.toc::check_second_toc_level tests/testsuite/toc.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.toc::summary_with_markdown_formatting tests/testsuite/toc.rs
- Churn × Complexity Hotspots Β· Hotspot: crates/mdbook-html/src/html_handlebars/hbs_renderer.rs crates/mdbook-html/src/html_handlebars/hbs_renderer.rs
- Dependency Vulnerabilities Β· REDACTED
- Exception handling Β· Swallowed exception (empty catch) crates/mdbook-html/front-end/js/book.js
- Exception handling Β· Swallowed exception (empty catch) crates/mdbook-html/front-end/js/book.js
- Exception handling Β· Swallowed exception (empty catch) crates/mdbook-html/front-end/js/book.js
- Exception handling Β· Swallowed exception (empty catch) crates/mdbook-html/front-end/js/book.js
Fixed since the last survey: 36 findings
- Cognitive Complexity Β· mdbook_core::utils::fs::copy_files_except_ext (cognitive 26) crates/mdbook-core/src/utils/fs.rs
- Test Reliability Β· Flaky test: mdbook::testsuite.build::create_missing
- Test Reliability Β· Flaky test: mdbook::testsuite.build::dest_dir_relative_path
- Test Reliability Β· Flaky test: mdbook::testsuite.build::failure_on_missing_file
- Test Reliability Β· Flaky test: mdbook::testsuite.config::bad_config_top_level
- Test Reliability Β· Flaky test: mdbook::testsuite.config::config_json_from_env
- Test Reliability Β· Flaky test: mdbook::testsuite.config::env_invalid_config_key
- Test Reliability Β· Flaky test: mdbook::testsuite.includes::recursive_include
- Test Reliability Β· Flaky test: mdbook::testsuite.includes::unclosed_quote
- Test Reliability Β· Flaky test: mdbook::testsuite.init::basic_init
- Test Reliability Β· Flaky test: mdbook::testsuite.init::init_api
- Test Reliability Β· Flaky test: mdbook::testsuite.init::no_git_config_with_title
- Test Reliability Β· Flaky test: mdbook::testsuite.markdown::footnotes
- Test Reliability Β· Flaky test: mdbook::testsuite.markdown::tables
- Test Reliability Β· Flaky test: mdbook::testsuite.preprocessor::missing_optional_not_fatal
- Test Reliability Β· Flaky test: mdbook::testsuite.preprocessor::nop_preprocessor
- Test Reliability Β· Flaky test: mdbook::testsuite.print::relative_links
- Test Reliability Β· Flaky test: mdbook::testsuite.renderer::missing_optional_not_fatal
- Test Reliability Β· Flaky test: mdbook::testsuite.renderer::missing_renderer
- Test Reliability Β· Flaky test: mdbook::testsuite.rendering::default_rust_edition
- Test Reliability Β· Flaky test: mdbook::testsuite.rendering::fontawesome_error_message
- Test Reliability Β· Flaky test: mdbook::testsuite.rendering::html_blocks
- Test Reliability Β· Flaky test: mdbook::testsuite.rendering::unclosed_html_tags
- Test Reliability Β· Flaky test: mdbook::testsuite.search::chapter_settings_validation_error
- Test Reliability Β· Flaky test: mdbook::testsuite.test::failing_tests
- Test Reliability Β· Flaky test: mdbook::testsuite.theme::fonts_css
- Test Reliability Β· Flaky test: mdbook::testsuite.toc::check_link_target_fallback
- Test Reliability Β· Flaky test: mdbook::testsuite.toc::check_spacers
- Dependency Vulnerabilities Β· Medium advisory (unsound): RUSTSEC-2026-0386 REDACTED
- Exception handling Β· Swallowed exception (empty catch) crates/mdbook-html/front-end/js/book.js
- Exception handling Β· Swallowed exception (empty catch) crates/mdbook-html/front-end/js/book.js
- Exception handling Β· Swallowed exception (empty catch) crates/mdbook-html/front-end/js/book.js
- Exception handling Β· Swallowed exception (empty catch) crates/mdbook-html/front-end/js/book.js
- Page structure Β· Page without a main landmark REDACTED
- Page structure Β· Data table has no header cells crates/mdbook-html/front-end/templates/toc.js.hbs
- A11y enforcement Β· Accessibility enforcement below the top rung
Rebuild cost: about β¬15,000 Β· Estimate
| Cost to rebuild | β¬4,900 to β¬25,000, for 81 to 258 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 47. 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 | Small: 12,399 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 crates.mdbook-html.front-end.js | 2 crates.mdbook-html.front-end.playground_editor | 3 crates.mdbook-html.front-end.searcher | 4 guide_helper.main | 5 mdbook | 6 mdbook.cmd.clean | 7 mdbook.cmd.init | 8 mdbook.cmd.serve | 9 mdbook.cmd.test | 10 mdbook.cmd.watch | 11 mdbook.cmd.watch.native | 12 mdbook_core.book | 13 mdbook_core.config | 14 mdbook_markdown | 15 mdbook_driver.init | 16 mdbook_html.html | 17 mdbook_html.theme | 18 mdbook_preprocessor | 19 mdbook_renderer | 20 mdbook_summary | 21 mdbook_wordcount | 22 guide_helper | 23 mdbook_driver.builtin_preprocessors.cmd | 24 mdbook_driver.builtin_preprocessors.index | 25 mdbook_driver.builtin_preprocessors.links | 26 mdbook_driver.builtin_renderers | 27 mdbook_driver.builtin_renderers.markdown_renderer | 28 mdbook_driver.mdbook | 29 mdbook_html.html.print | 30 mdbook_html.html.tree | 31 mdbook_html.html_handlebars.hbs_renderer | 32 mdbook_html.html_handlebars.helpers.fontawesome | 33 mdbook_html.html_handlebars.helpers.resources | 34 mdbook_html.html_handlebars.helpers.toc | 35 mdbook_html.html_handlebars.static_files | 36 mdbook.cmd.command_prelude | 37 mdbook.cmd.watch.poller | 38 mdbook_driver.load | 39 mdbook_html.html.serialize | 40 mdbook_html.html_handlebars.search |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 crates.mdbook-html.front-end.js | ||||||||||||||||||||||||||||||||||||||||
| 2 crates.mdbook-html.front-end.playground_editor | ||||||||||||||||||||||||||||||||||||||||
| 3 crates.mdbook-html.front-end.searcher | ||||||||||||||||||||||||||||||||||||||||
| 4 guide_helper.main | ||||||||||||||||||||||||||||||||||||||||
| 5 mdbook | ||||||||||||||||||||||||||||||||||||||||
| 6 mdbook.cmd.clean | ||||||||||||||||||||||||||||||||||||||||
| 7 mdbook.cmd.init | ||||||||||||||||||||||||||||||||||||||||
| 8 mdbook.cmd.serve | ||||||||||||||||||||||||||||||||||||||||
| 9 mdbook.cmd.test | ||||||||||||||||||||||||||||||||||||||||
| 10 mdbook.cmd.watch | ||||||||||||||||||||||||||||||||||||||||
| 11 mdbook.cmd.watch.native | ||||||||||||||||||||||||||||||||||||||||
| 12 mdbook_core.book | ||||||||||||||||||||||||||||||||||||||||
| 13 mdbook_core.config | ||||||||||||||||||||||||||||||||||||||||
| 14 mdbook_markdown | ||||||||||||||||||||||||||||||||||||||||
| 15 mdbook_driver.init | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 mdbook_html.html | 2 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 mdbook_html.theme | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 mdbook_preprocessor | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 mdbook_renderer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 mdbook_summary | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 mdbook_wordcount | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 guide_helper | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 mdbook_driver.builtin_preprocessors.cmd | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 24 mdbook_driver.builtin_preprocessors.index | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 mdbook_driver.builtin_preprocessors.links | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 mdbook_driver.builtin_renderers | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 mdbook_driver.builtin_renderers.markdown_renderer | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 mdbook_driver.mdbook | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 mdbook_html.html.print | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 mdbook_html.html.tree | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 mdbook_html.html_handlebars.hbs_renderer | 2 | 5 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 32 mdbook_html.html_handlebars.helpers.fontawesome | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 mdbook_html.html_handlebars.helpers.resources | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 mdbook_html.html_handlebars.helpers.toc | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 mdbook_html.html_handlebars.static_files | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 mdbook.cmd.command_prelude | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 mdbook.cmd.watch.poller | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 mdbook_driver.load | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 mdbook_html.html.serialize | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 mdbook_html.html_handlebars.search | 1 | 2 | 1 | 1 |
15β13 mdbook_driver.init uses mdbook_core.config✕
- Connections
- 1 pair of types, where a type in mdbook_driver.init uses a type in mdbook_core.config.
- The types involved
mdbook_driver.init.BookBuilderβmdbook_core.config.Config
- Direction
- mdbook_driver.init uses mdbook_core.config, so a change to mdbook_core.config can break mdbook_driver.init, while a change to mdbook_driver.init can't break mdbook_core.config.
- Position
- Below the diagonal: mdbook_driver.init uses a module listed above it, which is the healthy direction.
16β12 mdbook_html.html uses mdbook_core.book✕
- Connections
- 2 pairs of types, where a type in mdbook_html.html uses a type in mdbook_core.book.
- The types involved
mdbook_html.html.ChapterTreeβmdbook_core.book.Chaptermdbook_html.html.html$moduleβmdbook_core.book.Book
- Direction
- mdbook_html.html uses mdbook_core.book, so a change to mdbook_core.book can break mdbook_html.html, while a change to mdbook_html.html can't break mdbook_core.book.
- Position
- Below the diagonal: mdbook_html.html uses a module listed above it, which is the healthy direction.
16β13 mdbook_html.html uses mdbook_core.config✕
- Connections
- 4 pairs of types, where a type in mdbook_html.html uses a type in mdbook_core.config.
- The types involved
mdbook_html.html.HtmlRenderOptionsβmdbook_core.config.HtmlConfigmdbook_html.html.HtmlRenderOptionsβmdbook_core.config.RustEditionmdbook_html.html.html$moduleβmdbook_core.config.HtmlConfigmdbook_html.html.html$moduleβmdbook_core.config.RustEdition
- Direction
- mdbook_html.html uses mdbook_core.config, so a change to mdbook_core.config can break mdbook_html.html, while a change to mdbook_html.html can't break mdbook_core.config.
- Position
- Below the diagonal: mdbook_html.html uses a module listed above it, which is the healthy direction.
16β14 mdbook_html.html uses mdbook_markdown✕
- Connections
- 1 pair of types, where a type in mdbook_html.html uses a type in mdbook_markdown.
- The types involved
mdbook_html.html.HtmlRenderOptionsβmdbook_markdown.MarkdownOptions
- Direction
- mdbook_html.html uses mdbook_markdown, so a change to mdbook_markdown can break mdbook_html.html, while a change to mdbook_html.html can't break mdbook_markdown.
- Position
- Below the diagonal: mdbook_html.html uses a module listed above it, which is the healthy direction.
17β13 mdbook_html.theme uses mdbook_core.config✕
- Connections
- 1 pair of types, where a type in mdbook_html.theme uses a type in mdbook_core.config.
- The types involved
mdbook_html.theme.Themeβmdbook_core.config.HtmlConfig
- Direction
- mdbook_html.theme uses mdbook_core.config, so a change to mdbook_core.config can break mdbook_html.theme, while a change to mdbook_html.theme can't break mdbook_core.config.
- Position
- Below the diagonal: mdbook_html.theme uses a module listed above it, which is the healthy direction.
18β12 mdbook_preprocessor uses mdbook_core.book✕
- Connections
- 1 pair of types, where a type in mdbook_preprocessor uses a type in mdbook_core.book.
- The types involved
mdbook_preprocessor.Preprocessorβmdbook_core.book.Book
- Direction
- mdbook_preprocessor uses mdbook_core.book, so a change to mdbook_core.book can break mdbook_preprocessor, while a change to mdbook_preprocessor can't break mdbook_core.book.
- Position
- Below the diagonal: mdbook_preprocessor uses a module listed above it, which is the healthy direction.
18β13 mdbook_preprocessor uses mdbook_core.config✕
- Connections
- 1 pair of types, where a type in mdbook_preprocessor uses a type in mdbook_core.config.
- The types involved
mdbook_preprocessor.PreprocessorContextβmdbook_core.config.Config
- Direction
- mdbook_preprocessor uses mdbook_core.config, so a change to mdbook_core.config can break mdbook_preprocessor, while a change to mdbook_preprocessor can't break mdbook_core.config.
- Position
- Below the diagonal: mdbook_preprocessor uses a module listed above it, which is the healthy direction.
19β12 mdbook_renderer uses mdbook_core.book✕
- Connections
- 1 pair of types, where a type in mdbook_renderer uses a type in mdbook_core.book.
- The types involved
mdbook_renderer.RenderContextβmdbook_core.book.Book
- Direction
- mdbook_renderer uses mdbook_core.book, so a change to mdbook_core.book can break mdbook_renderer, while a change to mdbook_renderer can't break mdbook_core.book.
- Position
- Below the diagonal: mdbook_renderer uses a module listed above it, which is the healthy direction.
19β13 mdbook_renderer uses mdbook_core.config✕
- Connections
- 1 pair of types, where a type in mdbook_renderer uses a type in mdbook_core.config.
- The types involved
mdbook_renderer.RenderContextβmdbook_core.config.Config
- Direction
- mdbook_renderer uses mdbook_core.config, so a change to mdbook_core.config can break mdbook_renderer, while a change to mdbook_renderer can't break mdbook_core.config.
- Position
- Below the diagonal: mdbook_renderer uses a module listed above it, which is the healthy direction.
20β12 mdbook_summary uses mdbook_core.book✕
- Connections
- 2 pairs of types, where a type in mdbook_summary uses a type in mdbook_core.book.
- The types involved
mdbook_summary.Linkβmdbook_core.book.SectionNumbermdbook_summary.SummaryParserβmdbook_core.book.SectionNumber
- Direction
- mdbook_summary uses mdbook_core.book, so a change to mdbook_core.book can break mdbook_summary, while a change to mdbook_summary can't break mdbook_core.book.
- Position
- Below the diagonal: mdbook_summary uses a module listed above it, which is the healthy direction.
21β12 mdbook_wordcount uses mdbook_core.book✕
- Connections
- 1 pair of types, where a type in mdbook_wordcount uses a type in mdbook_core.book.
- The types involved
mdbook_wordcount.mdbook_wordcount$moduleβmdbook_core.book.Chapter
- Direction
- mdbook_wordcount uses mdbook_core.book, so a change to mdbook_core.book can break mdbook_wordcount, while a change to mdbook_wordcount can't break mdbook_core.book.
- Position
- Below the diagonal: mdbook_wordcount uses a module listed above it, which is the healthy direction.
22β12 guide_helper uses mdbook_core.book✕
- Connections
- 2 pairs of types, where a type in guide_helper uses a type in mdbook_core.book.
- The types involved
guide_helper.GuideHelperβmdbook_core.book.Bookguide_helper.guide_helper$moduleβmdbook_core.book.Book
- Direction
- guide_helper uses mdbook_core.book, so a change to mdbook_core.book can break guide_helper, while a change to guide_helper can't break mdbook_core.book.
- Position
- Below the diagonal: guide_helper uses a module listed above it, which is the healthy direction.
22β18 guide_helper uses mdbook_preprocessor✕
- Connections
- 2 pairs of types, where a type in guide_helper uses a type in mdbook_preprocessor.
- The types involved
guide_helper.GuideHelperβmdbook_preprocessor.Preprocessorguide_helper.GuideHelperβmdbook_preprocessor.PreprocessorContext
- Direction
- guide_helper uses mdbook_preprocessor, so a change to mdbook_preprocessor can break guide_helper, while a change to guide_helper can't break mdbook_preprocessor.
- Position
- Below the diagonal: guide_helper uses a module listed above it, which is the healthy direction.
23β12 mdbook_driver.builtin_preprocessors.cmd uses mdbook_core.book✕
- Connections
- 1 pair of types, where a type in mdbook_driver.builtin_preprocessors.cmd uses a type in mdbook_core.book.
- The types involved
mdbook_driver.builtin_preprocessors.cmd.CmdPreprocessorβmdbook_core.book.Book
- Direction
- mdbook_driver.builtin_preprocessors.cmd uses mdbook_core.book, so a change to mdbook_core.book can break mdbook_driver.builtin_preprocessors.cmd, while a change to mdbook_driver.builtin_preprocessors.cmd can't break mdbook_core.book.
- Position
- Below the diagonal: mdbook_driver.builtin_preprocessors.cmd uses a module listed above it, which is the healthy direction.
23β18 mdbook_driver.builtin_preprocessors.cmd uses mdbook_preprocessor✕
- Connections
- 2 pairs of types, where a type in mdbook_driver.builtin_preprocessors.cmd uses a type in mdbook_preprocessor.
- The types involved
mdbook_driver.builtin_preprocessors.cmd.CmdPreprocessorβmdbook_preprocessor.Preprocessormdbook_driver.builtin_preprocessors.cmd.CmdPreprocessorβmdbook_preprocessor.PreprocessorContext
- Direction
- mdbook_driver.builtin_preprocessors.cmd uses mdbook_preprocessor, so a change to mdbook_preprocessor can break mdbook_driver.builtin_preprocessors.cmd, while a change to mdbook_driver.builtin_preprocessors.cmd can't break mdbook_preprocessor.
- Position
- Below the diagonal: mdbook_driver.builtin_preprocessors.cmd uses a module listed above it, which is the healthy direction.
24β12 mdbook_driver.builtin_preprocessors.index uses mdbook_core.book✕
- Connections
- 1 pair of types, where a type in mdbook_driver.builtin_preprocessors.index uses a type in mdbook_core.book.
- The types involved
mdbook_driver.builtin_preprocessors.index.IndexPreprocessorβmdbook_core.book.Book
- Direction
- mdbook_driver.builtin_preprocessors.index uses mdbook_core.book, so a change to mdbook_core.book can break mdbook_driver.builtin_preprocessors.index, while a change to mdbook_driver.builtin_preprocessors.index can't break mdbook_core.book.
- Position
- Below the diagonal: mdbook_driver.builtin_preprocessors.index uses a module listed above it, which is the healthy direction.
24β18 mdbook_driver.builtin_preprocessors.index uses mdbook_preprocessor✕
- Connections
- 2 pairs of types, where a type in mdbook_driver.builtin_preprocessors.index uses a type in mdbook_preprocessor.
- The types involved
mdbook_driver.builtin_preprocessors.index.IndexPreprocessorβmdbook_preprocessor.Preprocessormdbook_driver.builtin_preprocessors.index.IndexPreprocessorβmdbook_preprocessor.PreprocessorContext
- Direction
- mdbook_driver.builtin_preprocessors.index uses mdbook_preprocessor, so a change to mdbook_preprocessor can break mdbook_driver.builtin_preprocessors.index, while a change to mdbook_driver.builtin_preprocessors.index can't break mdbook_preprocessor.
- Position
- Below the diagonal: mdbook_driver.builtin_preprocessors.index uses a module listed above it, which is the healthy direction.
25β12 mdbook_driver.builtin_preprocessors.links uses mdbook_core.book✕
- Connections
- 1 pair of types, where a type in mdbook_driver.builtin_preprocessors.links uses a type in mdbook_core.book.
- The types involved
mdbook_driver.builtin_preprocessors.links.LinkPreprocessorβmdbook_core.book.Book
- Direction
- mdbook_driver.builtin_preprocessors.links uses mdbook_core.book, so a change to mdbook_core.book can break mdbook_driver.builtin_preprocessors.links, while a change to mdbook_driver.builtin_preprocessors.links can't break mdbook_core.book.
- Position
- Below the diagonal: mdbook_driver.builtin_preprocessors.links uses a module listed above it, which is the healthy direction.
25β18 mdbook_driver.builtin_preprocessors.links uses mdbook_preprocessor✕
- Connections
- 2 pairs of types, where a type in mdbook_driver.builtin_preprocessors.links uses a type in mdbook_preprocessor.
- The types involved
mdbook_driver.builtin_preprocessors.links.LinkPreprocessorβmdbook_preprocessor.Preprocessormdbook_driver.builtin_preprocessors.links.LinkPreprocessorβmdbook_preprocessor.PreprocessorContext
- Direction
- mdbook_driver.builtin_preprocessors.links uses mdbook_preprocessor, so a change to mdbook_preprocessor can break mdbook_driver.builtin_preprocessors.links, while a change to mdbook_driver.builtin_preprocessors.links can't break mdbook_preprocessor.
- Position
- Below the diagonal: mdbook_driver.builtin_preprocessors.links uses a module listed above it, which is the healthy direction.
26β19 mdbook_driver.builtin_renderers uses mdbook_renderer✕
- Connections
- 2 pairs of types, where a type in mdbook_driver.builtin_renderers uses a type in mdbook_renderer.
- The types involved
mdbook_driver.builtin_renderers.CmdRendererβmdbook_renderer.RenderContextmdbook_driver.builtin_renderers.CmdRendererβmdbook_renderer.Renderer
- Direction
- mdbook_driver.builtin_renderers uses mdbook_renderer, so a change to mdbook_renderer can break mdbook_driver.builtin_renderers, while a change to mdbook_driver.builtin_renderers can't break mdbook_renderer.
- Position
- Below the diagonal: mdbook_driver.builtin_renderers uses a module listed above it, which is the healthy direction.
27β19 mdbook_driver.builtin_renderers.markdown_renderer uses mdbook_renderer✕
- Connections
- 2 pairs of types, where a type in mdbook_driver.builtin_renderers.markdown_renderer uses a type in mdbook_renderer.
- The types involved
mdbook_driver.builtin_renderers.markdown_renderer.MarkdownRendererβmdbook_renderer.RenderContextmdbook_driver.builtin_renderers.markdown_renderer.MarkdownRendererβmdbook_renderer.Renderer
- Direction
- mdbook_driver.builtin_renderers.markdown_renderer uses mdbook_renderer, so a change to mdbook_renderer can break mdbook_driver.builtin_renderers.markdown_renderer, while a change to mdbook_driver.builtin_renderers.markdown_renderer can't break mdbook_renderer.
- Position
- Below the diagonal: mdbook_driver.builtin_renderers.markdown_renderer uses a module listed above it, which is the healthy direction.
28β12 mdbook_driver.mdbook uses mdbook_core.book✕
- Connections
- 2 pairs of types, where a type in mdbook_driver.mdbook uses a type in mdbook_core.book.
- The types involved
mdbook_driver.mdbook.MDBookβmdbook_core.book.Bookmdbook_driver.mdbook.MDBookβmdbook_core.book.BookItems
- Direction
- mdbook_driver.mdbook uses mdbook_core.book, so a change to mdbook_core.book can break mdbook_driver.mdbook, while a change to mdbook_driver.mdbook can't break mdbook_core.book.
- Position
- Below the diagonal: mdbook_driver.mdbook uses a module listed above it, which is the healthy direction.
28β13 mdbook_driver.mdbook uses mdbook_core.config✕
- Connections
- 2 pairs of types, where a type in mdbook_driver.mdbook uses a type in mdbook_core.config.
- The types involved
mdbook_driver.mdbook.MDBookβmdbook_core.config.Configmdbook_driver.mdbook.mdbook$moduleβmdbook_core.config.Config
- Direction
- mdbook_driver.mdbook uses mdbook_core.config, so a change to mdbook_core.config can break mdbook_driver.mdbook, while a change to mdbook_driver.mdbook can't break mdbook_core.config.
- Position
- Below the diagonal: mdbook_driver.mdbook uses a module listed above it, which is the healthy direction.
28β15 mdbook_driver.mdbook uses mdbook_driver.init✕
- Connections
- 1 pair of types, where a type in mdbook_driver.mdbook uses a type in mdbook_driver.init.
- The types involved
mdbook_driver.mdbook.MDBookβmdbook_driver.init.BookBuilder
- Direction
- mdbook_driver.mdbook uses mdbook_driver.init, so a change to mdbook_driver.init can break mdbook_driver.mdbook, while a change to mdbook_driver.mdbook can't break mdbook_driver.init.
- Position
- Below the diagonal: mdbook_driver.mdbook uses a module listed above it, which is the healthy direction.
28β20 mdbook_driver.mdbook uses mdbook_summary✕
- Connections
- 1 pair of types, where a type in mdbook_driver.mdbook uses a type in mdbook_summary.
- The types involved
mdbook_driver.mdbook.MDBookβmdbook_summary.Summary
- Direction
- mdbook_driver.mdbook uses mdbook_summary, so a change to mdbook_summary can break mdbook_driver.mdbook, while a change to mdbook_driver.mdbook can't break mdbook_summary.
- Position
- Below the diagonal: mdbook_driver.mdbook uses a module listed above it, which is the healthy direction.
29β16 mdbook_html.html.print uses mdbook_html.html✕
- Connections
- 1 pair of types, where a type in mdbook_html.html.print uses a type in mdbook_html.html.
- The types involved
mdbook_html.html.print.print$moduleβmdbook_html.html.ChapterTree
- Direction
- mdbook_html.html.print uses mdbook_html.html, so a change to mdbook_html.html can break mdbook_html.html.print, while a change to mdbook_html.html.print can't break mdbook_html.html.
- Position
- Below the diagonal: mdbook_html.html.print uses a module listed above it, which is the healthy direction.
30β16 mdbook_html.html.tree uses mdbook_html.html✕
- Connections
- 1 pair of types, where a type in mdbook_html.html.tree uses a type in mdbook_html.html.
- The types involved
mdbook_html.html.tree.MarkdownTreeBuilderβmdbook_html.html.HtmlRenderOptions
- Direction
- mdbook_html.html.tree uses mdbook_html.html, so a change to mdbook_html.html can break mdbook_html.html.tree, while a change to mdbook_html.html.tree can't break mdbook_html.html.
- Position
- Below the diagonal: mdbook_html.html.tree uses a module listed above it, which is the healthy direction.
31β12 mdbook_html.html_handlebars.hbs_renderer uses mdbook_core.book✕
- Connections
- 2 pairs of types, where a type in mdbook_html.html_handlebars.hbs_renderer uses a type in mdbook_core.book.
- The types involved
mdbook_html.html_handlebars.hbs_renderer.HtmlHandlebarsβmdbook_core.book.Chaptermdbook_html.html_handlebars.hbs_renderer.hbs_renderer$moduleβmdbook_core.book.Book
- Direction
- mdbook_html.html_handlebars.hbs_renderer uses mdbook_core.book, so a change to mdbook_core.book can break mdbook_html.html_handlebars.hbs_renderer, while a change to mdbook_html.html_handlebars.hbs_renderer can't break mdbook_core.book.
- Position
- Below the diagonal: mdbook_html.html_handlebars.hbs_renderer uses a module listed above it, which is the healthy direction.
31β13 mdbook_html.html_handlebars.hbs_renderer uses mdbook_core.config✕
- Connections
- 5 pairs of types, where a type in mdbook_html.html_handlebars.hbs_renderer uses a type in mdbook_core.config.
- The types involved
mdbook_html.html_handlebars.hbs_renderer.HtmlHandlebarsβmdbook_core.config.HtmlConfigmdbook_html.html_handlebars.hbs_renderer.RenderChapterContextβmdbook_core.config.BookConfigmdbook_html.html_handlebars.hbs_renderer.RenderChapterContextβmdbook_core.config.HtmlConfigmdbook_html.html_handlebars.hbs_renderer.hbs_renderer$moduleβmdbook_core.config.Configmdbook_html.html_handlebars.hbs_renderer.hbs_renderer$moduleβmdbook_core.config.HtmlConfig
- Direction
- mdbook_html.html_handlebars.hbs_renderer uses mdbook_core.config, so a change to mdbook_core.config can break mdbook_html.html_handlebars.hbs_renderer, while a change to mdbook_html.html_handlebars.hbs_renderer can't break mdbook_core.config.
- Position
- Below the diagonal: mdbook_html.html_handlebars.hbs_renderer uses a module listed above it, which is the healthy direction.
31β16 mdbook_html.html_handlebars.hbs_renderer uses mdbook_html.html✕
- Connections
- 1 pair of types, where a type in mdbook_html.html_handlebars.hbs_renderer uses a type in mdbook_html.html.
- The types involved
mdbook_html.html_handlebars.hbs_renderer.HtmlHandlebarsβmdbook_html.html.ChapterTree
- Direction
- mdbook_html.html_handlebars.hbs_renderer uses mdbook_html.html, so a change to mdbook_html.html can break mdbook_html.html_handlebars.hbs_renderer, while a change to mdbook_html.html_handlebars.hbs_renderer can't break mdbook_html.html.
- Position
- Below the diagonal: mdbook_html.html_handlebars.hbs_renderer uses a module listed above it, which is the healthy direction.
31β17 mdbook_html.html_handlebars.hbs_renderer uses mdbook_html.theme✕
- Connections
- 1 pair of types, where a type in mdbook_html.html_handlebars.hbs_renderer uses a type in mdbook_html.theme.
- The types involved
mdbook_html.html_handlebars.hbs_renderer.hbs_renderer$moduleβmdbook_html.theme.Theme
- Direction
- mdbook_html.html_handlebars.hbs_renderer uses mdbook_html.theme, so a change to mdbook_html.theme can break mdbook_html.html_handlebars.hbs_renderer, while a change to mdbook_html.html_handlebars.hbs_renderer can't break mdbook_html.theme.
- Position
- Below the diagonal: mdbook_html.html_handlebars.hbs_renderer uses a module listed above it, which is the healthy direction.
31β19 mdbook_html.html_handlebars.hbs_renderer uses mdbook_renderer✕
- Connections
- 2 pairs of types, where a type in mdbook_html.html_handlebars.hbs_renderer uses a type in mdbook_renderer.
- The types involved
mdbook_html.html_handlebars.hbs_renderer.HtmlHandlebarsβmdbook_renderer.RenderContextmdbook_html.html_handlebars.hbs_renderer.HtmlHandlebarsβmdbook_renderer.Renderer
- Direction
- mdbook_html.html_handlebars.hbs_renderer uses mdbook_renderer, so a change to mdbook_renderer can break mdbook_html.html_handlebars.hbs_renderer, while a change to mdbook_html.html_handlebars.hbs_renderer can't break mdbook_renderer.
- Position
- Below the diagonal: mdbook_html.html_handlebars.hbs_renderer uses a module listed above it, which is the healthy direction.
32β19 mdbook_html.html_handlebars.helpers.fontawesome uses mdbook_renderer✕
- Connections
- 1 pair of types, where a type in mdbook_html.html_handlebars.helpers.fontawesome uses a type in mdbook_renderer.
- The types involved
mdbook_html.html_handlebars.helpers.fontawesome.fontawesome$moduleβmdbook_renderer.RenderContext
- Direction
- mdbook_html.html_handlebars.helpers.fontawesome uses mdbook_renderer, so a change to mdbook_renderer can break mdbook_html.html_handlebars.helpers.fontawesome, while a change to mdbook_html.html_handlebars.helpers.fontawesome can't break mdbook_renderer.
- Position
- Below the diagonal: mdbook_html.html_handlebars.helpers.fontawesome uses a module listed above it, which is the healthy direction.
33β19 mdbook_html.html_handlebars.helpers.resources uses mdbook_renderer✕
- Connections
- 1 pair of types, where a type in mdbook_html.html_handlebars.helpers.resources uses a type in mdbook_renderer.
- The types involved
mdbook_html.html_handlebars.helpers.resources.ResourceHelperβmdbook_renderer.RenderContext
- Direction
- mdbook_html.html_handlebars.helpers.resources uses mdbook_renderer, so a change to mdbook_renderer can break mdbook_html.html_handlebars.helpers.resources, while a change to mdbook_html.html_handlebars.helpers.resources can't break mdbook_renderer.
- Position
- Below the diagonal: mdbook_html.html_handlebars.helpers.resources uses a module listed above it, which is the healthy direction.
34β19 mdbook_html.html_handlebars.helpers.toc uses mdbook_renderer✕
- Connections
- 1 pair of types, where a type in mdbook_html.html_handlebars.helpers.toc uses a type in mdbook_renderer.
- The types involved
mdbook_html.html_handlebars.helpers.toc.RenderTocβmdbook_renderer.RenderContext
- Direction
- mdbook_html.html_handlebars.helpers.toc uses mdbook_renderer, so a change to mdbook_renderer can break mdbook_html.html_handlebars.helpers.toc, while a change to mdbook_html.html_handlebars.helpers.toc can't break mdbook_renderer.
- Position
- Below the diagonal: mdbook_html.html_handlebars.helpers.toc uses a module listed above it, which is the healthy direction.
35β13 mdbook_html.html_handlebars.static_files uses mdbook_core.config✕
- Connections
- 1 pair of types, where a type in mdbook_html.html_handlebars.static_files uses a type in mdbook_core.config.
- The types involved
mdbook_html.html_handlebars.static_files.StaticFilesβmdbook_core.config.HtmlConfig
- Direction
- mdbook_html.html_handlebars.static_files uses mdbook_core.config, so a change to mdbook_core.config can break mdbook_html.html_handlebars.static_files, while a change to mdbook_html.html_handlebars.static_files can't break mdbook_core.config.
- Position
- Below the diagonal: mdbook_html.html_handlebars.static_files uses a module listed above it, which is the healthy direction.
35β17 mdbook_html.html_handlebars.static_files uses mdbook_html.theme✕
- Connections
- 1 pair of types, where a type in mdbook_html.html_handlebars.static_files uses a type in mdbook_html.theme.
- The types involved
mdbook_html.html_handlebars.static_files.StaticFilesβmdbook_html.theme.Theme
- Direction
- mdbook_html.html_handlebars.static_files uses mdbook_html.theme, so a change to mdbook_html.theme can break mdbook_html.html_handlebars.static_files, while a change to mdbook_html.html_handlebars.static_files can't break mdbook_html.theme.
- Position
- Below the diagonal: mdbook_html.html_handlebars.static_files uses a module listed above it, which is the healthy direction.
36β28 mdbook.cmd.command_prelude uses mdbook_driver.mdbook✕
- Connections
- 1 pair of types, where a type in mdbook.cmd.command_prelude uses a type in mdbook_driver.mdbook.
- The types involved
mdbook.cmd.command_prelude.command_prelude$moduleβmdbook_driver.mdbook.MDBook
- Direction
- mdbook.cmd.command_prelude uses mdbook_driver.mdbook, so a change to mdbook_driver.mdbook can break mdbook.cmd.command_prelude, while a change to mdbook.cmd.command_prelude can't break mdbook_driver.mdbook.
- Position
- Below the diagonal: mdbook.cmd.command_prelude uses a module listed above it, which is the healthy direction.
37β28 mdbook.cmd.watch.poller uses mdbook_driver.mdbook✕
- Connections
- 1 pair of types, where a type in mdbook.cmd.watch.poller uses a type in mdbook_driver.mdbook.
- The types involved
mdbook.cmd.watch.poller.Watcherβmdbook_driver.mdbook.MDBook
- Direction
- mdbook.cmd.watch.poller uses mdbook_driver.mdbook, so a change to mdbook_driver.mdbook can break mdbook.cmd.watch.poller, while a change to mdbook.cmd.watch.poller can't break mdbook_driver.mdbook.
- Position
- Below the diagonal: mdbook.cmd.watch.poller uses a module listed above it, which is the healthy direction.
38β13 mdbook_driver.load uses mdbook_core.config✕
- Connections
- 1 pair of types, where a type in mdbook_driver.load uses a type in mdbook_core.config.
- The types involved
mdbook_driver.load.load$moduleβmdbook_core.config.BuildConfig
- Direction
- mdbook_driver.load uses mdbook_core.config, so a change to mdbook_core.config can break mdbook_driver.load, while a change to mdbook_driver.load can't break mdbook_core.config.
- Position
- Below the diagonal: mdbook_driver.load uses a module listed above it, which is the healthy direction.
38β20 mdbook_driver.load uses mdbook_summary✕
- Connections
- 2 pairs of types, where a type in mdbook_driver.load uses a type in mdbook_summary.
- The types involved
mdbook_driver.load.load$moduleβmdbook_summary.Summarymdbook_driver.load.load$moduleβmdbook_summary.SummaryItem
- Direction
- mdbook_driver.load uses mdbook_summary, so a change to mdbook_summary can break mdbook_driver.load, while a change to mdbook_driver.load can't break mdbook_summary.
- Position
- Below the diagonal: mdbook_driver.load uses a module listed above it, which is the healthy direction.
38β25 mdbook_driver.load uses mdbook_driver.builtin_preprocessors.links✕
- Connections
- 1 pair of types, where a type in mdbook_driver.load uses a type in mdbook_driver.builtin_preprocessors.links.
- The types involved
mdbook_driver.load.load$moduleβmdbook_driver.builtin_preprocessors.links.Link
- Direction
- mdbook_driver.load uses mdbook_driver.builtin_preprocessors.links, so a change to mdbook_driver.builtin_preprocessors.links can break mdbook_driver.load, while a change to mdbook_driver.load can't break mdbook_driver.builtin_preprocessors.links.
- Position
- Below the diagonal: mdbook_driver.load uses a module listed above it, which is the healthy direction.
39β30 mdbook_html.html.serialize uses mdbook_html.html.tree✕
- Connections
- 1 pair of types, where a type in mdbook_html.html.serialize uses a type in mdbook_html.html.tree.
- The types involved
mdbook_html.html.serialize.serialize$moduleβmdbook_html.html.tree.Element
- Direction
- mdbook_html.html.serialize uses mdbook_html.html.tree, so a change to mdbook_html.html.tree can break mdbook_html.html.serialize, while a change to mdbook_html.html.serialize can't break mdbook_html.html.tree.
- Position
- Below the diagonal: mdbook_html.html.serialize uses a module listed above it, which is the healthy direction.
40β12 mdbook_html.html_handlebars.search uses mdbook_core.book✕
- Connections
- 1 pair of types, where a type in mdbook_html.html_handlebars.search uses a type in mdbook_core.book.
- The types involved
mdbook_html.html_handlebars.search.search$moduleβmdbook_core.book.Chapter
- Direction
- mdbook_html.html_handlebars.search uses mdbook_core.book, so a change to mdbook_core.book can break mdbook_html.html_handlebars.search, while a change to mdbook_html.html_handlebars.search can't break mdbook_core.book.
- Position
- Below the diagonal: mdbook_html.html_handlebars.search uses a module listed above it, which is the healthy direction.
40β13 mdbook_html.html_handlebars.search uses mdbook_core.config✕
- Connections
- 2 pairs of types, where a type in mdbook_html.html_handlebars.search uses a type in mdbook_core.config.
- The types involved
mdbook_html.html_handlebars.search.search$moduleβmdbook_core.config.Searchmdbook_html.html_handlebars.search.search$moduleβmdbook_core.config.SearchChapterSettings
- Direction
- mdbook_html.html_handlebars.search uses mdbook_core.config, so a change to mdbook_core.config can break mdbook_html.html_handlebars.search, while a change to mdbook_html.html_handlebars.search can't break mdbook_core.config.
- Position
- Below the diagonal: mdbook_html.html_handlebars.search uses a module listed above it, which is the healthy direction.
40β16 mdbook_html.html_handlebars.search uses mdbook_html.html✕
- Connections
- 1 pair of types, where a type in mdbook_html.html_handlebars.search uses a type in mdbook_html.html.
- The types involved
mdbook_html.html_handlebars.search.search$moduleβmdbook_html.html.ChapterTree
- Direction
- mdbook_html.html_handlebars.search uses mdbook_html.html, so a change to mdbook_html.html can break mdbook_html.html_handlebars.search, while a change to mdbook_html.html_handlebars.search can't break mdbook_html.html.
- Position
- Below the diagonal: mdbook_html.html_handlebars.search uses a module listed above it, which is the healthy direction.
40β35 mdbook_html.html_handlebars.search uses mdbook_html.html_handlebars.static_files✕
- Connections
- 1 pair of types, where a type in mdbook_html.html_handlebars.search uses a type in mdbook_html.html_handlebars.static_files.
- The types involved
mdbook_html.html_handlebars.search.search$moduleβmdbook_html.html_handlebars.static_files.StaticFiles
- Direction
- mdbook_html.html_handlebars.search uses mdbook_html.html_handlebars.static_files, so a change to mdbook_html.html_handlebars.static_files can break mdbook_html.html_handlebars.search, while a change to mdbook_html.html_handlebars.search can't break mdbook_html.html_handlebars.static_files.
- Position
- Below the diagonal: mdbook_html.html_handlebars.search 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 | 21 | High / Critical |
| A03:2025 β Software Supply Chain Failures | 11 | Medium |
Roadmap
Top priorities: Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-β¦"` hash alongside `crossorigin="anonymous"` (both are required β an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the appβs own origin, so no consumer inherits a third-party dependency they did not choose; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Resolve the 1 No ADRs found finding(s) in ADR Quality β start with Cargo.toml.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-β¦"` hash alongside `crossorigin="anonymous"` (both are required β an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the appβs own origin, so no consumer inherits a third-party dependency they did not choose. | +7.6 pts | Medium | Web-Security Posture |
| Resolve the 1 No ADRs found finding(s) in ADR Quality β start with Cargo.toml. | +3.0 pts | Low | ADR Quality |
| Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED (6), REDACTED. | +2.8 pts | Low | Static Analysis (SAST) |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.6 pts | Medium | Keyboard semantics |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED, REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +2.8 pts | Medium | Visual & motion safety |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.4 pts | Low | Bus Factor |
| 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.3 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| crates/mdbook-html/src/html/tree.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/mdbook-html/src/html_handlebars/hbs_renderer.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| crates/mdbook-driver/src/mdbook.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| crates/mdbook-html/src/html/print.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| tests/testsuite/rendering.rs | 6.0 | Mixed | Test Reliability: Flaky test: mdbook::testsuite.rendering::busted_end_tag |
| tests/testsuite/theme.rs | 6.0 | Mixed | Test Reliability: Flaky test: mdbook::testsuite.theme::custom_fonts_css |
| tests/testsuite/config.rs | 6.1 | Mixed | Test Reliability: Flaky test: mdbook::testsuite.config::bad_config_in_rust_table |
| tests/testsuite/includes.rs | 6.3 | Mixed | Test Reliability: Flaky test: mdbook::testsuite.includes::anchored_include |
| tests/testsuite/toc.rs | 6.3 | Mixed | Test Reliability: Flaky test: mdbook::testsuite.toc::check_first_toc_level |
| tests/testsuite/build.rs | 6.5 | Mixed | Test Reliability: Flaky test: mdbook::testsuite.build::basic_build |
| tests/testsuite/markdown.rs | 6.5 | Mixed | Test Reliability: Flaky test: mdbook::testsuite.markdown::basic_markdown |
| tests/testsuite/redirects.rs | 6.5 | Mixed | Test Reliability: Flaky test: mdbook::testsuite.redirects::redirect_existing_page |
| tests/testsuite/search.rs | 6.5 | Mixed | Test Reliability: Flaky test: mdbook::testsuite.search::can_disable_individual_chapters |
| src/cmd/clean.rs | 7.0 | Near-clean | Cognitive Complexity: Clean::new (cognitive 20) |
| src/cmd/init.rs | 7.0 | Near-clean | Cognitive Complexity: mdbook::cmd::init::execute (cognitive 18) |
| src/cmd/watch/native.rs | 7.0 | Near-clean | Cognitive Complexity: mdbook::cmd::watch::native::rebuild_on_change (cognitive 18) |
| tests/testsuite/index.rs | 7.0 | Near-clean | Test Reliability: Flaky test: mdbook::testsuite.index::index_rewrite |
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 49 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked β 49 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, 223 of 254 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 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.
- D19 Documentation Quality β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. 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 β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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.
- AXR1 Runtime accessibility β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via ToolchainServer (.). the service exited before it opened a port β `cargo run --locked --bin 'mdbook' -- serve`: Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.08s Running `target/debug/mdbook serve` ERROR failed to read `src/SUMMARY.md`β¦; runtime evidence skipped (launch chosen because 'axum' dependency in Cargo.toml, binary 'mdbook', started with its 'serve' subcommand).
- 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 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 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.
- X24 Document value interpolated into markup unescaped β 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.
- X4 Structured logging β 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. 42 further occurrence(s) are not listed individually; the score already reflects all 82.
- 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 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image β the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers β we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles β a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree β a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy β mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history β a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension β pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual β undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded β it is never the team's dead code to delete.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project β a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- AC2 Forms & labels: Label association is read from static markup β a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively β flagged only when it carries NO label/aria-label/aria-labelledby/id/name β but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree β landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes β interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape β roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES β Vue v-if/v-else/v-show and Alpine x-if/x-show β so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction β literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${β¦}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics β a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MarkdownTreeBuilder::start_tag at 48.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity β start with MarkdownTreeBuilder::start_tag (cyclomatic 48). β Refactoring it lifts Cyclomatic Complexity from 7.6 to about 8.2/10.
D2 Β· Cognitive Complexity
26 method(s) exceeded the cognitive complexity threshold of 15; the worst was mdbook_html::html::print::rewrite_links at 60.
What to do
- Bring the 24 bodies over 15 down to 15 or less in Cognitive Complexity β start with mdbook_html::html::print::rewrite_links (cognitive 60), mdbook_html::html_handlebars::search::index_chapter (cognitive 53), MarkdownTreeBuilder::start_tag (cognitive 50). β 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 24 together lifts Cognitive Complexity from 4.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 Β· God Classes
8 god class(es) detected.
What to do
- Resolve the 3 MethodTooLong finding(s) in God Classes β start with tree.rs, hbs_renderer.rs, toc.rs. β One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 FileTooLong finding(s) in God Classes β start with tree.rs, book.js, hbs_renderer.rs. β One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes β start with tree.rs. β One of this dimension's main actionable groups (1 warning-level).
D4 Β· Code Duplication
6 duplicated block group(s) detected. 1.2 % of the production lines (146 of 12,399) are in a reported copy. A further 3 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 2 Edited copy of a member (17 corresponding lines) finding(s) in Code Duplication β start with links.rs, mdbook.rs. β One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication β start with static_files.rs, tree.rs. β One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (21 corresponding lines) finding(s) in Code Duplication β start with html.rs. β One of this dimension's main actionable groups (1 warning-level).
D5 Β· Coupling
12 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 10 of the 12 (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 2 Off the main sequence finding(s) in Coupling. β One of this dimension's main actionable groups (2 warning-level).
D6 Β· Cohesion (LCOM4)
0 of 18 classes have LCOM4 above 3.
D8 Β· Code Coverage
Line coverage 77.1% β 12 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 50 production file(s), 15 test binaries and 1 doc-test binaries).
What to do
- Resolve the 12 Low coverage finding(s) in Code Coverage β start with main.rs (4), markdown_renderer.rs, changelog.rs. β One of this dimension's main actionable groups (12 warning-level).
D11 Β· Test Reliability
61 flaky across 1 measured tier(s). Rust (repository root, 45 test files): measured (61 flaky).
What to do
- Resolve the 61 Flaky test finding(s) in Test Reliability β start with rendering.rs (15), theme.rs (7), config.rs (6). β One of this dimension's main actionable groups (61 issue-level).
D12 Β· Dependency Hygiene
13 outdated, 0 yanked direct Cargo dependencies. 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 253 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 MPL-2.0, 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 package.json, and the licences of those dependencies 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: crates/mdbook-html/src/html/tree.rs (4×48=192); crates/mdbook-html/src/html_handlebars/hbs_renderer.rs (4×30=120)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots β start with tree.rs, hbs_renderer.rs. β One of this dimension's main actionable groups (2 warning-level).
D16 Β· Bus Factor
12 source file(s) have their living knowledge concentrated in one author (β₯90% of recent, decayed contribution). The largest is src/cmd/watch/poller.rs. Counted over 41 of the 63 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. β One of this dimension's main actionable groups (1 recommendation-level).
D17 Β· Explicit Debt
8 deducted task-comment markers across 12399 LoC (0.1/KLoC) β score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 4 FixmeComment finding(s) in Explicit Debt β start with build.rs, poller.rs, hbs_renderer.rs. β One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 TodoComment finding(s) in Explicit Debt β start with print.rs, serialize.rs, tokenizer.rs. β One of this dimension's main actionable groups (4 warning-level).
D20 Β· ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality β start with Cargo.toml. β One of this dimension's main actionable groups (1 recommendation-level).
D24 Β· Comment Value
0 of 66 judged comments only repeat the code they sit on (0.0 %). 1 comment(s) in another language or script were not judged.
D26 Β· Project Cohesion
0 of 12 build units (Cargo, npm) flagged as possibly oversized/incoherent.
D28 Β· Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 Β· Static Analysis (SAST)
21 finding(s): 0 critical, 13 high, 8 medium, 0 low. 11 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` β one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) β `crates/mdbook-html/front-end/playground_editor/ace.js` β so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 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 7 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED (6), REDACTED. β One of this dimension's main actionable groups (7 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED, REDACTED. β One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) β all 11 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 (11 issue-level, 0 of them charged here).
D30 Β· Dependency Vulnerabilities
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- 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).
D34 Β· Knowledge Freshness
9 of 41 significant source file(s) are orphaned β their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/mdbook-driver/src/builtin_preprocessors/links/take_lines.rs. Counted over 41 of the 63 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 9 Orphaned file finding(s) in Knowledge Freshness β start with take_lines.rs, native.rs, clean.rs. β One of this dimension's main actionable groups (9 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. β One of this dimension's main actionable groups (1 recommendation-level).
D35 Β· Change Coupling
Strongest change-coupling: mod.rsβtake_lines.rs 50%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling β start with mod.rs. β One of this dimension's main actionable groups (1 warning-level).
D36 Β· Supply-chain Provenance & Signing
0/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 β start with REDACTED. β One of this dimension's main actionable groups (1 warning-level).
D43 Β· Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 Β· Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 2 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.
Frontend & cross-cutting dimensions
AC2 Β· Forms & labels
AC3 Β· Page structure
- An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. β REDACTED:136
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. β crates/mdbook-html/front-end/templates/toc.html.hbs:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 Β· Keyboard semantics
- The repo's own CSS styles .menu-title with `cursor: pointer`, so this <h1> is a control β but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. β REDACTED:169
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 Β· ARIA correctness
AC6 Β· Visual & motion safety
- `.page` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. β crates/mdbook-html/front-end/css/general.css:84
- `#fa-spin` moves (`animation: rotating 2s linear infinite`) and nothing reads prefers-reduced-motion for it β no @media (prefers-reduced-motion) rule for this element, no reset this project loads β so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. β crates/mdbook-html/front-end/css/chrome.css:371
- `html:not(.sidebar-resizing) .sidebar` moves (`transition: transform 0.3s`) and nothing reads prefers-reduced-motion for it β no @media (prefers-reduced-motion) rule for this element, no reset this project loads β so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. β crates/mdbook-html/front-end/css/chrome.css:487
- `.chapter-fold-toggle div` moves (`transition: transform 0.5s`) and nothing reads prefers-reduced-motion for it β no @media (prefers-reduced-motion) rule for this element, no reset this project loads β so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. β crates/mdbook-html/front-end/css/chrome.css:638
- `html:not(.js) .page-wrapper` moves (`transition: margin-left 0.3s ease, transform 0.3s ease`) and nothing reads prefers-reduced-motion for it β no @media (prefers-reduced-motion) rule for this element, no reset this project loads β so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. β crates/mdbook-html/front-end/css/general.css:94
- `[dir=rtl]:not(.js) .page-wrapper` moves (`transition: margin-right 0.3s ease, transform 0.3s ease`) and nothing reads prefers-reduced-motion for it β no @media (prefers-reduced-motion) rule for this element, no reset this project loads β so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. β crates/mdbook-html/front-end/css/general.css:98
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 Β· Code composition
AX3 Β· Project dependency cycles
AX4 Β· Dependency direction
AX9 Β· CQS / query purity
M1 Β· Documentation (README)
- The root README is 98 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise β or with no heading at all β is not seen and this row may understate what the document covers. β README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Add a build/run (quick start) section to the root README β the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape β no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is β¦" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document β not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 Β· Folder & project structure
M4 Β· Documentation accuracy
P1 Β· CI/CD gates
P10 Β· Library API & versioning
P2 Β· Observability
- Only 6/9 runnable modules use logging (modules with no entry point or server are excluded β they are libraries a runnable module hosts). Silent: `crates/xtask`, `guide/guide-helper`, `guide/src/for_developers/mdbook-wordcount`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 Β· Security & performance tooling
- `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`. β package.json:2
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
P6 Β· Release Hygiene
PF3 Β· Async & latency hygiene
S1 Β· Web-Security Posture
- `https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.1/MathJax.js?config=TeX-AMS-MML_HTMLorMML` is executed by this page with no Subresource Integrity. Whoever can answer that request β the CDN, anyone who compromises it, anyone on the network path β runs arbitrary script in this page's origin, with its session. β REDACTED:53
- This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy β so its traffic may cross the network in clear text. (β2.0 on this card.) The server: `axum::serve(` (src/cmd/serve.rs:177).
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, β¦) is set on a response this repository's Rust server sends β defense in depth, even when a proxy could set them. (β2.0 on this card.) The server: `axum::serve(` (src/cmd/serve.rs:177).
- No handler of this repository's Rust server answers 400, 413 or 422 (`StatusCode::BAD_REQUEST`, `HttpResponse::BadRequest()`, `Status::BadRequest`, tonic `Status::invalid_argument`), and nothing declares validation β no `validator`/`garde` derive, no body limit (`DefaultBodyLimit::max`, `RequestBodyLimitLayer`, `JsonConfig::default().limit(β¦)`, Rocket `Limits`) β nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (β2.0 on this card.) The server: `axum::serve(` (src/cmd/serve.rs:177).
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-β¦"` hash alongside `crossorigin="anonymous"` (both are required β an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the appβs own origin, so no consumer inherits a third-party dependency they did not choose.
- Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(β¦))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(β¦))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
- Set security response headers on what the server sends β actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(β¦)` on an axum router, or keep Rocket's default `Shield` β with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
- Validate what the server reads from a request β path, query, headers, body size and shape β and answer what fails with 400 (413 for an oversized body) before a handler acts on it: derive `validator::Validate` (or `garde::Validate`) on the request types and reject with `StatusCode::BAD_REQUEST`, and cap bodies with `DefaultBodyLimit::max`/`RequestBodyLimitLayer` or actix's `JsonConfig::default().limit(β¦)`.
X1 Β· Async correctness
X21 Β· Side-effecting pattern guard
X4 Β· Structured logging
- `error!` at line 142 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/main.rs:142
- `debug!` at line 76 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/init.rs:76
- `info!` at line 125 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/serve.rs:125
- `error!` at line 167 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/serve.rs:167
- `error!` at line 19 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/native.rs:19
- `error!` at line 29 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/native.rs:29
- `error!` at line 37 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/native.rs:37
- `error!` at line 49 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/native.rs:49
- `error!` at line 54 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/native.rs:54
- `warn!` at line 75 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/native.rs:75
- `info!` at line 90 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/native.rs:90
- `error!` at line 95 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/native.rs:95
- `error!` at line 101 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/native.rs:101
- `warn!` at line 116 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/native.rs:116
- `error!` at line 24 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/poller.rs:24
- `trace!` at line 52 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/poller.rs:52
- `info!` at line 59 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/poller.rs:59
- `error!` at line 64 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/poller.rs:64
- `error!` at line 71 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/poller.rs:71
- `warn!` at line 101 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/poller.rs:101
- `trace!` at line 176 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/poller.rs:176
- `debug!` at line 186 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/poller.rs:186
- `debug!` at line 200 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β src/cmd/watch/poller.rs:200
- `trace!` at line 202 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-summary/src/lib.rs:202
- `debug!` at line 208 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-summary/src/lib.rs:208
- `debug!` at line 296 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-summary/src/lib.rs:296
- `trace!` at line 445 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-summary/src/lib.rs:445
- `trace!` at line 477 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-summary/src/lib.rs:477
- `trace!` at line 489 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-summary/src/lib.rs:489
- `debug!` at line 495 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-summary/src/lib.rs:495
- `trace!` at line 542 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-summary/src/lib.rs:542
- `warn!` at line 557 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-summary/src/lib.rs:557
- `warn!` at line 111 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-html/src/theme/mod.rs:111
- `info!` at line 135 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-html/src/theme/mod.rs:135
- `debug!` at line 139 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-html/src/html_handlebars/hbs_renderer.rs:139
- `debug!` at line 275 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-html/src/html_handlebars/hbs_renderer.rs:275
- `info!` at line 485 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-html/src/html_handlebars/hbs_renderer.rs:485
- `error!` at line 706 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-html/src/html_handlebars/hbs_renderer.rs:706
- `warn!` at line 58 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-html/src/html_handlebars/search.rs:58
- `debug!` at line 254 is handed a format string with `{β¦}` values in it, so tracing records one finished `message` field β the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. β crates/mdbook-html/src/html_handlebars/static_files.rs:254
What to do
- Interpolated log message defeats structured logging
WCAG coverage β what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| 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 |
| AC4 Β· Keyboard semantics | 2.1.1, 2.4.3 | 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 | 67% | Adequate β gated by X4 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Solid. |
| Maturity | 53% | Adequate β gated by M2 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Readiness | 63% | Adequate β gated by D11 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Security | 38% | Weak β gated by D36, S1 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Accessibility | 45% | Adequate β gated by AC4, AC6 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored β 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene β 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 β 67 check(s) not relevant to this codebase
- AC1 Text alternatives β No image/media element found in the parsed markup β AC1 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; 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 β Not applicable: 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
- AXB2 Runtime readiness β Advisory β this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility β the service exited before it opened a port β `cargo run --locked --bin 'mdbook' -- serve`: Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.08s Running `target/debug/mdbook serve` ERROR failed to read `src/SUMMARY.md`β¦; runtime evidence skipped (launch chosen because 'axum' dependency in Cargo.toml, binary 'mdbook', started with its 'serve' subcommand) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection β 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 β ~3852 lines of test source are present (.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.
- D18 Solution Shape β D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality β D19 reads .NET projects and npm packages as units; 12 folder(s) declared by Cargo.toml were not judged for an overview, an example or the map.
- 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 Rust surface was not measured.
- D23 Boundary Type-Coupling β No bounded-context organisation was detected either β neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (β₯2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it β e.g. `architecture:` β `contexts:` β `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance β no ADRs to check
- 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
- DM1 Domain Modelling β not scored β this repository shows only 1 of the 3 signals this lens looks for (6 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 β no outbound HTTP usage detected β no HTTP client call or construction in the JavaScript/TypeScript, Rust source (service entry point: src/cmd/serve.rs:159 (Router::new()))
- 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 data present for 50 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against β if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline β Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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.
- X10 Duplicated predicate β Advisory β this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch β X12 reached only 10% of this repository's production lines β rust (12,399 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 10% of this repository's production lines β rust (12,399 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
- X2 Cancellation propagation β no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller β a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- 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 β X24 reached only 10% of this repository's production lines β rust (12,399 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated β not applicable β 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 10% of this repository's production lines β rust (12,399 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly β This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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.
- X7 Silent fallback defaults β Advisory β this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand β Advisory β this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A β Findings (grouped)
Critical β 76 finding(s)
- Flaky test: mdbook::testsuite.build::basic_build tests/testsuite/build.rs:10
- Flaky test: mdbook::testsuite.build::book_toml_isnt_required tests/testsuite/build.rs:60
- Flaky test: mdbook::testsuite.build::no_reserved_filename tests/testsuite/build.rs:46
- Flaky test: mdbook::testsuite.config::bad_config_in_rust_table tests/testsuite/config.rs:185
- Flaky test: mdbook::testsuite.config::bad_config_top_level_table tests/testsuite/config.rs:137
- Flaky test: mdbook::testsuite.config::config_from_env tests/testsuite/config.rs:7
- Flaky test: mdbook::testsuite.config::env_entire_book_table tests/testsuite/config.rs:263
- Flaky test: mdbook::testsuite.config::env_invalid_value tests/testsuite/config.rs:224
- Flaky test: mdbook::testsuite.config::zoomable_images tests/testsuite/config.rs:342
- Flaky test: mdbook::testsuite.includes::anchored_include tests/testsuite/includes.rs:48
- Flaky test: mdbook::testsuite.includes::include tests/testsuite/includes.rs:8
- Flaky test: mdbook::testsuite.includes::multiline_include tests/testsuite/includes.rs:34
- Flaky test: mdbook::testsuite.includes::rustdoc_include tests/testsuite/includes.rs:117
- Flaky test: mdbook::testsuite.index::index_rewrite tests/testsuite/index.rs:47
- Flaky test: mdbook::testsuite.index::readme_to_index tests/testsuite/index.rs:7
- Flaky test: mdbook::testsuite.init::copy_theme tests/testsuite/init.rs:212
- Flaky test: mdbook::testsuite.markdown::basic_markdown tests/testsuite/markdown.rs:146
- Flaky test: mdbook::testsuite.markdown::custom_header_attributes tests/testsuite/markdown.rs:8
- Flaky test: mdbook::testsuite.markdown::strikethrough tests/testsuite/markdown.rs:75
- Flaky test: mdbook::testsuite.playground::disabled_playground tests/testsuite/playground.rs:22
- Flaky test: mdbook::testsuite.print::chapter_no_h1 tests/testsuite/print.rs:26
- Flaky test: mdbook::testsuite.print::noindex tests/testsuite/print.rs:35
- Flaky test: mdbook::testsuite.redirects::redirect_existing_page tests/testsuite/redirects.rs:38
- Flaky test: mdbook::testsuite.redirects::redirect_removed_with_fragments_only tests/testsuite/redirects.rs:22
- Flaky test: mdbook::testsuite.redirects::redirects_are_emitted_correctly tests/testsuite/redirects.rs:8
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <iframe> without a title REDACTED:136
- Clickable element isn't keyboard-operable REDACTED:169
Serious β 99 finding(s)
- Low coverage: crates/mdbook-compare/src/main.rs crates/mdbook-compare/src/main.rs:1
- Low coverage: crates/mdbook-driver/src/builtin_renderers/markdown_renderer.rs crates/mdbook-driver/src/builtin_renderers/markdown_renderer.rs:1
- Low coverage: crates/xtask/src/changelog.rs crates/xtask/src/changelog.rs:1
- Low coverage: crates/xtask/src/main.rs crates/xtask/src/main.rs:1
- Low coverage: guide/guide-helper/src/lib.rs guide/guide-helper/src/lib.rs:1
- Low coverage: guide/guide-helper/src/main.rs guide/guide-helper/src/main.rs:1
- Low coverage: src/cmd/clean.rs src/cmd/clean.rs:1
- Low coverage: src/cmd/init.rs src/cmd/init.rs:1
- Low coverage: src/cmd/serve.rs src/cmd/serve.rs:1
- Low coverage: src/cmd/watch.rs src/cmd/watch.rs:1
- Low coverage: src/cmd/watch/native.rs src/cmd/watch/native.rs:1
- Low coverage: src/main.rs src/main.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Animation without a prefers-reduced-motion guard crates/mdbook-html/front-end/css/chrome.css:371
- Animation without a prefers-reduced-motion guard crates/mdbook-html/front-end/css/chrome.css:487
- Animation without a prefers-reduced-motion guard crates/mdbook-html/front-end/css/chrome.css:638
- Animation without a prefers-reduced-motion guard crates/mdbook-html/front-end/css/general.css:94
- Animation without a prefers-reduced-motion guard crates/mdbook-html/front-end/css/general.css:98
- FixmeComment src/cmd/build.rs:26
- FixmeComment src/cmd/watch/poller.rs:97
- FixmeComment crates/mdbook-html/src/html_handlebars/hbs_renderer.rs:39
- FixmeComment crates/mdbook-driver/src/mdbook.rs:257
- TodoComment crates/mdbook-html/src/html/print.rs:103
- TodoComment crates/mdbook-html/src/html/serialize.rs:86
- TodoComment crates/mdbook-html/src/html/tokenizer.rs:29
- TodoComment crates/mdbook-html/src/html/tree.rs:625
- mdbook_html::html::print::rewrite_links (cognitive 60) crates/mdbook-html/src/html/print.rs:124
- mdbook_html::html_handlebars::search::index_chapter (cognitive 53) crates/mdbook-html/src/html_handlebars/search.rs:103
- mdbook_html::html_handlebars::hbs_renderer::make_data (cognitive 39) crates/mdbook-html/src/html_handlebars/hbs_renderer.rs:491
- mdbook_html::html::print::make_root_id_map (cognitive 18) crates/mdbook-html/src/html/print.rs:74
- mdbook_driver::mdbook::determine_preprocessors (cognitive 26) crates/mdbook-driver/src/mdbook.rs:447
- mdbook_driver::load::create_missing (cognitive 21) crates/mdbook-driver/src/load.rs:25
- mdbook_driver::builtin_preprocessors::links::take_lines::take_rustdoc_include_anchored_lines (cognitive 19) crates/mdbook-driver/src/builtin_preprocessors/links/take_lines.rs:81
- mdbook_driver::builtin_preprocessors::links::take_lines::take_anchored_lines (cognitive 18) crates/mdbook-driver/src/builtin_preprocessors/links/take_lines.rs:31
- mdbook_html::html_handlebars::hbs_renderer::make_data (cyclomatic 30) crates/mdbook-html/src/html_handlebars/hbs_renderer.rs:491
- mdbook_html::html_handlebars::search::index_chapter (cyclomatic 23) crates/mdbook-html/src/html_handlebars/search.rs:103
- mdbook_html::html::print::rewrite_links (cyclomatic 17) crates/mdbook-html/src/html/print.rs:124
- MarkdownTreeBuilder::start_tag (cognitive 50) crates/mdbook-html/src/html/tree.rs:372
- MarkdownTreeBuilder::update_code_blocks (cognitive 26) crates/mdbook-html/src/html/tree.rs:989
- MarkdownTreeBuilder::convert_fontawesome (cognitive 23) crates/mdbook-html/src/html/tree.rs:1055
- MethodTooLong: MarkdownTreeBuilder.start_tag crates/mdbook-html/src/html/tree.rs:372
- MethodTooLong: HtmlHandlebars.render crates/mdbook-html/src/html_handlebars/hbs_renderer.rs:329
- MethodTooLong: RenderToc.call crates/mdbook-html/src/html_handlebars/helpers/toc.rs:16
- FileTooLong: html/tree.rs crates/mdbook-html/src/html/tree.rs
- FileTooLong: js/book.js crates/mdbook-html/front-end/js/book.js
- FileTooLong: html_handlebars/hbs_renderer.rs crates/mdbook-html/src/html_handlebars/hbs_renderer.rs
- MarkdownTreeBuilder::start_tag (cyclomatic 48) crates/mdbook-html/src/html/tree.rs:372
- MarkdownTreeBuilder::update_code_blocks (cyclomatic 18) crates/mdbook-html/src/html/tree.rs:989
- Hotspot: crates/mdbook-html/src/html/tree.rs crates/mdbook-html/src/html/tree.rs:372
- Hotspot: crates/mdbook-html/src/html_handlebars/hbs_renderer.rs crates/mdbook-html/src/html_handlebars/hbs_renderer.rs:491
- StaticFiles::hash_files (cognitive 30) crates/mdbook-html/src/html_handlebars/static_files.rs:168
- StaticFiles::write_files (cognitive 16) crates/mdbook-html/src/html_handlebars/static_files.rs:225
- mdbook::cmd::init::execute (cognitive 18) src/cmd/init.rs:32
- mdbook::cmd::watch::native::rebuild_on_change (cognitive 18) src/cmd/watch/native.rs:11
- Edited copy of a member (17 corresponding lines) crates/mdbook-driver/src/builtin_preprocessors/links.rs:308
- Edited copy of a member (17 corresponding lines) crates/mdbook-driver/src/mdbook.rs:72
- Duplicated block (6 lines × 2) crates/mdbook-html/src/html_handlebars/static_files.rs:174
- Duplicated block (6 lines × 2) crates/mdbook-html/src/html/tree.rs:320
- Off the main sequence: mdbook-markdown
- Off the main sequence: mdbook-core
- Page without a main landmark crates/mdbook-html/front-end/templates/toc.html.hbs:2
- Focus outline removed in CSS without a :focus replacement crates/mdbook-html/front-end/css/general.css:84
- searcher.globalKeyHandler (cyclomatic 29) crates/mdbook-html/front-end/searcher/searcher.js:356
- MDBook::test_chapter (cyclomatic 19) crates/mdbook-driver/src/mdbook.rs:236
- RenderToc::call (cyclomatic 19) crates/mdbook-html/src/html_handlebars/helpers/toc.rs:16
- book.document.addEventListener("keydown") (cyclomatic 19) crates/mdbook-html/front-end/js/book.js:671
- (anonymous) (cyclomatic 19) crates/mdbook-html/front-end/js/book.js:671
- searcher.makeTeaser (cyclomatic 16) crates/mdbook-html/front-end/searcher/searcher.js:163
- MDBook::test_chapter (cognitive 38) crates/mdbook-driver/src/mdbook.rs:236
- RenderToc::call (cognitive 37) crates/mdbook-html/src/html_handlebars/helpers/toc.rs:16
- searcher.globalKeyHandler (cognitive 35) crates/mdbook-html/front-end/searcher/searcher.js:356
- searcher.makeTeaser (cognitive 32) crates/mdbook-html/front-end/searcher/searcher.js:163
- mdbook_core::utils::fs::copy_files_except_ignored (cognitive 31) crates/mdbook-core/src/utils/fs.rs:112
- Clean::new (cognitive 20) src/cmd/clean.rs:53
- (anonymous) (cognitive 18) crates/mdbook-html/front-end/js/book.js:671
- Theme::new (cognitive 17) crates/mdbook-html/src/theme/mod.rs:66
- book.document.addEventListener("keydown") (cognitive 17) crates/mdbook-html/front-end/js/book.js:671
- REDACTED
- ClassTooLong: MarkdownTreeBuilder crates/mdbook-html/src/html/tree.rs:161
- FunctionTooLong: mdbook_html::html_handlebars::hbs_renderer::make_data crates/mdbook-html/src/html_handlebars/hbs_renderer.rs:491
- REDACTED
- Change coupling: mod.rs β take_lines.rs crates/mdbook-core/src/utils/mod.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (21 corresponding lines) crates/mdbook-core/src/utils/html.rs:6
- Duplicated block (12 lines × 2) crates/mdbook-core/src/utils/html.rs:18
- Duplicated block (7 lines × 2) crates/mdbook-core/src/utils/html.rs:8
- Duplicated block (5 lines × 2) crates/mdbook-html/src/html_handlebars/hbs_renderer.rs:557
- Duplicated block (5 lines × 3) crates/mdbook-html/src/html_handlebars/hbs_renderer.rs:557
- Third-party script without Subresource Integrity REDACTED:53
- JavaScript dependencies are not locked package.json:2
Minor β 66 finding(s)
- Interpolated log message defeats structured logging src/main.rs:142
- Interpolated log message defeats structured logging src/cmd/init.rs:76
- Interpolated log message defeats structured logging src/cmd/serve.rs:125
- Interpolated log message defeats structured logging src/cmd/serve.rs:167
- Interpolated log message defeats structured logging src/cmd/watch/native.rs:19
- Interpolated log message defeats structured logging src/cmd/watch/native.rs:29
- Interpolated log message defeats structured logging src/cmd/watch/native.rs:37
- Interpolated log message defeats structured logging src/cmd/watch/native.rs:49
- Interpolated log message defeats structured logging src/cmd/watch/native.rs:54
- Interpolated log message defeats structured logging src/cmd/watch/native.rs:75
- Interpolated log message defeats structured logging src/cmd/watch/native.rs:90
- Interpolated log message defeats structured logging src/cmd/watch/native.rs:95
- Interpolated log message defeats structured logging src/cmd/watch/native.rs:101
- Interpolated log message defeats structured logging src/cmd/watch/native.rs:116
- Interpolated log message defeats structured logging src/cmd/watch/poller.rs:24
- Interpolated log message defeats structured logging src/cmd/watch/poller.rs:52
- Interpolated log message defeats structured logging src/cmd/watch/poller.rs:59
- Interpolated log message defeats structured logging src/cmd/watch/poller.rs:64
- Interpolated log message defeats structured logging src/cmd/watch/poller.rs:71
- Interpolated log message defeats structured logging src/cmd/watch/poller.rs:101
- Interpolated log message defeats structured logging src/cmd/watch/poller.rs:176
- Interpolated log message defeats structured logging src/cmd/watch/poller.rs:186
- Interpolated log message defeats structured logging src/cmd/watch/poller.rs:200
- Interpolated log message defeats structured logging crates/mdbook-summary/src/lib.rs:202
- Interpolated log message defeats structured logging crates/mdbook-summary/src/lib.rs:208
- Orphaned file crates/mdbook-driver/src/builtin_preprocessors/links/take_lines.rs:1
- Orphaned file src/cmd/watch/native.rs:1
- Orphaned file src/cmd/clean.rs:1
- Orphaned file crates/mdbook-html/src/html/mod.rs:1
- Orphaned file crates/mdbook-html/src/html/admonitions.rs:1
- Orphaned file crates/mdbook-html/src/html/serialize.rs:1
- Orphaned file crates/mdbook-renderer/src/lib.rs:1
- Orphaned file crates/mdbook-html/src/html/tokenizer.rs:1
- Orphaned file crates/mdbook-core/src/utils/html.rs:1
- Off-boarding risk: anonymized user #1
- No ADRs found Cargo.toml:133
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No dependency-update automation package.json:2
- No app-layer HTTPS enforcement detected
- No security response headers detected
- No inbound request validation detected
Minor β 13 finding(s)
- Outdated: clap
- Outdated: clap_complete
- Outdated: ego-tree
- Outdated: futures-util
- Outdated: handlebars
- Outdated: ignore
- Outdated: indexmap
- Outdated: notify
- Outdated: serde_json
- Outdated: sha2
- Outdated: tokio
- Outdated: toml
- Outdated: tower-http
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-b9337e096ebf4f9a8fec59ee9a2ecac0/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-b9337e096ebf4f9a8fec59ee9a2ecac0/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 . | 21 | 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/** . | 1 | 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 |