AlDente is a macOS menu bar application designed to extend MacBook battery lifespan by limiting the maximum charging percentage. The application consists of two main components: a user-facing interface that runs with standard user privileges, and a privileged helper tool that communicates with the System Management Controller (SMC) to enforce battery charge limits. When the user sets a charge limit (e.g., 80%), the helper tool writes to the BCLM SMC key to prevent charging beyond that percentage. The app also monitors battery state and can prevent system sleep to maintain the charge limit when AC power is connected. The architecture cleanly separates concerns between the privileged operations (handled by the helper tool) and the user interface. Communication between components occurs via NSXPCConnection with a well-defined protocol (HelperToolProtocol). The application demonstrates solid macOS development practices including proper use of delegates for status updates, efficient polling for battery state, and clean separation of UI logic from business logic. While the repository contains legacy code from an older open-source version (as noted in the README), it includes a particularly valuable reusable component in SMC.swift. This file provides a robust, well-encapsulated interface for accessing the SMC on Intel-based Macs, handling all the low-level IOKit interactions, data type conversions, and error handling. The SMC implementation correctly manages the SMCParamStruct structure, supports various data types (UInt8, UInt32, FPE2, SP78), and includes extensions for reading temperature, fan speeds, and other sensor data.
Haaukins is a cybersecurity training and Capture The Flag (CTF) platform developed at Aalborg University. It orchestrates isolated lab environments for teams, combining Docker containers and VirtualBox VMs to deliver challenges. The system is built as a set of gRPC microservices: a central daemon manages event lifecycle, team assignments, and challenge verification; a store service provides persistence; and an exercise service defines challenge configurations. Participants access labs via a web frontend (Amigo) using browser-based RDP (Guacamole) or WireGuard VPN. The daemon also handles DNS/DHCP per lab subnet, real-time scoreboards via WebSocket, and keylogging for monitoring. The CLI client (hkn) allows administrators to manage events, teams, and exercises. The architecture is modular with clean interfaces for virtualization (Docker/VirtualBox) and storage (in-memory with hooks or gRPC backend), though some components show tight coupling and aging dependencies.
This repository is the Motoko Base Library, a standard library for the Motoko programming language targeting the Internet Computer platform. It provides fundamental types, data structures, and utilities for building smart contracts (canisters). The library includes purely functional collections (List, Trie, Deque), mutable containers (Buffer, HashMap, TrieMap, Stack), red-black tree based ordered sets and maps (OrderedSet, OrderedMap), fixed-width integer types (Int8-64, Nat8-64), Float, Text, Principal, and low-level IC APIs (ExperimentalCycles, StableMemory, CertifiedData, Timer, Random). The code is well-documented with examples and complexity annotations, and includes a comprehensive test suite using the mo:matchers framework. However, the README explicitly states this package is superseded by the official dfinity/motoko-core package, indicating migration is recommended. Some duplication exists between OrderedSet and OrderedMap (shared RB-tree logic), and several deprecated functions are present. The repository is in maintenance mode with periodic updates for compatibility, but active development has shifted to the core package.
This repository is a curated 'awesome' list of falsehoods programmers believe in. It is not a software application or data pipeline; it is a markdown-based collection of links to external articles, libraries, and resources organized by topic (dates, names, geography, etc.). The repository contains no executable code, no API endpoints, no CLI tools, and no data transformations. Its value lies in the curation and editorial quality of the links, along with a well-documented contribution guide and automated linting workflows (lychee for link checking, typos for spelling, awesome-lint for list formatting). The infrastructure includes GitHub Actions for autofix, autolock, docs, labels, and linting, all reused from a shared workflow repository (kdeldycke/repomatic). The pyproject.toml provides reusable configuration for link exclusion patterns and typo detection. While not a software project, the repository demonstrates high standards for maintaining a community-curated resource.
This repository is a community-maintained interactive web map for Red Dead Online (RDO), built as a single-page application using Leaflet. It provides players with a comprehensive overlay of in-game locations, including collectibles, animals, plants, shops, hideouts, random encounters, legendary animal spawns, free roam events, and daily challenges. The application is entirely client-side, loading static JSON data files and rendering markers on a Leaflet map with custom styling, clustering, and heatmaps. It features a rich side menu for filtering, a settings panel with localStorage persistence, user-customizable pins, and a localization system supporting over 30 languages via Crowdin. The architecture is modular, with separate JavaScript files for each map category (e.g., animals.js, plants.js, bounties.js) and utility modules for settings, language, and data loading. External dependencies include Leaflet, Bootstrap, Tippy, and several Leaflet plugins, all loaded via CDN or vendored copies. The repository also contains development scripts for extracting game data from binary files and generating route optimization algorithms. While primarily an application, it has a strong data component with curated JSON datasets that must be manually updated when the game changes.
Despite being classified as application-oriented, henki_ros2_best_practices contains no executable software. It is a documentation/standards repository: a single, carefully authored Markdown document (henki_ros2_best_practices.md) codifying architecture and clean-code guidelines for ROS 2 development, plus a README explaining how to integrate the document into AI coding workflows (e.g., Claude Code via CLAUDE.md) and a pointer to a companion examples repo comparing agent-generated ROS 2 packages with and without the practices applied. The actual deliverable is a concise, opinionated standards document covering node single-responsibility, separation of application logic from ROS 2 communication, launch file conventions (XML preferred), YAML config-based parameter handling, throttled logging, semantic custom message interfaces in '_msgs' packages, service-vs-action selection with enum-style error codes, C++ for performance-critical loops, SingleThreadedExecutor preference, rosdep/vcs-tool dependency management, package documentation requirements, and unit-test-first strategies that avoid flaky ROS communication sleeps. In production, this repository functions as a knowledge artifact rather than a running system: humans read it as a reference, and AI coding agents consume it as an enforced standard when generating ROS 2 packages. There are no API endpoints, data flows, or runtime dependencies; its 'architecture' is the structure and specificity of the guidelines themselves. The document is self-contained and could be dropped into any ROS 2 team's repository or agent configuration with minimal adaptation, making it a genuinely reusable engineering asset despite the complete absence of code.
Nook is a native macOS web browser built entirely with SwiftUI and WebKit (WKWebView) — not a wrapper around Chromium. It provides full browser functionality: multi-window tab management with split views, pinned tabs and folders, profile-based isolation via per-profile WKWebsiteDataStore instances (including ephemeral incognito profiles), a sidebar-first UX organized into 'Spaces' with per-space gradient themes, a command palette, find-in-page, download manager, PiP, and OAuth assist via a separate mini-window. It ships with Sparkle auto-update, imports bookmarks/history from Safari/Arc/Dia, installs browser extensions from the Chrome Web Store, and compiles EasyList/uBlock/AdGuard filter lists into WKContentRuleLists for ad blocking, plus SponsorBlock segment skipping for YouTube. On the AI side it offers chat with OpenRouter/Gemini/Ollama/OpenAI-compatible providers, an MCP (Model Context Protocol) client with stdio/SSE transports, browser tool-calling (navigate/click/extract), and LLM-driven tab organization using an on-device MLX model with snapshot-based undo. Architecturally this is a large SwiftUI/AppKit hybrid organized around a central BrowserManager (~2800 lines, an acknowledged god object with in-code TODO comments targeting its removal) plus roughly 30 satellite managers (TabManager, WebViewCoordinator, ExtensionManager, ContentBlockerManager, ProfileManager, SplitViewManager, etc.). Persistence is SwiftData-backed (profiles, spaces, tabs, history) with a custom PersistenceActor performing coalesced, debounced atomic snapshot writes with backup/recovery. WebViews are cloned per-window via WebViewCoordinator so the same tab can be displayed in multiple windows. Extension support uses the native WKWebExtension APIs (macOS 15.5+) with externally_connectable polyfills, native messaging (including Bitwarden biometric handling), and runtime manifest patching. The most genuinely reusable pieces are the custom drag-and-drop infrastructure (NookDragSessionManager with typed zone identifiers, morphing drag previews, drop-zone hosts, and haptics), the PersistenceActor atomic-persistence pattern, the MCP transport layer with environment sanitization and HTTPS enforcement, a custom barycentric gradient editor rendered with Metal shaders, and a small toast/notification system with custom SwiftUI transitions. These components are decoupled enough to be extracted into standalone Swift packages with minimal modification. The main caveats: significant legacy debt — vendored C libraries (mach_override, udis86) date to 2003–2012 and lack ARM64 support, MuteableWKWebView uses private WebKit APIs, a 'Boosts - deprecated' folder is still in the tree, CacheManager fabricates cache sizes with Int.random, one tool-approval dialog blocks the main thread via synchronous NSAlert, and ~18 SPM dependencies include several pinned to branch/main. Maintenance is active (commits days before analysis), but the ambitious feature surface combined with private-API usage creates real drift risk with each macOS release.
termbox-go is a minimalistic Go library for building text-based user interfaces (TUIs). It provides a clean API for cell-based screen manipulation, keyboard and mouse input, and multiple output modes (normal, 256, 216, grayscale, RGB). The library abstracts over Unix terminals (via terminfo and ANSI escape codes) and the Windows console (via Win32 API). Architecture uses double-buffering: a back buffer is modified by the user, then flushed to a front buffer and rendered to the terminal. Input events are processed asynchronously via a goroutine and channel. The library is stable and widely used (godit, termui, gocui, etc.) but the README explicitly states it is no longer actively maintained; users may consider gdamore/tcell as a more modern alternative. The codebase is well-organized with platform-specific files using Go build tags, though it exhibits some global state and sparse test coverage.
This repository provides a tool for repackaging official Zig programming language releases as Python binary wheels. The core functionality resides in make_wheels.py, which downloads Zig tarballs, verifies their integrity, extracts contents, and rebuilds them as installable Python wheels with appropriate metadata and entry points. The architecture is straightforward: a command-line Python script supported by a GitHub Actions workflow for automated building and deployment. The tool enables Python developers to easily install and use the Zig toolchain (including the zig cc compiler) as a dependency via pip. Key features include reproducible builds (bit-for-bit identical outputs regardless of build environment), support for multiple platforms (Windows, macOS, Linux variants), and automated publishing to PyPI with provenance attestations.
jsf is a Python library that generates fake data conforming to JSON schemas. It provides programmatic and CLI interfaces for creating realistic test data, supports custom data providers, maintains state for dependent data generation, validates output against schemas, and integrates with FastAPI for automatic API documentation. The architecture follows a modular design where each JSON schema type is handled by a specific class in jsf/schema_types/, with the core parsing logic in jsf/parser.py. The project uses Pants for building, has comprehensive test coverage, and maintains active CI/CD pipelines with automated releases based on conventional commits.
The code is pragmatic but not production-polished: there is duplicate legacy device code (devices.ts, devices-old.ts, devices-refactored.ts), reliance on global namespaces, handwritten Electron type shims, hardcoded Homebrew paths, and no automated test suite beyond module-loading smoke tests. Many helper modules are self-contained enough to lift into other macOS/Electron admin tools. Overall, this is a functional, actively maintained utility with solid safety checks and i18n work, but with maintainability debt from duplication, fragile global state, and environment assumptions.
Telecrawl is a Go CLI application that imports Telegram Desktop's `tdata` session data and creates encrypted, versioned backups. It reads the local Telegram Desktop data directory (platform-specific paths for macOS/Linux), parses the tdata format, and stores chat archives in a SQLite-backed store with merge/restore/tombstone semantics. The CLI exposes commands for import, backup, restore, search, and media reference handling. It runs as a Docker image with a non-root user, read-only tdata mount, and persistent /data volume. Architecturally, it is a monolith with a `cmd/telecrawl` entry point delegating to `internal/cli`, which orchestrates importers (`tdata`, `postbox`) and the `internal/store` persistence layer. The store handles schema migrations, snapshot merging, and search. Backup uses a Git remote pattern with safety guards against path overlaps. The codebase includes CI workflows, release automation, and security checks. Maintenance is active with frequent dependency bumps and CI. However, the store package is large and mixes concerns, and tdata/postbox importers are format-specific and may break if Telegram changes its data format. Hardcoded platform paths and schema backfill migrations are drift risks. Despite some data-audit scripts and fixture data, the dominant character is a CLI application.
This is a custom firmware project for the EleksTubeHAX family of IPS nixie-tube-style desk clocks. It is an embedded C++ application targeting ESP32 microcontrollers (ESP32, ESP32-S2, S3, C3) using the PlatformIO build system. The firmware provides a full-featured digital clock with customizable clock faces (stored as BMP or CLK images in LittleFS), WiFi connectivity (WPS, static IP), NTP time sync with adaptive polling intervals, battery-backed RTC support (DS1302, DS3231, RX8025T), and RGB backlight control (WS2812 LEDs) with multiple effects (pulse, breath, rainbow). It includes an on-device menu system with button (and gesture sensor) navigation, Home Assistant MQTT auto-discovery for remote control, and IP geolocation for automatic timezone/DST detection. The architecture is a monolith with clear class separation (Backlights, Buttons, Menu, TFTs, Clock, ChipSelect, WiFi_WPS, MQTT_client, IPGeolocation). The code heavily uses conditional compilation (#ifdef HARDWARE_*) to support over a dozen physical clock variants (EleksTube, SI HAI, Xunfeng, IPSTube, MarvelTubes, etc.), which increases complexity but enables a single codebase to target many boards. The project includes forked and modified libraries (TFT_eSPI, NTPClient, RTC_RX8025T, SparkFun APDS9960) integrated into the repo, which may diverge from upstream over time.
pytest-flask is a pytest plugin designed to simplify testing of Flask applications. It provides fixtures for Flask test clients, live servers (for end-to-end testing), configuration access, and content negotiation headers. The plugin automatically manages request contexts and patches response classes to enable easy JSON response testing. Architecture-wise, it follows pytest's plugin system with entry points defined in setup.cfg, separating concerns into fixtures, live server management, and plugin registration. The live_server fixture spawns a subprocess running the Flask app and handles health checks via socket connections, while autouse fixtures ensure proper test isolation by pushing request contexts and applying configuration markers. External dependencies include pytest, Flask, and Werkzeug.
Paper2Code is a research system that automatically generates runnable code repositories from machine learning research papers. The core pipeline, PaperCoder, uses a multi-agent LLM architecture (planning→analysis→coding) implemented as a sequence of Python scripts orchestrated via shell commands. It accepts papers in PDF (converted to JSON via s2orc-doc2json), JSON, or LaTeX format, and produces a complete Python project with config, model definitions, training loops, and evaluation scripts. The codebase supports both OpenAI API (o3-mini by default) and open-source models via vLLM (e.g., DeepSeek-Coder-V2-Lite-Instruct). It includes a debug stage that iteratively fixes runtime errors using LLM-generated SEARCH/REPLACE patches, and an evaluation module that scores generated repositories (reference-free or reference-based) using LLM judgment. The repository also bundles the Paper2Code benchmark dataset (90 papers from top ML conferences with gold repositories) and prompts for evaluation. Although primarily an application, it has research artifacts (evaluation scripts, prompt templates, benchmark data) that give it a hybrid character.
This repository is a translation management platform for the React documentation website (react.dev). It provides tools to create new translation repositories, automatically sync changes from the source documentation to translation forks, and displays a dashboard tracking translation progress across language teams. The architecture consists of Node.js scripts for backend operations (creation and synchronization) and a Next.js application for the frontend dashboard. Key entry points include the create-translation.js script for setting up new translations, sync-translations.js for periodic synchronization (triggered via GitHub Actions), and the Next.js web interface for viewing progress. The system relies on GitHub API for repository management, Vercel for deployment, and uses a scheduled workflow to keep translations updated with upstream changes.
Pomatez is a cross-platform Pomodoro timer desktop application built with a monorepo architecture managed by Lerna and Yarn workspaces. It provides a customizable timer with focus/break sessions, task management, system tray integration, desktop notifications, full-screen break enforcement, Discord Rich Presence, and auto-update capabilities. The application is implemented with two backend options: a primary Electron backend and an experimental Tauri (Rust) backend, both sharing a common React frontend (renderer) and a shared constants package. The frontend uses Redux Toolkit for state management, styled-components for theming (light/dark), react-i18next for internationalization (English, Spanish, Chinese, Japanese), and react-beautiful-dnd for task list drag-and-drop. The repository also includes a Gatsby-based marketing website for downloads and feature showcases. The core timer logic is driven by a React context (CounterContext) that manages countdown, session transitions, and full-screen break states. User settings and tasks are persisted to localStorage (and electron-store for the Electron backend) with debounced Redux store persistence. The application exposes a connector abstraction (ConnnectorContext) that decouples the frontend from the backend platform, allowing the same UI code to work with both Electron and Tauri via platform-specific connectors. The Electron main process handles window management, system tray, global shortcuts, and auto-updates, while the Tauri backend provides similar functionality through Rust commands. External dependencies include node-notifier for notifications, discord-rpc for Rich Presence, and electron-updater/tauri-plugin-updater for auto-updates. The codebase demonstrates solid engineering practices with reusable UI components, custom hooks, and a well-organized store structure. However, it shows signs of technical drift with outdated dependencies (React 16, TypeScript 4.9.4, deprecated husky v4) and the dual-backend approach introduces code duplication and maintenance overhead. Test coverage is minimal, with only one unit test file found. The Tauri backend is marked as experimental and has some incomplete features (e.g., set_ui_theme is a no-op). Overall, Pomatez is a functional and feature-rich desktop application with a clean frontend architecture, but its backend complexity and dependency age suggest moderate refactoring needs.
A well-structured monorepo for building cross-platform Expo (React Native) applications using pnpm and Turborepo. The repository demonstrates a scalable architecture with three shared packages (eslint configuration, reusable UI components, and a home feature) and a single example Expo app that leverages Expo Router for navigation, react-native-reanimated for animations (parallax scroll, wave animation), expo-haptics for haptic feedback, and expo-symbols/expo-image for platform-adaptive icons and images. The code is organized following modern React Native best practices: typed routes, strict TypeScript, automatic dark/light mode, absolute imports, and Jest + testing-library/react-native tests for components. CI/CD is fully implemented via GitHub Actions with workflows for linting, building, testing, EAS deployments, and preview builds. While the application itself is a simple template (home screen with steps, an explore screen with informational collapsibles, and a modal), the architecture showcases a effective monorepo workflow with Turborepo caching and pnpm workspace protocols. The most notable technical components are a cross-platform icon abstraction (SF Symbols to Material Icons), a standalone parallax scroll view with Reanimated, and an in-app browser link adapter—all of which are modular and easily extracted for other projects.
This repository is a comprehensive .NET SDK for integrating with the WeChat (Weixin) ecosystem, covering Official Accounts (MP), Enterprise WeChat (Work), Mini Programs (WxOpen), Open Platform, and WeChat Pay (TenPay V2/V3). It provides strongly-typed API wrappers for hundreds of WeChat endpoints, message/event handling with a rich class hierarchy, caching abstractions, and utilities for signature verification, encryption, and OAuth. The architecture is a modular monolith with separate packages per platform, sample MVC applications for .NET 4.5/8/10, and dependency injection support via registration modules. Key entry points include static API classes (e.g., `CommonJsonSend.Send<T>()`), message handler base classes, and container-based token management. The SDK also includes experimental components such as an MCP server for AI tool integration and a browser plugin for development assistance. The codebase demonstrates consistent patterns: base result classes with error code handling, container caching with capability flags, extension methods for payment notification decryption, and automatic access token refresh via `ApiHandlerWapper.TryCommonApi`. While the SDK is actively maintained and supports modern .NET versions, it carries some technical debt from legacy .NET 4.x support, duplicated DTOs across platforms, and incomplete test coverage that relies on live credentials. Overall, it is a functional and widely-used SDK (8900+ stars) with solid engineering practices but room for improvement in code consolidation and test automation.
This repository is a Ruby gem (`badge`) that programmatically overlays badges (e.g., beta/alpha ribbons) or shields (from shields.io) onto iOS, tvOS, and Android app icons. It is primarily used as a CLI tool or integrated via a fastlane plugin. The core logic uses MiniMagick (ImageMagick) to composite images, with optional SVG-to-PNG conversion via rsvg-convert for crisp shields. The gem intelligently parses Xcode asset catalog `Contents.json` files to detect legacy, single-size, or layered icon formats, and supports a wide range of customization options including dark/light themes, custom badge images, shield parameters, gravity, geometry, scaling, and grayscale conversion. It overwrites icons in place and preserves the original file format (PNG, WebP, JPEG). The codebase is well-structured with clear separation of concerns (options, runner, icon catalog, base constants) and includes a comprehensive smoke test suite (20 end-to-end cases). While the gem is functional and widely used (974 stars), it shows minor technical debt such as a load-bearing typo (`retry_attemps`), broad exception rescues, and reliance on the deprecated `open-uri` library. The icon catalog parser is a standout component that could be extracted for reuse in other Xcode asset catalog tooling.