This repository is an official Nx example showcasing a micro-frontend architecture with two frontends: an Angular application for product browsing and a React application for a shopping cart, backed by a .NET minimal API. The code demonstrates cross-framework component reuse via custom elements (Web Components), multi-framework state management (NgRx for Angular, useReducer/Context for React), and Nx's monorepo capabilities including code generation, dependency graph, and CI/CD integration. Data is entirely static, with the .NET API used only for OpenAPI codegen; there is no runtime API consumption. The architecture is clean and modular, emphasizing Nx best practices for large monorepos.
Ng-Matero Extensions is an Angular component library that extends Angular Material with 15+ additional UI components including grid, datetimepicker, colorpicker, popover, tooltip, select, split, dialog, drawer, loader, progress, alert, button loading, checkbox-group, and photoviewer. The library is built for Angular 22 and supports both Material Design 2 and 3 theming via Sass mixins and CSS custom properties. It provides date adapters for native, moment, luxon, and date-fns libraries. The repository includes a development app for interactive demos and a documentation site with live examples, API references, and i18n support (English and Chinese). The codebase demonstrates strong engineering practices with standalone components, CDK overlay usage, adapter patterns, and performance optimizations like coalesced style scheduling. However, it relies on several third-party dependencies (ng-select, color-picker, photoviewer) and uses some deprecated Angular Material APIs, indicating moderate maintenance risk.
Docgeni is a documentation generator for Angular component libraries and markdown documentation. It operates as a CLI tool (serve, build, init) and a set of libraries that parse Angular component metadata, build navigation, render markdown with custom extensions (embed, code groups, tabs), and generate a static or server-side rendered Angular site. The architecture is a monorepo with packages: @docgeni/cli (entry point), @docgeni/core (orchestration, builders, plugins), @docgeni/template (Angular site components and services), @docgeni/ngdoc (TypeScript parser for Angular decorators), @docgeni/toolkit (utilities for file system, git, templates), and @docgeni/create-docgeni (scaffolding). Key data flows: user provides markdown docs and Angular component libraries; the core builders parse docs, extract component metadata via ngdoc, generate navigation trees, and produce an Angular application with live examples, API tables, and multi-language support. External dependencies include Angular CLI, TypeScript compiler API, marked (markdown parser), Prism (syntax highlighting), Handlebars (templates), cosmiconfig (configuration), and chokidar (file watching). The generated site supports CSR, SSR, and SSG render modes, theming, and i18n.
This repository is an opinionated Angular style guide by John Papa, primarily targeting AngularJS (1.x). It is not a runnable application but a comprehensive documentation resource prescribing coding conventions, architecture patterns (LIFT, modularity, folder-by-feature), and best practices for building Angular 1 applications. The repo contains the full guide in English and 12+ community-translated versions, along with editor snippets for various IDEs. While no executable code exists, the guide itself serves as a reference for legacy Angular projects and continues to receive maintenance (last commit 2026-04-30). The companion guide for Angular 2+ is largely a stub pointing to official documentation.
FUXA is a full-stack web-based SCADA/HMI builder and runtime for industrial automation and IoT. It provides a visual editor (Angular + SVG) to create real-time dashboards, connect to field devices via 13+ protocols (Modbus, OPC UA, BACnet, Siemens S7, MQTT, etc.), and manage alarms, data acquisition (DAQ), scripting, scheduling, and user permissions. The backend (Node.js/Express) communicates with the frontend via Socket.IO for real-time device value updates. The system supports multiple time-series databases (SQLite, InfluxDB, QuestDB, TDengine) and can be deployed as a web server, Docker container, or Electron desktop app. It also integrates with Node-RED for low-code automation flows. The architecture is modular with a device driver factory pattern, JWT-based authentication, and a plugin system for extensibility. While the codebase is large and contains some monolithic components, it demonstrates solid engineering practices and has a rich set of reusable UI components and utility patterns.
This monorepo houses the entire Start9 ecosystem, centered on StartOS—a self-hosted Linux distribution for personal servers. The repository encompasses multiple products: StartOS (server OS with container orchestration, backup, networking, and marketplace), StartWRT (router firmware based on OpenWrt), StartTunnel (WireGuard-based tunnel service), StartCLI (command-line tool), StartRegistry (package registry), and StartSDK (TypeScript SDK for building service packages). The architecture is a hybrid of Rust backend services (using async Tokio, axum, and a custom RPC toolkit) and Angular frontends (using Taiga UI and a reactive PatchDB state store). Key orchestration is handled by the container runtime (Node.js with LXC) and a custom diff-based database (PatchDB) for real-time UI synchronization. The system manages service lifecycle, ACME certificates, DNS, port forwarding, VPNs, encrypted backups, and firmware updates. External dependencies include Linux kernel features (LXC, btrfs, eCryptFS, FUSE, nftables), WireGuard, and standard Rust/Angular libraries. The codebase is actively maintained with frequent version migrations and CI/CD pipelines, but carries some duplication across products and technical debt from rapid evolution.
This repository is a thin Node.js library that acts as a Protractor custom framework adapter, bridging Protractor and Cucumber.js. It relies on Serenity/JS to integrate testing across multiple Cucumber versions (1.x through 12.x) and Protractor 5/7. The core logic is in `index.js`, which delegates to `@serenity-js/protractor`'s `ProtractorFrameworkAdapter`. The `package.json` lists `@serenity-js/core`, `@serenity-js/cucumber`, and `@serenity-js/protractor` as runtime dependencies, with `cucumber` and `@cucumber/cucumber` as optional peer dependencies. The codebase is well-structured, with a comprehensive test suite that exercises every supported Cucumber version via a custom `multidep` test runner. The project is actively maintained (last commit 2026-05-13) and follows semantic release. However, it is a thin wrapper with limited standalone reusability outside of the Protractor–Cucumber ecosystem. The primary value is in providing backward compatibility and a unified interface for multiple Cucumber generations.
Nebular is a comprehensive Angular UI component library developed by Akveo. It provides over 40 reusable components (buttons, cards, tables, calendars, dialogs, etc.), a powerful theming engine with four built-in themes (default, dark, cosmic, corporate), and optional modules for authentication (password, OAuth2, Firebase) and role-based security. The repository is structured as a monorepo with multiple npm packages (@nebular/theme, @nebular/auth, @nebular/security, etc.), each with its own build configuration and tests. The library follows consistent patterns: all components use Angular's NgModule system, implement ControlValueAccessor for form integration, and leverage a custom overlay system built on Angular CDK for popups, tooltips, and modals. The codebase is well-organized with extensive unit tests and e2e tests, but shows signs of maintenance drift: the README explicitly states minimal active development (only Angular version bumps), many components still use deprecated Angular patterns (standalone: false, static ViewChild), and e2e tests rely on Protractor (deprecated). Despite this, the library remains functional and widely used, with a large set of documented examples and a dedicated documentation site.
NG-ALAIN is an enterprise-level Angular admin frontend scaffold built on NG-ZORRO Ant Design and the @delon ecosystem. It provides a complete, production-ready architecture with lazy-loaded routing, authentication (JWT), role-based access control (ACL), internationalization (i18n) for multiple languages, theme customization (dark/compact), and a comprehensive set of pre-built pages (dashboards, forms, lists, profiles, settings, etc.). The system uses HTTP interceptors for token refresh and error handling, and includes mock data patterns for development. It is designed as a starting point for enterprise applications, offering reusable layouts, shared modules, and utilities. The codebase is modern, using Angular 21+ standalone components with zoneless change detection, and follows strict coding conventions with ESLint and stylelint. While the primary value is the scaffold itself, several core patterns (HTTP interceptor, startup initializer, mock data architecture) are well-crafted and reusable in other Angular projects.
This repository is a full-stack marketing demo application powered by Google Cloud generative AI (Vertex AI Gemini, Imagen). It provides an end-to-end workflow for generating campaign content (emails, social media posts, website copy, images), analyzing audiences via natural language to BigQuery, and managing assets across platforms. The frontend is a modern Angular 17 single-page application with Firebase authentication and hosting, while the backend is a FastAPI Python service deployed on Cloud Run. Terraform infrastructure-as-code provisions all GCP resources including BigQuery datasets, Vertex AI Search datastores, Dialogflow CX agents, and Google Drive folder templates for content export. The application showcases marketing use cases like trendspotting via GDELT news summarization, audience insights using structured and unstructured data, and interactive image editing with inpainting/outpainting. While primarily a demo application, the repository also contains several Jupyter notebooks exploring model tuning, text-to-SQL, and clustering explanations, making it a hybrid resource for both application developers and data scientists.
ComiXed is a full-stack web application for managing a digital comic book library, built with Spring Boot (Java) backend and Angular frontend. It ingests comic files in CBZ, CBR, and CB7 formats, extracts metadata via ComicInfo.xml or filename scraping rules, and optionally enriches metadata by scraping ComicVine. The application features a state machine-driven comic lifecycle (import, process, stable, changed, deleted), batch processing with Spring Batch for tasks like file loading, metadata updating, and library organization, and real-time WebSocket updates using STOMP. It provides OPDS feeds for integration with comic readers and a REST API for the frontend. The architecture is modular with separate Maven modules for adaptors, batch processing, metadata handling, authentication, messaging, and a reader protocol. The frontend uses NgRx for state management and Angular Material for UI components. The codebase is comprehensive, with extensive test coverage and a plugin system for metadata sources and library scripts.
This is the Builder.io monorepo, a comprehensive headless CMS and visual page builder platform. It provides multi-framework SDKs (React, Angular, Vue, Svelte, Qwik, Solid, React Native, etc.) for fetching and rendering Builder.io content, a plugin ecosystem for extending the visual editor with custom components and data sources (commerce, CMS, media), CLI tools for project scaffolding and space management, and numerous example applications. The core SDK uses Mitosis for code generation to produce framework-specific implementations, and includes features like A/B testing, personalization, localization, visual editing, and server-side rendering. The repository also contains a Gatsby source plugin, a plugin loader, and integration plugins for Shopify, Contentful, Cloudinary, and others. While the codebase is large and actively maintained, it exhibits some technical drift with legacy Gen1 SDKs, duplicated configurations, and outdated dependencies in examples.
MaxKey is an enterprise-grade Identity and Access Management (IAM) / Single Sign-On (SSO) platform written in Java (Spring Boot) with Angular frontends. It supports a comprehensive set of authentication protocols (OAuth 2.0/OpenID Connect, SAML 2.0, CAS, JWT, form-based, token-based) and identity federation standards (SCIM 2.0, LDAP, Active Directory). The codebase is organized as a multi-module Maven project with clear separation between authentication providers, protocol implementations, persistence layer, and web UIs. Architecturally, it follows a service-oriented model with a custom OAuth2 stack (derived from Spring Security OAuth), MyBatis JPA for persistence, and Redis/Caffeine for caching. The frontends are built on NG-ALAIN (Angular 17) and share a common base for user portal and admin console. While the system is functionally rich and actively maintained, it contains some duplicated code across modules and relies on a legacy OAuth2 implementation that has been superseded by Spring Security 5+. The crypto utilities, OTP infrastructure, and adapter patterns are well-structured and demonstrate non-obvious craftsmanship.
iKy (I Know You) is a modular OSINT (Open Source Intelligence) aggregation platform built with FastAPI, Celery, Redis, and an Angular frontend. The system ingests a username or email and concurrently executes 26+ parallel tasks across social media, data breaches, search engines, and dark web sources, returning a structured JSON contract (module, param, validation, raw, graphic, profile, timeline, tasks) consumed by a visual graph/timeline UI. Key architectural patterns include a dynamic module registry that maps route names to Celery task paths, a decorator-based task wrapper (@iky_task) that centralizes dev-mode golden-file bypass, error classification, and performance logging, and a pluggable search provider orchestration layer. The codebase demonstrates a strong separation of concerns between API routing, task execution, and data enrichment, but suffers from fragile scraping logic (LinkedIn RSC parsing, TikTok SSR regex), heavy reliance on browser session cookies, and several deprecated external APIs (Twitter v1.1, FullContact). The project is actively maintained with an extensive test suite (~4K lines) and Docker Compose deployment, though many tests are heavily mocked and may not detect real API drift.
This repository contains shinpuru, a production-grade Discord bot written in Go with a React/TypeScript web dashboard. It serves as a comprehensive guild management and moderation platform, handling reports, kicks, bans, mutes, and community engagement features like karma, starboard, votes, and code execution. The backend is a monolith using the discordgo library for Discord interactions, Fiber for its REST API, and sarulabs/di for dependency injection, backed by MySQL, Redis, and MinIO. The architecture is well-structured with clear separation of concerns. The internal/ directory houses services (database, storage, permissions, karma, reports), event listeners, slash commands, and middleware. The pkg/ directory is a standout collection of over 30 reusable utility packages, covering areas like rate limiting (limiter), one-time authentication (onetimeauth), Discord embed building (embedbuilder), fuzzy object resolution (fetch), and permission management (permissions). These packages are largely self-contained and could be extracted for use in other Go projects. The frontend is a modern React SPA with i18n support (English and German), a typed API client (shinpuru-ts), and a comprehensive set of components for managing every aspect of the bot. The project demonstrates strong engineering practices with CI/CD pipelines, Docker support, and a clear contribution model. While the codebase is large and shows some signs of technical drift (legacy package versions, some raw SQL patterns, duplicated package versions), the core architecture and reusable packages make it a valuable reference for building complex Discord bots or Go web applications.
ng2-file-upload is an Angular library providing drag-and-drop and file selection directives for file upload. It consists of two directives (ng2FileSelect and ng2FileDrop) and a core FileUploader class that manages a queue of FileItems, handles XHR uploads with multipart or streaming (disableMultipart), and offers filter-based validation (file size, mime type, file type, queue limit). The demo application showcases standard usage with a remote API. The library is actively maintained with support for Angular 21, but its code style predates modern standalone components and uses legacy Angular patterns (non-standalone directives, manual DI via inject()). Tooling uses Nx 22, Jest, and ng-packagr. While functional and battle-tested (1899 stars), the codebase shows medium technical drift due to reliance on deprecated Angular patterns and a monolithic FileUploader class.
This repository is the web-based user interface for the Google Agent Development Kit (ADK). It functions as a comprehensive IDE and debugging console for building, running, and evaluating AI agents. The application is built on Angular (v21.0.0) using Standalone Components and Signals, serving as a client to a backend agent runtime. Key capabilities include a visual workflow builder for agent graphs, real-time chat interfaces supporting text/audio/video streaming, OpenTelemetry trace ingestion and visualization, and a structured evaluation framework for agent performance metrics. It acts as the control plane for agent execution, handling configuration via YAML and managing session state through WebSocket and HTTP communication.
The 21-Points Health application is a full-stack health tracking system built with a Spring Boot backend and an Angular frontend. It allows users to register, log in, and track various health metrics including weight, blood pressure, and activity points (from exercises, meals, and alcohol). Users can set personal preferences such as weekly goals and weight units (kg/lb). The application provides data visualization through lists, calendars, and charts, and includes administrative features for user management. The architecture follows a standard monolithic pattern with a clear separation of concerns. The backend exposes a RESTful API secured with JWT authentication, uses Spring Data JPA for persistence with a PostgreSQL database (H2 for development), and integrates Elasticsearch for search capabilities. The frontend is a modular Angular application that consumes the API, implements reactive state management with RxJS, and uses Bootstrap for responsive styling. The application also includes internationalization (English and French), Docker Compose configurations for development dependencies, and monitoring setups with Prometheus and Grafana. While the application leverages the JHipster generator for much of its boilerplate, it contains several custom components that demonstrate good engineering practices. Notable among these are a custom Logback converter for handling multi-line log messages, a utility service for file operations (base64 encoding and blob downloading), and a pipe for formatting time durations. These components are relatively isolated and could be reused in other projects with minimal modification.
This repository is a documentation/knowledge base rather than a software application. Its sole content asset is a single comprehensive README.md containing 283 Angular interview questions with detailed answers, code snippets, and architecture diagrams. Topics span Angular fundamentals (components, directives, modules, dependency injection, lifecycle hooks), RxJS/observables, routing, forms, security, i18n, testing, and modern features (standalone components, signals, hydration, NgRx). The only automation is a GitHub Actions workflow that converts README.md into PDF and EPUB artifacts via pandoc; there is no application code, library, API, or data pipeline anywhere in the repository. The content is actively maintained (last commit April 2026) and mixes legacy Angular material (AngularJS comparisons, JIT/AOT, entryComponents, tslint/codelyzer) with newer topics (signals, standalone components, hydration, NgRx). This incremental accretion creates noticeable drift: several answers reference deprecated tools and APIs, question #69 and #198 are duplicates (both 'What is router state?'), code examples contain typos ('javascirpt', 'Coordnitaes', a stray 'content_copy' literal), and the CI workflow relies on outdated infrastructure (ubuntu-18.04, actions/checkout@v2, upload-artifact@master). Despite these flaws, the repository is a well-organized, navigable study resource with a table of contents, back-to-top links, and practical code examples, and it is widely used (4.9k stars, 2.2k forks).
This is a full-stack web application starter kit combining Angular (frontend) and Spring Boot (backend) with JWT-based authentication. The system provides user registration, login, role-based access control (USER/ADMIN), and protected API endpoints. The frontend communicates with the backend via RESTful APIs, with authentication handled through JWT tokens stored in cookies. The architecture follows a standard client-server pattern with clear separation of concerns: Angular handles UI presentation and user interactions, while Spring Boot manages business logic, data persistence, and security. Key features include route guards for client-side protection, custom JWT filters for server-side authentication, and centralized service layers for API communication.