Executive summary
mjmlio/mjml is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 50 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 44, is the weakest lens and counts most in the score. The best first step is replacing the 100 deprecated dependencies, worth about 5 points. Adding a diagnostic log would lift Production Readiness itself, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 56.
Twenty-six known security holes in the packages the code depends on can be used by attackers. Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages and pinning each tool to an exact version would close both risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed.
The product code is 7,339 lines, about €11,000 to rebuild.
If Production Readiness rose from 44 to 70, the lowest score rated Strong, the score would rise from 50 to about 56.
New since the last survey: 6 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 3 findings
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Rebuild cost: about €11,000 · Estimate
| Cost to rebuild | €3,600 to €18,000, for 60 to 190 hours of work, under 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 50. 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: 7,339 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 (global) | 2 packages.mjml-core.src.createComponent | 3 packages.mjml-core.src.types.type | 4 packages.mjml-accordion.src.Accordion | 5 packages.mjml-accordion.src.AccordionElement | 6 packages.mjml-accordion.src.AccordionText | 7 packages.mjml-accordion.src.AccordionTitle | 8 packages.mjml-body.src | 9 packages.mjml-button.src | 10 packages.mjml-carousel.src.Carousel | 11 packages.mjml-carousel.src.CarouselImage | 12 packages.mjml-column.src | 13 packages.mjml-core.src.types.boolean | 14 packages.mjml-core.src.types.color | 15 packages.mjml-core.src.types.enum | 16 packages.mjml-core.src.types.integer | 17 packages.mjml-core.src.types.string | 18 packages.mjml-core.src.types.unit | 19 packages.mjml-divider.src | 20 packages.mjml-group.src | 21 packages.mjml-head-attributes.src | 22 packages.mjml-head-breakpoint.src | 23 packages.mjml-head-font.src | 24 packages.mjml-head-html-attributes.src | 25 packages.mjml-head-preview.src | 26 packages.mjml-head-style.src | 27 packages.mjml-head-title.src | 28 packages.mjml-head.src | 29 packages.mjml-hero.src | 30 packages.mjml-image.src | 31 packages.mjml-navbar.src.Navbar | 32 packages.mjml-navbar.src.NavbarLink | 33 packages.mjml-raw.src | 34 packages.mjml-section.src | 35 packages.mjml-social.src.Social | 36 packages.mjml-social.src.SocialElement | 37 packages.mjml-spacer.src | 38 packages.mjml-table.src | 39 packages.mjml-text.src | 40 packages.mjml-wrapper.src |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 packages.mjml-core.src.createComponent | ||||||||||||||||||||||||||||||||||||||||
| 3 packages.mjml-core.src.types.type | ||||||||||||||||||||||||||||||||||||||||
| 4 packages.mjml-accordion.src.Accordion | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 packages.mjml-accordion.src.AccordionElement | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 packages.mjml-accordion.src.AccordionText | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 packages.mjml-accordion.src.AccordionTitle | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 packages.mjml-body.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 packages.mjml-button.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 packages.mjml-carousel.src.Carousel | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 packages.mjml-carousel.src.CarouselImage | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 packages.mjml-column.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 packages.mjml-core.src.types.boolean | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 packages.mjml-core.src.types.color | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 packages.mjml-core.src.types.enum | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 packages.mjml-core.src.types.integer | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 packages.mjml-core.src.types.string | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 packages.mjml-core.src.types.unit | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 packages.mjml-divider.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 packages.mjml-group.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 packages.mjml-head-attributes.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 packages.mjml-head-breakpoint.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 packages.mjml-head-font.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 packages.mjml-head-html-attributes.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 packages.mjml-head-preview.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 packages.mjml-head-style.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 packages.mjml-head-title.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 packages.mjml-head.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 packages.mjml-hero.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 packages.mjml-image.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 packages.mjml-navbar.src.Navbar | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 packages.mjml-navbar.src.NavbarLink | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 packages.mjml-raw.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 packages.mjml-section.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 packages.mjml-social.src.Social | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 packages.mjml-social.src.SocialElement | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 packages.mjml-spacer.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 packages.mjml-table.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 packages.mjml-text.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 packages.mjml-wrapper.src | 1 |
4→2 packages.mjml-accordion.src.Accordion uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-accordion.src.Accordion uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-accordion.src.Accordion.MjAccordion→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-accordion.src.Accordion uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-accordion.src.Accordion, while a change to packages.mjml-accordion.src.Accordion can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-accordion.src.Accordion uses a module listed above it, which is the healthy direction.
5→2 packages.mjml-accordion.src.AccordionElement uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-accordion.src.AccordionElement uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-accordion.src.AccordionElement.MjAccordionElement→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-accordion.src.AccordionElement uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-accordion.src.AccordionElement, while a change to packages.mjml-accordion.src.AccordionElement can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-accordion.src.AccordionElement uses a module listed above it, which is the healthy direction.
6→2 packages.mjml-accordion.src.AccordionText uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-accordion.src.AccordionText uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-accordion.src.AccordionText.MjAccordionText→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-accordion.src.AccordionText uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-accordion.src.AccordionText, while a change to packages.mjml-accordion.src.AccordionText can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-accordion.src.AccordionText uses a module listed above it, which is the healthy direction.
7→2 packages.mjml-accordion.src.AccordionTitle uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-accordion.src.AccordionTitle uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-accordion.src.AccordionTitle.MjAccordionTitle→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-accordion.src.AccordionTitle uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-accordion.src.AccordionTitle, while a change to packages.mjml-accordion.src.AccordionTitle can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-accordion.src.AccordionTitle uses a module listed above it, which is the healthy direction.
8→2 packages.mjml-body.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-body.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-body.src.MjBody→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-body.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-body.src, while a change to packages.mjml-body.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-body.src uses a module listed above it, which is the healthy direction.
9→2 packages.mjml-button.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-button.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-button.src.MjButton→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-button.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-button.src, while a change to packages.mjml-button.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-button.src uses a module listed above it, which is the healthy direction.
10→2 packages.mjml-carousel.src.Carousel uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-carousel.src.Carousel uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-carousel.src.Carousel.MjCarousel→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-carousel.src.Carousel uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-carousel.src.Carousel, while a change to packages.mjml-carousel.src.Carousel can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-carousel.src.Carousel uses a module listed above it, which is the healthy direction.
11→2 packages.mjml-carousel.src.CarouselImage uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-carousel.src.CarouselImage uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-carousel.src.CarouselImage.MjCarouselImage→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-carousel.src.CarouselImage uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-carousel.src.CarouselImage, while a change to packages.mjml-carousel.src.CarouselImage can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-carousel.src.CarouselImage uses a module listed above it, which is the healthy direction.
12→2 packages.mjml-column.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-column.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-column.src.MjColumn→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-column.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-column.src, while a change to packages.mjml-column.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-column.src uses a module listed above it, which is the healthy direction.
13→3 packages.mjml-core.src.types.boolean uses packages.mjml-core.src.types.type✕
- Connections
- 1 pair of types, where a type in packages.mjml-core.src.types.boolean uses a type in packages.mjml-core.src.types.type.
- The types involved
packages.mjml-core.src.types.boolean.Boolean→packages.mjml-core.src.types.type.Type
- Direction
- packages.mjml-core.src.types.boolean uses packages.mjml-core.src.types.type, so a change to packages.mjml-core.src.types.type can break packages.mjml-core.src.types.boolean, while a change to packages.mjml-core.src.types.boolean can't break packages.mjml-core.src.types.type.
- Position
- Below the diagonal: packages.mjml-core.src.types.boolean uses a module listed above it, which is the healthy direction.
14→3 packages.mjml-core.src.types.color uses packages.mjml-core.src.types.type✕
- Connections
- 1 pair of types, where a type in packages.mjml-core.src.types.color uses a type in packages.mjml-core.src.types.type.
- The types involved
packages.mjml-core.src.types.color.Color→packages.mjml-core.src.types.type.Type
- Direction
- packages.mjml-core.src.types.color uses packages.mjml-core.src.types.type, so a change to packages.mjml-core.src.types.type can break packages.mjml-core.src.types.color, while a change to packages.mjml-core.src.types.color can't break packages.mjml-core.src.types.type.
- Position
- Below the diagonal: packages.mjml-core.src.types.color uses a module listed above it, which is the healthy direction.
15→3 packages.mjml-core.src.types.enum uses packages.mjml-core.src.types.type✕
- Connections
- 1 pair of types, where a type in packages.mjml-core.src.types.enum uses a type in packages.mjml-core.src.types.type.
- The types involved
packages.mjml-core.src.types.enum.Enum→packages.mjml-core.src.types.type.Type
- Direction
- packages.mjml-core.src.types.enum uses packages.mjml-core.src.types.type, so a change to packages.mjml-core.src.types.type can break packages.mjml-core.src.types.enum, while a change to packages.mjml-core.src.types.enum can't break packages.mjml-core.src.types.type.
- Position
- Below the diagonal: packages.mjml-core.src.types.enum uses a module listed above it, which is the healthy direction.
16→3 packages.mjml-core.src.types.integer uses packages.mjml-core.src.types.type✕
- Connections
- 1 pair of types, where a type in packages.mjml-core.src.types.integer uses a type in packages.mjml-core.src.types.type.
- The types involved
packages.mjml-core.src.types.integer.NInteger→packages.mjml-core.src.types.type.Type
- Direction
- packages.mjml-core.src.types.integer uses packages.mjml-core.src.types.type, so a change to packages.mjml-core.src.types.type can break packages.mjml-core.src.types.integer, while a change to packages.mjml-core.src.types.integer can't break packages.mjml-core.src.types.type.
- Position
- Below the diagonal: packages.mjml-core.src.types.integer uses a module listed above it, which is the healthy direction.
17→3 packages.mjml-core.src.types.string uses packages.mjml-core.src.types.type✕
- Connections
- 1 pair of types, where a type in packages.mjml-core.src.types.string uses a type in packages.mjml-core.src.types.type.
- The types involved
packages.mjml-core.src.types.string.NString→packages.mjml-core.src.types.type.Type
- Direction
- packages.mjml-core.src.types.string uses packages.mjml-core.src.types.type, so a change to packages.mjml-core.src.types.type can break packages.mjml-core.src.types.string, while a change to packages.mjml-core.src.types.string can't break packages.mjml-core.src.types.type.
- Position
- Below the diagonal: packages.mjml-core.src.types.string uses a module listed above it, which is the healthy direction.
18→3 packages.mjml-core.src.types.unit uses packages.mjml-core.src.types.type✕
- Connections
- 1 pair of types, where a type in packages.mjml-core.src.types.unit uses a type in packages.mjml-core.src.types.type.
- The types involved
packages.mjml-core.src.types.unit.Unit→packages.mjml-core.src.types.type.Type
- Direction
- packages.mjml-core.src.types.unit uses packages.mjml-core.src.types.type, so a change to packages.mjml-core.src.types.type can break packages.mjml-core.src.types.unit, while a change to packages.mjml-core.src.types.unit can't break packages.mjml-core.src.types.type.
- Position
- Below the diagonal: packages.mjml-core.src.types.unit uses a module listed above it, which is the healthy direction.
19→2 packages.mjml-divider.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-divider.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-divider.src.MjDivider→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-divider.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-divider.src, while a change to packages.mjml-divider.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-divider.src uses a module listed above it, which is the healthy direction.
20→2 packages.mjml-group.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-group.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-group.src.MjGroup→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-group.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-group.src, while a change to packages.mjml-group.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-group.src uses a module listed above it, which is the healthy direction.
21→2 packages.mjml-head-attributes.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-head-attributes.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-head-attributes.src.MjAttributes→packages.mjml-core.src.createComponent.HeadComponent
- Direction
- packages.mjml-head-attributes.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-head-attributes.src, while a change to packages.mjml-head-attributes.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-head-attributes.src uses a module listed above it, which is the healthy direction.
22→2 packages.mjml-head-breakpoint.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-head-breakpoint.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-head-breakpoint.src.MjBreakpoint→packages.mjml-core.src.createComponent.HeadComponent
- Direction
- packages.mjml-head-breakpoint.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-head-breakpoint.src, while a change to packages.mjml-head-breakpoint.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-head-breakpoint.src uses a module listed above it, which is the healthy direction.
23→2 packages.mjml-head-font.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-head-font.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-head-font.src.MjFont→packages.mjml-core.src.createComponent.HeadComponent
- Direction
- packages.mjml-head-font.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-head-font.src, while a change to packages.mjml-head-font.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-head-font.src uses a module listed above it, which is the healthy direction.
24→2 packages.mjml-head-html-attributes.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-head-html-attributes.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-head-html-attributes.src.MjHtmlAttributes→packages.mjml-core.src.createComponent.HeadComponent
- Direction
- packages.mjml-head-html-attributes.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-head-html-attributes.src, while a change to packages.mjml-head-html-attributes.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-head-html-attributes.src uses a module listed above it, which is the healthy direction.
25→2 packages.mjml-head-preview.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-head-preview.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-head-preview.src.MjPreview→packages.mjml-core.src.createComponent.HeadComponent
- Direction
- packages.mjml-head-preview.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-head-preview.src, while a change to packages.mjml-head-preview.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-head-preview.src uses a module listed above it, which is the healthy direction.
26→2 packages.mjml-head-style.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-head-style.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-head-style.src.MjStyle→packages.mjml-core.src.createComponent.HeadComponent
- Direction
- packages.mjml-head-style.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-head-style.src, while a change to packages.mjml-head-style.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-head-style.src uses a module listed above it, which is the healthy direction.
27→2 packages.mjml-head-title.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-head-title.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-head-title.src.MjTitle→packages.mjml-core.src.createComponent.HeadComponent
- Direction
- packages.mjml-head-title.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-head-title.src, while a change to packages.mjml-head-title.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-head-title.src uses a module listed above it, which is the healthy direction.
28→2 packages.mjml-head.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-head.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-head.src.MjHead→packages.mjml-core.src.createComponent.HeadComponent
- Direction
- packages.mjml-head.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-head.src, while a change to packages.mjml-head.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-head.src uses a module listed above it, which is the healthy direction.
29→2 packages.mjml-hero.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-hero.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-hero.src.MjHero→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-hero.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-hero.src, while a change to packages.mjml-hero.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-hero.src uses a module listed above it, which is the healthy direction.
30→2 packages.mjml-image.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-image.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-image.src.MjImage→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-image.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-image.src, while a change to packages.mjml-image.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-image.src uses a module listed above it, which is the healthy direction.
31→2 packages.mjml-navbar.src.Navbar uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-navbar.src.Navbar uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-navbar.src.Navbar.MjNavbar→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-navbar.src.Navbar uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-navbar.src.Navbar, while a change to packages.mjml-navbar.src.Navbar can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-navbar.src.Navbar uses a module listed above it, which is the healthy direction.
32→2 packages.mjml-navbar.src.NavbarLink uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-navbar.src.NavbarLink uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-navbar.src.NavbarLink.MjNavbarLink→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-navbar.src.NavbarLink uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-navbar.src.NavbarLink, while a change to packages.mjml-navbar.src.NavbarLink can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-navbar.src.NavbarLink uses a module listed above it, which is the healthy direction.
33→2 packages.mjml-raw.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-raw.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-raw.src.MjRaw→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-raw.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-raw.src, while a change to packages.mjml-raw.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-raw.src uses a module listed above it, which is the healthy direction.
34→2 packages.mjml-section.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-section.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-section.src.MjSection→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-section.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-section.src, while a change to packages.mjml-section.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-section.src uses a module listed above it, which is the healthy direction.
35→2 packages.mjml-social.src.Social uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-social.src.Social uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-social.src.Social.MjSocial→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-social.src.Social uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-social.src.Social, while a change to packages.mjml-social.src.Social can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-social.src.Social uses a module listed above it, which is the healthy direction.
36→2 packages.mjml-social.src.SocialElement uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-social.src.SocialElement uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-social.src.SocialElement.MjSocialElement→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-social.src.SocialElement uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-social.src.SocialElement, while a change to packages.mjml-social.src.SocialElement can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-social.src.SocialElement uses a module listed above it, which is the healthy direction.
37→2 packages.mjml-spacer.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-spacer.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-spacer.src.MjSpacer→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-spacer.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-spacer.src, while a change to packages.mjml-spacer.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-spacer.src uses a module listed above it, which is the healthy direction.
38→2 packages.mjml-table.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-table.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-table.src.MjTable→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-table.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-table.src, while a change to packages.mjml-table.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-table.src uses a module listed above it, which is the healthy direction.
39→2 packages.mjml-text.src uses packages.mjml-core.src.createComponent✕
- Connections
- 1 pair of types, where a type in packages.mjml-text.src uses a type in packages.mjml-core.src.createComponent.
- The types involved
packages.mjml-text.src.MjText→packages.mjml-core.src.createComponent.BodyComponent
- Direction
- packages.mjml-text.src uses packages.mjml-core.src.createComponent, so a change to packages.mjml-core.src.createComponent can break packages.mjml-text.src, while a change to packages.mjml-text.src can't break packages.mjml-core.src.createComponent.
- Position
- Below the diagonal: packages.mjml-text.src uses a module listed above it, which is the healthy direction.
40→34 packages.mjml-wrapper.src uses packages.mjml-section.src✕
- Connections
- 1 pair of types, where a type in packages.mjml-wrapper.src uses a type in packages.mjml-section.src.
- The types involved
packages.mjml-wrapper.src.MjWrapper→packages.mjml-section.src.MjSection
- Direction
- packages.mjml-wrapper.src uses packages.mjml-section.src, so a change to packages.mjml-section.src can break packages.mjml-wrapper.src, while a change to packages.mjml-wrapper.src can't break packages.mjml-section.src.
- Position
- Below the diagonal: packages.mjml-wrapper.src 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 52 | High / Critical |
| A05:2025 — Injection | 20 | High / Critical |
Roadmap
Top priorities: Resolve the 100 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (100); Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 100 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (100). | +4.7 pts | Medium | Dependency Hygiene |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +4.3 pts | Medium | Observability |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +4.3 pts | Medium | Security & performance tooling |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. | +1.5 pts | Low | ADR Quality |
| Resolve the 20 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (20). | +2.1 pts | Medium | Dependency Vulnerabilities |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +2.0 pts | Medium | Type Safety |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.0 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.0 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| packages/mjml-cli/src/client.js | 7.1 | Mixed | Cyclomatic Complexity: (anonymous) (cyclomatic 94) |
| packages/mjml-parser-xml/src/index.js | 7.2 | Mixed | Cyclomatic Complexity: index.MJMLParser (cyclomatic 70) |
| package.json | 7.2 | Mixed | Dependency Hygiene: Deprecated: @babel/plugin-proposal-class-properties |
| packages/mjml-section/src/index.js | 7.4 | Mixed | Cyclomatic Complexity: MjSection.renderWithBackground (cyclomatic 26) |
| packages/mjml-browser/package.json | 7.8 | Mixed | Dependency Hygiene: Deprecated: @babel/plugin-proposal-class-properties |
| packages/mjml-cli/package.json | 8.0 | Near-clean | Dependency Hygiene: Deprecated: rimraf |
| packages/mjml-parser-xml/package.json | 8.0 | Near-clean | Dependency Hygiene: Deprecated: rimraf |
| packages/mjml-validator/src/dependencies.js | 8.5 | Near-clean | Cognitive Complexity: dependencies.assignDependencies (cognitive 24) |
| packages/mjml-core/src/helpers/mjmlconfig.js | 8.5 | Near-clean | Cognitive Complexity: mjmlconfig.resolveComponentPath (cognitive 16) |
| packages/mjml-accordion/package.json | 8.5 | Near-clean | Dependency Hygiene: Deprecated: rimraf |
| packages/mjml-body/package.json | 8.5 | Near-clean | Dependency Hygiene: Deprecated: rimraf |
| packages/mjml-button/package.json | 8.5 | Near-clean | Dependency Hygiene: Deprecated: rimraf |
| packages/mjml-carousel/package.json | 8.5 | Near-clean | Dependency Hygiene: Deprecated: rimraf |
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 58 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 58 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, 289 of 314 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
- D11 Test Reliability — 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. Test reliability for the mocha suite in packages/mjml/ was NOT MEASURED: the mocha run in packages/mjml/ produced no per-test report (Exception during run: Error: Cannot find module 'node_modules/mjml-social/lib/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — 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. Test reliability for the mocha suite in packages/mjml-parser-xml/ was NOT MEASURED: the mocha run in packages/mjml-parser-xml/ produced no per-test report (Exception during run: Error: Cannot find module 'node_modules/mjml-social/lib/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (packages/mjml-wrapper/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/mjml-cli/src/client.js` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 81 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was (anonymous) at 94.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with (anonymous) (cyclomatic 94), client.default (cyclomatic 91), index.mjml2html (cyclomatic 84). — 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 5 together lifts Cyclomatic Complexity from 7.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
14 method(s) exceeded the cognitive complexity threshold of 15; the worst was index.mjml2html at 115.
What to do
- Bring the 5 bodies over 30 down to 30 or less in Cognitive Complexity — start with index.mjml2html (cognitive 115), (anonymous) (cognitive 86), index.MJMLParser (cognitive 82). — 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 5 together lifts Cognitive Complexity from 6.3 to about 8.0/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
4 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with REDACTED, client.js. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
0 duplicated block group(s) detected. 0.0 % of the production lines (0 of 7,339) are in a reported copy.
D5 · Coupling
32 production modules (npm), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations, and main-sequence distance (abstractness) is not computed for these modules yet.
What to do
- Resolve the 1 Unstable project mjml-preset-core finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 2 classes have LCOM4 above 3.
D10 · Test Quality
1 skipped (1 with a documented reason), 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 105 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (mocha via `yarn install --frozen-lockfile --ignore-scripts` in packages/mjml/; mocha via `yarn install --frozen-lockfile --ignore-scripts` in packages/mjml-core/ (20 tests); mocha via `yarn install --frozen-lockfile --ignore-scripts` in packages/mjml-parser-xml/): measured (0 flaky).
D12 · Dependency Hygiene
11 outdated direct production npm dependency(ies) of 19 graded, 0 pinning defect(s), across 33 package.json (33 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 4 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 100 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (100). — One of this dimension's main actionable groups (100 recommendation-level).
- Resolve the 37 Deprecated finding(s) in Dependency Hygiene — start with package.json (37). — One of this dimension's main actionable groups (37 warning-level).
- Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 177 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 177 package(s) this repository's committed lockfile installs for a consumer — its 19 production, optional and peer dependency(ies), across 33 product package.json manifest(s), and everything those install in turn. Its 102 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
8 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/mjml-column/src/index.js. Counted over 26 of the 88 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).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 53 document(s) read across 33 unit(s).
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 package.json. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (31 contexts). Contexts: mjml, mjml-accordion, mjml-body, mjml-browser, mjml-button, mjml-carousel, mjml-cli, mjml-column, mjml-core, mjml-divider, mjml-group, mjml-head and 19 more.
D24 · Comment Value
2 of 108 judged comments only repeat the code they sit on (1.9 %). 5 comment(s) in another language or script were not judged.
What to do
- Resolve the 2 redundant comment finding(s) in Comment Value — start with REDACTED, include-path-security.test.js. — One of this dimension's main actionable groups (2 recommendation-level).
D26 · Project Cohesion
0 of 33 build units (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)
20 finding(s): 0 critical, 10 high, 10 medium, 0 low. 8 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) — `packages/mjml-cli/src/client.js` (lines 327–328) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 8 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 (8 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
45 finding(s): 3 critical, 23 high, 17 medium, 2 low.
What to do
- Resolve the 20 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (20). — One of this dimension's main actionable groups (20 issue-level).
- Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
D34 · Knowledge Freshness
10 of 26 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/mjml-core/src/createComponent.js. Counted over 26 of the 88 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 10 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (4), createComponent.js, Navbar.js. — One of this dimension's main actionable groups (10 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: mediaQueries.js↔REDACTED 55%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with mediaQueries.js. — 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:2
- `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:19
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
- `fs.existsSync` in `mjml2html` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:591
- `fs.realpathSync` in `mjml2html` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:592
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
- 0 typed · 96 plain JS — the untyped files are packages/mjml-accordion/src/Accordion.js, packages/mjml-accordion/src/AccordionElement.js, packages/mjml-accordion/src/AccordionText.js, packages/mjml-accordion/src/AccordionTitle.js, packages/mjml-accordion/src/index.js, packages/mjml-body/src/helpers/preview.js (+90 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- 8 duplicated blocks under packages/ have copies in at least two of the sibling directories mjml-button, mjml-column, mjml-group, mjml-hero, mjml-navbar, mjml-section (+2 more sibling(s) not listed) — 7 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/mjml-column/src/index.js:529
- packages/mjml-accordion/src/AccordionText.js:38 · packages/mjml-accordion/src/AccordionTitle.js:35 — the two spans are one implementation copied and then locally edited — 186 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mjml-accordion/src/AccordionText.js:38
- packages/mjml-parser-xml/src/index.js:140 · packages/mjml-parser-xml/src/index.js:213 — the two spans are one implementation copied and then locally edited — 135 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mjml-parser-xml/src/index.js:140
- REDACTED:209 · REDACTED:240 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:209
- packages/mjml-column/src/index.js:529 · packages/mjml-hero/src/index.js:202 — the 2 copies are spread across 2 files, and the CITED SPAN is a DECLARATION HEADER — the name, parameter list with its constraints and defaults, and base-type clause of a declaration — rather than statements inside a body. A header cannot be lifted into a helper: there is no expression position for a call to stand in, and the copies are frequently required to match, because one declaration passes its parameters straight through to the other. So the move is not extraction. Give the repeated pieces names — factor a long constraint or base-type expression into one named type both declarations refer to — and where the headers must stay identical, derive one from the other (a shared base declaration, or a single alias that spells the parameter set once) so that changing it once changes both. Where the language offers neither, treat the two as a pair that must be edited together: they drift apart the first time only one of them is changed, which is why this is reported. — packages/mjml-column/src/index.js:529
- packages/mjml-column/src/index.js:182 · packages/mjml-group/src/index.js:70 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/mjml-column/src/index.js:182
- packages/mjml-accordion/src/Accordion.js:81 · packages/mjml-accordion/src/AccordionElement.js:51 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/mjml-accordion/src/Accordion.js:81
- REDACTED:136 · REDACTED:168 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:136
- packages/mjml-column/src/index.js:48 · packages/mjml-group/src/index.js:26 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/mjml-column/src/index.js:48
- REDACTED:276 · REDACTED:324 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:276
- packages/mjml-section/src/index.js:256 · packages/mjml-wrapper/src/index.js:14 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/mjml-section/src/index.js:256
- packages/mjml-group/src/index.js:172 · packages/mjml-social/src/Social.js:92 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mjml-group/src/index.js:172
- packages/mjml-button/src/index.js:88 · packages/mjml-navbar/src/NavbarLink.js:46 — the two spans are one implementation copied and then locally edited — 80 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mjml-button/src/index.js:88
- REDACTED:84 · REDACTED:96 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:84
- packages/mjml-column/src/index.js:76 · packages/mjml-section/src/index.js:90 — the two spans are one implementation copied and then locally edited — 55 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mjml-column/src/index.js:76
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- packages/mjml-browser/browser-mocks/mjmlconfig.js:3 reaches past another workspace package's public entry into its internals with a relative path (../../mjml-core/lib/components) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/mjml-browser/browser-mocks/mjmlconfig.js:3
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- (anonymous) has cyclomatic complexity 79 and cognitive complexity 72; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mjml-cli/src/client.js:36
- mjml2html has cyclomatic complexity 67 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:466
- renderWithBackground has cyclomatic complexity 17 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mjml-section/src/index.js:292
- onopentag has cyclomatic complexity 13 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mjml-parser-xml/src/index.js:324
- handleInclude has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mjml-parser-xml/src/index.js:213
- MJMLParser has cyclomatic complexity 11 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mjml-parser-xml/src/index.js:29
- resolveComponentPath has cyclomatic complexity 11 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mjml-core/src/helpers/mjmlconfig.js:46
R3 · Large Files
- REDACTED has 882 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
- packages/mjml-column/src/index.js has 490 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mjml-column/src/index.js:1
- packages/mjml-section/src/index.js has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mjml-section/src/index.js:1
- packages/mjml-parser-xml/src/index.js has 406 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mjml-parser-xml/src/index.js:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×7) — packages/mjml-cli/src/client.js:1, packages/mjml-cli/src/commands/watchFiles.js:1, REDACTED:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
- 8 file(s) (~736 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/mjml-cli
- Nothing imports this binding — it is safe to review for removal. — packages/mjml-core/src/helpers/formatHtml.js:31
R8 · Dependency Hygiene
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
- Declared in packages/mjml-core/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X24 · Document value interpolated into markup unescaped
- `height` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the `height` attribute of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `height` at this site, or validate it against the shape the position accepts before interpolating it. — packages/mjml-text/src/index.js:75
- `this.getAttribute('align',)` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the `align` attribute of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `this.getAttribute('align',)` at this site, or validate it against the shape the position accepts before interpolating it. — packages/mjml-navbar/src/Navbar.js:166
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — packages/mjml-parser-xml/src/index.js:74, packages/mjml-cli/src/client.js:152, REDACTED:65
- `catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — packages/mjml-parser-xml/src/index.js:87
What to do
- Swallowed exception (empty catch)
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 55% | Adequate — gated by R1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 97% | Exemplary | Strongest area. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 44% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 47% | Weak — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 70% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- 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.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not applicable — JavaScript has no interface declaration, so there is no declared member list whose width this check could measure
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. 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.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (614 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — packages/mjml/ runs mocha but declares no coverage provider, so the suite can run and still produce no lcov — add `c8` (or `nyc`) as a devDependency so the suite can be wrapped for coverage. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a 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.
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: 81 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — 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
- X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Plain JavaScript carries no type annotations and commits no tsconfig, so it states no null-typed discipline for this check to grade: there is nothing here that switches null checking on or off, and TypeScript (or `// @ts-check`) is how a repository acquires one — advice, not a defect this card measures. Not a gap in the analyzer and not a finding about your code.
- 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 — 36 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 135 finding(s)
- Deprecated: @babel/plugin-proposal-class-properties package.json:22
- Deprecated: babel-eslint package.json:26
- Deprecated: eslint package.json:30
- Deprecated: rimraf package.json:39
- Deprecated: rimraf packages/mjml-accordion/package.json:30
- Deprecated: rimraf packages/mjml-body/package.json:30
- Deprecated: @babel/plugin-proposal-class-properties packages/mjml-browser/package.json:27
- Deprecated: rimraf packages/mjml-browser/package.json:32
- Deprecated: rimraf packages/mjml-button/package.json:30
- Deprecated: rimraf packages/mjml-carousel/package.json:30
- Deprecated: rimraf packages/mjml-cli/package.json:41
- Deprecated: rimraf packages/mjml-column/package.json:30
- Deprecated: rimraf packages/mjml-core/package.json:41
- Deprecated: rimraf packages/mjml-divider/package.json:30
- Deprecated: rimraf packages/mjml-group/package.json:30
- Deprecated: rimraf packages/mjml-head-attributes/package.json:30
- Deprecated: rimraf packages/mjml-head-breakpoint/package.json:30
- Deprecated: rimraf packages/mjml-head-font/package.json:30
- Deprecated: rimraf packages/mjml-head-html-attributes/package.json:30
- Deprecated: rimraf packages/mjml-head-preview/package.json:30
- Deprecated: rimraf packages/mjml-head-style/package.json:30
- Deprecated: rimraf packages/mjml-head-title/package.json:30
- Deprecated: rimraf packages/mjml-head/package.json:30
- Deprecated: rimraf packages/mjml-hero/package.json:30
- Deprecated: rimraf packages/mjml-image/package.json:30
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No test reaches this file packages/mjml-cli/src/client.js:1
- No test reaches this file packages/mjml-cli/src/commands/watchFiles.js:1
- No test reaches this file REDACTED:1
- No test reaches this file packages/mjml-cli/src/commands/outputToFile.js:1
- No test reaches this file packages/mjml-cli/src/commands/readStream.js:1
- No test reaches this file packages/mjml-cli/src/commands/readFile.js:1
- No test reaches this file packages/mjml-cli/src/commands/outputToConsole.js:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Swallowed exception (empty catch) packages/mjml-parser-xml/src/index.js:74
- Swallowed exception (empty catch) packages/mjml-cli/src/client.js:152
- Swallowed exception (empty catch) REDACTED:65
- FunctionTooLong: index.MJMLParser packages/mjml-parser-xml/src/index.js:29
- FunctionTooLong: client.default packages/mjml-cli/src/client.js:36
- Sync-over-async blocking REDACTED:591
- Sync-over-async blocking REDACTED:592
- Duplicated block (17 lines × 2 locations) packages/mjml-accordion/src/Accordion.js:81
- Duplicated block (17 lines × 2 locations) REDACTED:136
- Duplicated block (14 lines × 2 locations) REDACTED:276
- Duplicated block (14 lines × 2 locations) packages/mjml-section/src/index.js:256
- Unused dependency 'cssnano'
- Unused dependency 'cssnano'
- Document value reaches a markup attribute unescaped packages/mjml-text/src/index.js:75
- Document value reaches a markup attribute unescaped packages/mjml-navbar/src/Navbar.js:166
- (anonymous) (cyclomatic 94) packages/mjml-cli/src/client.js:36
- client.default (cyclomatic 91) packages/mjml-cli/src/client.js:36
- index.mjml2html (cyclomatic 84) REDACTED:466
- index.MJMLParser (cyclomatic 70) packages/mjml-parser-xml/src/index.js:29
- MjSection.renderWithBackground (cyclomatic 26) packages/mjml-section/src/index.js:292
- index.mjml2html (cognitive 115) REDACTED:466
- (anonymous) (cognitive 86) packages/mjml-cli/src/client.js:36
- index.MJMLParser (cognitive 82) packages/mjml-parser-xml/src/index.js:29
- client.default (cognitive 81) packages/mjml-cli/src/client.js:36
- renderWithBackground (cognitive 33) packages/mjml-section/src/index.js:292
- dependencies.assignDependencies (cognitive 24) packages/mjml-validator/src/dependencies.js:1
- MJMLParser::onopentag (cognitive 17) packages/mjml-parser-xml/src/index.js:324
- (anonymous) (cognitive 17) REDACTED:12
- mjmlconfig.resolveComponentPath (cognitive 16) packages/mjml-core/src/helpers/mjmlconfig.js:46
- REDACTED
- FileTooLong: REDACTED REDACTED
- MethodTooLong: MjSection.renderWithBackground packages/mjml-section/src/index.js:292
- Change coupling: mediaQueries.js ↔ REDACTED packages/mjml-core/src/helpers/mediaQueries.js:1
- REDACTED
- REDACTED
- REDACTED
- Unstable project mjml-preset-core
- Coverage not measured — JavaScript/TypeScript suite
- No structured logging
- Type Safety
- Duplication concentrated across 8 sibling directories (8 clone groups) packages/mjml-column/src/index.js:529
- Duplicated block with local edits (34 matched lines × 2 locations) packages/mjml-accordion/src/AccordionText.js:38
- Duplicated block with local edits (30 matched lines × 2 locations) packages/mjml-parser-xml/src/index.js:140
- Duplicated block (20 lines × 2 locations) REDACTED:209
- Duplicated block (19 lines × 2 locations) packages/mjml-column/src/index.js:529
- Duplicated block (18 lines × 2 locations) packages/mjml-column/src/index.js:182
- Duplicated block (16 lines × 2 locations) packages/mjml-column/src/index.js:48
- Duplicated block with local edits (12 matched lines × 2 locations) packages/mjml-group/src/index.js:172
- Duplicated block with local edits (11 matched lines × 2 locations) packages/mjml-button/src/index.js:88
- Duplicated block (11 lines × 2 locations) REDACTED:84
- Duplicated block with local edits (7 matched lines × 2 locations) packages/mjml-column/src/index.js:76
- Boundary violation [package:test-cross-package-internals] packages/mjml-browser/browser-mocks/mjmlconfig.js:3
- Complex function (anonymous) (cyclomatic 79, cognitive 72) packages/mjml-cli/src/client.js:36
- Complex function mjml2html (cyclomatic 67, cognitive 89) REDACTED:466
- Complex function renderWithBackground (cyclomatic 17, cognitive 17) packages/mjml-section/src/index.js:292
- Complex function onopentag (cyclomatic 13, cognitive 17) packages/mjml-parser-xml/src/index.js:324
- Complex function handleInclude (cyclomatic 13, cognitive 11) packages/mjml-parser-xml/src/index.js:213
- Complex function MJMLParser (cyclomatic 11, cognitive 18) packages/mjml-parser-xml/src/index.js:29
- Complex function resolveComponentPath (cyclomatic 11, cognitive 16) packages/mjml-core/src/helpers/mjmlconfig.js:46
- REDACTED: 882 lines of code REDACTED:1
- packages/mjml-column/src/index.js: 490 lines of code packages/mjml-column/src/index.js:1
- packages/mjml-section/src/index.js: 479 lines of code packages/mjml-section/src/index.js:1
- packages/mjml-parser-xml/src/index.js: 406 lines of code packages/mjml-parser-xml/src/index.js:1
- No typecheck script
- Swallowed exception (caught, then discarded) packages/mjml-parser-xml/src/index.js:87
Minor — 132 finding(s)
- Deprecated: @evocateur/libnpmaccess REDACTED:1265
- Deprecated: @evocateur/libnpmpublish REDACTED:1276
- Deprecated: @evocateur/npm-registry-fetch REDACTED:1291
- Deprecated: @evocateur/pacote REDACTED:1304
- Deprecated: @humanwhocodes/config-array REDACTED:1339
- Deprecated: @humanwhocodes/object-schema REDACTED:1348
- Deprecated: @lerna/add REDACTED:1408
- Deprecated: @lerna/bootstrap REDACTED:1424
- Deprecated: @lerna/changed REDACTED:1453
- Deprecated: @lerna/check-working-tree REDACTED:1463
- Deprecated: @lerna/clean REDACTED:1481
- Deprecated: @lerna/cli REDACTED:1495
- Deprecated: @lerna/collect-uncommitted REDACTED:1505
- Deprecated: @lerna/collect-updates REDACTED:1515
- Deprecated: @lerna/command REDACTED:1526
- Deprecated: @lerna/conventional-commits REDACTED:1542
- Deprecated: @lerna/create-symlink REDACTED:1559
- Deprecated: @lerna/create REDACTED:1568
- Deprecated: @lerna/describe-ref REDACTED:1592
- Deprecated: @lerna/diff REDACTED:1600
- Deprecated: @lerna/exec REDACTED:1610
- Deprecated: @lerna/filter-options REDACTED:1623
- Deprecated: @lerna/filter-packages REDACTED:1634
- Deprecated: @lerna/get-npm-exec-opts REDACTED:1643
- Deprecated: @lerna/get-packed REDACTED:1650
- Orphaned file packages/mjml-core/src/createComponent.js:1
- Orphaned file packages/mjml-navbar/src/Navbar.js:1
- Orphaned file packages/mjml-group/src/index.js:1
- Orphaned file packages/mjml-button/src/index.js:1
- Orphaned file packages/mjml-image/src/index.js:1
- Orphaned file packages/mjml-core/src/helpers/mjmlconfig.js:1
- Orphaned file packages/mjml-accordion/src/AccordionTitle.js:1
- Orphaned file packages/mjml-navbar/src/NavbarLink.js:1
- Orphaned file packages/mjml-accordion/src/AccordionElement.js:1
- Orphaned file packages/mjml-divider/src/index.js:1
- Duplicated predicate packages/mjml-column/src/index.js:461
- Duplicated predicate packages/mjml-cli/src/client.js:295
- Duplicated predicate packages/mjml-cli/src/client.js:296
- Duplicated predicate packages/mjml-accordion/src/AccordionText.js:76
- Duplicated predicate packages/mjml-accordion/src/AccordionText.js:73
- Duplicated predicate packages/mjml-accordion/src/AccordionText.js:67
- redundant comment packages/mjml-group/src/index.js:120
- redundant comment packages/mjml/test/include-path-security.test.js:164
- REDACTED
- REDACTED
- Outdated (npm): htmlparser2 packages/mjml-parser-xml/package.json:27
- Off-boarding risk: anonymized user #1
- No ADRs found packages/mjml-cli/package.json:6
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:2
- No dependency-update automation package.json:19
- Unused export 'default' packages/mjml-core/src/helpers/formatHtml.js:31
Minor — 11 finding(s)
- Outdated (npm): @babel/runtime
- Outdated (npm): chokidar
- Outdated (npm): cssnano
- Outdated (npm): cssnano-preset-lite
- Outdated (npm): glob
- Outdated (npm): htmlnano
- Outdated (npm): juice
- Outdated (npm): minimatch
- Outdated (npm): postcss
- Outdated (npm): yargs
- Skipped (documented): recompiles when a symlinked include target changes packages/mjml/test/watch-cli.test.js:272
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-7aa4e231e0324806b8c04c8505ccc7fd/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-7aa4e231e0324806b8c04c8505ccc7fd/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 --exclude packages/mjml-core/src/types . | 20 | 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/** . | 45 | 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. semgrep could not parse 1 file(s) — `packages/mjml-cli/src/client.js` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 |