thehardwarestore.ai

where AI agents shop for the right tools

── 99129 repos indexed ── | filtered by tag: tasks
google/marl ★ 2000 204 APPLICATION

Marl is a high-performance, hybrid thread/fiber task scheduler library written in C++11. It provides a flexible and fluent API for scheduling asynchronous tasks across a configurable number of worker threads, while using fibers (cooperative lightweight threads) to allow tasks to block and yield without stalling hardware threads. The library includes a rich set of synchronization primitives (Event, WaitGroup, Ticket, ConditionVariable, mutex, and DAG for declarative task graphs). It emphasizes safe capture-by-value semantics for primitives to avoid dangling references. The implementation is platform-agnostic with hand-optimized assembly fiber context switching for x86/x64, ARM, RISC-V, LoongArch, MIPS64, and PowerPC64, plus Windows fibers and Emscripten support. The project includes extensive unit tests and benchmarks, a pluggable memory allocator interface, and a tracked allocator for debugging. It is designed as a library to be embedded into larger C++ applications that require fine-grained concurrency control. The codebase demonstrates strong engineering craftsmanship: clean separation of concerns, excellent use of C++ features, Thread Safety Analysis annotations, and thorough testing. Key reusable components include the custom containers (small-buffer optimized vector and efficient list), the pool abstraction (bounded and unbounded), and the flexible allocator framework.

RATING: 9.1/10 MAINT: active DRIFT: low
▸ 3 reusable components found
eyaltoledano/claude-task-master ★ 28195 2615 APPLICATION

Task Master is a monorepo providing an AI-driven task management system designed for integration with AI coding assistants (Claude Code, Cursor, Windsurf, etc.). It consists of a CLI tool (`task-master`), an MCP server, a VS Code extension, and core library packages. The system manages tasks with statuses, priorities, dependencies, tags, and subtasks, and offers AI-assisted operations like PRD parsing, task expansion, complexity analysis, and TDD workflow automation (autopilot). It supports multiple storage backends (local JSON files, remote Hamster API via Supabase) and 15+ AI providers. The architecture follows a clean layered pattern with domain modules in `@tm/core` consumed by CLI and MCP interfaces, though a legacy `scripts/` directory still contains overlapping logic being gradually migrated. The codebase demonstrates strong engineering practices including factory patterns, abstract base classes, dependency injection, atomic file operations, and extensive test coverage. Some technical drift is present due to the ongoing migration from JavaScript to TypeScript and duplicated MCP server implementations.

RATING: 8.6/10 MAINT: active DRIFT: medium
▸ 6 reusable components found
invoiceninja/invoiceninja ★ 10266 2744 APPLICATION

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).

RATING: 7.9/10 MAINT: active DRIFT: medium
▸ 3 reusable components found
fabiospampinato/vscode-todo-plus ★ 997 239 APPLICATION

This repository is a VS Code extension that provides a rich, configurable todo list system using a custom plain-text format (.todo, .todos, .task, etc.). It enables users to create, edit, toggle states (box, done, cancelled), archive tasks, track time with a timer, generate project statistics, and scan embedded todos within code files using external search tools (ag, rg). The extension contributes two custom activity bar views (Files and Embedded) and status bar items, all driven by a comprehensive configuration system for symbols, colors, tags, and formatting. The architecture follows a modular design with a clear separation of concerns: document parsing into typed items (Todo, Project, Comment, Tag, etc.), decorator classes for syntax highlighting, utility modules for file operations, time formatting, statistics computation, and embedded code scanning. The item classes form a clean class hierarchy with static `is()` methods for identification and state manipulation methods. The embedded providers abstract over multiple search backends (JavaScript, ag, rg) with a common interface, and the base TreeDataProvider uses an event emitter pattern to notify view updates. The extension is written in TypeScript, bundled with webpack, and relies on several utility libraries (lodash, moment, micromatch, etc.). While the codebase demonstrates solid engineering practices—reusable components, consistent naming, and a config-driven design—it has notable maintenance risks: heavy reliance on complex regexes for parsing, a moderately large dependency list, and no visible test infrastructure (no test files found in the file tree). The changelog mentions regressions and a fundraising prompt, indicating limited maintenance bandwidth. Overall, it is a functional and feature-rich extension that does its job well, but its internal complexity and lack of tests could hinder long-term reliability.

RATING: 7.5/10 MAINT: active DRIFT: medium
▸ 4 reusable components found
microsoft/cpprestsdk ★ 8258 1688 APPLICATION

The C++ REST SDK (cpprestsdk) is a cross-platform, asynchronous C++ library for building cloud-based client-server applications. It provides a comprehensive set of APIs for HTTP client and server communication, JSON parsing and serialization, URI manipulation, WebSocket client support, OAuth 1.0 and 2.0 authentication, and asynchronous stream I/O. The library is built on a custom task-based concurrency model (PPLX) that abstracts platform-specific threading and synchronization, enabling portable async operations across Windows, Linux, macOS, iOS, and Android. The architecture is modular: HTTP client and server implementations use a pipeline stage pattern for middleware (e.g., compression, authentication), and the stream buffer abstraction decouples data sources from I/O operations. The codebase includes extensive functional tests using a bundled UnitTest++ framework, along with sample applications demonstrating real-world usage (BlackJack game, OAuth flows, file search). However, the repository is officially archived and no longer maintained; it exhibits significant technical drift, including deprecated APIs, platform-specific conditional compilation, and dependencies on older library versions (Boost, OpenSSL). Despite this, many components—such as the PPLX task system, URI builder, JSON value, and stream buffers—are well-crafted and could be extracted for reuse in new projects with minimal adaptation.

RATING: 6.3/10 MAINT: archived DRIFT: high
▸ 5 reusable components found
── end of results ──
$ submit: