Public report — popcorn, published 6 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
149findings with an exact file:lineof 159 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
37/106dimensions across the health lenses45024 LoC — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
software-mansion/popcorn carries serious gaps (44%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
It is strongest in Architecture (93%) — the structure is clean and changes stay contained. Code Health (83%) is solid too.
Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.
The area that most needs attention is Readiness (30%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Accessibility (45%) is the next concern — it raises ongoing delivery and operational cost.
Leadership focus, highest impact first: 14 Leaked secret finding(s) (Secret Scanning); SAST step to CI running what this repository's stack ships (Security & performance tooling); tests that import the unreached modules (directly or through… (Test Coverage).
For scale: Medium (~45,024 production lines); rebuilding it from scratch would take roughly ~0.3 person-years (~1 engineer). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (93%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
AC6 · Low contrast colour pair in CSS (1.6:1) examples/iex-wasm/assets/style.css
AC6 · Low contrast colour pair in CSS (1.6:1) examples/eval-in-wasm/assets/style.css
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
0.7× (at 44% quality) — the last 20% of quality is most of the work
Size & shape
Medium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
Dead frontend code
~496 LoC unreachable (4 file(s)) — that slice of this estimate buys code with zero runtime value; deleting it is the cheapest win in this report (the R7 card lists every file)
This codebase represents roughly ~0.3 person-years of build effort (about ~€49,000 to rebuild). Its weakest lens is Readiness at 30% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 14 Leaked secret finding(s) in Secret Scanning — start with test.exs (7), dev.exs (7).
Add a SAST step to CI running what this repository's stack ships: sobelow (Elixir/Phoenix) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Value concentrated against a weak lens · High · Value at risk
This is a Medium asset (~0.3 person-years to rebuild), and its weakest lens is Readiness at 30%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Resolve the 14 Leaked secret finding(s) in Secret Scanning — start with test.exs (7), dev.exs (7). The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Resolve the 14 Leaked secret finding(s) in Secret Scanning — start with test.exs (7), dev.exs (7).
Architecture — module dependency matrix
64 modules, 12 dependencies — every dependency points down the layering, so there are no cycles. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A06:2021 — Vulnerable & Outdated Components
50
High / Critical
A03:2021 — Injection
48
High / Critical
A05:2021 — Security Misconfiguration
20
High / Critical
A02:2021 — Cryptographic Failures
16
High / Critical
Roadmap
First, eliminate the 14 leaked secrets in the codebase, focusing on test.exs and dev.exs. Next, integrate a SAST step into the CI pipeline to fail the build on security regressions. Then, expand test coverage to include all unreached production modules. Finally, clean up the dependency list by removing unused packages and updating outdated ones to reduce security and upgrade debt.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 14 Leaked secret finding(s) in Secret Scanning — start with test.exs (7), dev.exs (7).
Add a SAST step to CI running what this repository's stack ships: sobelow (Elixir/Phoenix) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI.
Watchdog 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. 35 of 37 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.5 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 37 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 149 of 159 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
Repo exclusion declarations: 6 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
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.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
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").
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
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.
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 clean result is "no unlabelled native 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.
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.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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".
The LLM boundary
LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 14 Leaked secret finding(s) in Secret Scanning — start with test.exs (7), dev.exs (7). — One of this dimension's main actionable groups (14 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.6 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is popcorn/js/src/errors.ts.
Off-boarding risk: anonymized user #1
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The Popcorn ecosystem is well documented across READMEs and popdoc files: a clear README with Popcorn's license badge, an interactive Popdoc guide for Elixir code evaluation via Popcorn, detailed repository structure, first-steps instructions for LocalLiveView demos (HTML script, module definition, data-pop-view), a browser-based Elixir Language Tour Guide covering architecture, folder structure, and error-tracking, and standalone examples such as the Hello Popcorn demo. The documentation is complete, well-organized, and covers both client-side runtime integration and local-first LiveView behavior. The e2e test README and architecture doc both show strong, focused documentation for their respective topics. The Playwright e2e suite explains how it runs (serverless ExUnit + Phoenix endpoint in the same BEAM), the commands (`mix test`, `pnpm install && pnpm run test:headed`), and notes about drag/drop using native HTML5 events while noting that Playwright's mouse-based drag is not used. The Popcorn architecture doc covers main browser window/lib, an isolated iframe with AtomVM runtime, a custom patching mechanism (`.beam` decompilation + `:emscripten` modules), and a runtime initialization diagram, all of which are present in the clipped outline.
The single-expression Popdoc example is a minimal fixture that does not show the full Popcorn runtime behavior (e.g. error handling, stack traces) and lacks any accompanying documentation for the popdoc server.popdoc/e2e/fixture/README.md
What to do
Resolve the 1 The single-expression Popdoc example is a minimal fixture that does not… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
Secret: generic-api-keyexamples/local-lv-compare/config/dev.exs:16detected by gitleaks finding
Rotate the exposed credentials — git history can't be un-committed
✓ On the Gold path — maintain.
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
High: run-shell-injection · ×48.github/actions/build-atomvm/action.yml:34detected by semgrep finding
What to do
Resolve the 48 High finding(s) in Static Analysis (SAST) — start with action.yml (12), demo_prod_build_and_deploy.yml (9), demo_staging_build_and_deploy.yml (9). — One of this dimension's main actionable groups (48 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
High IaC: DS-0002 · ×6docker/base.Dockerfiledetected by trivy finding
Medium IaC: DS-0013 · ×12docker/base.Dockerfiledetected by trivy finding
Low IaC: DS-0026 · ×2docker/landing.Dockerfiledetected by trivy finding
What to do
Resolve the 12 Medium IaC finding(s) in IaC & Container Security — start with base.Dockerfile (3), Dockerfile (3), landing.Dockerfile (2). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 6 High IaC finding(s) in IaC & Container Security — start with base.Dockerfile (2), release.Dockerfile (2), landing.Dockerfile. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with landing.Dockerfile, langtour.Dockerfile. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No artifact signing finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No SBOM finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — read natively from whatever lockfile the repository ships (Cargo, npm, Go, Python, Maven, RubyGems, …). D33 and D30 add ecosystem-specific scanners on top for npm and .NET.
Method: Multi-ecosystem dependency-CVE scan via osv-scanner --recursive (queries the osv.dev database + parses lockfiles natively across ecosystems: npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven/Gradle pom.xml/gradle.lockfile, PyPI requirements.txt/poetry.lock/Pipfile.lock, Composer composer.lock, RubyGems Gemfile.lock, Hex mix.lock, pub pubspec.lock, Swift Package.resolved); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable only when the repo declares no supported non-.NET dependency lockfile (a NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain); coverage needs a resolved lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.
High CVE: [GHSA redacted] · ×29landing-page/package-lock.jsondetected by osv-scanner finding
High vulnerability: [GHSA redacted] · ×5pnpm-lock.yamldetected by osv-scanner finding
Critical CVE: [GHSA redacted] · ×3landing-page/package-lock.jsondetected by osv-scanner finding
Medium CVE: EEF-[CVE redacted] · ×10local-live-view/mix.lockdetected by osv-scanner finding
Medium vulnerability: [GHSA redacted]landing-page/package-lock.jsondetected by osv-scanner finding
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 29 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (15), pnpm-lock.yaml (8), mix.lock (6). — One of this dimension's main actionable groups (29 issue-level).
Resolve the 5 High vulnerability finding(s) in OSV Dependency Vulnerabilities — start with pnpm-lock.yaml (3), package-lock.json (2). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 3 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (2), pnpm-lock.yaml. — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×2) — Navigation.tsx:65, NavigationList.tsx:54
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable. — NavigationButton.tsx:26
What to do
Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
`button:active` sets color: #c1c6e5 on background-color: #00a9f0 — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — style.css:127, style.css:127
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.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time.
What to do
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a README to the 17 of 36 project(s) that lack one — worth up to 0.9 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no `NNNN-title.md` documents and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add sobelow (Elixir/Phoenix) (or `semgrep --config=auto`, which runs on any language) as a CI step.
What to do
Add a SAST step to CI running what this repository's stack ships: sobelow (Elixir/Phoenix) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Do you agree with this assessment?
R1 · Type Safety8.8 / 10Strong✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm over JS/TS tokens, D-386).
Method: Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm run over JS/TS tokens). Deterministic.
local-live-view/assets/local_live_view/events.ts:70 · local-live-view/priv/static/local_live_view.js:777 — 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. — events.ts:70
language-tour/src/utils/content/navigation-builder.ts:8 · language-tour/src/utils/content/route-builder.tsx:7 — 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. — navigation-builder.ts:8
local-live-view/priv/static/AtomVM.mjs:5705 · local-live-view/priv/static/AtomVM.mjs:6033 — 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. — AtomVM.mjs:5705
local-live-view/priv/static/AtomVM.mjs:5813 · local-live-view/priv/static/AtomVM.mjs:5848 — 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. — AtomVM.mjs:5813
local-live-view/priv/static/AtomVM.mjs:5913 · local-live-view/priv/static/AtomVM.mjs:6168 · local-live-view/priv/static/AtomVM.mjs:6197 · local-live-view/priv/static/AtomVM.mjs:6262 — all 4 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. — AtomVM.mjs:5913
local-live-view/priv/static/AtomVM.mjs:6133 · local-live-view/priv/static/AtomVM.mjs:6387 — 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. — AtomVM.mjs:6133
local-live-view/priv/static/local_live_view.js:365 · popcorn-2/js/src/popcorn.ts:352 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — local_live_view.js:365
language-tour/src/components/navigation/NavigationList.tsx:79 · language-tour/src/components/navigation/NavigationList.tsx:100 — 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. — NavigationList.tsx:79
What to do
Extract the duplicated blocks into shared functions/components.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
Branch-heavy code is where defects cluster — extract decisions into smaller functions. (×8) — AtomVM.mjs:4580, AtomVM.mjs:4, parser.ts:51, …
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files7.9 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage2.0 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
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. (×8) — AtomVM.mjs, local_live_view.js, index.ts, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D33 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D33). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.4 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
15 file(s) (~1767 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: popcorn-2/js/src/iframe.ts imports './AtomVM.mjs', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — js
3 file(s) (~113 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — setup
23 file(s) (~4869 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: popcorn/js/src/worker.ts imports '../assets/beam.mjs', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — js
Unreachable from the 39 application, 19 tooling and 25 test entry point(s) detected in this repo. Gate removals on your build/type-check — an undetected custom entry would make these reachable.
no import path from any entry point (39 application, 19 tooling, 25 test roots considered) (×4) — 3dModel.ts, History.tsx, executionHistory.ts, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in landing-page/package.json but never imported anywhere in that package or its workspace members — dead weight and attack surface. Verify against build tooling before removing. (×3)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Break each cycle by extracting the shared piece into a module both sides can import.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 12 of 55 WCAG 2.2 Level A/AA success criteria (22%; ≈24% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 43 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not included — 69 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AX1 Captive dependencies — no DI registrations detected
AX10 Code composition — not assessed — code composition is computed by ROLE over a document set 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
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) 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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D1 Cyclomatic Complexity — Most of this repository's production source (.erl, .exs, .hrl, .ts, .tsx) had no cyclomatic complexity computed for it, so cyclomatic complexity was not measured — whatever else this pass did read is not this repository's complexity. Not scored: no method bodies were exposed for those file kinds by any language model this pass could load. This is a gap in the analysis run, not a finding about this repository.
D10 Test Quality — ~10678 lines of test source are present (.exs, .ts, .js, .mjs) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included
D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
D14 License Compliance — Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (package.json), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D2 Cognitive Complexity — Most of this repository's production source (.erl, .exs, .hrl, .ts, .tsx) had no cognitive complexity computed for it, so cognitive complexity was not measured — whatever else this pass did read is not this repository's complexity. Not scored: no method bodies were exposed for those file kinds by any language model this pass could load. This is a gap in the analysis run, not a finding about this repository.
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.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Production source is present (.erl, .ex, .exs, .hrl, .ts, .tsx) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D3 God Classes — Most of this repository's production source (.erl, .exs, .hrl, .ts, .tsx) 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.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (package.json — not scanned yet) — where an OSV-supported manifest exists, dependency vulnerabilities for this repository are reported under D38 instead.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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.
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is .erl, .ex, .exs, .hrl, .ts, .tsx, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
D9 Test Distribution — Test source is present (.exs, .ts, .js, .mjs) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 104 value object(s); 3 domain event(s)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check 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 check looks for
GD1 Unfinished & placeholder code — no source files
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — not assessed — schema-migration practice is read from 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
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `mix test --cover` with `excoveralls` (`mix coveralls.lcov`)) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — 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
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X3 Exception handling — 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
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not 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
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
High: run-shell-injection .github/actions/build-atomvm/action.yml:34— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/actions/build-atomvm/action.yml:38— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/cache@<40-character SHA>`. This step references `actions/cache@v4`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v4 --jq .sha`.
High: run-shell-injection .github/actions/build-atomvm/action.yml:47— Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/actions/build-atomvm/action.yml:58— Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/actions/build-otp-wasm/action.yml:24— Using variable interpolation `${{...}}` with a workflow input / an expression value in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input / an expression value is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/actions/build-otp-wasm/action.yml:60— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/cache@<40-character SHA>`. This step references `actions/cache@v4`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/actions/build-otp-wasm/action.yml:95— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/cache@<40-character SHA>`. This step references `actions/cache@v4`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/actions/build-otp-wasm/action.yml:102— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/cache@<40-character SHA>`. This step references `actions/cache@v4`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v4 --jq .sha`.
High: run-shell-injection .github/actions/build-otp-wasm/action.yml:120— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/actions/setup-playwright/action.yml:20— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/cache@<40-character SHA>`. This step references `actions/cache@v4`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v4 --jq .sha`.
High: run-shell-injection .github/actions/setup-playwright/action.yml:28— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/actions/setup-toolchain/action.yml:8— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: mymindstorm/setup-emsdk@<40-character SHA>`. This step references `mymindstorm/setup-emsdk@v14`; resolve the SHA it points at today with `gh api repos/mymindstorm/setup-emsdk/commits/v14 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/demo_prod_build_and_deploy.yml:19— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/demo_prod_build_and_deploy.yml:24— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: docker/setup-buildx-action@<40-character SHA>`. This step references `docker/setup-buildx-action@v3`; resolve the SHA it points at today with `gh api repos/docker/setup-buildx-action/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/demo_prod_build_and_deploy.yml:27— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: docker/login-action@<40-character SHA>`. This step references `docker/login-action@v3`; resolve the SHA it points at today with `gh api repos/docker/login-action/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/demo_prod_build_and_deploy.yml:35— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: docker/metadata-action@<40-character SHA>`. This step references `docker/metadata-action@v5`; resolve the SHA it points at today with `gh api repos/docker/metadata-action/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/demo_prod_build_and_deploy.yml:45— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: docker/build-push-action@<40-character SHA>`. This step references `docker/build-push-action@v6`; resolve the SHA it points at today with `gh api repos/docker/build-push-action/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/demo_prod_build_and_deploy.yml:60— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: docker/build-push-action@<40-character SHA>`. This step references `docker/build-push-action@v6`; resolve the SHA it points at today with `gh api repos/docker/build-push-action/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/demo_prod_build_and_deploy.yml:77— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: docker/build-push-action@<40-character SHA>`. This step references `docker/build-push-action@v6`; resolve the SHA it points at today with `gh api repos/docker/build-push-action/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/demo_prod_build_and_deploy.yml:93— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: docker/build-push-action@<40-character SHA>`. This step references `docker/build-push-action@v6`; resolve the SHA it points at today with `gh api repos/docker/build-push-action/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/demo_prod_build_and_deploy.yml:118— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: appleboy/ssh-action@<40-character SHA>`. This step references `appleboy/ssh-action@v1`; resolve the SHA it points at today with `gh api repos/appleboy/ssh-action/commits/v1 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/demo_staging_build_and_deploy.yml:38— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/demo_staging_build_and_deploy.yml:43— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: docker/setup-buildx-action@<40-character SHA>`. This step references `docker/setup-buildx-action@v3`; resolve the SHA it points at today with `gh api repos/docker/setup-buildx-action/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/demo_staging_build_and_deploy.yml:47— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: docker/login-action@<40-character SHA>`. This step references `docker/login-action@v3`; resolve the SHA it points at today with `gh api repos/docker/login-action/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/demo_staging_build_and_deploy.yml:55— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: docker/metadata-action@<40-character SHA>`. This step references `docker/metadata-action@v5`; resolve the SHA it points at today with `gh api repos/docker/metadata-action/commits/v5 --jq .sha`.
+ 23 more in this group — see findings.md.
D38 · OSV Dependency Vulnerabilities· High CVE · ×29
High CVE: [GHSA redacted] landing-page/package-lock.json— astro 5.10.1: [GHSA redacted] — this repo declares astro ^6.0.6, but the vulnerable 5.10.1 is a SEPARATE copy on another release line, so editing your own astro entry cannot move it: upgrade the dependency that pulls it in (— 6.4.6 is a MAJOR ahead of the resolved 5.10.1, so an `overrides` pin would force a breaking version under a dependent written against 5.10.1; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 19 advisories with a published fix this scan raises against astro 5.10.1, and their fixed versions do not agree — anything below 5.18.1 still leaves at least one of them open. Take this package to 5.18.1 or later: that is the floor for the package, not this row's target alone. This one row stands for the 19 advisories this scan raises against astro 5.10.1: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] pnpm-lock.yaml— astro 6.2.2: [GHSA redacted] — this repo declares astro ^6.0.6, a range that ALREADY admits the fixed 6.4.6, so there is no manifest edit to make here. Re-resolve the lock so astro moves onto 6.4.6 or later; if the flagged 6.2.2 comes back, a dependency is pinning it — upgrade that dependent, or pin astro with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm) so only one copy resolves. This is 1 of 6 advisories with a published fix this scan raises against astro 6.2.2, and their fixed versions do not agree — anything below 6.4.6 still leaves at least one of them open. Take this package to 6.4.6 or later: that is the floor for the package, not this row's target alone. This one row stands for the 6 advisories this scan raises against astro 6.2.2: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] landing-page/package-lock.json— axios 1.10.0: [GHSA redacted] — axios is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin axios to 1.16.0 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 29 advisories with a published fix this scan raises against axios 1.10.0, and their fixed versions do not agree — anything below 1.18.0 still leaves at least one of them open. Take this package to 1.18.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 29 advisories this scan raises against axios 1.10.0: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] pnpm-lock.yaml— brace-expansion 5.0.5: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 5.0.7 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 4 advisories with a published fix this scan raises against brace-expansion 5.0.5, and their fixed versions do not agree — anything below 5.0.9 still leaves at least one of them open. Take this package to 5.0.9 or later: that is the floor for the package, not this row's target alone. This one row stands for the 4 advisories this scan raises against brace-expansion 5.0.5: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] local-live-view/mix.lock— cowlib 2.7.3: [GHSA redacted] — upgrade to 2.16.1. This is 1 of 4 advisories with a published fix this scan raises against cowlib 2.7.3, and their fixed versions do not agree — anything below 2.19.0 still leaves at least one of them open. Take this package to 2.19.0 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: local-live-view/mix.lock, popcorn-2/elixir/mix.lock) This one row stands for the 4 advisories this scan raises against cowlib 2.7.3: EEF-[CVE redacted], EEF-[CVE redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] landing-page/package-lock.json— defu 6.1.4: [GHSA redacted] — defu is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin defu to 6.1.5 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)).
High CVE: [GHSA redacted] landing-page/package-lock.json— devalue 5.1.1: [GHSA redacted] — devalue is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin devalue to 5.6.2 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 6 advisories with a published fix this scan raises against devalue 5.1.1, and their fixed versions do not agree — anything below 5.6.4 still leaves at least one of them open. Take this package to 5.6.4 or later: that is the floor for the package, not this row's target alone. This one row stands for the 6 advisories this scan raises against devalue 5.1.1: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] pnpm-lock.yaml— devalue 5.8.0: [GHSA redacted] — devalue is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin devalue to 5.8.1 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)).
High CVE: [GHSA redacted] landing-page/package-lock.json— form-data 4.0.4: [GHSA redacted] — form-data is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin form-data to 4.0.6 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)).
High CVE: [GHSA redacted] local-live-view/mix.lock— gun 1.3.3: [GHSA redacted] — upgrade to 2.4.0. This is 1 of 2 advisories with a published fix this scan raises against gun 1.3.3, and their fixed versions do not agree — anything below 2.16.0 still leaves at least one of them open. Take this package to 2.16.0 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: local-live-view/mix.lock, popcorn-2/elixir/mix.lock) This one row stands for the 2 advisories this scan raises against gun 1.3.3: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] landing-page/package-lock.json— h3 1.15.3: [GHSA redacted] — h3 is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin h3 to 1.15.6 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 5 advisories with a published fix this scan raises against h3 1.15.3, and their fixed versions do not agree — anything below 1.15.9 still leaves at least one of them open. Take this package to 1.15.9 or later: that is the floor for the package, not this row's target alone. This one row stands for the 5 advisories this scan raises against h3 1.15.3: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] landing-page/package-lock.json— js-yaml 4.1.0: [GHSA redacted] — js-yaml is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin js-yaml to 4.3.0 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 3 advisories with a published fix this scan raises against js-yaml 4.1.0, and their fixed versions do not agree — anything below 4.3.0 still leaves at least one of them open. Take this package to 4.3.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 3 advisories this scan raises against js-yaml 4.1.0: [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] pnpm-lock.yaml— js-yaml 4.1.1: [GHSA redacted] — js-yaml is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin js-yaml to 4.3.0 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 2 advisories with a published fix this scan raises against js-yaml 4.1.1, and their fixed versions do not agree — anything below 4.3.0 still leaves at least one of them open. Take this package to 4.3.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against js-yaml 4.1.1: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] landing-page/package-lock.json— lodash-es 4.17.21: [GHSA redacted] — lodash-es is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin lodash-es to 4.18.0 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This one row stands for the 2 advisories this scan raises against lodash-es 4.17.21: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] local-live-view/mix.lock— mint 1.7.1: [GHSA redacted] — upgrade to 1.9.0. This is 1 of 8 advisories with a published fix this scan raises against mint 1.7.1, and their fixed versions do not agree — anything below 1.9.3 still leaves at least one of them open. Take this package to 1.9.3 or later: that is the floor for the package, not this row's target alone. This one row stands for the 8 advisories this scan raises against mint 1.7.1: EEF-[CVE redacted], EEF-[CVE redacted], EEF-[CVE redacted], EEF-[CVE redacted], EEF-[CVE redacted], EEF-[CVE redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] local-live-view/mix.lock— phoenix 1.8.4: [GHSA redacted] — upgrade to 1.8.6. This is 1 of 3 advisories with a published fix this scan raises against phoenix 1.8.4, and their fixed versions do not agree — anything below 1.8.9 still leaves at least one of them open. Take this package to 1.8.9 or later: that is the floor for the package, not this row's target alone. This one row stands for the 3 advisories this scan raises against phoenix 1.8.4: EEF-[CVE redacted], EEF-[CVE redacted], [GHSA redacted].
High CVE: [GHSA redacted] landing-page/package-lock.json— picomatch 2.3.1: [GHSA redacted] — picomatch is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin picomatch to 2.3.2 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This one row stands for the 2 advisories this scan raises against picomatch 2.3.1: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] landing-page/package-lock.json— picomatch 4.0.2: [GHSA redacted] — picomatch is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin picomatch to 4.0.4 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This one row stands for the 2 advisories this scan raises against picomatch 4.0.2: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] landing-page/package-lock.json— playwright 1.53.2: [GHSA redacted] — this repo already declares playwright ^1.60.0 directly, at or above the fixed 1.55.1; the vulnerable 1.53.2 is a second copy resolved for a dependency that requires an older range. Upgrade those dependents, or pin playwright with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm) so only one copy resolves.
High CVE: [GHSA redacted] local-live-view/mix.lock— plug 1.19.1: [GHSA redacted] — upgrade to 1.19.2. This is 1 of 4 advisories with a published fix this scan raises against plug 1.19.1, and their fixed versions do not agree — anything below 1.19.5 still leaves at least one of them open. Take this package to 1.19.5 or later: that is the floor for the package, not this row's target alone. This one row stands for the 4 advisories this scan raises against plug 1.19.1: EEF-[CVE redacted], EEF-[CVE redacted], EEF-[CVE redacted], [GHSA redacted].
High CVE: [GHSA redacted] landing-page/package-lock.json— postcss 8.5.6: [GHSA redacted] — postcss is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin postcss to 8.5.12 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 4 advisories with a published fix this scan raises against postcss 8.5.6, and their fixed versions do not agree — anything below 8.5.23 still leaves at least one of them open. Take this package to 8.5.23 or later: that is the floor for the package, not this row's target alone. This one row stands for the 4 advisories this scan raises against postcss 8.5.6: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] pnpm-lock.yaml— react-router 7.15.0: [GHSA redacted] — this repo declares react-router ^7.7.1, a range that ALREADY admits the fixed 7.18.0, so there is no manifest edit to make here. Re-resolve the lock so react-router moves onto 7.18.0 or later; if the flagged 7.15.0 comes back, a dependency is pinning it — upgrade that dependent, or pin react-router with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm) so only one copy resolves. This is 1 of 6 advisories with a published fix this scan raises against react-router 7.15.0, and their fixed versions do not agree — anything below 7.18.0 still leaves at least one of them open. Take this package to 7.18.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 6 advisories this scan raises against react-router 7.15.0: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] local-live-view/mix.lock— req 0.5.17: [GHSA redacted] — upgrade to 0.6.1. This is 1 of 2 advisories with a published fix this scan raises against req 0.5.17, and their fixed versions do not agree — anything below 0.6.1 still leaves at least one of them open. Take this package to 0.6.1 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against req 0.5.17: EEF-[CVE redacted], [GHSA redacted].
High CVE: [GHSA redacted] landing-page/package-lock.json— rollup 4.44.1: [GHSA redacted] — rollup is not declared by the manifests that govern this lockfile: it is pulled in transitively here (the ^4.60.3 this repo declares for it belongs to a separate install root and does not reach this one), so upgrade the dependency that requires it (or pin rollup to 4.59.0 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)).
High CVE: [GHSA redacted] landing-page/package-lock.json— undici 6.21.3: [GHSA redacted] — undici is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin undici to 6.24.0 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 13 advisories with a published fix this scan raises against undici 6.21.3, and their fixed versions do not agree — anything below 6.28.0 still leaves at least one of them open. Take this package to 6.28.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 13 advisories this scan raises against undici 6.21.3: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Leaked secret: high-entropy-secret examples/local-lv-thermostat/config/test.exs:7— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Leaked secret: high-entropy-secret examples/local-lv-thermostat/config/dev.exs:16— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Leaked secret: high-entropy-secret examples/local-lv-pong/config/test.exs:7— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Leaked secret: high-entropy-secret examples/local-lv-pong/config/dev.exs:16— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Leaked secret: high-entropy-secret examples/local-lv-kanban/config/test.exs:20— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Leaked secret: high-entropy-secret examples/local-lv-kanban/config/dev.exs:32— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Leaked secret: high-entropy-secret examples/local-lv-forms/config/test.exs:7— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Leaked secret: high-entropy-secret examples/local-lv-forms/config/dev.exs:16— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Leaked secret: high-entropy-secret examples/local-lv-compare/config/test.exs:7— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Leaked secret: high-entropy-secret examples/local-lv-compare/config/dev.exs:16— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Leaked secret: high-entropy-secret examples/local-lv-checkout/config/test.exs:7— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Leaked secret: high-entropy-secret examples/local-lv-checkout/config/dev.exs:16— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Leaked secret: high-entropy-secret examples/local-lv-burrito/config/test.exs:5— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Leaked secret: high-entropy-secret examples/local-lv-burrito/config/dev.exs:8— high-entropy-secret detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
High IaC: DS-0002 docker/base.Dockerfile— Image user should not be 'root' A container that starts as root runs your process with root's capabilities inside the namespace, so a compromise of the process starts from there. The step: create an unprivileged account in the image (`RUN adduser --system --no-create-home app`), give it ownership of the paths the process writes at runtime (`COPY --chown=` on those layers, or a `RUN chown -R`), and end the final stage with `USER app` so it is the default at start. Build stages that only compile can stay root; it is the stage that RUNS that needs the account. If the process genuinely requires root — it manages the container runtime, ptraces another process or opens raw devices — say so here rather than making a change that breaks it.
High IaC: DS-0029 docker/base.Dockerfile— 'apt-get' missing '--no-install-recommends'
High IaC: DS-0002 docker/landing.Dockerfile— Image user should not be 'root' A container that starts as root runs your process with root's capabilities inside the namespace, so a compromise of the process starts from there. The step: create an unprivileged account in the image (`RUN useradd -r -M app` — or whatever this base image's account tooling is, `adduser` and `useradd` are not both present everywhere`), give it ownership of the paths the process writes at runtime (`COPY --chown=` on those layers, or a `RUN chown -R`), and end the final stage with `USER app` so it is the default at start. Build stages that only compile can stay root; it is the stage that RUNS that needs the account. If the process genuinely requires root — it manages the container runtime, ptraces another process or opens raw devices — say so here rather than making a change that breaks it.
High IaC: DS-0002 docker/langtour.Dockerfile— Image user should not be 'root' A container that starts as root runs your process with root's capabilities inside the namespace, so a compromise of the process starts from there. The step: create an unprivileged account in the image (`RUN useradd -r -M app` — or whatever this base image's account tooling is, `adduser` and `useradd` are not both present everywhere`), give it ownership of the paths the process writes at runtime (`COPY --chown=` on those layers, or a `RUN chown -R`), and end the final stage with `USER app` so it is the default at start. Build stages that only compile can stay root; it is the stage that RUNS that needs the account. If the process genuinely requires root — it manages the container runtime, ptraces another process or opens raw devices — say so here rather than making a change that breaks it.
High IaC: DS-0002 docker/release.Dockerfile— Image user should not be 'root' A container that starts as root runs your process with root's capabilities inside the namespace, so a compromise of the process starts from there. The step: create an unprivileged account in the image (`RUN adduser --system --no-create-home app`), give it ownership of the paths the process writes at runtime (`COPY --chown=` on those layers, or a `RUN chown -R`), and end the final stage with `USER app` so it is the default at start. Build stages that only compile can stay root; it is the stage that RUNS that needs the account. If the process genuinely requires root — it manages the container runtime, ptraces another process or opens raw devices — say so here rather than making a change that breaks it.
High IaC: DS-0029 docker/release.Dockerfile— 'apt-get' missing '--no-install-recommends'
D38 · OSV Dependency Vulnerabilities· High vulnerability · ×5
High vulnerability: [GHSA redacted] pnpm-lock.yaml— postcss 8.5.14: [GHSA redacted] — postcss is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin postcss to 8.5.18 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 2 advisories with a published fix this scan raises against postcss 8.5.14, and their fixed versions do not agree — anything below 8.5.23 still leaves at least one of them open. Take this package to 8.5.23 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against postcss 8.5.14: [GHSA redacted], [GHSA redacted].
High vulnerability: [GHSA redacted] landing-page/package-lock.json— sharp 0.33.5: [GHSA redacted] — this repo declares sharp ^0.34.5, but the vulnerable 0.33.5 is a SEPARATE copy on another release line, so editing your own sharp entry cannot move it: upgrade the dependency that pulls it in (or pin sharp to 0.35.0 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)).
High vulnerability: [GHSA redacted] pnpm-lock.yaml— sharp 0.34.5: [GHSA redacted] — upgrade to 0.35.0
High vulnerability: [GHSA redacted] landing-page/package-lock.json— svgo 3.3.2: [GHSA redacted] — svgo is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin svgo to 3.3.4 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 2 advisories with a published fix this scan raises against svgo 3.3.2, and their fixed versions do not agree — anything below 3.3.4 still leaves at least one of them open. Take this package to 3.3.4 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against svgo 3.3.2: [GHSA redacted], [GHSA redacted].
High vulnerability: [GHSA redacted] pnpm-lock.yaml— svgo 4.0.1: [GHSA redacted] — svgo is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin svgo to 4.0.2 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)).
Critical CVE: [GHSA redacted] landing-page/package-lock.json— tar 6.2.1: [GHSA redacted] — tar is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 7.5.19 is a MAJOR ahead of the resolved 6.2.1, so an `overrides` pin would force a breaking version under a dependent written against 6.2.1; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 12 advisories with a published fix this scan raises against tar 6.2.1, and their fixed versions do not agree — anything below 7.5.21 still leaves at least one of them open. Take this package to 7.5.21 or later: that is the floor for the package, not this row's target alone. This one row stands for the 12 advisories this scan raises against tar 6.2.1: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] landing-page/package-lock.json— tar 7.4.3: [GHSA redacted] — tar is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin tar to 7.5.19 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 12 advisories with a published fix this scan raises against tar 7.4.3, and their fixed versions do not agree — anything below 7.5.21 still leaves at least one of them open. Take this package to 7.5.21 or later: that is the floor for the package, not this row's target alone. This one row stands for the 12 advisories this scan raises against tar 7.4.3: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] pnpm-lock.yaml— tar 7.5.14: [GHSA redacted] — tar is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin tar to 7.5.19 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 6 advisories with a published fix this scan raises against tar 7.5.14, and their fixed versions do not agree — anything below 7.5.21 still leaves at least one of them open. Take this package to 7.5.21 or later: that is the floor for the package, not this row's target alone. This one row stands for the 6 advisories this scan raises against tar 7.5.14: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Medium IaC: DS-0013 docker/base.Dockerfile— 'RUN cd ...' to change directory
Medium IaC: DS-0001 docker/burrito/Dockerfile— ':latest' tag used A `:latest` base pins nothing: the stage rebuilds against whatever that tag points at on the day, so the same commit produces different images and a change you did not make arrives without a diff. The step: pin the base to a concrete release and, where the registry offers one, its digest — `FROM alpine:3.21@sha256:…` — then bump it deliberately, which is a review a bot can raise. A build stage that only compiles is worth pinning for the same reason: it decides what ends up in the layers you ship.
Medium IaC: DS-0013 docker/burrito/Dockerfile— 'RUN cd ...' to change directory
Medium IaC: DS-0001 docker/landing.Dockerfile— ':latest' tag used A `:latest` base pins nothing: the stage rebuilds against whatever that tag points at on the day, so the same commit produces different images and a change you did not make arrives without a diff. The step: pin the base to a concrete release and, where the registry offers one, its digest — `FROM alpine:3.21@sha256:…` — then bump it deliberately, which is a review a bot can raise. A build stage that only compiles is worth pinning for the same reason: it decides what ends up in the layers you ship.
Medium IaC: DS-0001 docker/langtour.Dockerfile— ':latest' tag used A `:latest` base pins nothing: the stage rebuilds against whatever that tag points at on the day, so the same commit produces different images and a change you did not make arrives without a diff. The step: pin the base to a concrete release and, where the registry offers one, its digest — `FROM alpine:3.21@sha256:…` — then bump it deliberately, which is a review a bot can raise. A build stage that only compiles is worth pinning for the same reason: it decides what ends up in the layers you ship.
Medium IaC: CKV_DOCKER_3 docker/langtour.Dockerfile:1— Ensure that a user for the container has been created
Medium IaC: CKV_DOCKER_9 docker/release.Dockerfile:25— Ensure that APT isn't used
Medium IaC: CKV_DOCKER_3 docker/release.Dockerfile:1— Ensure that a user for the container has been created
Medium IaC: CKV_DOCKER_9 docker/base.Dockerfile:26— Ensure that APT isn't used
Medium IaC: CKV_DOCKER_3 docker/base.Dockerfile:1— Ensure that a user for the container has been created
Medium IaC: CKV_DOCKER_2 docker/burrito/Dockerfile:1— Ensure that HEALTHCHECK instructions have been added to container images
Medium IaC: CKV_DOCKER_3 docker/landing.Dockerfile:1— Ensure that a user for the container has been created
D38 · OSV Dependency Vulnerabilities· Medium CVE · ×10
Medium CVE: EEF-[CVE redacted] local-live-view/mix.lock— decimal 2.4.1: EEF-[CVE redacted] — upgrade to 3.0.0
Medium CVE: [GHSA redacted] landing-page/package-lock.json— dompurify 3.2.6: [GHSA redacted] — dompurify is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin dompurify to 3.4.0 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 17 advisories with a published fix this scan raises against dompurify 3.2.6, and their fixed versions do not agree — anything below 3.4.12 still leaves at least one of them open. Take this package to 3.4.12 or later: that is the floor for the package, not this row's target alone. This one row stands for the 18 advisories this scan raises against dompurify 3.2.6: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Medium CVE: [GHSA redacted] pnpm-lock.yaml— dompurify 3.4.2: [GHSA redacted] — dompurify is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin dompurify to 3.4.7 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)). This is 1 of 8 advisories with a published fix this scan raises against dompurify 3.4.2, and their fixed versions do not agree — anything below 3.4.12 still leaves at least one of them open. Take this package to 3.4.12 or later: that is the floor for the package, not this row's target alone. This one row stands for the 9 advisories this scan raises against dompurify 3.4.2: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Medium CVE: [GHSA redacted] landing-page/package-lock.json— follow-redirects 1.15.9: [GHSA redacted] — follow-redirects is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin follow-redirects to 1.16.0 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)).
Medium CVE: EEF-[CVE redacted] local-live-view/mix.lock— hpax 1.0.3: EEF-[CVE redacted] — upgrade to 1.0.4
Medium CVE: [GHSA redacted] landing-page/package-lock.json— mdast-util-to-hast 13.2.0: [GHSA redacted] — mdast-util-to-hast is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin mdast-util-to-hast to 13.2.1 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)).
Medium CVE: [GHSA redacted] pnpm-lock.yaml— mermaid 11.14.0: [GHSA redacted] — this repo declares mermaid ^11.7.0, a range that ALREADY admits the fixed 11.15.0, so there is no manifest edit to make here. Re-resolve the lock so mermaid moves onto 11.15.0 or later; if the flagged 11.14.0 comes back, a dependency is pinning it — upgrade that dependent, or pin mermaid with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm) so only one copy resolves. This one row stands for the 4 advisories this scan raises against mermaid 11.14.0: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Medium CVE: [GHSA redacted] landing-page/package-lock.json— mermaid 11.7.0: [GHSA redacted] — this repo declares mermaid ^11.7.0, a range that ALREADY admits the fixed 11.15.0, so there is no manifest edit to make here. Re-resolve the lock so mermaid moves onto 11.15.0 or later; if the flagged 11.7.0 comes back, a dependency is pinning it — upgrade that dependent, or pin mermaid with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm) so only one copy resolves. This is 1 of 6 advisories with a published fix this scan raises against mermaid 11.7.0, and their fixed versions do not agree — anything below 11.15.0 still leaves at least one of them open. Take this package to 11.15.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 6 advisories this scan raises against mermaid 11.7.0: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Medium CVE: EEF-[CVE redacted] pnpm-lock.yaml— phoenix 1.8.7: EEF-[CVE redacted] — this repo declares phoenix ^1.8.0, a range that ALREADY admits the fixed 1.8.9, so there is no manifest edit to make here. Re-resolve the lock so phoenix moves onto 1.8.9 or later; if the flagged 1.8.7 comes back, a dependency is pinning it — upgrade that dependent, or pin phoenix with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm) so only one copy resolves.
Medium CVE: [GHSA redacted] landing-page/package-lock.json— uuid 11.1.0: [GHSA redacted] — uuid is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin uuid to 11.1.1 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)).
Duplicated block (6 lines × 2) examples/eval-in-wasm/lib/eval_in_wasm.ex:71— examples/eval-in-wasm/lib/eval_in_wasm.ex:71-76 | popcorn-2/elixir/lib/popcorn/support/atom_vm.ex:322-327 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) examples/local-lv-burrito/lib/burrito_web/controllers/order_controller.ex:15— examples/local-lv-burrito/lib/burrito_web/controllers/order_controller.ex:15-20 | examples/local-lv-burrito/lib/burrito_web/controllers/order_controller.ex:27-32 — 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.
Hotspot: local-live-view/priv/static/AtomVM.mjs local-live-view/priv/static/AtomVM.mjs— local-live-view/priv/static/AtomVM.mjs changed 3 times in last 90 days, max complexity 43. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Change coupling: Results.tsx ↔ PopcornProvider.tsx language-tour/src/components/execution/Results.tsx— `language-tour/src/components/execution/Results.tsx` and `language-tour/src/context/popcorn/PopcornProvider.tsx` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking.
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 81 floating ref(s) across 18 workflow file(s). Each floating ref is itemized at file:line by the SAST (D29) lens.
D38 · OSV Dependency Vulnerabilities· Medium vulnerability · ×1
Medium vulnerability: [GHSA redacted] landing-page/package-lock.json— smol-toml 1.3.4: [GHSA redacted] — smol-toml is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin smol-toml to 1.6.1 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)).
Duplicated block (17 lines × 2) examples/local-lv-burrito/local/lib/burrito_live.ex:75— examples/local-lv-burrito/local/lib/burrito_live.ex:75-91 | examples/local-lv-burrito/local/lib/burrito_live.ex:97-113 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 6) examples/local-lv-checkout/lib/local_lv_checkout_web/telemetry.ex:41— examples/local-lv-checkout/lib/local_lv_checkout_web/telemetry.ex:41-56 | examples/local-lv-compare/lib/compare_live_views_web/telemetry.ex:41-56 | examples/local-lv-forms/lib/form_demo_web/telemetry.ex:41-56 | examples/local-lv-kanban/lib/local_lv_kanban_web/telemetry.ex:41-56 | examples/local-lv-pong/lib/local_lv_pong_web/telemetry.ex:41-56 | examples/local-lv-thermostat/lib/local_thermostat_web/telemetry.ex:41-56 — before extracting anything, compare `examples/local-lv-checkout/lib/local_lv_checkout_web/telemetry.ex` and `examples/local-lv-compare/lib/compare_live_views_web/telemetry.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 7) examples/local-lv-checkout/lib/local_lv_checkout_web/components/core_components.ex:106— examples/local-lv-checkout/lib/local_lv_checkout_web/components/core_components.ex:106-118 | examples/local-lv-compare/lib/compare_live_views_web/components/core_components.ex:99-111 | examples/local-lv-forms/lib/form_demo_web/components/core_components.ex:99-111 | examples/local-lv-forms/local/lib/core_components.ex:99-111 | examples/local-lv-kanban/lib/local_lv_kanban_web/components/core_components.ex:99-111 | examples/local-lv-pong/lib/local_lv_pong_web/components/core_components.ex:99-111 | examples/local-lv-thermostat/lib/local_thermostat_web/components/core_components.ex:99-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times.
Duplicated block (11 lines × 2) examples/local-lv-burrito/lib/burrito_web/live/ordering_form_component.ex:45— examples/local-lv-burrito/lib/burrito_web/live/ordering_form_component.ex:45-55 | examples/local-lv-burrito/lib/burrito_web/live/ordering_form_component.ex:59-69 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 7) examples/local-lv-burrito/lib/burrito_web/telemetry.ex:21— examples/local-lv-burrito/lib/burrito_web/telemetry.ex:21-30 | examples/local-lv-checkout/lib/local_lv_checkout_web/telemetry.ex:27-39 | examples/local-lv-compare/lib/compare_live_views_web/telemetry.ex:27-39 | examples/local-lv-forms/lib/form_demo_web/telemetry.ex:27-39 | examples/local-lv-kanban/lib/local_lv_kanban_web/telemetry.ex:27-39 | examples/local-lv-pong/lib/local_lv_pong_web/telemetry.ex:27-39 | examples/local-lv-thermostat/lib/local_thermostat_web/telemetry.ex:27-39 — before extracting anything, compare `examples/local-lv-checkout/lib/local_lv_checkout_web/telemetry.ex` and `examples/local-lv-compare/lib/compare_live_views_web/telemetry.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) examples/local-lv-burrito/lib/burrito_web/live/ordering_form_component.ex:124— examples/local-lv-burrito/lib/burrito_web/live/ordering_form_component.ex:124-133 | examples/local-lv-burrito/lib/burrito_web/live/sync_table_live.ex:101-110 | examples/local-lv-burrito/local/lib/burrito_live.ex:216-225 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (9 lines × 6) examples/local-lv-burrito/lib/burrito_web/telemetry.ex:31— examples/local-lv-burrito/lib/burrito_web/telemetry.ex:31-39 | examples/local-lv-checkout/lib/local_lv_checkout_web/telemetry.ex:47-59 | examples/local-lv-compare/lib/compare_live_views_web/telemetry.ex:47-59 | examples/local-lv-forms/lib/form_demo_web/telemetry.ex:47-59 | examples/local-lv-pong/lib/local_lv_pong_web/telemetry.ex:47-59 | examples/local-lv-thermostat/lib/local_thermostat_web/telemetry.ex:47-59 — before extracting anything, compare `examples/local-lv-checkout/lib/local_lv_checkout_web/telemetry.ex` and `examples/local-lv-compare/lib/compare_live_views_web/telemetry.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) examples/local-lv-checkout/local/lib/checkout_live.ex:119— examples/local-lv-checkout/local/lib/checkout_live.ex:119-127 | examples/local-lv-checkout/local/lib/checkout_live.ex:131-143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) popcorn/utils/popcorn_server.ex:108— popcorn/utils/popcorn_server.ex:108-115 | popcorn/utils/popcorn_server.ex:116-123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) examples/local-lv-burrito/lib/burrito_web/live/sync_table_live.ex:83— examples/local-lv-burrito/lib/burrito_web/live/sync_table_live.ex:83-89 | examples/local-lv-burrito/local/lib/burrito_live.ex:181-187 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 7) examples/local-lv-checkout/lib/local_lv_checkout_web/components/core_components.ex:192— examples/local-lv-checkout/lib/local_lv_checkout_web/components/core_components.ex:192-196 | examples/local-lv-compare/lib/compare_live_views_web/components/core_components.ex:185-189 | examples/local-lv-forms/lib/form_demo_web/components/core_components.ex:185-189 | examples/local-lv-forms/local/lib/core_components.ex:171-175 | examples/local-lv-kanban/lib/local_lv_kanban_web/components/core_components.ex:185-189 | examples/local-lv-pong/lib/local_lv_pong_web/components/core_components.ex:185-189 | examples/local-lv-thermostat/lib/local_thermostat_web/components/core_components.ex:185-189 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times.
Low IaC: DS-0026 docker/landing.Dockerfile— No HEALTHCHECK defined Without one the runtime only knows whether the process is alive, not whether it is serving, so a wedged container is restarted by nobody. The step: add a `HEALTHCHECK` to the image that probes the service the way a client would — this image already declares `EXPOSE 8080`, so a request to `localhost:8080` on the service's own health or root route, exiting non-zero when it does not answer, is the probe — and give it an `--interval`, a `--timeout` and a `--start-period` long enough to cover startup. If the image ships no HTTP client, probe with whatever the runtime already has, or declare the check in the orchestrator instead and say so here.
Low IaC: DS-0026 docker/langtour.Dockerfile— No HEALTHCHECK defined Without one the runtime only knows whether the process is alive, not whether it is serving, so a wedged container is restarted by nobody. The step: add a `HEALTHCHECK` to the image that probes the service the way a client would — this image already declares `EXPOSE 8080`, so a request to `localhost:8080` on the service's own health or root route, exiting non-zero when it does not answer, is the probe — and give it an `--interval`, a `--timeout` and a `--start-period` long enough to cover startup. If the image ships no HTTP client, probe with whatever the runtime already has, or declare the check in the orchestrator instead and say so here.
Low CVE: [GHSA redacted] landing-page/package-lock.json— @babel/core 7.27.7: [GHSA redacted] — @babel/core is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/core to 7.29.6 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)).
Low CVE: [GHSA redacted] pnpm-lock.yaml— @babel/core 7.29.0: [GHSA redacted] — @babel/core is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/core to 7.29.6 with an `overrides` entry (the `overrides:` block in `pnpm-workspace.yaml` for pnpm)).
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — Test source is present (.exs, .ts, .js, .mjs) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 5 significant file(s) lose their only recent owner: popcorn/js/src/errors.ts, popcorn/js/plugins/shared.ts, popcorn/js/plugins/vite.ts, popcorn/js/src/types.ts, popdoc/lib/popdoc/markdown.ex. Pair on, review, or document these before any departure.
D19 · Documentation Quality· The single-expression Popdoc example is a minimal fixture that does not show the full Popcorn runtime behavior (e.g. error handling, stack traces) and lacks any accompanying documentation for the popdoc server. · ×1
The single-expression Popdoc example is a minimal fixture that does not show the full Popcorn runtime behavior (e.g. error handling, stack traces) and lacks any accompanying documentation for the popdoc server. popdoc/e2e/fixture/README.md— Expand the fixture to cover more Popcorn features such as error with stacktrace output and add notes on how to run the docs locally after building.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Rotate the exposed credentials — git history can't be un-committed — Some of these secrets are in git HISTORY: deleting the file does not remove them (the commit persists on every clone, fork and backup). The remediation is to ROTATE each historically-exposed credential and treat it as compromised — not to delete the file. Rewriting history is disruptive and unreliable across existing forks. (Working-tree-only secrets — no commit — can instead be removed from the file and moved to a secret store.) Every location above sits inside a test/fixture/sample tree, so there may be no live credential to revoke — in that case the performable actions are different ones: confirm each value was never reused outside the tests (a fixture key shared with a staging or demo environment IS a live credential and must be rotated), generate this material at test time instead of committing it so the next one cannot be mistaken for a real leak, and record the deliberate exposure where a reader of the file will see it. Rotate anything that fails the first check.
D34 · Knowledge Freshness· knowledge concentrated in recent work · ×1
knowledge concentrated in recent work — freshness signal contradicted by repo activity — File-level freshness contradicts repo activity: 112 commits in the last 90 days, yet 96 of 116 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
No artifact signing — No artifact signing found in CI — sign your released artifacts with whatever your ecosystem ships (a GPG/minisign detached signature — or `cosign sign-blob` — over the release archives, or over a checksum file published alongside them) so consumers can verify what you built.
D36 · Supply-chain Provenance & Signing· No SBOM · ×1
No SBOM — No SBOM generation or committed SBOM found — produce one with what your ecosystem ships (`cdxgen -t pnpm` (or `syft` below) over the pnpm workspace — `npm sbom` cannot read `pnpm-lock.yaml`, `syft` (or `anchore/sbom-action` in CI) over the source tree or released image). Publish it as a release asset (`*.spdx.json` / `*.cdx.json`) so consumers can see what they are installing.
Coverage not included — suite not readable by the collector — Coverage NOT MEASURED: test source is present (.exs, .ts, .js, .mjs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `mix test --cover` with `excoveralls` (`mix coveralls.lcov`), or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored.
Info — 2 finding(s)
D12 · Dependency Hygiene· Dependency hygiene not measured · ×1
Dependency hygiene not measured — dependency manifest found but not parsed for hygiene — This repository's dependency manifest (package.json) was found, but this pass cannot parse it for hygiene, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D38 wherever the manifest is OSV-readable. Your package.json IS read in this same run: the frontend dependency lens (R8) parses it for unused declarations, undeclared imports and misplaced production dependencies — what is missing here is the outdated/deprecated/unmaintained signal for those npm packages, not the manifest.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
0
—
Run 019fd4e0-1a49-708a-9803-e6b1728fb1ad · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 106 · Warnings: 39 · Recommendations: 12 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 06-08-2026 @ 02:21 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.