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 is a modern Next.js 16 starter template using the App Router, designed to jumpstart full-stack web applications. It provides a production-ready monolith with authentication via NextAuth (GitHub provider), payment processing through Stripe subscriptions, and a PostgreSQL database layer using Drizzle ORM and Neon serverless. The application includes internationalization (i18n) with next-intl, dark mode theming, custom fonts, and standard SEO features like sitemap and robots.txt. The codebase demonstrates disciplined engineering with TypeScript, Zod environment validation, Biome linting, Husky git hooks, and both unit (Jest) and end-to-end (Playwright) testing. While functionally complete and well-structured, it is fundamentally a starter kit composed of framework boilerplate and standard integrations, without innovative or deeply reusable custom abstractions beyond what is typical for such templates.
This repository implements a RESTful API for a simple todo application with user authentication, built using NestJS, Passport, TypeORM, and PostgreSQL. It provides registration and login (local strategy with JWT), session management via cookies, and CRUD operations for todos and user profiles. The architecture is a monolithic NestJS application with clearly separated modules (Auth, Todo, User) and uses standard patterns such as guards, interceptors, pipes, and filters. The codebase is well-tested with unit and end-to-end tests, includes stress testing with k6, and follows modern TypeScript practices with decorators and dependency injection. It serves as a practical example of integrating Passport authentication (local and JWT strategies) with NestJS and TypeORM, including custom validators, pagination interceptors, and ownership checks.
This repository provides a Pluggable Authentication Module (PAM) for two-factor authentication using TOTP (RFC 6238) and HOTP (RFC 4226) one-time passwords. It consists of a PAM shared library (`pam_google_authenticator.so`) that integrates with any PAM-aware service (SSH, login, etc.) to require a verification code in addition to the user's password, and a command-line tool (`google-authenticator`) for generating secret keys and configuring per-user state files. The implementation is written in C using autotools for building, and includes self-contained cryptographic primitives (Base32 encoding, HMAC-SHA1, SHA-1) that are also reused across the PAM module and the CLI tool. The code is well-structured, with careful attention to security (explicit memory zeroing, file permission checks, rate limiting, and reuse prevention). While the build system and CI (Travis CI) are somewhat dated, the core functionality is mature and actively maintained.
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.
axum-login is a Rust library providing user identification, authentication, and authorization as tower middleware for Axum web applications. It enables pluggable authentication backends through well-designed traits (AuthUser, AuthnBackend, AuthzBackend) and offers flexible route protection via both macro-based and builder-based middleware APIs. The library uses tower-sessions for secure session management and includes features like session fixation mitigation and constant-time password verification. Examples demonstrate usage with various backends including SQLite, OAuth2, and permission-based systems.
This is a production-oriented full-stack SaaS starter kit (not a data/research project). It is a monorepo template pairing a Next.js web app (landing page, auth flow, account dashboard, marketing sections) with a Flutter cross-platform app (iOS/Android/macOS/Windows/Linux/web) on top of a shared Supabase backend. The backend is a Postgres schema (users, customers, products, prices, subscriptions, invoices) protected by row-level security, plus Deno edge functions that orchestrate Stripe Checkout sessions and process Stripe webhooks. PostHog handles analytics on both frontends, Loops.so handles transactional email, and an optional Monero cryptocurrency payment variant can be toggled in via patch scripts, giving the template two billing backends.
This is a large TypeScript monorepo for Sourceloop, a LoopBack 4-based microservices platform for building multi-tenant enterprise SaaS applications. It contains 14+ pre-built microservices covering authentication, audit, notification, chat, scheduler, payment, survey, search, video-conferencing, BPMN/workflow, task management, reporting, feature toggles, OIDC, and user-tenant management. Each service is packaged as a pluggable LoopBack component with controllers, models, repositories, providers, and database migrations for both PostgreSQL and MySQL. The repo also includes reusable cross-cutting packages for caching, observability, file uploads, feature flags, and a CLI for scaffolding new microservices and UI projects, plus many sandbox example applications demonstrating real-world integrations.
This repository is the `express-jwt` npm package, a widely-used Express.js middleware for validating JSON Web Tokens (JWTs). The core function `expressjwt(options)` returns a middleware that extracts the JWT from the request (defaulting to the Authorization Bearer header), decodes it, verifies its signature using a provided secret or async callback, checks standard claims like audience and issuer, and optionally checks token revocation. The decoded payload is attached to `req.auth`. The middleware supports CORS preflight handling and integrates with `express-unless` for conditional skipping. It is a focused, well-structured library with clean TypeScript types and a simple architecture. The code is actively maintained by Auth0 with automated CI/CD for releases and testing across multiple Node.js versions. The primary reusable component is a generic deep property setter utility.
This repository is a Payload CMS authentication plugin (payload-auth-plugin) that provides OAuth2, OIDC, password, and passkey authentication strategies. It is designed to be used with Payload CMS v3+ and integrates deeply with Payload's admin panel and frontend via custom API endpoints, collection field injection, and a client-side library. The plugin supports multiple providers (Google, GitHub, Apple, etc.) via a clean provider factory pattern and manages its own session cookies, credential hashing (PBKDF2), and account linking. The architecture is a plugin that hooks into Payload's lifecycle, extending the CMS with authentication endpoints and database collections. The example application (examples/with-website/) demonstrates a full Payload CMS + Next.js website with admin and public authentication flows. Despite being pre-1.0, the codebase exhibits solid engineering patterns: strategy pattern for endpoint registration, collection helper functions that merge user-defined configs, and a reusable AuthClient class for browser-side authentication. However, it lacks automated tests, has several FIXME comments in passkey and password protocols, and is tightly coupled to Payload's internal DB and cookie mechanisms, which introduces technical drift risk as Payload evolves. The plugin is actively maintained with frequent releases and a changelog documenting 50+ versions.
This is a SvelteKit application demonstrating authentication using Auth.js. It provides sign-in with multiple providers (Google, GitHub, etc.) and protects a route requiring authentication. The application consists of standard SvelteKit routes, components for UI (header, footer, sign-in button), and centralized authentication configuration in auth.ts. The session is managed via cookies and made available to all pages through a layout load function. The code follows SvelteKit conventions and uses Auth.js's SvelteKit adapter for authentication handling.
GoAuthing is a command-line authentication tool for Tsinghua University's network (TUNET). It provides login, logout, and keep-alive functionality for both IPv4 and IPv6 connections. The application features a clean separation between the CLI interface (built with urfave/cli) and the core authentication logic (in the libauth package). It handles credential input via prompts or config files, communicates with the authentication server using custom encryption and encoding schemes, and can run as a daemon via systemd or init.d scripts. The project is actively maintained with regular releases and CI/CD pipelines for multi-platform builds.
httpc is a TypeScript framework for building function-based APIs with end-to-end type safety. It abstracts HTTP into typed function calls, providing a server with a middleware pipeline (parsers, rewriters, renderers), a typed client generator that produces proxy-based clients with full autocompletion, a CLI for scaffolding projects and generating clients, and a comprehensive kit (authentication, caching, validation, dependency injection, event bus, permissions, logging, email, geo). The architecture is a monorepo with packages: server, client, kit, cli, and adapters for Vercel, Netlify, and Cloudflare. Key entry points include `createHttpCServer` (server), `createClient` (client), and CLI commands (`create`, `client`, `call`). Data flows: HTTP request → parser → middleware pipeline → call execution → renderer → response. External dependencies include tsyringe, zod, valibot, winston, lru-cache, redis, maxmind, and jws. The framework is experimental (v0.1.0) but demonstrates strong engineering practices with clean abstractions and reusable patterns.
volc-sdk-python is the official Volcengine SDK for Python, a programmatic client library for Volcengine cloud services. It is not a standalone application: it exposes service classes that wrap REST APIs and protobuf-defined services. The dominant architecture is a base Service class that handles credential resolution (AK/SK, environment variables, ~/.volc/config), request signing, and HTTP dispatch, while each service defines an api_info mapping from action names to HTTP method/path/query. Some services (TLS, Live) use protobuf-generated models; others use legacy ApiInfo-style raw dicts, creating inconsistent implementation styles across the SDK.
This is a monorepo containing starter templates and final code for the official Next.js Learn courses. It includes multiple independent Next.js applications demonstrating the Pages Router, App Router, data fetching, authentication, SEO optimization, and more. The code is educational, well-structured, and follows modern Next.js patterns (server actions, streaming, suspense, etc.). It is not a production application but serves as a reference implementation for learning. The dashboard example includes a full CRUD invoice management system with PostgreSQL, NextAuth authentication, and Tailwind CSS styling. The basics examples cover static generation, dynamic routes, API routes, and TypeScript. The SEO example demonstrates performance optimization techniques like dynamic imports and lazy loading.
Pingvin Share is a self-hosted file sharing platform designed as an alternative to services like WeTransfer. It provides a full-stack application with a NestJS backend and a Next.js frontend, featuring user authentication (local, OAuth2, TOTP, LDAP), file uploads with chunked transfers, password-protected and expiring shares, reverse shares for receiving files, an administrative panel for managing users and system configuration, and support for multiple storage backends (local filesystem or S3). The application includes virus scanning via ClamAV, email notifications, and extensive internationalization. The backend employs a modular architecture with distinct modules for authentication, user management, share handling, file storage, configuration, and scheduled jobs. Key reusable patterns include an abstracted file storage service (supporting local and S3 providers), a strategy-based OAuth provider interface, and a dynamic configuration service that loads settings from the database with optional YAML file overrides and runtime update notifications. The frontend presents a polished user interface with custom hooks for configuration and user state, reusable input components for timespans and file sizes, and a sophisticated chunked file upload UI with progress tracking and error recovery. Although the original repository has been archived (as of June 2025) with a recommendation to use a maintained fork, the codebase demonstrates solid engineering practices, clear separation of concerns, and several reusable components that could be adapted for similar projects. The Dockerized deployment and comprehensive feature set make it a viable self-hosted solution for file sharing needs.
This repository implements an Apple Home Key Reader application that enables NFC-based authentication for Apple HomeKit smart locks. The system acts as a bridge between NFC-enabled devices (iPhones/Apple Watches with Home Keys) and HomeKit accessory control, allowing users to unlock locks by tapping their devices on an NFC reader. The architecture follows a modular design with clear separation: main.py coordinates initialization, accessory.py handles HomeKit Accessory Protocol interfaces, service.py implements core NFC authentication logic, homekey.py manages Apple-specific NFC protocols, and repository.py handles persistent state management. The application relies on external dependencies including pyhap for HomeKit, nfcpy for NFC communication, and cryptography for security operations.
This is a large collection of over 1000 sample projects and templates for developing Microsoft Office Add-ins (Excel, Word, Outlook, PowerPoint, OneNote). The repository demonstrates a wide range of features: task panes, custom functions, authentication/SSO (MSAL, nested app auth, OAuth), Microsoft Graph integration, Blazor WebAssembly add-ins, shared runtime, event-based activation for Outlook, ribbon customization, keyboard shortcuts, offline storage, and legacy VSTO/COM samples. The codebase spans multiple technology stacks including JavaScript/TypeScript with webpack, ASP.NET Core MVC, Node.js, and Blazor. While many samples are functional and serve as good learning resources, the repository suffers from massive duplication of localization files (outlook_strings.js in dozens of languages) and outdated dependencies (jQuery 1.9.1, AngularJS, VSTO). The overall code quality is typical of sample collections – functional but not production-grade – with isolated reusable patterns for authentication and Graph API interaction.
This is a fully-featured OAuth2 and OpenID Connect authentication and authorization server built with Node.js/TypeScript and the Curveball framework. It provides user management, role-based access control, multi-factor authentication (TOTP, WebAuthn), and an administrative web UI. The project is self-contained with its own database migrations, CLI binary, and Docker support. It supports multiple database backends (PostgreSQL, MySQL, SQLite) via Knex. The codebase is well-structured following a modular architecture with clear separation between controllers, services, and format handlers. It implements the OAuth2 authorization framework including authorization code, client credentials, implicit, and refresh token grants with PKCE support. The OpenID Connect layer provides discovery, JWKS, and userinfo endpoints. Authentication is modular with pluggable challenge strategies for passwords, TOTP, email OTP, and WebAuthn. The project is retired, as explicitly stated in the README, and the authors recommend migrating to Keycloak. Despite being deprecated, the code remains a solid reference implementation for OAuth2/OIDC in Node.js and contains several reusable components including an abstract key-value store, an SMS adapter pattern, and cryptographic utilities.
This repository is a Node.js library implementing an OpenID 1.0/1.1/2.0 Relying Party (client). It enables Node.js applications to authenticate users via OpenID providers by handling discovery, association, authentication, and assertion verification. The library is modular, with separate modules for HTTP requests, XRDS parsing, and extension handling (Supporting SREG, AX, OAuth, UI, and PAPE extensions). It uses a callback-based asynchronous style and provides default in-memory storage for associations and discovered information, which can be overridden for persistent storage. The codebase shows signs of age but remains functional, with a test suite that includes integration tests against real OpenID providers.