Cognee is an open-source AI memory platform that enables agents and applications to build, store, and query persistent knowledge graphs from documents, code, and conversations. The system provides a Python SDK, a FastAPI REST API, a CLI, a Next.js frontend, and an MCP server for agent integration. Core operations include ingesting data (remember), extracting entities and relationships via LLMs or GLiNER (cognify), retrieving context (recall), and self-improvement loops (improve). The architecture is modular with adapter/registry patterns for graph databases (Ladybug, Neo4j, Turso), vector stores (LanceDB, PGVector), LLM providers (LiteLLM, OpenAI, Anthropic, Ollama), and integrations (Slack, GitHub, Google Drive). The frontend provides a dashboard for dataset management, knowledge graph visualization, and business analytics. The project also includes an evaluation framework for benchmarking retrieval strategies against standard datasets like HotpotQA and BEAM. While production-grade in many areas, some components are marked as demo-quality or have cloud-only stubs.
vue-cesium is a comprehensive Vue 3 component library that wraps CesiumJS, enabling developers to build 3D geospatial web applications using declarative Vue components. It provides a rich set of components for the Cesium viewer, imagery layers, terrain providers, entities, primitives, geometries, graphics, controls (compass, zoom, navigation, status bar, print), overlays (HTML, heatmap, ECharts, wind, dynamic, typhoon), drawing/measurement tools, analysis features (viewshed, flood), post-process effects, and a full UI kit (buttons, icons, tooltips, sliders, spinners, fab). The library follows a composable-based architecture where each Cesium object type has a corresponding composable managing its lifecycle, prop reactivity, and event bridging. It supports multiple map providers (Baidu, Tianditu, ArcGIS, etc.) with custom coordinate transformations for Chinese coordinate systems. The project is a monorepo with packages for components, composables, shared utilities, locale, theme, and directives. It includes a comprehensive documentation site built with Vitepress featuring live demos and bilingual support (en-US, zh-CN). The codebase demonstrates solid engineering practices with reusable composables, custom material extensions, and a consistent component pattern, though it has some technical debt such as bundled Cesium workers, global Cesium references, and deep watchers that may impact performance with large datasets.
FreakWAN is a LoRa-based wide-area network (WAN) messaging system designed for ESP32 and T-ECHO devices. It implements a fully distributed, open chat network independent of internet or cellular infrastructure. The system supports plaintext and encrypted messaging, group chats, media sharing (small images), sensor data collection, and includes features like duty cycle tracking, automatic retransmission with ACK suppression, and neighborhood discovery via HELLO messages. The codebase is written in MicroPython (with a C port for T-ECHO) and is entirely self-contained, relying only on standard libraries. Architecturally, the application runs as a single asyncio event loop with multiple tasks for periodic message sending, HELLO advertising, serial input handling, and optional IRC/Telegram bot integration. The radio layer is abstracted behind SX1276 and SX1262 drivers, and the display uses a terminal-like Scroller view with splash screen and status icons. The protocol layer defines message types (Data, Ack, Hello, Ping, Pong) and supports encryption via AES-CBC with HMAC integrity. The repository is well-structured, with clear separation of concerns and reusable components that can be extracted for other projects.
autocannon is a high-performance HTTP/1.1 benchmarking tool written in Node.js, inspired by wrk and wrk2. It operates as both a CLI tool and a programmable library. The architecture is centered around a run loop that manages multiple concurrent HTTP clients, each capable of pipelining requests. Key components include a request builder that constructs raw HTTP request buffers, a pipelined request queue for handling out-of-order responses, and a histogram-based statistics engine using hdr-histogram-js with WebAssembly for efficient percentile calculations. The tool supports HTTPS, Unix sockets, multipart forms, HAR file replay, worker threads for parallel execution, rate limiting with coordinated omission correction, and extensive customization via setup functions and event hooks. The codebase is well-structured with clear separation of concerns, comprehensive test coverage, and active maintenance.
Apollo is a distributed configuration management system designed for microservices architectures. It provides a centralized web portal (AngularJS frontend with Spring Boot backend) for managing application configurations across multiple environments (DEV, FAT, UAT, PRO, etc.) and clusters. The system supports real-time configuration updates via long-polling, version management, grayscale (canary) releases, role-based access control, and comprehensive audit logging. It exposes REST APIs for programmatic management through an OpenAPI v1 layer and provides client SDKs for various languages. The architecture consists of three main services: apollo-portal (management UI and OpenAPI endpoints), apollo-adminservice (admin CRUD operations), and apollo-configservice (client-facing configuration delivery with long-polling notifications). These services share a common business logic module (apollo-biz) and persist data in MySQL databases (ApolloConfigDB and ApolloPortalDB). The portal communicates with admin services via REST, while clients poll the config service for updates. The system also includes a service registry module for discovery of admin service instances, supporting multiple discovery mechanisms (Eureka, Consul, Nacos, Zookeeper, database, Kubernetes). Key entry points include the portal web UI, OpenAPI v1 endpoints (/openapi/v1/), admin service REST APIs, and config service APIs for client configuration retrieval and notification. The primary data flow involves creating/modifying configurations through the portal or OpenAPI, which are stored in the database. Changes trigger release messages that are scanned by the config service to notify connected clients. Clients then fetch the latest configurations via the config service. The system also supports gray releases, branching, rollback, and configuration import/export. External dependencies include MySQL (primary database), optional service discovery mechanisms (Eureka, Consul, Nacos, Zookeeper, Kubernetes), LDAP/OIDC for authentication, and email/MQ services for notifications. The codebase is modular with clear separation of concerns, extensive test coverage, and a well-defined SPI (Service Provider Interface) pattern for extensibility.
Sockseek is a command-line music downloader for the Soulseek peer-to-peer network, written in C# (.NET). It searches the Soulseek network for songs and albums, ranks candidates using a sophisticated multi-level sorting algorithm (bitrate, format, user reputation, etc.), and downloads the best match. The application supports multiple input sources: free-text search strings, Spotify/YouTube/Bandcamp/MusicBrainz URLs, CSV files, Soulseek links, and list files. It can run as a one-shot CLI tool or as a persistent daemon with an HTTP API and SignalR real-time event hub for remote control and live progress monitoring. Architecturally, the codebase is modular with four main projects: `Sockseek.Core` (core domain logic, search, download orchestration, extractors, file management), `Sockseek.Cli` (CLI entry point, interactive mode, progress rendering), `Sockseek.Server` (ASP.NET Core daemon with SignalR, event coalescing, state store), and `Sockseek.Api` (DTOs, JSON serialization context, client library). The system uses an event-driven architecture for decoupled progress reporting and state management. Extensive unit and integration tests (over 50 test files) and performance benchmarks (BenchmarkDotNet) ensure reliability and performance. Key features include incremental search result projection (album folders, aggregate tracks), a flexible profile system with condition-based auto-profiles, file condition evaluation (bitrate, sample rate, strict title/artist/album matching), fallback downloads via yt-dlp, stale download detection, and post-download command execution with variable substitution. The daemon exposes a full REST API and OpenAPI specification, enabling remote CLI clients and potential third-party integrations.
This repository is the Microsoft Desired State Configuration (DSC) v3 platform, a cross-platform (Linux, macOS, Windows) configuration management CLI tool written in Rust. It provides a declarative, idempotent system for managing operating system and application settings through resources (e.g., registry, services, firewall, packages) and configuration documents (JSON/YAML). The architecture is a Rust workspace of ~30 crates including the main `dsc` CLI binary, a core library (`dsc-lib`) with resource discovery and invocation, a JSON schema generation library (`dsc-lib-jsonschema`) with VS Code integration, platform abstraction libraries, and many individual resource executables (each a separate binary). It supports adapters for PowerShell and Windows PowerShell, extensions for discovery and secrets, an MCP server for AI tool integration, and Bicep integration via a gRPC server. The codebase is well-engineered with extensive tests, i18n, and consistent patterns, though its large surface area and Windows-specific code present maintenance challenges.
Gavel is a Flask-based web application designed for ranking projects at events like hackathons using pairwise comparisons. The system presents judges with pairs of projects to compare, updating rankings in real-time via a Bayesian inference algorithm. Key components include a custom SQLAlchemy class for serializable transaction isolation, a standalone ranking algorithm module (crowd_bt.py), and utility functions for data handling and security. The application uses PostgreSQL for data storage, Celery for asynchronous email tasks, and relies on Redis as a message broker. Admin interfaces allow managing projects, judges, and global settings, with real-time updates to project rankings displayed via the Mu parameter.
junixsocket is a Java/JNI library providing Unix domain socket (AF_UNIX) support and other advanced socket families (AF_TIPC, AF_VSOCK, AF_SYSTEM) to Java applications. It extends standard Java Socket and NIO APIs with features like ancillary data (file descriptor passing), peer credentials, abstract namespace, SSL/TLS, RMI, and shared memory. The architecture is modular with core modules (junixsocket-common, junixsocket-native) and protocol-specific extensions. Key entry points include factory methods in AFUNIXSocket/AFUNIXServerSocket, SSLContextBuilder, and AFUNIXNaming. Data flows involve JNI-mediated socket operations for IPC, with advanced features using native ancillary messaging. External dependencies include optional integrations (MySQL Connector/J, Jetty, Netty) and platform-specific toolchains for native builds.
The Alfresco Content Application (ACA) is a production-quality Angular single-page application serving as the reference frontend for Alfresco Content Services (ACS). It provides enterprise content management capabilities including file/folder browsing, search with saved searches and faceted filters, document preview and versioning, sharing, favorites, trash management, library management, and folder-based automation rules. The application is built as an Nx monorepo with multiple distributable libraries (aca-content, aca-shared, aca-playwright-shared) and follows an extension architecture that allows plugins to add custom actions, evaluators, routes, and sidebar panels. State management is handled by NgRx, and the UI leverages Angular Material and the Alfresco Development Framework (ADF). Extensive end-to-end tests are implemented using Playwright, with shared page objects and API wrappers for maintainability. The codebase is actively maintained with frequent releases and a well-defined version matrix tracking compatibility with ADF, ACS, Node, and Angular versions.
org-modern is an Emacs Lisp package that provides a modern visual style for Org mode buffers. It uses font-lock keywords and text properties to prettify headlines, tables, source blocks, timestamps, tags, TODO keywords, priorities, checkboxes, lists, progress bars, footnotes, internal/radio targets, horizontal rules, block names, and block fringes. The package is implemented as a single-file minor mode (`org-modern-mode`) with a global variant (`global-org-modern-mode`) and an agenda styling function (`org-modern-agenda`). It relies on Emacs 29.1, Org 9.6, and the Compat library. The code is well-structured, extensively customizable via defcustom options, and follows modern Emacs Lisp conventions. It does not contain reusable components outside the Org mode context, but the implementation demonstrates high craftsmanship in leveraging Emacs' font-lock and text property systems for UI styling.
Pipelines-as-Code is a Kubernetes-native CI/CD controller that triggers Tekton PipelineRuns in response to Git webhook events from multiple providers (GitHub, GitLab, Gitea/Forgejo, Bitbucket Cloud/Data Center). In production, it listens for webhook payloads on a configurable endpoint, detects and validates the provider, matches events to PipelineRun templates stored in the repository's `.tekton/` directory using CEL expressions and annotations, resolves remote tasks and pipelines via hub or URL, creates PipelineRun resources with appropriate parameters and secrets, and reports status back to the Git provider (commit statuses, check runs, comments). It supports ChatOps commands (`/test`, `/retest`, `/cancel`), GitOps-style push commands, concurrency limits, automatic cleanup of old PipelineRuns, and optional LLM-driven failure analysis. The architecture consists of three main controllers (controller, watcher, webhook) plus a CLI tool (`tkn-pac`) for bootstrapping, repository management, and local testing. The codebase is well-structured, with clean provider abstractions, a modular queue system, extensive OpenTelemetry instrumentation, and comprehensive test coverage across all providers. While the multi-provider support introduces some duplication, the core patterns (event matching, pipeline resolution, status reporting) are cleanly separated and reusable.
GoTrue is a self-contained user registration and authentication API written in Go. It provides endpoints for signup, login (via email/password or OAuth2 providers like GitHub, GitLab, Google, Bitbucket, Facebook), token refresh, password recovery, email verification, and user management (CRUD for admin users). The architecture is a monolithic HTTP API using the chi router, backed by a MySQL database (via pop/v5 ORM) and a configurable mailer (SMTP or noop). It supports both single-tenant and multi-tenant deployments, with JWT-based authentication (HS256) and optional SAML SSO. The codebase is well-organized into packages: api for HTTP handlers, models for database entities, conf for configuration, mailer for email sending, and crypto for security utilities. It includes extensive unit tests and integration tests using a MySQL test database.
Dotdrop is a professional-grade CLI tool for managing dotfiles (configuration files) across multiple machines and environments. It allows users to define profiles (e.g., laptop, server, work), map source files to destinations, and deploy them with a single command. It supports templating via Jinja2, symlinks, file permissions, and pre/post deployment actions, making it a comprehensive solution for configuration management. The codebase is a well-structured monolithic Python application. It features a clean two-layer config parsing system (low-level dict normalization in `cfg_yaml.py`, high-level object creation in `cfg_aggregator.py`), a robust templating engine, and a comprehensive ignore/action/transformation pipeline. The project demonstrates high craftsmanship with several extractable components, such as the `DictParser` base class, the `FTreeDir` directory comparison utility, and the Jinja2 helper library. Actively maintained with a strong CI/CD pipeline (GitHub Actions for testing, PyPI, Homebrew, AUR, Snap releases). The project has a large and active test suite. While the core architecture is solid, there are signs of technical drift, including support for a wide range of Python versions (3.6-3.14), the use of the largely abandoned `docopt` library for CLI parsing, and the presence of deprecated configuration options that add maintenance overhead.
This is an MCP (Model Context Protocol) server implementation that provides LLMs with MySQL database access. The server exposes a single `mysql_query` tool for executing SQL queries and resources for listing tables and column metadata. It supports both stdio and HTTP transport modes, the latter with bearer token authentication. Key features include multi-database mode (querying across schemas without reconnection), schema-specific write permissions (INSERT/UPDATE/DELETE/DDL per database), SSL/TLS with mTLS, Unix socket connections, and a sophisticated PII redaction system that combines column-name heuristics with regex value scanning and Luhn-verified credit card detection. The architecture is monolithic: a single Express server (or stdio process) manages a mysql2 connection pool and routes all MCP protocol requests through zod-validated schemas. The codebase is well-tested with unit, integration, and end-to-end test suites, and demonstrates careful engineering in areas like query parsing (using node-sql-parser), permission enforcement, and secure defaults (write operations disabled by default).
pymupdf4llm is a Python library for converting PDF documents into Markdown, JSON, text, or structured chunks optimized for LLM/RAG ingestion. It is the official PDF-to-Markdown converter for the PyMuPDF ecosystem, delivered as part of the pymupdf package. The system provides two parallel conversion paths: a legacy mode (pymupdf_rag.py) and a layout-aware mode (document_layout.py) that uses a GNN-based page segmentation model (PyMuPDF-Layout) for improved table, header, and list detection. A dedicated chunking subsystem (src/helpers/chunking/) splits documents into retrieval-friendly pieces using layout signals (bounding boxes, font sizes, gaps) without semantic embeddings, and supports export to LangChain Document and LlamaIndex Node objects. OCR support is integrated via multiple backends (Tesseract, RapidOCR, PaddleOCR) with an ONNX-based decision model that classifies pages to determine if OCR is needed. The library also includes a batch converter with automatic worker sizing, a Gradio-based GUI example, and a LlamaIndex reader integration. External dependencies include pymupdf, optional pymupdf-layout for layout mode, tiktoken for token counting, and optional OCR engines. The codebase is modular with clear separation of concerns, comprehensive tests, and active maintenance, though it carries some technical debt from dual code paths and a custom build backend.
Arthas is a production-grade Java diagnostic and monitoring agent developed by Alibaba. It attaches to running JVMs without code changes or restarts, enabling real-time inspection of threads, memory, classes, method invocations, and system properties through an interactive shell (telnet/HTTP/WebSocket) or programmatic APIs. The architecture consists of a core agent (bytecode instrumentation via ASM/ByteKit), a command framework with over 40 built-in commands (watch, trace, stack, dashboard, profiler, etc.), multiple transport protocols (telnet, HTTP, gRPC, MCP for AI integration), and a tunnel server for remote connectivity. It also includes experimental modules for JFR analysis, cluster management, and gRPC-web proxies. Key external dependencies include Netty, OGNL, CFR decompiler, and async-profiler.
This is a Python library for quantitative finance, specifically portfolio optimization and risk management. It implements Conditional Value-at-Risk (CVaR) optimization using Benders decomposition, mean-variance optimization via quadratic programming, and entropy pooling for adjusting scenario probabilities under user-defined views and stress tests. The library also includes fully flexible resampling (FFR) for simulation, Black's model for option pricing, and a set of helper functions for financial statistics. It is designed as a monolithic Python package with a clean API, extensive tests (100% coverage), and 14 Jupyter notebooks that serve as reproducible examples. While the primary character is an application library, it has a strong research and educational orientation, referencing academic papers and providing walkthroughs. The code is well-structured, but domain-specific and depends on cvxopt with GLPK for linear programming, which may limit portability.
Nostalgist.js is a JavaScript library that provides a high-level API for running retro console emulators (NES, SNES, Game Boy, Sega Genesis, etc.) directly within web browsers. It wraps RetroArch compiled to WebAssembly via Emscripten, handling the complex setup of virtual file systems, core loading, ROM resolution, and configuration. The library exposes a clean facade (`Nostalgist`) with static methods like `launch`, `nes`, `snes` for quick starts, and instance methods for save/load states, screenshots, button presses, cheat management, and low-level Emscripten access. It supports caching, shaders, multi-disc games, and custom resolvers for cores, ROMs, and BIOS files, making it a versatile tool for embedding retro gaming into web applications. The architecture is modular: `Nostalgist` orchestrates the launch process, `EmulatorOptions` resolves and caches all file inputs (cores, ROMs, BIOS, states, cheats), `Emulator` manages the Emscripten runtime and RetroArch communication, and `EmulatorFileSystem` abstracts the virtual file system. The `ResolvableFile` class handles diverse input types (URLs, Blobs, Responses, etc.) uniformly. The library is well-tested with both integration and end-to-end tests, follows semantic versioning, and has active maintenance with frequent releases.
This repository implements a Build Server Protocol (BSP) server that integrates Xcode builds with language servers like sourcekit-lsp. It parses Xcode build logs (either from IDE builds or xcodebuild) to extract compiler flags and serves them via BSP to provide accurate code completion, navigation, and other language features for Swift, C, C++, Objective-C, and Objective-C++ projects. The server operates in two modes: 'xcode' mode automatically monitors build logs via a post-build script or file watching, and 'manual' mode processes build logs on demand. Key components include a robust compilation database handler, a parser for Xcode's proprietary xcactivitylog binary format, and a log parser that handles various Xcode build output formats. The project is actively maintained with recent commits and shows no significant technical debt.