entelect-incubator/Project-Templates
41.4
Weak · 8 November 2026
5.2k
lines of production code
TypeScript
with JavaScript
4
measurements over time
What this system is
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.
Features
Add automated OpenAPI client generation for React and Angular
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
Angular frontend template with .NET Aspire orchestration and development tooling
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
Initial backend and frontend templates for pizza ordering
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
New .NET Clean Architecture template with layered backend and client generation
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
Behavioural changes
Angular frontend templates updated with SSR, observability, and order features
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
Modularized application startup pipeline into CommonApp and SecurityApp
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
Fixes
Added missing GetPizzaQueryHandler to dependency injection across all architecture templates
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
1 commit adding/updating tests in backend/Java/target/test-classes/com/example
Test coverage in backend/Java/target/test-classes/com/example — 1 commit, 1 file.
backend/Java/target/test-classes/com/example · high confidence · unverified
Dependencies
Upgrade .NET project templates to target .NET 10.0
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 cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 40 → 41 (+1.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 71 → 71 (+0.0)
- Architecture 63 → 53 (-9.3)
- Maturity 49 → 55 (+6.1)
- Readiness 23 → 28 (+4.4)
- Security 63 → 62 (-0.6)
- Accessibility 56 → 48 (-7.7)
- Performance 66 → 72 (+5.8)
Resolved (51)
- ADR has no Decision and Consequences section (docs/REVIEW_STATUS.md)
- Disclosure policy has no reporting contact
- Duplicate interface definition. Both Infrastructure.Contracts.Pizzas.V1.IPizzaDataAccess and DataAccess.Contracts.Pizzas.V1.IPizzaDataAccess have identical method signatures and names. This creates ambiguity about which interface should be consumed.
- 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] (backend/Node/package-lock.json)
- Inconsistent naming for the same database column concept ('Name'). Some fields use 'Table.Name' while others use 'Columns.Name'. While 'Table' and 'Columns' might refer to different scopes (table-level vs column-level metadata), the parallel structure suggests 'Columns.Name' is the standard for column definitions, making 'Table.Name' potentially confusing or inconsistent if they refer to the same underlying DB column name.
- Inconsistent naming style for client methods. 'Search_for_pizzas' and 'Update_pizza' use snake_case with underscores, whereas the rest of the codebase (e.g., 'CreateAsync', 'DeleteAsync', 'GetAllPizzasQuery') uses PascalCase. This breaks the naming convention for public API methods.
- Inconsistent return types for Search within the same root namespace (DataAccess.Contracts). One uses ListResult<PizzaModel> and the other uses Result<IEnumerable<PizzaModel>>. This forces consumers to handle different result wrappers for the same logical operation.
- Low CVE: [GHSA redacted] (backend/Node/package-lock.json)
- Low CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
- Medium CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
- Medium CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
- Medium CVE: [GHSA redacted] (backend/Java/pom.xml)
- Medium CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
- Three different interfaces named IPizzaDataAccess exist across different namespaces. Two share the same namespace path structure (DataAccess.Contracts.Pizzas.V1 vs Infrastructure.Contracts.Pizzas.V1) and identical signatures, suggesting duplication. The third (DataAccess.Contracts.V1) has a different signature (Result<IEnumerable<PizzaModel>> vs ListResult<PizzaModel>), indicating inconsistent return types for the same operation.
- Vulnerable: OpenTelemetry.Api
- Vulnerable: OpenTelemetry.Exporter.OpenTelemetryProtocol
- …and 31 more
New (71)
- Critical CVE: [GHSA redacted] (frontend/React/package-lock.json)
- Critical CVE: [GHSA redacted] (frontend/React/package-lock.json)
- Critical CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
- Disclosure policy has no reporting contact (SECURITY.md)
- 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/React/package-lock.json)
- High CVE: [GHSA redacted] (frontend/React/package-lock.json)
- High CVE: [GHSA redacted] (frontend/React/package-lock.json)
- 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/React/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/React/package-lock.json)
- High CVE: [GHSA redacted] (frontend/React/package-lock.json)
- High CVE: [GHSA redacted] (frontend/Angular/package-lock.json)
- …and 51 more
Architecture
- Unchanged — 5 containers · 2 contexts · 0 edges
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
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.
About this page
- The score is its most recent published measurement, taken on 8 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit cb2c49708f1c740fd18b8974a59c1f7da7b3ee49 — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-45ab2cab63de.