Harness Gitness is an open-source DevOps platform that provides Git hosting, CI/CD pipelines, artifact registries, and cloud development environments (Gitspaces). The system is built as a monolithic Go backend with a React/TypeScript frontend, using Google Wire for dependency injection and supporting both PostgreSQL and SQLite databases. Key entry points include the main server binary (`cmd/gitness`), REST API handlers organized by resource (repos, pull requests, spaces, pipelines, gitspaces, registries), and a CLI for administrative tasks. The architecture follows a layered pattern: HTTP handlers → controllers → services → stores, with an event-driven subsystem for asynchronous processing (pull requests, checks, gitspace lifecycle, merge queues). External dependencies include Drone runner libraries for pipeline execution, Docker API for container orchestration, and cloud provider SDKs (AWS, GCP) for infrastructure provisioning. The artifact registry is based on a fork of Harbor and supports OCI, Maven, npm, NuGet, Python, Helm, RPM, and other package formats. The frontend is modular, with separate codebases for the core Git UI, artifact registry (AR), and CDE (Gitspaces), using Harness UI components and custom factories for extensible package-type rendering.
Harbor is an open-source, cloud-native container registry platform for managing OCI/Docker images, Helm charts, and other artifacts. It provides a full-stack solution with a Go backend, Angular web portal, PostgreSQL database, and Redis/ValKey job queue. The system supports artifact storage, vulnerability scanning (Trivy integration), SBOM generation, multi-registry replication (Docker Hub, Quay, JFrog, cloud CRs), tag retention policies, immutable tags, RBAC with LDAP/OIDC, robot accounts, webhook/notification pipelines, P2P preheat, and audit logging. The architecture follows a layered pattern: REST API handlers (v2.0) → controllers → managers → DAOs, with middleware chains for security, quota, and content trust. Key entry points include the core API server, job service for background tasks, registry controller for blob/manifest management, and the Angular portal for administration. External dependencies include PostgreSQL, Redis, Trivy scanner, and various cloud registry APIs. The codebase is well-structured with extensive unit and integration tests, though it exhibits some technical debt from generated mocks and legacy components.
Gitleaks is a command-line secret detection tool written in Go that scans for sensitive information like API keys, tokens, and passwords in git repositories, directories, files, and stdin. It features a modular architecture with separate components for configuration loading, source abstraction (file/git/archive handling), detection logic with multi-layer decoding, rule-based matching, and flexible reporting. The tool uses a Cobra-based CLI interface with commands for different scan modes and supports output formats including JSON, CSV, JUnit, SARIF, and custom templates. Key strengths include its pluggable decoder pipeline for handling encoded secrets, configurable rule system with entropy checks and keyword filtering, and sophisticated allowlist mechanism for reducing false positives. While actively maintained for security patches, the project is feature-complete with ongoing dependency management challenges due to its extensive rule set and reliance on unstable packages like golang.org/x/exp.
Bagisto is a production-ready open-source eCommerce platform built on Laravel with a modular monolith architecture. It provides a complete admin panel and storefront for managing multi-channel, multi-locale, multi-currency online stores. The system supports a wide range of product types (simple, configurable, bundle, grouped, downloadable, virtual, booking), payment gateways (Stripe, PayPal, Razorpay, PayU, PhonePe, PayGlocal), marketing promotions (cart rules, catalog rules), full-page caching, Elasticsearch integration, GDPR compliance, EU withdrawal management, RMA (returns), data import/export, and AI-powered features (MagicAI). The architecture is event-driven with listeners for cache invalidation, notifications, and indexing. The admin panel uses Vue 3 components with Blade templates, while the storefront is built with Tailwind CSS and Vue. The codebase is organized into ~40+ packages under packages/Webkul/, each with its own models, repositories, migrations, translations, and tests. Key entry points include the admin routes (packages/Webkul/Admin/src/Routes/web.php), shop routes (packages/Webkul/Shop/src/Routes/), and the installer wizard. The system relies on MySQL, Redis, Elasticsearch, and various external payment/shipping APIs. The core framework (Concord) provides facades for core services, ACL, menu, system config, and Elasticsearch. The DataGrid system offers a reusable abstraction for listing and filtering entities across the admin panel. Notable engineering highlights include the CurrencyFormatter trait for locale-aware currency display, the MediaFileName helper for safe file upload handling, the ForgetsPages trait for full-page cache invalidation, and the DynamicMailTransport for configurable email delivery. The event-driven architecture with listeners and the repository pattern are consistently applied across all modules.
PySyft is a privacy-preserving data science platform that enables data owners to share private datasets and approve code execution without exposing raw data. The codebase is a monorepo with multiple interdependent packages: `syft` (sync engine, peer management, encryption), `syft-rds` (high-level remote data science client for datasets and jobs), `syft-job` (job lifecycle, runner, disclosures), `syft-datasets` (dataset storage with versioned protocol codecs), `syft-enclave` (confidential computing with TEE attestation via Confidential Spaces or Tinfoil, signed receipts), `syft-bg` (background services for auto-approval, email notifications, systemd management, TUI), `syft-permissions` (declarative ACL engine), `syft-restrict` (static code verification and obfuscation for private regions), `syft-migration` (generic versioned migration framework for objects), `syft-notebook-ui` (rich HTML representation for Jupyter), and `syft-perms` (file-level permission browser). The core workflow: data scientists submit Python jobs encapsulating analysis code → data owners approve (manually or automatically) → jobs run in sandboxed environments or TEE enclaves → results and logs are staged and released according to multi-party disclosure policies. The system uses Google Drive as the default sync transport with offline-first P2P file exchange, protocol versioning for backward compatibility, and cryptographic key pinning for trust.
Apache Iceberg is a high-performance table format for analytic data lakes, providing ACID transactions, snapshot isolation, schema evolution, and time travel. The repository contains the Java reference implementation, including core libraries for table metadata management, file format support (Parquet, ORC, Avro, Arrow), expression evaluation, encryption, and a REST catalog protocol. It integrates deeply with Spark (versions 3.5, 4.0, 4.1, 4.2), Flink (1.20, 2.2, 2.3), Kafka Connect, Hive, and cloud object stores (AWS S3, Azure ADLS, Aliyun OSS, GCS). The architecture is modular: the `api` module defines public interfaces (Table, Catalog, Scan, FileIO), `core` provides implementations and utilities, and separate modules handle engine-specific integrations and cloud backends. Key entry points include the Table interface for DDL/DML operations, Scan for query planning, FileIO for storage access, and the REST catalog client for remote metadata management. Data flows involve reading/writing manifest files, applying expressions for predicate pushdown, and coordinating commits via optimistic concurrency control. External dependencies include Apache Parquet, ORC, Avro, Arrow, and various cloud SDKs, but the core is designed to be lightweight and extensible.
Atlantis is a self-hosted Go application that automates Terraform and OpenTofu workflows triggered by pull request events. It listens for webhooks from GitHub, GitLab, Bitbucket Cloud/Server, Azure DevOps, and Gitea, then executes Terraform commands (plan, apply, import, state rm, version) and reports results via PR comments and commit statuses. The system enforces approval, mergeability, and policy requirements, supports drift detection and remediation, and provides a web UI for lock management and streaming logs. The architecture is a monolithic server with modular components: HTTP controllers for webhook handling, command runners for orchestrating workflows, step runners for individual Terraform operations, VCS client abstractions for multi-provider support, and pluggable persistence (BoltDB embedded, optional Redis, S3 for plan storage). Configuration is layered via server-side YAML, repo-level atlantis.yaml, and CLI flags. Key entry points include main.go (CLI), cmd/server.go (server command), server/controllers/events/events_controller.go (webhook dispatcher), and server/events/command_runner.go (command orchestration). External dependencies include Terraform/OpenTofu binaries, Conftest for policy checks, VCS APIs, and optional Redis/S3. The codebase demonstrates strong engineering practices with extensive unit/integration/e2e tests, instrumentation for metrics, structured logging, and security-conscious design (webhook signature validation, path traversal prevention, shell injection mitigation). While the project is actively maintained, technical drift is medium due to large dependency surface, mock generation sprawl, and complex VCS integration parity.
ChakraCore is a standalone, community-maintained JavaScript engine originally developed by Microsoft. It implements the full ECMAScript specification (ES5/ES6/ES7+), WebAssembly, and Asm.js, with a high-performance JIT compiler supporting x64, x86, ARM, and ARM64 architectures. The engine includes a generational garbage collector (Recycler), a bytecode interpreter, a parser, and a comprehensive debugger with time-travel debugging support. It is designed to be embedded via a C API (Jsrt) and also ships with a lightweight command-line host (`ch`). The codebase is highly modular, with clear separation between the runtime, backend, parser, and platform abstraction layer (PAL). It contains an extensive test suite covering language features, optimizer edge cases, and regression tests. While the original Microsoft support ended in 2021, the community actively maintains the project, with recent commits and ongoing issue triage. The engine is production-grade and has been used in various applications, including Node.js (prior to the move to V8) and Windows applications.
MQTT.js is a comprehensive MQTT protocol client library for Node.js and browsers, implementing MQTT 3.1.1 and 5.0 specifications. It provides core functionality for connecting to brokers, publishing/subscribing with QoS levels, keepalive management, and offline message queuing. The architecture features modular transport abstraction (TCP/TLS/WebSocket/platform-specific), event-driven design with TypedEventEmitter, and pluggable persistence via Store. Entry points include the main library (src/mqtt.ts), CLI tools (src/bin/*), and platform-specific adapters. The codebase demonstrates strong craftsmanship in handling protocol complexities, cross-platform concerns, and maintainable abstractions.
This repository is a Next.js SEO library that provides React components for generating JSON-LD structured data (Schema.org) to enhance search engine optimization. The library offers over 50 specialized components for various Schema.org types (Article, Recipe, Product, Event, etc.) and a core JsonLdScript component for rendering JSON-LD tags. It includes utility processors for normalizing flexible input data into Schema.org-compliant formats and emphasizes security through XSS prevention in JSON-LD stringification. The architecture follows a modular component pattern with strong TypeScript typing, comprehensive testing (unit and E2E), and support for both Pages Router and App Router in Next.js. The library is actively maintained with recent updates, a changeset-based versioning system, and extensive documentation.
Collision is a PHP library that provides beautiful error reporting for CLI applications, particularly integrated with Laravel, PHPUnit, and Pest. It wraps the Whoops error handler to render exceptions with syntax-highlighted code snippets, stack traces, and solution suggestions. Additionally, it includes a custom PHPUnit/Pest test printer that outputs test results with color-coded summaries, warnings, and slow-test profiling. The library is built on top of Symfony Console, Termwind, and Whoops, and is designed as a drop-in replacement for default error handling in Laravel's artisan commands and PHPUnit test runners. The codebase is well-structured with clear separation of concerns: core error rendering (Provider, Handler, Writer), terminal styling (ConsoleColor, Highlighter), argument formatting (ArgumentFormatter), code coverage reporting (Coverage), and framework-specific adapters (Laravel service provider, PHPUnit event subscribers). The PHPUnit adapter demonstrates advanced event-driven architecture by hooking into PHPUnit's event system to produce a rich, compact test output.
Aedes is a barebone MQTT broker library for Node.js, supporting MQTT 3.1 and 3.1.1. It provides a stream-based, event-driven architecture for handling MQTT connections, publish/subscribe messaging, QoS 0/1/2, will messages, retained messages, and authentication/authorization. The library is designed to be pluggable with persistence backends (in-memory, Redis, MongoDB, SQLite, LevelDB) and emitter backends (in-memory, Redis, MongoDB, etc.) for clustering and high availability. Aedes is the successor to Mosca, focusing on performance and stability. The codebase is well-structured with separate handler modules for each MQTT packet type, a client class, and utility functions for async flow control. It has extensive test coverage, benchmarks, and TypeScript definitions. Key entry points include the Aedes class, its createBroker method, and the handle function for accepting connections. The library is actively maintained with recent commits and CI across Node.js 20, 22, and 24. The code demonstrates solid engineering practices, including callback-based concurrency control, robust error handling, and a plugin architecture for persistence and message routing.
diagram-js is a modular, extensible JavaScript library for building interactive web-based diagram editors. It provides the foundational infrastructure—an event-driven architecture via EventBus, a command pattern with full undo/redo support via CommandStack, and a DI container (didi) for composing features as independent modules. The codebase includes core services (Canvas, ElementRegistry, GraphicsFactory) for managing SVG rendering, hit testing, and element lifecycle, along with a rich set of interaction features: drag-and-drop creation/move/resize/connect, snapping, grid snapping, auto-resize, auto-place, bendpoint editing, lasso selection, space tool, popup menus, context pads, palettes, search, overlays, copy/paste, and keyboard bindings. It is designed for downstream domain-specific editors (e.g., bpmn-js, dmn-js) which extend it via provider interfaces and rule systems. The library is well-tested with an extensive suite using Mocha/Chai/Sinon and runs on modern browsers. Its architecture emphasizes decoupling, extensibility, and reusable patterns.
This is a PHP library that converts HTML strings to Markdown. It parses HTML into a DOMDocument, then recursively traverses the DOM tree, converting each node to its Markdown equivalent using a registry of converter classes. The architecture is clean: an `HtmlConverter` orchestrates the process, an `Environment` manages configuration and converter registration, and individual converter classes handle specific HTML elements (headers, links, lists, tables, etc.). The library supports extensive configuration options including stripping tags, preserving comments, customizing emphasis styles, and enabling table conversion. It provides both a programmatic API and a CLI binary. The code is well-structured with strict typing, interfaces, and comprehensive test coverage. It demonstrates solid software engineering practices and is actively maintained.
phpspec is a mature Behavior-Driven Development (BDD) testing framework for PHP, delivered both as a CLI tool (`bin/phpspec`) and an embeddable library. In production it runs executable specifications (spec files extending `ObjectBehavior`) via two Symfony Console commands: `describe` generates a spec skeleton from a class name, and `run` discovers spec files through PSR-0/PSR-4 locators, executes them through a layered runner stack (suite -> specification -> example), evaluates assertions through a pluggable matcher library (identity, comparison, throw, trigger, iterable, array, string, etc.), and renders results through swappable formatters (progress, pretty, dot, JUnit, TAP, TeamCity, HTML, JSON). A distinctive feature is listener-driven code generation: when a spec references a missing class, method, collaborator, or named constructor, listeners prompt the developer and generate real PHP source via token-based code writers, then transparently re-run the suite using platform-specific process re-runners (pcntl, proc_open, Windows passthru). The framework couples to Prophecy for mocking and rewrites type hints in spec files at load time using a tokenizer state machine so Prophecy doubles work with modern PHP union/intersection types.
Impress is an enterprise application server for Node.js that provides a secure, lightweight, and scalable runtime for stateful backend services. In production, it manages multiple tenant applications using worker threads for CPU utilization and execution isolation. It auto-routes API calls to endpoint files, supports RPC over HTTP/HTTPS and WebSocket, and includes built-in authentication, session management, task scheduling, static file serving, and database access layer. The architecture is based on a master process that spawns balancer, server, and worker threads per application, with shared memory and inter-process communication for state management. Key entry points include the impress.js master process, which loads applications from .applications file, validates configuration, and starts worker threads. Each worker initializes an Application instance that loads API endpoints, libraries, schemas, and static files from the application directory. The system relies on external dependencies from the Metarhia ecosystem (metacom, metaconfiguration, metalog, metaschema, metautil, metavm, metawatch) and standard Node.js modules. It does not use third-party npm packages for core functionality. Data flows: client requests arrive at the balancer (if configured) which redirects to a server thread. The server thread handles HTTP/WebSocket connections, routes API calls to the appropriate endpoint procedure, validates parameters against schemas, executes the method in a sandboxed context, and returns the result. Static files are served from memory cache with optional compression. Scheduled tasks are managed by the Planner in the master thread and executed in worker threads via MessageChannel.
evmone is a high-performance Ethereum Virtual Machine (EVM) implementation written in C++20, designed as a plugin for Ethereum clients via the EVMC interface. It provides two execution engines: a baseline interpreter using computed goto dispatch for simplicity and speed, and an advanced interpreter using indirect call threading with precomputed basic block analysis for further optimization. The implementation supports all EVM revisions from Frontier through the upcoming Amsterdam, including precompiled contracts for cryptographic operations such as SHA-256, RIPEMD-160, BLAKE2b, BN254 pairings, BLS12-381, KZG point evaluation, and secp256r1 verification. The codebase is structured as a shared library (libevmone) with a CLI tool (evmone) for running bytecode and executing state transitions (t8n), along with extensive benchmarking and testing infrastructure. The architecture is modular: core EVM logic resides in lib/evmone/, precompiled contracts in lib/evmone_precompiles/, and test utilities in test/. The project uses CMake with Hunter for dependency management and includes a self-contained CMake bootstrap library (Cable) for build configuration. It features a comprehensive test suite including unit tests (Google Test), state transition tests, blockchain tests, fuzzing, and integration tests against Ethereum execution-spec-tests. The code demonstrates strong engineering practices with heavy use of templates, constexpr, and platform-specific optimizations (e.g., SHA-NI, BMI) while maintaining portability across x86, ARM, and RISC-V. Notable reusable components include a generic LRU cache, Montgomery modular arithmetic for arbitrary precision, a bytecode construction DSL for testing, a generic elliptic curve library, and a modular exponentiation implementation with CIOS multiplication. The project is actively maintained with frequent releases tracking Ethereum protocol upgrades, and its design emphasizes performance without sacrificing correctness, as evidenced by rigorous testing and fuzzing.
Suwayomi-JUI is a multiplatform manga reader application built with Kotlin Multiplatform, targeting Android, Desktop, and iOS. It functions as a client for the Suwayomi-Server backend, communicating via GraphQL (Apollo) and REST (Ktor) to manage a personal manga library, download content for offline reading, and provide a customizable reading experience. The architecture follows a clean layered structure: core utilities, data layer (repositories and network clients), domain layer (business logic and use cases), and presentation layer (UI with Jetpack Compose/SwiftUI). Key features include library management with categorization, extension/plugin support, download queue management, reading interface with various navigation modes, backup/restore functionality, and comprehensive settings. The application employs dependency injection via custom annotations, reactive programming with Kotlin Flows and coroutines, and a cross-platform preference storage system. It is actively maintained with recent commits and demonstrates strong engineering practices in modularity and platform abstraction.
This repository is a PHP implementation of the Pact contract testing framework, enabling consumer-driven contract testing for APIs and microservices. It allows developers to define expected interactions in consumer tests (generating Pact files) and verify provider compliance against those contracts. The library supports multiple transport protocols (HTTP/REST, gRPC, message queues) and data formats (JSON, XML, CSV, Protobuf, etc.) through a plugin architecture. It uses FFI to interface with a Rust-based Pact core and includes a mock server for simulating providers during testing. The codebase features a well-structured domain model, extensive matcher/generator system, and comprehensive compatibility suite validating adherence to Pact specifications v1-v4.
The repository implements Hipo, a decentralized liquid staking protocol on the TON blockchain. Users deposit GRAM to receive hGRAM tokens representing a share in a staking pool that lends to validators for validation rounds. Rewards increase the hGRAM/GRAM exchange rate, accruing value to stakers. The system features a modular smart contract architecture with upgradeable contracts (Treasury, Parent, Wallet, Loan, Bill, Collection, Librarian), a participation state machine tracking validation rounds, and a library management system for code reuse. It includes a comprehensive test suite with custom Jest matchers, deployment scripts, and diagnostic tools for monitoring state and analytics.