entelect-incubator/Project-Templates

This system is a multi-architecture backend and frontend template library designed for building pizza ordering applications. It provides pre-configured implementations in Java, Node.js, Python, and .NET, each featuring in-memory repositories, middleware for security and observability, and CQRS-based API endpoints. The frontend templates for React and Angular include SSR support, state management for carts and orders, and automated client generation from OpenAPI specifications.

Developers can now automatically generate type-safe API clients for React and Angular from the backend's OpenAPI specification. The \clients/generation\ directory now contains scripts (\generate-react-client\, \generate-angular-client\) and configuration files (e.g., \openapi-generator-react.json\) that download the OpenAPI spec and produce TypeScript clients in \clients/generated/react\ and \clients/generated/angular\. This includes the core generated client code (\generated.ts\), export barrels (\index.ts\), and comprehensive documentation (\README.md\, \QUICK\_REFERENCE.md\, \OPENAPI\_GENERATION\_GUIDE.md\) to help developers integrate these clients into their frontend applications.

clients · high confidence

The Angular frontend now includes a complete project template with integrated .NET Aspire support. A new \apphost.cs\ file configures the Aspire distributed application, linking the Angular app as a Vite-based service that depends on the backend API. Development is streamlined via VS Code launch and task configurations, a proxy configuration for API calls, and npm scripts to run the full stack with a single command. The project also includes comprehensive documentation covering coding standards, architecture, and onboarding, alongside an OpenAPI client generator setup for type-safe API integration.

frontend · high confidence

The repository now includes initial scaffolding for a pizza ordering feature across Java, Node.js, and Python backends, alongside React frontend types. Each backend provides in-memory repositories and handlers for creating and retrieving pizzas, with shared core utilities for results, errors, logging, and OpenTelemetry. The Java implementation adds a Spring Boot application with security headers, rate limiting, and API key validation. The Node.js implementation uses Express with similar middleware and routing. The Python implementation uses FastAPI with equivalent middleware. Frontend React types define order and customer information structures. A test file validates the Java pizza creation handler.

(repo-wide) · high confidence

A new .NET Clean Architecture template is introduced, providing a pre-configured backend solution structured into layers (API, Core, Common, Providers) with a layered project structure. The template includes an auto-generated C\# API client (Api-Client-v1.cs) and its corresponding OpenAPI/Swagger definition (Api-Client-v1.json), generated via NSwag from the API project. The API exposes endpoints for managing Orders (create, complete, status) and Pizzas (CRUD, search, image retrieval) using a CQRS-based dispatcher pattern. Additionally, the template includes standard configuration files (.editorconfig, .dockerignore, .gitignore) and a Dockerfile for containerization.

backend · high confidence

The Angular frontend templates have been updated to support server-side rendering (SSR) and enhanced observability. The application now includes server-side route configuration and a dedicated server configuration file to enable SSR capabilities. Additionally, OpenTelemetry-based telemetry and logging services have been introduced to provide centralized observability, including automatic HTTP request tracing, error tracking, and custom metric recording. The order feature has been expanded with a new order page component and modal for capturing customer details and managing the cart, alongside a new cart service for state management. Core interceptors for authentication, error handling, and loading states have also been added to the application configuration.

(repo-wide) · high confidence

The application startup pipeline in both the CleanTemplate and TemplateWithDataAccess projects has been refactored into two distinct modules: CommonApp and SecurityApp. CommonApp now handles standard middleware such as logging, compression, HTTPS redirection, Swagger, routing, static files, rate limiting, and health checks. SecurityApp encapsulates all security-related headers and policies, including Content Security Policy, X-Frame-Options, Permissions-Policy, CORS, and HSTS. This change separates general application configuration from security-specific concerns, making the startup process more modular and easier to maintain.

backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/StartupApp · high confidence

The GetPizzaQueryHandler was not registered in the dependency injection containers for any of the five architecture templates (Layered, Clean, and Vertical Slice). This caused the GET /api/pizzas/{id} endpoint to fail with a 'No service for type' error. The fix adds the missing \IQueryHandler\<GetPizzaQuery, Result\<PizzaModel\>\>\ registration to all five templates' DI configurations, ensuring the PizzaController can successfully resolve the handler.

(repo-wide) · high confidence

Test coverage in backend/Java/target/test-classes/com/example — 1 commit, 1 file.

backend/Java/target/test-classes/com/example · high confidence · unverified

All .NET project files in the backend templates (Clean, TemplateWithDataAccess, and CleanArchitecture) have been updated to target the .NET 10.0 framework. This upgrade brings the templates up to date with the latest .NET runtime, ensuring compatibility with new language features and runtime improvements available in .NET 10.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 52 → 50 (-1.4)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 84 → 72 (-12.4)
• Architecture 94 → 66 (-28.4)
• Maturity 73 → 73 (-0.3)
• Readiness 39 → 33 (-5.9)
• Security 44 → 71 (+27.3)
• Accessibility 77 → 78 (+0.4)
• Performance 60 (new)

• Critical CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
• Critical CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
• Critical CVE: [GHSA redacted] (backend/Node/package-lock.json)
• Critical CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
• Critical CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
• Critical CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
• Dependency hygiene not measured — no packages were read
• High CVE: [GHSA redacted] (backend/Node/package-lock.json)
• High CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/React/package-lock.json)
• High CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/React/package-lock.json)
• High CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
• High CVE: [GHSA redacted] (backend/Node/package-lock.json)
• High CVE: [GHSA redacted] (backend/Node/package-lock.json)
• High CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
• …and 203 more

• (anonymous) (cyclomatic 16) (backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/order-endpoints.js)
• (anonymous) (cyclomatic 16) (backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/LoadTesting/k6/order-endpoints.js)
• (anonymous) (cyclomatic 16) (backend/.NET/2.CleanArchitecture/LoadTesting/k6/order-endpoints.js)
• (anonymous) (cyclomatic 16) (backend/.NET/3.VerticalSliceArchitecture/1.Traditional/LoadTesting/k6/order-endpoints.js)
• (anonymous) (cyclomatic 16) (backend/.NET/3.VerticalSliceArchitecture/1.Traditional/k6/order-endpoints.js)
• (anonymous) (cyclomatic 16) (backend/.NET/3.VerticalSliceArchitecture/2.Minimal/LoadTesting/k6/order-endpoints.js)
• (anonymous) (cyclomatic 16) (backend/.NET/3.VerticalSliceArchitecture/2.Minimal/k6/order-endpoints.js)
• (anonymous) (cyclomatic 18) (backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/comprehensive-all-endpoints.js)
• (anonymous) (cyclomatic 18) (backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/LoadTesting/k6/comprehensive-all-endpoints.js)
• (anonymous) (cyclomatic 18) (backend/.NET/2.CleanArchitecture/LoadTesting/k6/comprehensive-all-endpoints.js)
• (anonymous) (cyclomatic 18) (backend/.NET/3.VerticalSliceArchitecture/1.Traditional/LoadTesting/k6/comprehensive-all-endpoints.js)
• (anonymous) (cyclomatic 18) (backend/.NET/3.VerticalSliceArchitecture/1.Traditional/k6/comprehensive-all-endpoints.js)
• (anonymous) (cyclomatic 18) (backend/.NET/3.VerticalSliceArchitecture/2.Minimal/LoadTesting/k6/comprehensive-all-endpoints.js)
• (anonymous) (cyclomatic 18) (backend/.NET/3.VerticalSliceArchitecture/2.Minimal/k6/comprehensive-all-endpoints.js)
• Ambiguous use of 'Id' vs specific entity names like 'PizzaId'. In Order-related contexts, 'Id' likely refers to OrderId, but in Command/Entity contexts involving Pizzas, 'PizzaId' is used. However, 'DeletePizzaCommand.Id' is ambiguous (is it the Pizza ID or the Command ID?). Similarly, 'OrderModel.Id' is ambiguous without context. The inconsistency lies in mixing generic 'Id' with specific 'PizzaId' for different concepts.
• CommentedOutCode (backend/.NET/1.LayeredArchitecture/1. CleanTemplate/AspireHost/Extensions.cs)
• CommentedOutCode (backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/AspireHost/Extensions.cs)
• CommentedOutCode (backend/.NET/2.CleanArchitecture/AspireHost/Extensions.cs)
• CommentedOutCode (backend/.NET/3.VerticalSliceArchitecture/1.Traditional/AspireHost/Extensions.cs)
• Coverage not measured — .NET and JavaScript/TypeScript suite
• …and 273 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

entelect-incubator/Project-Templates was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.