Executive summary
Nagi-ovo/dsh-ads falls short of our standard for a preview release because we found no automated security scanning of the code, its secrets or its dependencies. It scores 58.6 out of 100 and is rated Adequate, and six of its nine critical findings are security problems in the build pipeline and in the packages it uses.
Production Readiness, at 54.6, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is keeping a changelog, worth about 2.1 points. Recording design decisions comes next, worth about 1.9 points.
Three known security holes in the packages the code depends on can be used by attackers. Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and three controls can't be used without a mouse. Updating the vulnerable packages, pinning each tool to an exact version and making the controls work with a keyboard would close these risks.
The product code is 14,597 lines, about €17,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
Rebuild cost: about €17,000 · Estimate
| Cost to rebuild | €5,800 to €29,000, for 97 to 306 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. 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: 14,597 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: which parts of the code depend on which
| uses → | 1 (global) | 2 scripts | 3 src.catalog | 4 src.client.AdsSection | 5 src.client.feed | 6 src.client.hitbox | 7 src.client.persist | 8 src.client.plugin-banner | 9 src.client.schedule | 10 src.client.sound | 11 src.client.speed-score | 12 src.client.star-check | 13 src.client.types | 14 src.client.useDrag | 15 src.protocol | 16 src | 17 src.client.AdLayer | 18 src.client.InferenceRewardGate | 19 src.client.InlineAd | 20 src.client.Lightbox | 21 src.client.ShieldToast | 22 src.client.SpeedToast | 23 src.client.ToastPopup | 24 src.client.VirusToast | 25 src.client.contrib-ads_generated | 26 src.client.placement | 27 src.client.settings | 28 src.client.AdBanner | 29 src.client.AdControls | 30 src.client.GamePoster | 31 src.client |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | |||||||||||||||||||||||||||||||
| 2 scripts | |||||||||||||||||||||||||||||||
| 3 src.catalog | |||||||||||||||||||||||||||||||
| 4 src.client.AdsSection | |||||||||||||||||||||||||||||||
| 5 src.client.feed | |||||||||||||||||||||||||||||||
| 6 src.client.hitbox | |||||||||||||||||||||||||||||||
| 7 src.client.persist | |||||||||||||||||||||||||||||||
| 8 src.client.plugin-banner | |||||||||||||||||||||||||||||||
| 9 src.client.schedule | |||||||||||||||||||||||||||||||
| 10 src.client.sound | |||||||||||||||||||||||||||||||
| 11 src.client.speed-score | |||||||||||||||||||||||||||||||
| 12 src.client.star-check | |||||||||||||||||||||||||||||||
| 13 src.client.types | |||||||||||||||||||||||||||||||
| 14 src.client.useDrag | |||||||||||||||||||||||||||||||
| 15 src.protocol | |||||||||||||||||||||||||||||||
| 16 src | 2 | 3 | |||||||||||||||||||||||||||||
| 17 src.client.AdLayer | 1 | 1 | |||||||||||||||||||||||||||||
| 18 src.client.InferenceRewardGate | 4 | ||||||||||||||||||||||||||||||
| 19 src.client.InlineAd | 1 | ||||||||||||||||||||||||||||||
| 20 src.client.Lightbox | 2 | ||||||||||||||||||||||||||||||
| 21 src.client.ShieldToast | 1 | ||||||||||||||||||||||||||||||
| 22 src.client.SpeedToast | 1 | 1 | |||||||||||||||||||||||||||||
| 23 src.client.ToastPopup | 2 | ||||||||||||||||||||||||||||||
| 24 src.client.VirusToast | 1 | ||||||||||||||||||||||||||||||
| 25 src.client.contrib-ads_generated | 1 | ||||||||||||||||||||||||||||||
| 26 src.client.placement | 1 | ||||||||||||||||||||||||||||||
| 27 src.client.settings | 1 | ||||||||||||||||||||||||||||||
| 28 src.client.AdBanner | 2 | 1 | |||||||||||||||||||||||||||||
| 29 src.client.AdControls | 1 | 1 | |||||||||||||||||||||||||||||
| 30 src.client.GamePoster | 1 | 2 | 1 | ||||||||||||||||||||||||||||
| 31 src.client | 1 | 1 | 1 | 3 | 1 | 1 | 8 | 1 | 2 | 1 | 5 | 1 | 1 | 1 | 1 | 1 | 5 | 1 | 1 | 1 |
16→13 src uses src.client.types✕
- Connections
- 2 pairs of types, where a type in src uses a type in src.client.types.
- The types involved
src.index→src.client.types.AdCreativesrc.index→src.client.types.AdLocale
- Direction
- src uses src.client.types, so a change to src.client.types can break src, while a change to src can't break src.client.types.
- Position
- Below the diagonal: src uses a module listed above it, which is the healthy direction.
16→15 src uses src.protocol✕
- Connections
- 3 pairs of types, where a type in src uses a type in src.protocol.
- The types involved
src.CacheSlot→src.protocol.RegistryPayloadsrc.catalog→src.protocol.RegistryPayloadsrc.star-host→src.protocol.StarCheckPayload
- Direction
- src uses src.protocol, so a change to src.protocol can break src, while a change to src can't break src.protocol.
- Position
- Below the diagonal: src uses a module listed above it, which is the healthy direction.
17→9 src.client.AdLayer uses src.client.schedule✕
- Connections
- 1 pair of types, where a type in src.client.AdLayer uses a type in src.client.schedule.
- The types involved
src.client.AdLayer.AdLayerProps→src.client.schedule.SpawnConfig
- Direction
- src.client.AdLayer uses src.client.schedule, so a change to src.client.schedule can break src.client.AdLayer, while a change to src.client.AdLayer can't break src.client.schedule.
- Position
- Below the diagonal: src.client.AdLayer uses a module listed above it, which is the healthy direction.
17→13 src.client.AdLayer uses src.client.types✕
- Connections
- 1 pair of types, where a type in src.client.AdLayer uses a type in src.client.types.
- The types involved
src.client.AdLayer.AdLayerProps→src.client.types.AdLocale
- Direction
- src.client.AdLayer uses src.client.types, so a change to src.client.types can break src.client.AdLayer, while a change to src.client.AdLayer can't break src.client.types.
- Position
- Below the diagonal: src.client.AdLayer uses a module listed above it, which is the healthy direction.
18→13 src.client.InferenceRewardGate uses src.client.types✕
- Connections
- 4 pairs of types, where a type in src.client.InferenceRewardGate uses a type in src.client.types.
- The types involved
src.client.InferenceRewardGate.InferenceRewardGateProps→src.client.types.AdCreativesrc.client.InferenceRewardGate.InferenceRewardGateProps→src.client.types.AdLocalesrc.client.InferenceRewardGate.RewardCardProps→src.client.types.AdCreativesrc.client.InferenceRewardGate.RewardCardProps→src.client.types.AdLocale
- Direction
- src.client.InferenceRewardGate uses src.client.types, so a change to src.client.types can break src.client.InferenceRewardGate, while a change to src.client.InferenceRewardGate can't break src.client.types.
- Position
- Below the diagonal: src.client.InferenceRewardGate uses a module listed above it, which is the healthy direction.
19→13 src.client.InlineAd uses src.client.types✕
- Connections
- 1 pair of types, where a type in src.client.InlineAd uses a type in src.client.types.
- The types involved
src.client.InlineAd.InlineAdInjected→src.client.types.AdLocale
- Direction
- src.client.InlineAd uses src.client.types, so a change to src.client.types can break src.client.InlineAd, while a change to src.client.InlineAd can't break src.client.types.
- Position
- Below the diagonal: src.client.InlineAd uses a module listed above it, which is the healthy direction.
20→13 src.client.Lightbox uses src.client.types✕
- Connections
- 2 pairs of types, where a type in src.client.Lightbox uses a type in src.client.types.
- The types involved
src.client.Lightbox.LightboxProps→src.client.types.AdCreativesrc.client.Lightbox.LightboxProps→src.client.types.AdLocale
- Direction
- src.client.Lightbox uses src.client.types, so a change to src.client.types can break src.client.Lightbox, while a change to src.client.Lightbox can't break src.client.types.
- Position
- Below the diagonal: src.client.Lightbox uses a module listed above it, which is the healthy direction.
21→13 src.client.ShieldToast uses src.client.types✕
- Connections
- 1 pair of types, where a type in src.client.ShieldToast uses a type in src.client.types.
- The types involved
src.client.ShieldToast.ShieldToastProps→src.client.types.AdLocale
- Direction
- src.client.ShieldToast uses src.client.types, so a change to src.client.types can break src.client.ShieldToast, while a change to src.client.ShieldToast can't break src.client.types.
- Position
- Below the diagonal: src.client.ShieldToast uses a module listed above it, which is the healthy direction.
22→11 src.client.SpeedToast uses src.client.speed-score✕
- Connections
- 1 pair of types, where a type in src.client.SpeedToast uses a type in src.client.speed-score.
- The types involved
src.client.SpeedToast.SpeedToastProps→src.client.speed-score.SpeedReading
- Direction
- src.client.SpeedToast uses src.client.speed-score, so a change to src.client.speed-score can break src.client.SpeedToast, while a change to src.client.SpeedToast can't break src.client.speed-score.
- Position
- Below the diagonal: src.client.SpeedToast uses a module listed above it, which is the healthy direction.
22→13 src.client.SpeedToast uses src.client.types✕
- Connections
- 1 pair of types, where a type in src.client.SpeedToast uses a type in src.client.types.
- The types involved
src.client.SpeedToast.SpeedToastProps→src.client.types.AdLocale
- Direction
- src.client.SpeedToast uses src.client.types, so a change to src.client.types can break src.client.SpeedToast, while a change to src.client.SpeedToast can't break src.client.types.
- Position
- Below the diagonal: src.client.SpeedToast uses a module listed above it, which is the healthy direction.
23→13 src.client.ToastPopup uses src.client.types✕
- Connections
- 2 pairs of types, where a type in src.client.ToastPopup uses a type in src.client.types.
- The types involved
src.client.ToastPopup.ToastPopupProps→src.client.types.AdCreativesrc.client.ToastPopup.ToastPopupProps→src.client.types.AdLocale
- Direction
- src.client.ToastPopup uses src.client.types, so a change to src.client.types can break src.client.ToastPopup, while a change to src.client.ToastPopup can't break src.client.types.
- Position
- Below the diagonal: src.client.ToastPopup uses a module listed above it, which is the healthy direction.
24→13 src.client.VirusToast uses src.client.types✕
- Connections
- 1 pair of types, where a type in src.client.VirusToast uses a type in src.client.types.
- The types involved
src.client.VirusToast.VirusToastProps→src.client.types.AdLocale
- Direction
- src.client.VirusToast uses src.client.types, so a change to src.client.types can break src.client.VirusToast, while a change to src.client.VirusToast can't break src.client.types.
- Position
- Below the diagonal: src.client.VirusToast uses a module listed above it, which is the healthy direction.
25→8 src.client.contrib-ads_generated uses src.client.plugin-banner✕
- Connections
- 1 pair of types, where a type in src.client.contrib-ads_generated uses a type in src.client.plugin-banner.
- The types involved
src.client.contrib-ads_generated.ContribAd→src.client.plugin-banner.AdCopy
- Direction
- src.client.contrib-ads_generated uses src.client.plugin-banner, so a change to src.client.plugin-banner can break src.client.contrib-ads_generated, while a change to src.client.contrib-ads_generated can't break src.client.plugin-banner.
- Position
- Below the diagonal: src.client.contrib-ads_generated uses a module listed above it, which is the healthy direction.
26→13 src.client.placement uses src.client.types✕
- Connections
- 1 pair of types, where a type in src.client.placement uses a type in src.client.types.
- The types involved
src.client.placement.LaidOut→src.client.types.PlacedAd
- Direction
- src.client.placement uses src.client.types, so a change to src.client.types can break src.client.placement, while a change to src.client.placement can't break src.client.types.
- Position
- Below the diagonal: src.client.placement uses a module listed above it, which is the healthy direction.
27→13 src.client.settings uses src.client.types✕
- Connections
- 1 pair of types, where a type in src.client.settings uses a type in src.client.types.
- The types involved
src.client.settings.PlacementRow→src.client.types.AdLocale
- Direction
- src.client.settings uses src.client.types, so a change to src.client.types can break src.client.settings, while a change to src.client.settings can't break src.client.types.
- Position
- Below the diagonal: src.client.settings uses a module listed above it, which is the healthy direction.
28→13 src.client.AdBanner uses src.client.types✕
- Connections
- 2 pairs of types, where a type in src.client.AdBanner uses a type in src.client.types.
- The types involved
src.client.AdBanner.AdBannerProps→src.client.types.AdLocalesrc.client.AdBanner.AdBannerProps→src.client.types.PlacedAd
- Direction
- src.client.AdBanner uses src.client.types, so a change to src.client.types can break src.client.AdBanner, while a change to src.client.AdBanner can't break src.client.types.
- Position
- Below the diagonal: src.client.AdBanner uses a module listed above it, which is the healthy direction.
28→26 src.client.AdBanner uses src.client.placement✕
- Connections
- 1 pair of types, where a type in src.client.AdBanner uses a type in src.client.placement.
- The types involved
src.client.AdBanner.AdBannerProps→src.client.placement.AdBox
- Direction
- src.client.AdBanner uses src.client.placement, so a change to src.client.placement can break src.client.AdBanner, while a change to src.client.AdBanner can't break src.client.placement.
- Position
- Below the diagonal: src.client.AdBanner uses a module listed above it, which is the healthy direction.
29→13 src.client.AdControls uses src.client.types✕
- Connections
- 1 pair of types, where a type in src.client.AdControls uses a type in src.client.types.
- The types involved
src.client.AdControls.AdControlsProps→src.client.types.AdLocale
- Direction
- src.client.AdControls uses src.client.types, so a change to src.client.types can break src.client.AdControls, while a change to src.client.AdControls can't break src.client.types.
- Position
- Below the diagonal: src.client.AdControls uses a module listed above it, which is the healthy direction.
29→27 src.client.AdControls uses src.client.settings✕
- Connections
- 1 pair of types, where a type in src.client.AdControls uses a type in src.client.settings.
- The types involved
src.client.AdControls.AdControlsProps→src.client.settings.AdSettings
- Direction
- src.client.AdControls uses src.client.settings, so a change to src.client.settings can break src.client.AdControls, while a change to src.client.AdControls can't break src.client.settings.
- Position
- Below the diagonal: src.client.AdControls uses a module listed above it, which is the healthy direction.
30→7 src.client.GamePoster uses src.client.persist✕
- Connections
- 1 pair of types, where a type in src.client.GamePoster uses a type in src.client.persist.
- The types involved
src.client.GamePoster.GamePosterProps→src.client.persist.Anchor
- Direction
- src.client.GamePoster uses src.client.persist, so a change to src.client.persist can break src.client.GamePoster, while a change to src.client.GamePoster can't break src.client.persist.
- Position
- Below the diagonal: src.client.GamePoster uses a module listed above it, which is the healthy direction.
30→13 src.client.GamePoster uses src.client.types✕
- Connections
- 2 pairs of types, where a type in src.client.GamePoster uses a type in src.client.types.
- The types involved
src.client.GamePoster.GamePosterProps→src.client.types.AdCreativesrc.client.GamePoster.GamePosterProps→src.client.types.AdLocale
- Direction
- src.client.GamePoster uses src.client.types, so a change to src.client.types can break src.client.GamePoster, while a change to src.client.GamePoster can't break src.client.types.
- Position
- Below the diagonal: src.client.GamePoster uses a module listed above it, which is the healthy direction.
30→29 src.client.GamePoster uses src.client.AdControls✕
- Connections
- 1 pair of types, where a type in src.client.GamePoster uses a type in src.client.AdControls.
- The types involved
src.client.GamePoster.GamePosterProps→src.client.AdControls.AdControlsProps
- Direction
- src.client.GamePoster uses src.client.AdControls, so a change to src.client.AdControls can break src.client.GamePoster, while a change to src.client.GamePoster can't break src.client.AdControls.
- Position
- Below the diagonal: src.client.GamePoster uses a module listed above it, which is the healthy direction.
31→4 src.client uses src.client.AdsSection✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.AdsSection.
- The types involved
src.client.AdsSection→src.client.AdsSection.ToggleProps
- Direction
- src.client uses src.client.AdsSection, so a change to src.client.AdsSection can break src.client, while a change to src.client can't break src.client.AdsSection.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→6 src.client uses src.client.hitbox✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.hitbox.
- The types involved
src.client.hitbox→src.client.hitbox.Hitbox
- Direction
- src.client uses src.client.hitbox, so a change to src.client.hitbox can break src.client, while a change to src.client can't break src.client.hitbox.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→7 src.client uses src.client.persist✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.persist.
- The types involved
src.client.useDrag→src.client.persist.Anchor
- Direction
- src.client uses src.client.persist, so a change to src.client.persist can break src.client, while a change to src.client can't break src.client.persist.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→8 src.client uses src.client.plugin-banner✕
- Connections
- 3 pairs of types, where a type in src.client uses a type in src.client.plugin-banner.
- The types involved
src.client.plugin-banner→src.client.plugin-banner.AdCopysrc.client.plugin-banner→src.client.plugin-banner.Draftsrc.client.plugin-banner→src.client.plugin-banner.Palette
- Direction
- src.client uses src.client.plugin-banner, so a change to src.client.plugin-banner can break src.client, while a change to src.client can't break src.client.plugin-banner.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→9 src.client uses src.client.schedule✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.schedule.
- The types involved
src.client.schedule→src.client.schedule.SpawnConfig
- Direction
- src.client uses src.client.schedule, so a change to src.client.schedule can break src.client, while a change to src.client can't break src.client.schedule.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→12 src.client uses src.client.star-check✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.star-check.
- The types involved
src.client.star-check→src.client.star-check.StarVerdict
- Direction
- src.client uses src.client.star-check, so a change to src.client.star-check can break src.client, while a change to src.client can't break src.client.star-check.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→13 src.client uses src.client.types✕
- Connections
- 8 pairs of types, where a type in src.client uses a type in src.client.types.
- The types involved
src.client.AdLayer→src.client.types.AdLocalesrc.client.feed→src.client.types.AdCreativesrc.client.feed→src.client.types.AdLocalesrc.client.locale→src.client.types.AdLocalesrc.client.plugin-banner→src.client.types.AdCreativesrc.client.plugin-banner→src.client.types.AdLocalesrc.client.registry→src.client.types.AdCreativesrc.client.registry→src.client.types.AdLocale
- Direction
- src.client uses src.client.types, so a change to src.client.types can break src.client, while a change to src.client can't break src.client.types.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→14 src.client uses src.client.useDrag✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.useDrag.
- The types involved
src.client.useDrag→src.client.useDrag.DragHandle
- Direction
- src.client uses src.client.useDrag, so a change to src.client.useDrag can break src.client, while a change to src.client can't break src.client.useDrag.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→15 src.client uses src.protocol✕
- Connections
- 2 pairs of types, where a type in src.client uses a type in src.protocol.
- The types involved
src.client.plugin-banner→src.protocol.SponsoredPluginsrc.client.registry→src.protocol.SponsoredPlugin
- Direction
- src.client uses src.protocol, so a change to src.protocol can break src.client, while a change to src.client can't break src.protocol.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→17 src.client uses src.client.AdLayer✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.AdLayer.
- The types involved
src.client.AdLayer→src.client.AdLayer.AdLayerProps
- Direction
- src.client uses src.client.AdLayer, so a change to src.client.AdLayer can break src.client, while a change to src.client can't break src.client.AdLayer.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→18 src.client uses src.client.InferenceRewardGate✕
- Connections
- 5 pairs of types, where a type in src.client uses a type in src.client.InferenceRewardGate.
- The types involved
src.client.InferenceRewardGate→src.client.InferenceRewardGate.GateTargetsrc.client.InferenceRewardGate→src.client.InferenceRewardGate.InferenceRewardGatePropssrc.client.InferenceRewardGate→src.client.InferenceRewardGate.RewardCardPropssrc.client.InferenceRewardGate→src.client.InferenceRewardGate.RewardSchedulesrc.client.InferenceRewardGate→src.client.InferenceRewardGate.WheelPrize
- Direction
- src.client uses src.client.InferenceRewardGate, so a change to src.client.InferenceRewardGate can break src.client, while a change to src.client can't break src.client.InferenceRewardGate.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→20 src.client uses src.client.Lightbox✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.Lightbox.
- The types involved
src.client.Lightbox→src.client.Lightbox.LightboxProps
- Direction
- src.client uses src.client.Lightbox, so a change to src.client.Lightbox can break src.client, while a change to src.client can't break src.client.Lightbox.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→21 src.client uses src.client.ShieldToast✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.ShieldToast.
- The types involved
src.client.ShieldToast→src.client.ShieldToast.ShieldToastProps
- Direction
- src.client uses src.client.ShieldToast, so a change to src.client.ShieldToast can break src.client, while a change to src.client can't break src.client.ShieldToast.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→22 src.client uses src.client.SpeedToast✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.SpeedToast.
- The types involved
src.client.SpeedToast→src.client.SpeedToast.SpeedToastProps
- Direction
- src.client uses src.client.SpeedToast, so a change to src.client.SpeedToast can break src.client, while a change to src.client can't break src.client.SpeedToast.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→23 src.client uses src.client.ToastPopup✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.ToastPopup.
- The types involved
src.client.ToastPopup→src.client.ToastPopup.ToastPopupProps
- Direction
- src.client uses src.client.ToastPopup, so a change to src.client.ToastPopup can break src.client, while a change to src.client can't break src.client.ToastPopup.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→24 src.client uses src.client.VirusToast✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.VirusToast.
- The types involved
src.client.VirusToast→src.client.VirusToast.VirusToastProps
- Direction
- src.client uses src.client.VirusToast, so a change to src.client.VirusToast can break src.client, while a change to src.client can't break src.client.VirusToast.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→26 src.client uses src.client.placement✕
- Connections
- 5 pairs of types, where a type in src.client uses a type in src.client.placement.
- The types involved
src.client.AdLayer→src.client.placement.SafeAreasrc.client.AdLayer→src.client.placement.Viewportsrc.client.placement→src.client.placement.AdSidesrc.client.placement→src.client.placement.SafeAreasrc.client.placement→src.client.placement.Viewport
- Direction
- src.client uses src.client.placement, so a change to src.client.placement can break src.client, while a change to src.client can't break src.client.placement.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→27 src.client uses src.client.settings✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.settings.
- The types involved
src.client.settings→src.client.settings.AdSettings
- Direction
- src.client uses src.client.settings, so a change to src.client.settings can break src.client, while a change to src.client can't break src.client.settings.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→28 src.client uses src.client.AdBanner✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.AdBanner.
- The types involved
src.client.AdBanner→src.client.AdBanner.AdBannerProps
- Direction
- src.client uses src.client.AdBanner, so a change to src.client.AdBanner can break src.client, while a change to src.client can't break src.client.AdBanner.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
31→30 src.client uses src.client.GamePoster✕
- Connections
- 1 pair of types, where a type in src.client uses a type in src.client.GamePoster.
- The types involved
src.client.GamePoster→src.client.GamePoster.GamePosterProps
- Direction
- src.client uses src.client.GamePoster, so a change to src.client.GamePoster can break src.client, while a change to src.client can't break src.client.GamePoster.
- Position
- Below the diagonal: src.client uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 8 | High / Critical |
| A05:2025 — Injection | 3 | High / Critical |
Roadmap
Top priorities: Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Add eslint as package.json scripts and run them in CI.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.1 pts | Medium | Release Hygiene |
| 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. | +1.9 pts | Medium | Architecture documentation |
| Add eslint as package.json scripts and run them in CI. | +1.6 pts | Medium | Tooling |
| Swallowed exception (caught, then discarded) | +1.1 pts | Medium | Exception handling |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +1.1 pts | Medium | Keyboard semantics |
| 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. | +1.0 pts | Medium | Documentation (README) |
| Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with AdLayer.tsx, GamePoster.tsx. | +0.5 pts | Medium | Churn × Complexity Hotspots |
| Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals. | +1.0 pts | Medium | Import Boundaries |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.5 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
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 55 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 55 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, 123 of 134 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
- D1 Cyclomatic Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.js) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.js) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D12 Dependency Hygiene — 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. This repository's 1 package.json manifest(s) and its 1 committed lockfile(s) WERE read; what went unanswered is the currency half, because it grades the production `dependencies` a lockfile resolves and these manifests declare none — only 21 devDependencies, which D12 does not grade. So registry.npmjs.org was never asked, and there was nothing here for it to grade. This is a true statement about the repository and NOT a gap on our side: the lockfile was resolved, and no reader we could write would find a production dependency in it.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's committed lockfile was read and it resolves no production dependency: everything it installs is declared under `devDependencies`, or is a workspace-internal package with no registry release behind it. Licences are resolved from registry.npmjs.org, because an npm checkout does not contain its dependencies' licences. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 79 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 1 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- 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. `src/client/InferenceRewardGate.tsx`, `tsdown.config.ts` 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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 13 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- 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.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: run `pnpm test` (declared in `package.json`) as an explicit pipeline step so the gate is unambiguous to a reader and to this pass.
- 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 none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
- 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. 36 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP 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
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 141 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root (141 tests)): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: src/client/AdLayer.tsx (3×78=234); src/client/GamePoster.tsx (2×25=50)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with AdLayer.tsx, GamePoster.tsx. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 6140 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D24 · Comment Value
0 of 158 judged comments only repeat the code they sit on (0.0 %).
D27 · Navigability
5 % of calls cross a namespace and 3 % go through an interface, but 91 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. 3 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 2 file(s) — `src/client/InferenceRewardGate.tsx` (line 81), `tsdown.config.ts` (line 58) — 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.
What to do
- No action in Static Analysis (SAST) — all 3 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 (3 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 3 high, 2 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 32 of the 37 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×3) — src/client/AdBanner.tsx:81, src/client/GamePoster.tsx:263, src/client/ToastPopup.tsx:78
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- <div> moves — its inline style sets `transition: opacity 320ms ease, transform 320ms cubic-bezier(0.2, 1.4, 0.4, 1)` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — src/client/AdBanner.tsx:81
- <span> moves — its inline style sets `transition: left 160ms ease` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — src/client/AdsSection.tsx:144
- <div> moves — its inline style sets `transition: transform 220ms ease-out` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — src/client/InferenceRewardGate.tsx:400
- <span> moves — its inline style sets `animation: dsh-unlock-shine 900ms linear infinite` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — src/client/InferenceRewardGate.tsx:409
- <button> moves — its inline style sets `transition: transform 100ms ease, opacity 100ms ease` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — src/client/InferenceRewardGate.tsx:459
- <div> moves — its inline style sets `transition: transform 420ms cubic-bezier(0.16, 1, 0.3, 1)` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×3) — src/client/ShieldToast.tsx:86, src/client/SpeedToast.tsx:137, src/client/ToastPopup.tsx:78
- <div> moves — its inline style sets `animation: dsh-ads-shake 0.42s infinite, dsh-ads-alarm 0.6s infinite` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — src/client/VirusToast.tsx:334
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. (×2) — lib/client.js:5175, src/client/plugin-banner.ts:380
What to do
- Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`pnpm test`, declared in `package.json`) and gate merges on it.
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 1 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.
- `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:65
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, 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
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release. — REDACTED:54
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- 15 duplicated blocks under the repository root have copies in at least two of the sibling directories lib, src — 13 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 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 15 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. — lib/client.js:5622
- src/client/SpeedToast.tsx:152 · src/client/VirusToast.tsx:357 — the two spans are one implementation copied and then locally edited — 395 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. — src/client/SpeedToast.tsx:152
- lib/client.js:5622 · src/client/registry.ts:49 — the two spans are one implementation copied and then locally edited — 290 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/client.js:5622
- lib/client.js:3883 · src/client/InferenceRewardGate.tsx:123 — the two spans are one implementation copied and then locally edited — 296 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/client.js:3883
- lib/index.js:1667 · src/catalog.ts:63 — the two spans are one implementation copied and then locally edited — 327 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/index.js:1667
- lib/client.js:3026 · lib/client.js:3052 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — lib/client.js:3026
- lib/client.js:2026 · src/client/useDrag.ts:56 — the two spans are one implementation copied and then locally edited — 289 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/client.js:2026
- src/client/GamePoster.tsx:225 · src/client/ToastPopup.tsx:97 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/client/GamePoster.tsx:225
- src/client/AdBanner.tsx:97 · src/client/InlineAd.tsx:151 — the two spans are one implementation copied and then locally edited — 93 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/client/AdBanner.tsx:97
- src/client/AdBanner.tsx:97 · src/client/Lightbox.tsx:147 — 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. — src/client/AdBanner.tsx:97
- lib/client.js:582 · src/client/star-check.ts:50 — the two spans are one implementation copied and then locally edited — 164 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/client.js:582
- lib/client.js:5403 · src/client/feed.ts:69 — the two spans are one implementation copied and then locally edited — 159 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/client.js:5403
- lib/client.js:5316 · src/client/rotation.ts:44 — the two spans are one implementation copied and then locally edited — 188 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/client.js:5316
- src/client/AdLayer.tsx:511 · src/client/AdLayer.tsx:531 — 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. — src/client/AdLayer.tsx:511
- lib/client.js:2960 · lib/client.js:3039 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/client.js:2960
- lib/index.js:1970 · lib/index.js:1989 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/index.js:1970
- lib/client.js:444 · lib/client.js:1478 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/client.js:444
- lib/client.js:383 · src/client/sound.ts:58 — the two spans are one implementation copied and then locally edited — 85 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/client.js:383
- src/index.ts:111 · src/index.ts:133 — 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. — src/index.ts:111
- lib/client.js:206 · lib/client.js:4001 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/client.js:206
- lib/client.js:1722 · src/client/persist.ts:82 — the two spans are one implementation copied and then locally edited — 74 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/client.js:1722
- lib/client.js:1830 · src/client/settings.ts:87 — the two spans are one implementation copied and then locally edited — 106 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/client.js:1830
- src/client/InferenceRewardGate.tsx:273 · src/client/Lightbox.tsx:91 — 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. — src/client/InferenceRewardGate.tsx:273
- src/client/SpeedToast.tsx:112 · src/client/ToastPopup.tsx:67 — 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. — src/client/SpeedToast.tsx:112
- lib/client.js:850 · lib/client.js:1492 · lib/client.js:2171 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — lib/client.js:850
- lib/client.js:1192 · src/client/ShieldToast.tsx:78 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/client.js:1192
- lib/client.js:11 · src/client/hitbox.ts:36 — the two spans are one implementation copied and then locally edited — 53 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/client.js:11
- lib/client.js:5210 · lib/client.js:5242 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/client.js:5210
- lib/client.js:5211 · src/client/plugin-banner.ts:424 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/client.js:5211
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
- src/client/AdsSection.tsx:23 imports lucide-react/dist/esm/icons/bell-ring.mjs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/client/AdsSection.tsx:23
- src/client/AdsSection.tsx:24 imports lucide-react/dist/esm/icons/gamepad-2.mjs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/client/AdsSection.tsx:24
- src/client/AdsSection.tsx:25 imports lucide-react/dist/esm/icons/gauge.mjs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/client/AdsSection.tsx:25
- src/client/AdsSection.tsx:26 imports lucide-react/dist/esm/icons/newspaper.mjs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/client/AdsSection.tsx:26
- src/client/AdsSection.tsx:27 imports lucide-react/dist/esm/icons/panels-left-right.mjs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/client/AdsSection.tsx:27
- src/client/AdsSection.tsx:28 imports lucide-react/dist/esm/icons/badge-cent.mjs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/client/AdsSection.tsx:28
- src/client/AdsSection.tsx:29 imports lucide-react/dist/esm/icons/shield-alert.mjs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/client/AdsSection.tsx:29
- src/client/AdsSection.tsx:30 imports lucide-react/dist/esm/icons/volume-2.mjs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/client/AdsSection.tsx:30
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
- RewardCard has cyclomatic complexity 52 and cognitive complexity 48; 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. (×2) — lib/client.js:3998, src/client/InferenceRewardGate.tsx:270
- VirusToast has cyclomatic complexity 35 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. (×2) — lib/client.js:820, src/client/VirusToast.tsx:250
- GamePoster has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. (×2) — lib/client.js:2158, src/client/GamePoster.tsx:121
- AdLayer has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/client.js:2865
- AdLayer has cyclomatic complexity 23 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/client/AdLayer.tsx:325
- SpeedToast has cyclomatic complexity 20 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — lib/client.js:1487, src/client/SpeedToast.tsx:107
- toSponsor has cyclomatic complexity 16 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — lib/index.js:1664, src/catalog.ts:60
- AdsSection has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — lib/client.js:3673, src/client/AdsSection.tsx:166
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/client.js:3302
- Lightbox has cyclomatic complexity 12 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. (×2) — lib/client.js:193, src/client/Lightbox.tsx:71
- ShieldToast has cyclomatic complexity 12 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. (×2) — lib/client.js:1192, src/client/ShieldToast.tsx:78
- AdSettingsMenu has cyclomatic complexity 11 and cognitive complexity 10; 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. (×2) — lib/client.js:1922, src/client/AdControls.tsx:87
R3 · Large Files
- lib/index.js has 2005 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/index.js:1
- src/client/AdLayer.tsx has 706 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/client/AdLayer.tsx:1
- src/client/InferenceRewardGate.tsx has 584 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/client/InferenceRewardGate.tsx:1
- src/client/VirusToast.tsx has 485 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/client/VirusToast.tsx:1
- src/client/plugin-banner.ts has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/client/plugin-banner.ts: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. (×2) — lib/client.js:1, lib/index.js: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 eslint as package.json scripts and run them in CI.
R7 · Dead Code
- This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — tests/client.spec.tsx:172
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. — package.json:68
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
X2 · Cancellation propagation
- Only 2/10 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `viaToken` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — src/star-host.ts:71, lib/index.js:1905
- `fetchPlugins` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — src/client/registry.ts:49, lib/client.js:5622
- `checkHostStar` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — src/client/star-check.ts:74, lib/client.js:603
- `checkStarred` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — src/client/star-check.ts:100, lib/client.js:626
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X3 · Exception handling
- `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. (×4) — src/catalog.ts:218, lib/client.js:584, lib/client.js:5325, …
- 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. (×7) — src/client/persist.ts:84, src/client/persist.ts:113, src/client/rotation.ts:78, …
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×4) — src/client/Lightbox.tsx:87, src/client/Lightbox.tsx:188, lib/client.js:205, …
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 58.2 | Adequate — gated by X3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 69.4 | Adequate — gated by R11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 58.5 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 54.6 | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 83.3 | Strong | Solid. |
| Accessibility | 64.7 | Adequate — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D12 Dependency Hygiene — 1 observation(s) recorded · Dependency currency not established — this repository declares no production dependency to grade
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 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 — 70 check(s) not relevant to this codebase
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, 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.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .js exposed no member bodies
- D14 License Compliance — npm licences not graded — this repository's lockfile resolves no production dependency
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D2 Cognitive Complexity — cognitive complexity not measured — .js exposed no member bodies
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed JavaScript surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (14597 LoC, 73 module-visible types across 4 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D3 God Classes — Most of this repository's production source (.js) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- 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) — 2 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.
- D4 Code Duplication — This repository's production source (.js, .mjs, .ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D6 Cohesion (LCOM4) — No production classes were analyzable, so cohesion (LCOM4) was not measured (the solution likely failed to load or has no production code).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JavaScript/TypeScript source (1 module(s), 35 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- 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 pnpm 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: 36 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
- 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.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- 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
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 9 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Click handler on a non-interactive <div> src/client/AdBanner.tsx:81
- Click handler on a non-interactive <div> src/client/ToastPopup.tsx:78
- Click handler on a non-interactive <img> src/client/GamePoster.tsx:263
Serious — 107 finding(s)
- Swallowed exception (empty catch) src/client/persist.ts:84
- Swallowed exception (empty catch) src/client/persist.ts:113
- Swallowed exception (empty catch) src/client/rotation.ts:78
- Swallowed exception (empty catch) src/client/sound.ts:82
- Swallowed exception (empty catch) src/client/Lightbox.tsx:87
- Swallowed exception (empty catch) src/client/Lightbox.tsx:188
- Swallowed exception (empty catch) lib/client.js:205
- Swallowed exception (empty catch) lib/client.js:297
- Swallowed exception (empty catch) lib/client.js:402
- Swallowed exception (empty catch) lib/client.js:1724
- Swallowed exception (empty catch) lib/client.js:5344
- Animation without a prefers-reduced-motion guard src/client/AdBanner.tsx:81
- Animation without a prefers-reduced-motion guard src/client/AdsSection.tsx:144
- Animation without a prefers-reduced-motion guard src/client/InferenceRewardGate.tsx:400
- Animation without a prefers-reduced-motion guard src/client/InferenceRewardGate.tsx:409
- Animation without a prefers-reduced-motion guard src/client/InferenceRewardGate.tsx:459
- Animation without a prefers-reduced-motion guard src/client/ShieldToast.tsx:86
- Animation without a prefers-reduced-motion guard src/client/SpeedToast.tsx:137
- Animation without a prefers-reduced-motion guard src/client/ToastPopup.tsx:78
- Animation without a prefers-reduced-motion guard src/client/VirusToast.tsx:334
- Boundary violation [package:third-party-deep-import] src/client/AdsSection.tsx:23
- Boundary violation [package:third-party-deep-import] src/client/AdsSection.tsx:24
- Boundary violation [package:third-party-deep-import] src/client/AdsSection.tsx:25
- Boundary violation [package:third-party-deep-import] src/client/AdsSection.tsx:26
- Boundary violation [package:third-party-deep-import] src/client/AdsSection.tsx:27
- Boundary violation [package:third-party-deep-import] src/client/AdsSection.tsx:28
- Boundary violation [package:third-party-deep-import] src/client/AdsSection.tsx:29
- Boundary violation [package:third-party-deep-import] src/client/AdsSection.tsx:30
- Async function without AbortSignal: viaToken src/star-host.ts:71
- Async function without AbortSignal: fetchPlugins src/client/registry.ts:49
- Async function without AbortSignal: checkHostStar src/client/star-check.ts:74
- Async function without AbortSignal: checkStarred src/client/star-check.ts:100
- Async function without AbortSignal: checkHostStar lib/client.js:603
- Async function without AbortSignal: checkStarred lib/client.js:626
- Async function without AbortSignal: fetchPlugins lib/client.js:5622
- Async function without AbortSignal: viaToken lib/index.js:1905
- Swallowed exception (caught, then discarded) src/catalog.ts:218
- Swallowed exception (caught, then discarded) lib/client.js:584
- Swallowed exception (caught, then discarded) lib/client.js:5325
- Swallowed exception (caught, then discarded) lib/index.js:1829
- Hotspot: src/client/AdLayer.tsx src/client/AdLayer.tsx:325
- Hotspot: src/client/GamePoster.tsx src/client/GamePoster.tsx:121
- REDACTED
- REDACTED
- Both branches are identical — the condition decides nothing lib/client.js:5175
- Both branches are identical — the condition decides nothing src/client/plugin-banner.ts:380
- Duplicated block with local edits (18 matched lines × 2 locations) src/client/AdBanner.tsx:97
- Duplicated block with local edits (18 matched lines × 2 locations) src/client/AdBanner.tsx:97
- Duplicated block with local edits (16 matched lines × 2 locations) lib/client.js:5403
- Duplicated block with local edits (16 matched lines × 2 locations) lib/client.js:5316
- Duplicated block (14 lines × 2 locations) lib/client.js:2960
- Duplicated block (14 lines × 2 locations) lib/index.js:1970
- Duplicated block (9 lines × 2 locations) lib/client.js:206
- Duplicated block (9 lines × 2 locations) src/client/InferenceRewardGate.tsx:273
- Duplicated block with local edits (9 matched lines × 2 locations) lib/client.js:1722
- Duplicated block with local edits (9 matched lines × 2 locations) lib/client.js:1830
- Duplicated block with local edits (6 matched lines × 2 locations) lib/client.js:1192
- Duplicated block with local edits (6 matched lines × 2 locations) lib/client.js:11
- Duplicated block (5 lines × 2 locations) lib/client.js:5210
- Duplicated block (5 lines × 2 locations) lib/client.js:5211
- Complex function RewardCard (cyclomatic 52, cognitive 48) lib/client.js:3998
- Complex function RewardCard (cyclomatic 52, cognitive 48) src/client/InferenceRewardGate.tsx:270
- Complex function VirusToast (cyclomatic 35, cognitive 34) lib/client.js:820
- Complex function VirusToast (cyclomatic 35, cognitive 34) src/client/VirusToast.tsx:250
- Complex function GamePoster (cyclomatic 23, cognitive 22) lib/client.js:2158
- Complex function GamePoster (cyclomatic 23, cognitive 22) src/client/GamePoster.tsx:121
- Complex function SpeedToast (cyclomatic 20, cognitive 19) lib/client.js:1487
- Complex function SpeedToast (cyclomatic 20, cognitive 19) src/client/SpeedToast.tsx:107
- Complex function toSponsor (cyclomatic 16, cognitive 13) lib/index.js:1664
- Complex function toSponsor (cyclomatic 16, cognitive 13) src/catalog.ts:60
- Complex function AdsSection (cyclomatic 15, cognitive 14) lib/client.js:3673
- Complex function AdsSection (cyclomatic 15, cognitive 14) src/client/AdsSection.tsx:166
- Complex function Lightbox (cyclomatic 12, cognitive 11) lib/client.js:193
- Complex function Lightbox (cyclomatic 12, cognitive 11) src/client/Lightbox.tsx:71
- Complex function ShieldToast (cyclomatic 12, cognitive 11) lib/client.js:1192
- Complex function ShieldToast (cyclomatic 12, cognitive 11) src/client/ShieldToast.tsx:78
- Complex function AdSettingsMenu (cyclomatic 11, cognitive 10) lib/client.js:1922
- Complex function AdSettingsMenu (cyclomatic 11, cognitive 10) src/client/AdControls.tsx:87
- No test reaches this file lib/client.js:1
- No test reaches this file lib/index.js:1
- REDACTED
- Coverage not measured — JavaScript/TypeScript suite
- Duplication concentrated across 2 sibling directories (15 clone groups) lib/client.js:5622
- Duplicated block with local edits (51 matched lines × 2 locations) src/client/SpeedToast.tsx:152
- Duplicated block with local edits (36 matched lines × 2 locations) lib/client.js:5622
- Duplicated block with local edits (32 matched lines × 2 locations) lib/client.js:3883
- Duplicated block with local edits (30 matched lines × 2 locations) lib/index.js:1667
- Duplicated block (22 lines × 2 locations) lib/client.js:3026
- Duplicated block with local edits (21 matched lines × 2 locations) lib/client.js:2026
- Duplicated block (19 lines × 2 locations) src/client/GamePoster.tsx:225
- Duplicated block with local edits (17 matched lines × 2 locations) lib/client.js:582
- Duplicated block (16 lines × 2 locations) src/client/AdLayer.tsx:511
- Duplicated block (12 lines × 2 locations) lib/client.js:444
- Duplicated block with local edits (11 matched lines × 2 locations) lib/client.js:383
- Duplicated block (10 lines × 2 locations) src/index.ts:111
- Duplicated block (7 lines × 2 locations) src/client/SpeedToast.tsx:112
- Duplicated block (6 lines × 3 locations) lib/client.js:850
- Complex function AdLayer (cyclomatic 23, cognitive 22) lib/client.js:2865
- Complex function AdLayer (cyclomatic 23, cognitive 18) src/client/AdLayer.tsx:325
- Complex function (anonymous) (cyclomatic 15, cognitive 10) lib/client.js:3302
- lib/index.js: 2005 lines of code lib/index.js:1
- src/client/AdLayer.tsx: 706 lines of code src/client/AdLayer.tsx:1
- src/client/InferenceRewardGate.tsx: 584 lines of code src/client/InferenceRewardGate.tsx:1
- src/client/VirusToast.tsx: 485 lines of code src/client/VirusToast.tsx:1
- src/client/plugin-banner.ts: 459 lines of code src/client/plugin-banner.ts:1
- No lint script
- Unused dependency '@deepseek-ai/dsh-client-store' package.json:68
Minor — 16 finding(s)
- Silent fallback default in catch lib/index.js:1911
- Silent fallback default in catch src/client/star-check.ts:80
- Silent fallback default in catch src/client/registry.ts:55
- Duplicated predicate lib/index.js:1790
- Duplicated predicate lib/index.js:1667
- Deprecated: whatwg-encoding REDACTED:1054
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation package.json:65
- No release approval gate REDACTED:54
- No changelog
- Unused module-local declaration 'closeSpeed' tests/client.spec.tsx:172
- Not all async functions that make a request accept an AbortSignal
Minor — 2 finding(s)
- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (the committed lockfile resolved no direct production dependency)
- doc comments repeat the names lib/client.js:1827
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-a2a8f959b4a442b398f569781d26a0d3/history.json --exit-code 0 --source . | 10 | 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-a2a8f959b4a442b398f569781d26a0d3/tree.json --exit-code 0 --source . | 5 | 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 . | 3 | 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/** . | 5 | 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 2 file(s) — `src/client/InferenceRewardGate.tsx`, `tsdown.config.ts` — 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 |