This repository is the official Composer project template for bootstrapping new Sulu CMS applications. It is not a standalone CMS but a pre-configured Symfony 7.4 application skeleton that wires together the Sulu 3.0 bundles (admin, media, security, page, search, article, snippet, etc.) with Doctrine ORM, MySQL, Twig, Messenger, Flysystem, and a React-based admin SPA built via Webpack. The application exposes two runtime contexts through a single kernel: an admin backend under /admin with a JSON API and a website frontend serving Twig templates. Entry points are public/index.php for web requests and bin/console, bin/adminconsole, bin/websiteconsole for CLI operations. The template includes production-oriented infrastructure: HTTP cache layer via SuluHttpCache, FOSHttpCache for proxy caching, 2FA via scheb/2fa, search via CMSIG Seal with Loupe adapter, media handling, and a maintenance mode script that works without framework dependencies. The composer.json defines an extensive lint/test pipeline (PHPStan level max, PHP-CS-Fixer, Rector, Twig CS Fixer, container validation, Doctrine schema validation) and the GitHub Actions workflow tests the template across PHP 8.2-8.5, MySQL 5.7-8.4, and Node.js 20-24, including a create-project test that verifies the template can bootstrap a new project. Because this is a skeleton, the actual application code is minimal (a Kernel class, empty fixtures, and basic Twig templates). Its value lies in the configuration and integration of the Sulu ecosystem, serving as a starting point for multi-lingual, multi-portal CMS websites. The repository is actively maintained with recent commits and a comprehensive CI pipeline.
This repository is a storage provider plugin for Synapse, the Matrix homeserver, that stores media in S3-compatible object storage. It is a Python package installed as a module and loaded by Synapse at runtime. The core is a single module, s3_storage_provider.py, which implements Synapse's storage provider API and translates local media operations into S3 GET/PUT/HEAD/DELETE calls via boto3. It supports SSE-C encryption, custom S3 endpoints, and a local cache. A companion CLI script, s3_media_upload, migrates existing local media to S3. Architecturally, the system is a library/plugin rather than a standalone service. Synapse invokes the provider's methods to store and retrieve media; the provider uses background threads (_S3DownloadThread, _S3UploadThread) to perform asynchronous operations with backpressure. The code uses threading locks and events to coordinate concurrent access, and includes tests, CI workflows, and release automation. The primary entry point is the S3StorageProvider class instantiated by Synapse; the module can also be run as a script for maintenance, and scripts/s3_media_upload provides a CLI. External dependencies include boto3 for S3 access, Synapse as the host application, and Twisted for tests. The repository is actively maintained with recent commits, dependabot updates, and GitHub Actions for CI and releases.
This repository is a PHP client library for the Mautic marketing automation REST API. It provides a clean, object-oriented interface for performing CRUD and custom operations on Mautic entities such as contacts, campaigns, emails, segments, and companies. The library is built on PSR-18 (HTTP client) and PSR-7 (HTTP messages) abstractions, making it compatible with any modern PHP HTTP client via php-http/discovery. It supports three authentication methods: OAuth 1.0a, OAuth 2.0, and BasicAuth, each handling token lifecycle and refresh automatically. The architecture follows a factory pattern: the `MauticApi` class instantiates context-specific API classes (e.g., `Contacts`, `Emails`) that extend a common `Api` base class. The base class implements generic `get()`, `getList()`, `create()`, `edit()`, `delete()`, and batch operations, while context classes add custom endpoints (e.g., `addContact()` for campaigns). A fluent `QueryBuilder` allows building complex WHERE/ORDER/SELECT clauses for list requests. The library also includes a backwards-compatibility layer that transparently falls back to deprecated API URLs when a 404 is returned. External dependencies include any PSR-18 HTTP client implementation (e.g., Guzzle, Symfony HttpClient) and a PSR-3 logger (optional). The library is designed for integration into PHP applications that need programmatic access to Mautic data. It includes a legacy web-based API tester (`apitester/`) for manual testing, which vendors Bootstrap 3.2.0 and jQuery. The test suite requires a live Mautic instance and is run in CI against temporary installations. While the core library is modern and well-structured, the apitester UI is outdated and the backwards-compatibility layer introduces some technical debt. Overall, this is a solid, production-ready API client with good separation of concerns and reusable patterns.
This is an npm library that provides the GitHub GraphQL schema in JSON and IDL formats, along with a validation function and TypeScript type definitions. It is used by other Octokit libraries to validate GraphQL queries against the official GitHub GraphQL API. The schema is automatically updated hourly via a GitHub Action that fetches the latest schema from GitHub and creates pull requests for changes. The library is simple but robust, relying on the `graphql` package for validation and `graphql-codegen` for TypeScript types. It is not a data research project; it is a straightforward software library.
Collision is a desktop application for generating and verifying cryptographic hashes of files. Built with Crystal, GTK 4, and libadwaita, it provides a clean GUI interface to calculate MD5, SHA-1, SHA-256, SHA-512, Blake3, CRC32, and Adler32 hashes. The application features concurrent hash calculation using Crystal's fiber system, a Nautilus extension for file manager integration, and proper handling of Flatpak sandboxed environments. It follows a modular architecture with separate concerns for UI, core functionality, and application logic.
A distributed transaction processing system built on Apache Accumulo that provides snapshot-isolated transactions with observer-driven incremental processing. The system implements the Google Percolator model, allowing efficient incremental updates to large datasets without full reprocessing. It includes a client API, worker processes for executing user-defined observers, an oracle service for timestamp allocation, and command-line tools for administration. The architecture is modular with separate modules for API, core implementation, Accumulo-specific iterators, MapReduce integration, and a mini testing harness. Key design patterns include immutable data types (Bytes, Column, Span), a pluggable observer framework, hash-based notification partitioning, and an asynchronous commit pipeline with lock resolution. The codebase demonstrates strong engineering practices with extensive unit and integration tests, metrics integration, and a well-structured Maven multi-module build.
PSWriteColor is a PowerShell module that makes console output easier to scan by letting scripts write text with multiple foreground and background colors, padding, separators, timestamps, and optional log-file output. The core Write-Color function accepts parallel arrays of text and color, interleaves them on a single line, and supports line breaks, padding, and host fallback when RawUI dimensions are unavailable. It is designed for operational scripts that need clear status messages, prompts, or lightweight menus without pulling in a full TUI framework. The module can write to the console and a log file simultaneously, and it degrades gracefully in constrained hosts.
This repository is the canonical source of tldr-pages, a community-maintained collection of simplified man pages for command-line tools. It contains tens of thousands of Markdown files organized by language and platform, each providing concise usage examples for a CLI command. The repository also includes a suite of validation scripts, a build system for generating indexes and archives, and a client specification for consuming the pages. While primarily a documentation project, the tooling (Node.js and Python scripts) constitutes a small application layer that ensures consistency, quality, and automated releases. The repo supports translations in over 30 languages, with strict formatting and linting enforced by CI/CD pipelines. It is not a standalone application but the authoritative dataset and tooling for the tldr ecosystem.
Redash is a full-stack business intelligence platform that enables users to connect to multiple data sources, write and schedule queries, build interactive visualizations, and create dashboards with alerting and sharing capabilities. The backend is a Python Flask application with SQLAlchemy for database access, Redis for caching and task queuing, and RQ for background job execution. The frontend is a React single-page application using Ant Design, Plotly, D3, and Leaflet, organized into pages for queries, dashboards, alerts, data sources, and administration. The system exposes a RESTful API for all operations and supports authentication via password, Google OAuth, SAML, LDAP, JWT, and API keys. The architecture follows a modular plugin pattern for query runners and visualizations. Over 35 query runners (e.g., PostgreSQL, BigQuery, Snowflake, MongoDB, Prometheus) are registered via a common base class, each implementing run_query, get_schema, and configuration_schema. The visualization library (viz-lib) is a separate package that registers chart types (line, bar, pie, map, table, cohort, sankey, etc.) with editors and renderers. Dashboards use a grid layout with widgets that can display visualizations, text, or embedded content. Alerts evaluate query results against conditions and send notifications to destinations like Slack, email, PagerDuty, and webhooks. Key data flows: users write SQL or use query runners to fetch data from connected sources; results are cached and can be visualized; dashboards aggregate multiple visualizations with parameter bindings; scheduled queries refresh results and trigger alerts. The system also supports embedding visualizations in external sites and public sharing of dashboards. While primarily an application, the extensive query runner and visualization plugin systems make it a flexible platform for data exploration and operational reporting.
TheAlgorithms/Rust is a large educational library of algorithm and data structure implementations in Rust, organized into over 20 modules covering sorting, searching, graph theory, dynamic programming, cryptography, machine learning, math, string processing, and more. The codebase is structured as a reusable Rust library crate with a flat module hierarchy, each module containing self-contained functions and types with extensive inline documentation and unit tests. It serves as a reference and learning resource rather than a production application, with many implementations based on textbook algorithms and well-known specifications (RFCs, NIST standards). The code demonstrates good engineering practices such as modular design, property-based testing with quickcheck, use of generics and traits for abstraction, and consistent test patterns. However, some modules show inconsistencies in naming and error-handling conventions, and the sheer variety of implementations means code quality varies. The repository is actively maintained with recent commits, automated CI/CD workflows, and dependency updates via Dependabot. While the implementations are pedagogical and not necessarily production-grade (e.g., simplified RSA, educational AES without side-channel resistance), they are functionally correct and well-documented, making this a valuable resource for learning algorithms in Rust.
Invoice Ninja is a full-featured open-source invoicing and billing platform designed for small to medium businesses. It handles the complete lifecycle of invoices, quotes, credits, purchase orders, payments, and expenses. The system supports multi-tenant SaaS and self-hosted deployments with per-company database isolation, and integrates with over 20 payment gateways (Stripe, PayPal, Mollie, GoCardless, etc.). It provides client and vendor portals for self-service, along with extensive reporting, CSV export, and e-invoicing capabilities (Peppol, Verifactu, France e-reporting). The application follows a monolithic MVC architecture built on a custom PHP framework (Illuminate) similar to Laravel. It uses an event-driven architecture with domain events and listeners for side effects (email, webhooks, activity logging). Background jobs are queued for async processing. The frontend uses Blade templates, Livewire components, and a separate React app for some admin panels. The API is RESTful with OpenAPI documentation. Key entry points are HTTP controllers under app/Http/Controllers, with request validation classes. Core data flows involve creating entities through factories, persisting via repositories, and triggering events that listeners handle. Payment flows go through abstract payment drivers that encapsulate gateway-specific logic. The system also includes extensive reporting, CSV export, and e-invoicing (Peppol, Verifactu, France e-reporting). External dependencies include a relational database (MySQL/PostgreSQL), Redis for caching and queues, Elasticsearch for search, and various third-party APIs for payment processing, tax calculation (ZipTax), bank integration (Nordigen, Yodlee), email delivery (Mailgun, Postmark, Brevo), and e-invoicing gateways (Storecove, Qvalia).
This repository is the OpenWrt packages feed: a collection of roughly 5,000 package build recipes, patches, init scripts, UCI defaults, netifd protocol handlers, and small utility programs that extend the OpenWrt embedded Linux distribution. It is not a standalone application; it is a software distribution layer consumed by OpenWrt's feed mechanism. Each package directory contains a Makefile that wraps an upstream project (download, patch, cross-compile, install) plus OpenWrt-specific runtime glue such as /etc/init.d scripts, configuration files, and ubus/rpcd plugins. It also contains language build helpers for Python, Go, Rust, Perl, and Lua packages, plus a shared CI/test framework.
Hercules is a C-based MMORPG server emulator for Ragnarok Online. It is a multi-process application suite: the login server handles account authentication and IP banning, the char server manages persistent character data, guilds, mail, pets, homunculi, and other account-wide state, the map server runs the real-time game world with combat, NPC scripting, instances, battlegrounds, item systems, and chat, and the API server exposes HTTP endpoints for external tools. All servers persist to MySQL/MariaDB through a shared SQL abstraction and communicate using custom binary inter-server packets. The architecture is modular at the subsystem level through interface structs containing function pointers, which also power a runtime plugin system (HPM). The primary data flow is: client packets arrive at login/char/map servers; map servers mutate real-time game state and delegate persistence to the char server; the char server executes SQL against the database; the API server proxies selected requests through login/char connections. External dependencies include MariaDB/MySQL, libconfig, cJSON, zlib, PCRE, GRF archive files, and bundled HTTP/multipart parsers. The codebase is actively maintained with CI covering GCC, Clang, MSVC, sanitizers, and multiple database backends, and it has recently transitioned toward CMake and Conan. However, it retains significant legacy weight: extensive PACKETVER conditionals, autogenerated packet header files, bundled third-party libraries, monolithic source files, and historical SQL migrations. It is a specialized game-server project rather than a general-purpose library, but several low-level infrastructure components are cleanly separated and reusable.
Nanocl is a distributed container orchestration system designed as a Kubernetes alternative, focusing on simplicity and declarative state management. The system manages workloads termed 'Cargoes' (containers), 'VMs', and 'Jobs' using Docker as the underlying runtime. It features a client-server architecture with a CLI (`nanocl`), a central daemon (`nanocld`), and auxiliary sidecar services for proxying (`ncproxy`) and DNS (`ncdns`). The architecture relies on Rust for performance and safety, utilizing `ntex` for async HTTP handling and `diesel` for database persistence. The core operational model is driven by declarative Statefiles (YAML/TOML/JSON) processed with Liquid templating. These files define the desired infrastructure state, which the daemon reconciles against the actual runtime state. The system integrates directly with the Docker daemon via the `bollard` library to manage container lifecycles, networking, and images. It features a robust event-driven architecture where state changes trigger sidecar updates, such as Nginx configuration regeneration for routing. The codebase demonstrates a modular design with shared crates for error handling, stubs, and utilities. It implements a generic repository pattern for database access and abstract lifecycle traits for resource management. The API is versioned and documented via OpenAPI/Swagger, supporting RESTful CRUD operations and real-time event streaming. While the project shows strong architectural patterns, it carries medium technical drift due to API versioning fragmentation and heavy dependency on Docker API behavior.
Sopel is an IRC bot framework written in Python designed for extensibility through plugins. It provides core IRC protocol handling, plugin management, configuration systems, and utilities for time, calculation, and web interactions. The architecture centers around a plugin system where functionality is added via decorators (@command, @rule, etc.) and plugins can access bot state, configuration, and persistent storage. Key entry points include the `sopel` CLI for running the bot, `sopel-config` for configuration management, and `sopel-plugins` for plugin operations. The system supports IRCv3 features like SASL authentication and capability negotiation, uses SQLAlchemy for persistent storage of nick/channel data, and includes numerous built-in plugins for utilities such as calculations, URL title fetching, and user tracking. While actively maintained with recent commits, the codebase shows ongoing evolution with deprecated APIs marked for removal (e.g., sopel.loader, sopel.module) indicating moderate technical drift.
SteamDepotDownloaderGUI is a Tauri v2 desktop application that provides a graphical interface for DepotDownloader, a CLI tool for downloading specific versions (manifests) of Steam games. The app allows users to input Steam credentials (or download anonymously), app/depot/manifest IDs, and an output directory. The Rust backend downloads the DepotDownloader binary from GitHub, extracts it, and spawns it as a child process via a pseudo-terminal (PTY), streaming output to an xterm.js terminal component in the Preact frontend. The frontend also includes a clipboard parser that extracts identifiers from SteamDB's copy format, auto-filling the form. The architecture is a standard monolithic desktop app with clear separation between Rust backend (Tauri commands) and Preact frontend, communicating via Tauri's invoke system. Settings for output directory naming and mobile authentication are managed through a context. The code is well-organized, with reusable input components and a clean PTY abstraction, though testing is minimal beyond a single URL validation test.
This repository is a curated list of awesome Python testing resources, organized by category (assertions, BDD, code coverage, fake data, fixtures, mocking, property-based testing, etc.). It is not a software application or data pipeline; it is a reference list of tools, libraries, and resources for Python testing. The repository contains no executable code; its primary content is a README.md file with links and brief descriptions. The CI workflows ensure link validity and spelling. It is a well-maintained, community-driven resource that serves as a comprehensive directory for Python testing tools and practices.
This is a Laravel notification channel package for sending push notifications via OneSignal. It integrates with Laravel's notification system to allow applications to send OneSignal notifications using Laravel's familiar notification syntax. The package provides a service provider, channel implementation, message builder with trait-based feature composition, and a payload factory for translating Laravel notification targeting to OneSignal parameters. It supports all major OneSignal features including targeting by player ID, email, tags, segments, external user IDs, buttons, web buttons, attachments, and silent notifications.
This repository implements a Terraform provider for managing Incus, a container and virtual machine orchestration platform. It provides full CRUD operations for Incus resources such as instances, networks, storage pools, profiles, projects, certificates, cluster groups, and server configuration, along with corresponding data sources for reading existing state. The provider is built using the Terraform Plugin Framework (v1.19.0) with some fallback to Plugin SDK v2, and communicates with Incus via its client library (github.com/lxc/incus/v7). Key entry points include the main.go provider server, internal/provider/provider.go for resource registration, and individual resource files under internal/{certificate,cluster,image,instance,network,profile,project,server,storage}. The provider supports multiple remotes, OIDC authentication, clustering, and PKI, and includes a code generation tool (cmd/generate-datasources) that produces consistent data source implementations and documentation from a YAML configuration and Go templates. Acceptance tests require a live Incus environment and cover complex scenarios like instance lifecycle, exec triggers, file uploads, and import. The codebase is well-structured with shared utilities in internal/common for config/device/file/import handling, and demonstrates a consistent pattern for state synchronization and error handling. However, it carries some technical debt from its fork of the LXD provider, including dual SDK usage and heavy boilerplate that could benefit from further abstraction.
This is a desktop application launcher for the open.mp multiplayer modification for GTA San Andreas. It acts as a server browser, providing features such as searching, filtering, and sorting game servers from a master list, querying servers via UDP for live information (players, rules, ping), and launching the game with DLL injection to connect. The application includes a favorites system, recently joined history, import/export of bookmark files, per-server nickname and SA-MP version settings, a notification system, and theme support. Built with Tauri (Rust backend for system-level operations like injection, registry access, and UDP queries) and a React/React Native Web frontend using Vite, Zustand for state management, and i18next for internationalization (32 languages). The architecture is a hybrid desktop app with heavy Windows dependency due to DLL injection and registry operations, though frontend is cross-platform. Notable technical characteristics include a custom UDP query protocol with rate limiting, a TCP IPC server for in-game overlay communication, and a modular state pattern with persisted stores.