Your_Spotify is a self-hosted web application that tracks your Spotify listening history and provides a rich dashboard for exploring statistics. It consists of a React frontend (with Redux, MUI, Recharts) and an Express backend (with MongoDB, Mongoose, JWT auth). The system polls Spotify's recently played endpoint every two minutes and also supports importing historical data from Spotify's privacy exports. Users can view top songs, artists, albums, listening time breakdowns, collaborative affinity between users, and create Spotify playlists from their stats. The architecture is a monorepo with two main apps (client and server) deployed via Docker. The codebase is well-structured with clear separation of concerns, reusable UI components, and custom server-side patterns like a queued HTTP client and a write lock mechanism. However, there are no visible tests, and some aggregation pipelines are complex.
Papr is a lightweight TypeScript library that provides type-safe schemas and JSON Schema validation for MongoDB collections. It wraps the official MongoDB Node.js driver, offering a familiar API (find, insertOne, updateOne, etc.) while automatically generating JSON Schema validators that are applied to MongoDB collections via `collMod` or `createCollection`. The library supports a wide range of BSON types, timestamps, defaults (static, dynamic, async), hooks (before/after), and custom filter types for enhanced type safety in queries and updates. It is designed as a thin, performant alternative to Mongoose, offloading validation to the MongoDB server. The codebase is well-structured with modular source files, extensive unit and type tests, benchmarks comparing performance against raw MongoDB driver and Mongoose, and comprehensive documentation. It is actively maintained with CI/CD pipelines, automated releases, and dependency management via Renovate.
ApostropheCMS is a full-stack content management system built with Node.js, MongoDB, and Vue.js. It provides a modular architecture with extendable content types (pages, pieces, widgets), a rich admin UI with in-context editing, headless API support via Astro integration, and extensive internationalization and permission systems. The monorepo contains the core CMS package, CLI tools, database adapters, file storage abstraction, AI content generation helpers, import/export utilities, and many first-party modules for SEO, forms, events, and more. The codebase is large and well-tested, with a strong emphasis on security (prototype pollution guards, permission regression tests) and developer experience (scaffolding, OpenAPI generation). However, it shows signs of technical drift in some legacy packages and a complex build pipeline.
Commonly is an open-source multi-agent collaboration platform where humans and AI agents work together in shared workspaces called 'pods'. The system provides real-time messaging, task management, agent runtime (native, hosted, or bring-your-own), marketplace for agent skills, and integrations with external chat platforms like Discord, Slack, Telegram, and GroupMe. The architecture is a full-stack monolith with separate external agent bridge services and a Cloudflare Workers-based agent runtime. The backend (Node.js/Express) uses a dual-database design (MongoDB for primary data, PostgreSQL for messages/tasks) with automatic sync. The frontend is a React SPA with a v2 design system. The CLI allows local agents to participate via device-code auth and polling. The MCP server provides standard tools for agents to interact with the platform. The codebase is well-structured with extensive test coverage (unit, integration, E2E), Architecture Decision Records (ADRs), and reusable packages for types, integration SDK, and MCP tools. Notable craftsmanship includes pluggable storage drivers, deterministic agent wake targeting, and a test utility that replicates the production PostgreSQL schema to catch DDL drift.
Meteor is an ultra-simple full-stack JavaScript framework for building modern web and mobile applications. This monorepo contains the Meteor CLI tool (`meteor`), the build system (isobuild, Rspack integration), core runtime packages (reactive data via DDP, MongoDB integration, accounts, Blaze templating, modules, bundling), and a rich ecosystem of OAuth providers, testing infrastructure, and developer tools (ESLint plugin, Babel preset, installer). The codebase is organized as a monorepo with `tools/` for the CLI and build system, `packages/` for framework packages, and `npm-packages/` for standalone npm packages. It demonstrates a real-time data synchronization pattern using DDP (Distributed Data Protocol), a custom constraint solver for package dependency resolution, and a compiler plugin system for transpilation. Despite being a well-established framework with extensive testing, the codebase shows signs of technical drift: deprecated packages remain in-tree, there is a dual sync/async API surface due to ongoing migration from Fibers to async/await, and the build system is transitioning from a legacy compiler to Rspack.
Appsmith is a comprehensive low-code application development platform that enables users to build internal tools, dashboards, and admin panels via a visual editor. The architecture consists of a React/TypeScript frontend (SPA) for the IDE and a Java Spring Boot backend (WebFlux) for business logic and data persistence. It features a robust plugin system for connecting to diverse datasources (SQL, NoSQL, SaaS, AI) and deep Git integration for version control and CI/CD workflows. The system is containerized for deployment and supports both Community and Enterprise editions through feature-flagged code paths.
This is an example application demonstrating how to set up and run a Parse Server instance using Express. It serves as a reference implementation for the Parse Server open-source backend-as-a-service. The codebase includes a minimal Express server that mounts the Parse Server middleware at a configurable path, serves static assets and a test page, and provides health check endpoints. It uses modern ES6 modules, TypeScript, and the latest Parse Server version (9.x). Cloud code functions (hello, beforeSave) and schema definitions are included to illustrate common patterns. The project also includes comprehensive deployment configurations for various platforms (Heroku, AWS, Google Cloud, etc.), Docker support, CI/CD with GitHub Actions, and automated semantic releases. While simple in scope, the code is well-structured, follows current best practices, and includes a test suite with a reusable test runner utility for programmatically starting/stopping the server during integration tests. This repository is best used as a starter template for new Parse Server projects or as a reference for migration to Parse Server 8+.
This repository is the personal blog and knowledge base of digoal, a prominent PostgreSQL DBA and database expert. It contains over a decade of blog posts (2010–2026) covering PostgreSQL internals, performance tuning, database architecture, and related topics, along with a large collection of images, PDFs, and other attachments. The blog is organized by year and month, with each post as a markdown file. The repository also includes a 'skills' directory that defines reusable AI agent skill definitions (SKILL.md files) for various tasks such as fact-checking, stock prediction, bug hunting, and course writing. These skills are structured with agent prompts, reference materials, and supporting scripts, making them extractable and reusable in AI-assisted workflows. The repo is actively maintained and serves as both a reference for database professionals and a library of AI agent capabilities.
Pritunl is a production-grade, distributed VPN server management system that provides a web-based admin interface for configuring and monitoring OpenVPN and WireGuard instances. The Python backend (Flask with MongoDB) handles authentication, organization/user management, certificate generation, IP pool allocation, bandwidth monitoring, and enterprise features like site-to-site network links and SSO (SAML, OAuth, LDAP). It runs as a daemon with multiple background runners for task queues, event processing, and firewall rule management. The legacy frontend uses Backbone.js with a newer Dart/AngularDart component set in transition. The architecture is monolithic but modular, with well-defined subsystems for settings, caching, transactions, and plugins. External dependencies include MongoDB, Redis, InfluxDB, OpenVPN, WireGuard, and various cloud provider APIs. The codebase demonstrates strong engineering practices with clean abstractions (MongoObject ORM, event system, queue system, plugin system) but shows some technical drift in the frontend stack and vendored libraries.
Ackee is a self-hosted, privacy-focused web analytics tool. It tracks page views, durations, referrers, browsers, devices, operating systems, screen sizes, languages, and custom events without using cookies or collecting personally identifiable information. Visitor identity is anonymized via SHA-256 hashing of IP + user agent + domain ID with a daily rotating salt. The architecture is a full-stack Node.js application: an Express server with Apollo Server for GraphQL, a React single-page application frontend (using `createElement` instead of JSX), and MongoDB for persistence. The backend provides a GraphQL API for querying aggregated statistics and managing domains, events, and authentication tokens. The frontend consumes this API via Apollo Client and renders a dashboard with reusable card and presentation components. Key design patterns include a `pipe` utility for chaining resolver middleware (auth, demo mode blocking), modular MongoDB aggregation stages stored in `src/stages/`, and a custom build pipeline using Rosid handlers. The application supports multiple deployment targets: Docker, Heroku, Vercel, Netlify, and manual Node.js processes.
FreeAPI is an open-source API hub that provides free REST APIs for learning and demonstration purposes. The backend is a monolithic Express.js application with MongoDB, offering a range of endpoints: static public data (cats, dogs, quotes, etc.), kitchen-sink features (HTTP methods, status codes, cookies, redirects), and full-featured CRUD applications (ecommerce, social media, chat, todo) with authentication (JWT, OAuth via Google/GitHub), real-time chat via Socket.IO, file uploads, email notifications, and payment integration (Razorpay, PayPal). The codebase is well-structured with reusable utilities (asyncHandler, ApiError, pagination helpers), modular validators, and seeding scripts. It also includes multiple React/Vite frontend examples (ecommerce with Redux, chat with Socket.IO, todo app, status code quiz) that demonstrate best practices in consuming APIs. The project is clearly a learning resource and demo platform, not a production service.
Coral is an open-source, multi-tenant comment moderation platform developed by Vox Media. It provides a full-stack application with embedded commenting widgets (stream), a comprehensive admin panel for moderation, configuration, and community management, an authentication system supporting local, OAuth2/OIDC, Google, Facebook, SSO, and account management pages. The system architecture consists of a Node.js/Express server with Apollo GraphQL, MongoDB for persistence, Redis for caching and pub/sub, and Bull for job queues. The client uses React with Relay for GraphQL data fetching, and is organized into several bundles: stream (the embeddable comment widget), admin, auth, account, install, count, and embed. The core data flow involves comments being submitted via GraphQL mutations, processed through a modular pipeline (spam detection, word list filtering, toxicity analysis via Perspective API, external moderation phases, and pre-moderation rules), stored in MongoDB, and then distributed via GraphQL subscriptions and notifications (email, Slack, webhooks). The codebase is extensive and well-tested, though it exhibits some legacy patterns (recompose HOCs, partial migration from class components to hooks, duplicated utility code between client and server scripts).
buji-pac4j is a bridge library that integrates pac4j (a comprehensive security library supporting OAuth, CAS, SAML, OpenID Connect, etc.) with Apache Shiro. It automatically pushes pac4j authentication and authorization profiles into the Shiro security context, allowing developers to use pac4j's wide range of authentication mechanisms while leveraging Shiro for authorization and session management. The bridge is implemented as a set of classes that adapt pac4j's session store, profile manager, and framework adapter to Shiro's APIs, plus a custom Realm, SubjectFactory, and Token. It includes sophisticated logic to avoid unnecessary session renewal when the same user's profiles are updated (e.g., after token refresh), demonstrating deep understanding of both frameworks' internals. The library is production-ready, actively maintained, and used in legacy applications that want to adopt pac4j without fully migrating away from Shiro.
This is a comprehensive e-commerce backend platform built with Spring Boot 3.5+, JDK 17, and a multi-module Maven architecture. In production, it serves two distinct APIs: `mall-admin` (admin management) and `mall-portal` (customer-facing storefront), plus a dedicated `mall-search` module for Elasticsearch-powered product search. The system handles product cataloging, order lifecycle management, user registration/authentication, coupon and promotion calculations, shopping cart operations, payment integration (Alipay), and content management (home page banners, recommendations). It uses MySQL as the primary database via MyBatis (with generated mappers), Redis for caching and session management, MongoDB for user activity data (browsing history, favorites), RabbitMQ for delayed order cancellation, and MinIO/Aliyun OSS for file storage. Security is implemented with Spring Security and JWT, including dynamic path-based authorization. The codebase follows a layered architecture (Controller → Service → Mapper/DAO) with shared modules `mall-common` and `mall-security` providing reusable utilities for API responses, pagination, exception handling, Redis caching, and authentication. While heavily reliant on MyBatis Generator for data access objects and includes some long service methods, the overall structure is well-organized and modular, making it suitable as a reference for similar e-commerce projects. No data research or analytical components are present; this is purely an application codebase.
Chat2DB is an AI-powered database client and SQL workspace supporting over 40 databases via a plugin architecture. It provides a full-featured SQL editor with syntax highlighting, autocompletion, and execution, along with database metadata browsing, data import/export, BI dashboards, and an AI assistant that can generate SQL, explain queries, and create charts. The system is designed as a hybrid desktop/web application, with a React/TypeScript frontend (using Ant Design, Monaco Editor, Zustand for state management) and a Java Spring Boot backend with a layered domain model. The desktop version uses JCEF (Chromium Embedded Framework) for native integration, while the web version runs as a standalone server. Database support is modular via SPI plugins, each providing metadata, SQL builders, value processors, and completion logic. The architecture is centered around a plugin system where each database type implements interfaces like IPlugin, IDbMetaData, and IDbManager, enabling extensible multi-database support. The frontend uses Zustand stores with slice-based state management, and the backend provides REST APIs for SQL execution, AI chat, and data management. Key entry points include the frontend main page (CommunityMainPage), backend controllers (e.g., DbSqlController, AiChatController), and plugin registration via META-INF/services. Data flows involve SQL execution requests from the editor to the backend, which delegates to the appropriate database plugin and returns results asynchronously with streaming support for AI and large result sets. External dependencies include Java/Spring Boot, React, Monaco Editor, ANTLR for SQL parsing, ECharts for charts, and various JDBC drivers for database connectivity. The system also integrates with AI model APIs (e.g., OpenAI, Claude) via configurable endpoints. The codebase demonstrates a strong separation of concerns through its SPI plugin pattern and state management slices, though it exhibits some duplication across database plugins and has limited test coverage.
Turms is a production-grade, open-source instant messaging engine designed for 100K to 10M concurrent users. The system follows a microservices architecture with two core Java/Spring Boot servers: turms-gateway (handles client connections, authentication, session management, and push) and turms-service (implements business logic for messaging, groups, users, conversations, storage, and admin API). Both servers are built on a reactive stack (Project Reactor, Netty) for non-blocking I/O and high throughput. The platform includes a Vue.js admin UI (turms-admin), multiple client SDKs (JavaScript, Kotlin, Swift, Dart, C++), a Flutter chat demo, and a plugin system for extensibility (anti-spam, push notifications, MinIO storage, Rasa chatbot, LiveKit conferencing). Data is stored in MongoDB (sharded), Redis (session, blocklist, sequence IDs), and optionally Elasticsearch for full-text search. The codebase demonstrates strong engineering practices: custom RPC codecs for cluster communication, a property metadata framework for configuration validation, thread-safe rate limiting, and a well-defined plugin extension point system. While primarily an application, it includes an AI serving module (PaddleOCR) for content moderation, but this is a minor component. The repository is actively maintained with frequent commits, comprehensive CI/CD pipelines, and Terraform deployment scripts.
CloudDM is a database management platform providing unified access to multiple database systems. It features a web-based console interface built with Vue.js and a Java/Spring Boot backend with a plugin architecture for database drivers. The platform combines database querying, management, access control, SQL auditing, CI/CD capabilities, and workflow automation in a single system. The architecture follows a modular, layered design with clear separation between frontend, backend API, service layer, data access layer, and plugin system. Key features include multi-database support (MySQL, PostgreSQL, Oracle, SQL Server, MongoDB, Redis, etc.), SQL parsing and analysis, security rule engine, and extensibility through plugins.
Broadcastarr is a media broadcasting service that scrapes broadcast schedules from websites, processes and stores broadcast information, and publishes notifications to platforms like Discord and Gotify. It integrates with media servers (Jellyfin) to make content available as M3U8 streams. The architecture consists of a monolithic application with separate server (API), worker (background tasks), and bootstrap (initialization) components. It uses Agenda for job scheduling, Mongoose for MongoDB ODM, Puppeteer for web scraping, Express for API server, and Discord.js for bot functionality. The system provides a REST API for monitoring and control, along with Discord slash commands for management.
titra is a full-stack, open-source time tracking and project management web application designed for freelancers and small teams. It is built on Meteor.js 3.x with a monolithic architecture spanning server/client/imports directories, using MongoDB as its primary data store, Blaze templates for the UI, and Rspack for bundling. The application provides core time tracking features (day/week/month calendar views, timeline, timers, bulk entry), project/task management with Gantt charts, dashboards with password-protected sharing and slug URLs, CSV import/export, and rich reporting tables. While primarily an application, it includes significant data-analytics tooling through extensive MongoDB aggregation pipelines (e.g., projectStats, timecard totals) used to power its charts and reporting views, giving it a hybrid nature. The architecture relies heavily on Meteor's reactive publication/subscription model and ValidatedMethod mixins for authenticated, transaction-logged server methods. A standout feature is its integration layer: it supports sandboxed JavaScript execution via Node's VM module for inbound/outbound data interfaces and webhook verification, alongside LDAP, OIDC, Google Workspace (Gmail/Calendar), and OpenAI integrations. The UI is polished with a custom SCSS theming system (dark/light modes) built on Bootstrap, wrapping Frappe charts, datatables, and Gantt charts. External dependencies include MongoDB, Google APIs, LDAP, and multiple third-party SaaS tools (Wekan, Zammad, GitLab). Maintenance is active with a recent commit and zero Dependabot alerts, but technical drift is medium due to reliance on deprecated Blaze templates, a monolithic ~1200-line SCSS file with heavy !important usage, and known minor bugs (e.g., an inverted OpenAI API key guard, an undefined variable in projectlist.js, and duplicated dashboard components). The codebase mixes older callback styles with async/await, indicating ongoing modernization. Despite these issues, the core architecture is solid, well-separated by domain (projects, timecards, users), and offers several genuinely reusable, well-crafted utility components, making it a strong candidate for teams seeking a self-hosted time tracking solution or studying Meteor best practices.
winston-mongodb is a Node.js transport plugin that lets winston write log entries to MongoDB. When loaded via `require('winston-mongodb')`, it registers `winston.transports.MongoDB`. The transport accepts a MongoDB URI, a promise resolving to a MongoClient, or an existing client/db object; it creates the target collection (optionally capped), reconciles a TTL index on `timestamp` when `expireAfterSeconds` is set, and queues log/query/stream operations until the database is ready. Logging flattens winston's `info` object into a document with timestamp, level, message, optional hostname/label, and sanitized metadata. Internally, the code has a well-tested metadata sanitizer (`lib/helpers.js`) that clones arbitrary JS objects into MongoDB-safe form: it replaces `.` and `$` in keys, preserves Date/Buffer/ObjectId, converts Error into plain objects, and replaces circular references with `[Circular]`. The transport also supports querying and streaming logs: capped collections use a tailable cursor, while non-capped collections fall back to 2-second polling. The test suite uses `mongodb-memory-server`, the `abstract-winston-transport` conformance suite, and includes tests for connection flavors (URI, promise, Mongoose) and capped collections. Maintenance is currently active with CI across Node 20/22/24 and MongoDB 7/8, but code inspection shows some drift: the `silent` option calls the callback without returning and therefore still writes the log entry, a deprecation warning still says pre-connected object support 'will be removed in v5' although the package is at v7, and the query path uses `fields`/`background` options that are legacy in the current MongoDB driver. These are manageable rough edges rather than fundamental flaws.