Executive summary
MinhHungPhan/aws-hands-on-labs is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 46.8 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Production Readiness, at 29.5, is the weakest lens and counts most in the score. The best first step is tidying the declared packages, worth about 5.2 points. Fixing the block of code copied to several places comes next, worth about 4.7 points. Raising Production Readiness to 52 would lift the score to about 56.7.
320 known security holes in the packages the code depends on can be used by attackers. Twelve settings leave the servers or containers unsafe. Updating the vulnerable packages and correcting the unsafe settings would close both risks.
The product code is 620 lines, too few for a meaningful rebuild estimate.
If Production Readiness rose from 29.5 to 52, the lowest score rated Strong, the score would rise from 46.8 to about 56.7.
Top priorities
Diagnosis: what the measurements show together
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 488 | High / Critical |
| A02:2025 — Security Misconfiguration | 48 | High / Critical |
Roadmap
Top priorities: Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Resolve the 1 Duplicated block (61 lines × 2) finding(s) in Code Duplication — start with lambda_function.py; Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +5.2 pts | Medium | Dependency Hygiene |
| Resolve the 1 Duplicated block (61 lines × 2) finding(s) in Code Duplication — start with lambda_function.py. | +4.7 pts | Medium | Code Duplication |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +4.7 pts | Medium | Type Safety |
| Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract. | +4.7 pts | Medium | Code Duplication |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +1.4 pts | Low | Documentation Quality |
| Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete. | +2.5 pts | Medium | DR & Backup |
| Add tests that import the unreached modules (directly or through their public entry). | +2.3 pts | Medium | Test Coverage |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.4 pts | Medium | Deployment & Rollback |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.7 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 48 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 48 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 744 of 764 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.js) and the coverage collector does support this ecosystem — it drives jest, vitest and mocha — but the runner its test command uses is one the coverage collector has no executor for (`react-scripts`). Read from the manifests: `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`. Not scored — this is a gap in the analyzer's runner coverage, not a missing .js runner and not a defect in this repository.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.js) and the reliability runner does support this ecosystem — it drives jest, vitest, mocha and egg-bin — but the runner its test command uses is one the re-runner has no executor for (`react-scripts`). Read from the manifests: `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`; `03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app` has a `scripts.test` of `react-scripts test` and declares `react-scripts`. So flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's runner coverage, not a missing .js runner and not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 201 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D34 Knowledge Freshness — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 30 production source file(s) in this repository were read, and every one is under the ~2,400-byte (~100-line) size floor this dimension measures over (or declares itself generated), so there is no significant file to judge and knowledge freshness is not applicable. This is the size of the repository's files, not a file the engine failed to read.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, Kotlin source, and Rust source only, and no C# was loaded, no TypeScript was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
1 duplicated block group(s) detected. 19.4 % of the production lines (120 of 620) are in a reported copy. Measured on part of this repository only: .js (65% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 1 Duplicated block (61 lines × 2) finding(s) in Code Duplication — start with lambda_function.py. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
8 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations, and main-sequence distance (abstractness) is not computed for these modules yet.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 8 tests.
D12 · Dependency Hygiene
6 outdated direct production npm dependency(ies) of 7 graded, 0 pinning defect(s), across 8 package.json (8 of them the product) and 8 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 1128 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1128 package(s) this repository's committed lockfile installs for a consumer — its 7 production, optional and peer dependency(ies), across 8 product package.json manifest(s), and everything those install in turn. Its 0 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. No third-party code was found shipping without a manifest entry (vendored or copied-in directories, licence comments preserved in committed bundles, bundled module paths, compiled wasm modules).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 220 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F4 map. 81 document(s) read across 9 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 9 build units (checkout, npm) flagged as possibly oversized/incoherent.
D27 · Navigability
100 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
488 finding(s): 32 critical, 288 high, 112 medium, 56 low.
What to do
- Resolve the 272 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (272). — One of this dimension's main actionable groups (272 issue-level).
- Resolve the 32 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (32). — One of this dimension's main actionable groups (32 issue-level).
- Resolve the 16 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (16). — One of this dimension's main actionable groups (16 issue-level).
D31 · IaC & Container Security
48 finding(s): 0 critical, 12 high, 28 medium, 8 low.
What to do
- Resolve the 28 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (9), REDACTED (9), REDACTED (8). — One of this dimension's main actionable groups (28 warning-level).
- Resolve the 12 High IaC finding(s) in IaC & Container Security — start with REDACTED (8), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (12 issue-level).
- Resolve the 8 Low IaC finding(s) in IaC & Container Security — start with REDACTED (8). — One of this dimension's main actionable groups (8 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AC3 · Page structure
AC6 · Visual & motion safety
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app)` ships in a production host and references `@testing-library/jest-dom`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:6
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app)` ships in a production host and references `@testing-library/react`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:7
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app)` ships in a production host and references `@testing-library/user-event`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:8
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app)` ships in a production host and references `@testing-library/jest-dom`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:6
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app)` ships in a production host and references `@testing-library/react`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:7
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app)` ships in a production host and references `@testing-library/user-event`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:8
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app)` ships in a production host and references `@testing-library/jest-dom`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:6
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app)` ships in a production host and references `@testing-library/react`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:7
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app)` ships in a production host and references `@testing-library/user-event`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:8
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app)` ships in a production host and references `@testing-library/jest-dom`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/package.json:6
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app)` ships in a production host and references `@testing-library/react`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/package.json:7
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app)` ships in a production host and references `@testing-library/user-event`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/package.json:8
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app)` ships in a production host and references `@testing-library/jest-dom`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/package.json:6
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app)` ships in a production host and references `@testing-library/react`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/package.json:7
- `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app)` ships in a production host and references `@testing-library/user-event`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/package.json:8
- `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app)` ships in a production host and references `@testing-library/jest-dom`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:6
- `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app)` ships in a production host and references `@testing-library/react`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:7
- `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app)` ships in a production host and references `@testing-library/user-event`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:8
- `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app)` ships in a production host and references `@testing-library/jest-dom`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:6
- `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app)` ships in a production host and references `@testing-library/react`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:7
- `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app)` ships in a production host and references `@testing-library/user-event`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:8
- `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app)` ships in a production host and references `@testing-library/jest-dom`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:6
- `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app)` ships in a production host and references `@testing-library/react`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:7
- `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app)` ships in a production host and references `@testing-library/user-event`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app)` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:8
What to do
- Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- CONTRIBUTING.md links to `CODE_OF_CONDUCT.md`, but `CODE_OF_CONDUCT.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:7
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/03-creating-an-elastic-container-registry/README.md links to `../04-setting-up-aws-iam-user-and-permissions/README.md`, but `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/04-setting-up-aws-iam-user-and-permissions/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/03-creating-an-elastic-container-registry/README.md:180
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/03-creating-an-elastic-container-registry/README.md links to `../05-setting-up-github-actions-workflow/README.md`, but `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/03-creating-an-elastic-container-registry/README.md:181
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/03-creating-an-elastic-container-registry/README.md links to `../07-deploying-to-amazon-ecs/README.md`, but `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/03-creating-an-elastic-container-registry/README.md:182
What to do
- Reconcile the README with reality: CONTRIBUTING.md links to `CODE_OF_CONDUCT.md`, but `CODE_OF_CONDUCT.md` does not exist; 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/03-creating-an-elastic-container-registry/README.md links to `../04-setting-up-aws-iam-user-and-permissions/README.md`, but `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/04-setting-up-aws-iam-user-and-permissions/README.md` does not exist; 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/03-creating-an-elastic-container-registry/README.md links to `../05-setting-up-github-actions-workflow/README.md`, but `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/README.md` does not exist; 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/03-creating-an-elastic-container-registry/README.md links to `../07-deploying-to-amazon-ecs/README.md`, but `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/README.md` does not exist.
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`pytest` for the toolchain this pipeline already uses) and gate merges on it.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:5
What to do
- Run what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/.github/workflows/deploy-to-ecs.yml:52
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P5 · DR & Backup
What to do
- Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
R1 · Type Safety
- 0 typed · 40 plain JS — the untyped files are 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/App.js, 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/App.test.js, 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/index.js, 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/reportWebVitals.js, 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/setupTests.js, 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/src/App.js (+34 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/ and 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/ and 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/ and 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/ and 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 19 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 19 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/ and 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/ and 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/ and 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 19 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 19 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/ and 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/ and 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 19 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 19 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/ and 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 19 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 19 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 18 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 19 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 19 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 19 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 18 and 19 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/ and 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/ are near-verbatim copies of each other: 17 files are byte-identical under the same relative paths (~18801 lines; the trees hold 19 and 19 files). That is one structural fact, not 17 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/App.js:4 · 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/src/App.js:4 · 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/src/App.js:4 · 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/src/App.js:4 · +4 more site(s) not listed — the 8 copies are spread across 8 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. There is one copy in each of 8 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/App.js:4
- 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/reportWebVitals.js:1 · 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/src/reportWebVitals.js:1 · 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/src/reportWebVitals.js:1 · 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/src/reportWebVitals.js:1 · +4 more site(s) not listed — the 8 copies are spread across 8 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. There is one copy in each of 8 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/reportWebVitals.js:1
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×16) — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/index.js:1, 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/src/index.js:1, 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/src/index.js:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
R8 · Dependency Hygiene
- Declared in 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:8
- Declared in 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:8
- Declared in 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:8
- Declared in 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/package.json:8
- Declared in 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/package.json:8
- Declared in 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:8
- Declared in 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:8
- Declared in 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:8
- Only test files import it (first: 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/App.test.js:1) — move it to devDependencies. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:7
- Only test files import it (first: 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/src/App.test.js:1) — move it to devDependencies. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:7
- Only test files import it (first: 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/src/App.test.js:1) — move it to devDependencies. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:7
- Only test files import it (first: 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/src/App.test.js:1) — move it to devDependencies. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/package.json:7
- Only test files import it (first: 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/src/App.test.js:1) — move it to devDependencies. — 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/package.json:7
- Only test files import it (first: 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/App.test.js:1) — move it to devDependencies. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:7
- Only test files import it (first: 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/src/App.test.js:1) — move it to devDependencies. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:7
- Only test files import it (first: 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/src/App.test.js:1) — move it to devDependencies. — 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:7
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X12 · Unreachable branch
X3 · Exception handling
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 49.8 | Adequate — gated by D4, R1, R10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 67.2 | Adequate — gated by AX8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 71.4 | Strong | Solid. |
| Readiness | 29.5 | Weak — gated by R4, R8, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 76.6 | Adequate — gated by D31 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 100.0 | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- AXH1 Runtime security headers — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXI1 Runtime container hardening — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 80 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no interface, protocol or abstract type declares an operation an implementer must write
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXA1 Runtime unauthenticated reachability — This run crawled public routes only — it had no logged-in session, so there is no authenticated surface to compare anonymous access against and nothing was measured. This is a statement about this run, not about your application: nothing here says access control is missing, and nothing here says it is present.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility (rendered) — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXS1 Runtime exposed surface — 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 — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not included — no executor for the `react-scripts` test runner
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (48 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — 8 of 16 comment blocks were not judged (8 in a language other than English): redundancy is judged by word overlap with the code's identifiers, which cannot be measured across languages.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — every production source file is under the ~100-line size floor — too little code for knowledge freshness to be judged
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 5 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (3 with fewer than two methods, 2 stateless), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is 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 measured — no executor for the `react-scripts` test runner
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's Python, JavaScript/TypeScript source (9 module(s), 29 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 356 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app) → @testing-library/jest-dom 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:6
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app) → @testing-library/react 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:7
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app) → @testing-library/user-event 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:8
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app) → @testing-library/jest-dom 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:6
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app) → @testing-library/react 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:7
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app) → @testing-library/user-event 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:8
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app) → @testing-library/jest-dom 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:6
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app) → @testing-library/react 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:7
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app) → @testing-library/user-event 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:8
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app) → @testing-library/jest-dom 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/package.json:6
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app) → @testing-library/react 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/package.json:7
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app) → @testing-library/user-event 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/package.json:8
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app) → @testing-library/jest-dom 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/package.json:6
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app) → @testing-library/react 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/package.json:7
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app) → @testing-library/user-event 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/package.json:8
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app) → @testing-library/jest-dom 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:6
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app) → @testing-library/react 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:7
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app) → @testing-library/user-event 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:8
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app) → @testing-library/jest-dom 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:6
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app) → @testing-library/react 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:7
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app) → @testing-library/user-event 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:8
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app) → @testing-library/jest-dom 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:6
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app) → @testing-library/react 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:7
- Production project references a test package: my-react-app (03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app) → @testing-library/user-event 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:8
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 208 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- Forked directory tree (17 identical files, ~18801 lines × 2 trees) REDACTED:1
- No test reaches this file 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/index.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/src/index.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/src/index.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/src/index.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/src/index.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/index.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/src/index.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/src/index.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/reportWebVitals.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/src/reportWebVitals.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/src/reportWebVitals.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/src/reportWebVitals.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/src/reportWebVitals.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/reportWebVitals.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/src/reportWebVitals.js:1
- No test reaches this file 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/src/reportWebVitals.js:1
- Runtime security header not set: content-security-policy
- Runtime security header not set: cross-origin-embedder-policy
- Runtime security header not set: cross-origin-opener-policy
- Runtime security header not set: cross-origin-resource-policy
- Runtime security header not set: permissions-policy
- Runtime security header not set: referrer-policy
- Runtime security header not set: strict-transport-security
- Runtime security header not set: x-content-type-options
- Runtime security header not set: x-dns-prefetch-control
- Runtime security header not set: x-frame-options
- Runtime security header not set: x-permitted-cross-domain-policies
- Unused dependency '@testing-library/user-event' 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:8
- Unused dependency '@testing-library/user-event' 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:8
- Unused dependency '@testing-library/user-event' 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:8
- Unused dependency '@testing-library/user-event' 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/package.json:8
- Unused dependency '@testing-library/user-event' 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/package.json:8
- Unused dependency '@testing-library/user-event' 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:8
- Unused dependency '@testing-library/user-event' 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:8
- Unused dependency '@testing-library/user-event' 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:8
- Container process runs as root: wd-runtime-app
- Duplicated block (61 lines × 2) 06-API-Gateway/02-associate/01-working-with-rest-api/01-building-a-rest-api-with-lambda-proxy-integration/01-setting-up-a-lambda-function-for-rest-api/resources/HTTPMethodHandler/lambda_function.py:5
- Type Safety
- Duplicated block (20 lines × 8 locations) 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/App.js:4
- Duplicated block (11 lines × 8 locations) 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/reportWebVitals.js:1
- No typecheck script
Minor — 196 finding(s)
- Deprecated: @babel/plugin-proposal-class-properties REDACTED:564
- Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:596
- Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:612
- Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:628
- Deprecated: @babel/plugin-proposal-private-methods REDACTED:645
- Deprecated: abab REDACTED:4936
- Deprecated: domexception REDACTED:7167
- Deprecated: rollup-plugin-terser REDACTED:15535
- Deprecated: sourcemap-codec REDACTED:16097
- Deprecated: stable REDACTED:16136
- Deprecated: svgo REDACTED:16653
- Deprecated: w3c-hr-time REDACTED:17409
- Deprecated: workbox-cacheable-response REDACTED:18085
- Deprecated: workbox-google-analytics REDACTED:18108
- Deprecated: @babel/plugin-proposal-class-properties REDACTED:564
- Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:596
- Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:612
- Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:628
- Deprecated: @babel/plugin-proposal-private-methods REDACTED:645
- Deprecated: abab REDACTED:4936
- Deprecated: domexception REDACTED:7167
- Deprecated: rollup-plugin-terser REDACTED:15535
- Deprecated: sourcemap-codec REDACTED:16097
- Deprecated: stable REDACTED:16136
- Deprecated: svgo REDACTED:16653
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test-only dependency '@testing-library/react' in production deps 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:7
- Test-only dependency '@testing-library/react' in production deps 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/01-setting-up-github-actions-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:7
- Test-only dependency '@testing-library/react' in production deps 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/05-setting-up-github-actions-workflow/02-setting-up-github-actions-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:7
- Test-only dependency '@testing-library/react' in production deps 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/06-configuring-aws-credentials-for-github-actions-using-github-oidc-provider/03-updating-github-actions-workflow-to-use-github-oidc-identity-provider/resources/my-react-app/package.json:7
- Test-only dependency '@testing-library/react' in production deps 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/package.json:7
- Test-only dependency '@testing-library/react' in production deps 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:7
- Test-only dependency '@testing-library/react' in production deps 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/01-setting-up-gitlab-ci-worflow-for-amazon-ecr-public-repository/resources/my-react-app/package.json:7
- Test-only dependency '@testing-library/react' in production deps 03-Amazon-ECS/03-professional/03-deploy-applications-on-amazon-ecs-using-gitlab-ci/05-setting-up-gitlab-ci-workflow/02-setting-up-gitlab-ci-worflow-for-amazon-ecr-private-repository/resources/my-react-app/package.json:7
- README/code drift CONTRIBUTING.md:7
- README/code drift 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/03-creating-an-elastic-container-registry/README.md:180
- README/code drift 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/03-creating-an-elastic-container-registry/README.md:181
- README/code drift 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/03-creating-an-elastic-container-registry/README.md:182
- Outdated (npm): @testing-library/react 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:7
- Outdated (npm): web-vitals 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:12
- Documentation: no map of the repository's parts README.md:1
- No ADRs
- No SAST
- No dependency-update automation 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/package.json:5
- No release approval gate 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/07-deploying-to-amazon-ecs/02-updating-github-actions-workflow-to-deploy-ecs-task-definition-to-amazon-ecs/resources/my-react-app/.github/workflows/deploy-to-ecs.yml:52
- Duplicated predicate 03-Amazon-ECS/03-professional/02-deploy-applications-on-amazon-ecs-using-github-actions/02-creating-a-container-image-for-amazon-ecs/resources/my-react-app/src/reportWebVitals.js:2
Minor — 4 finding(s)
- Outdated (npm): @testing-library/jest-dom
- Outdated (npm): @testing-library/user-event
- Outdated (npm): react
- Outdated (npm): react-dom
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-d9187f621ff44df59de139bbcde294c9/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=1" --report-format json --report-path /tmp/watchdog-gitleaks-d9187f621ff44df59de139bbcde294c9/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d9187f621ff44df59de139bbcde294c9/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 488 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 48 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |