DeepTeam is a comprehensive LLM red-teaming framework that systematically generates adversarial attacks (single-turn and multi-turn) against target AI applications and evaluates their responses for security vulnerabilities. It covers 50+ vulnerability types (bias, toxicity, PII leakage, SQL injection, jailbreaking, etc.), 20+ attack strategies (prompt injection, base64 encoding, crescendo jailbreaking, etc.), and aligns with industry frameworks (OWASP, MITRE ATLAS, NIST, EU AI Act). The system uses an LLM-as-a-judge evaluation pattern, cost tracking, and multi-turn progression logic. It also provides guardrails for runtime safety, a static code scanner for AI security issues, and trace scanning for agentic systems. The architecture follows a library pattern with an optional CLI, and integrates tightly with the deepeval framework and the Confident AI cloud platform. While the framework is functionally rich and the base abstractions are well-designed, the codebase suffers from massive copy-paste duplication across concrete vulnerability and metric implementations, leading to maintenance overhead and latent bugs.
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.
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.
Arroyo is a distributed stream processing platform written in Rust, inspired by Apache Flink. It allows users to define real-time data pipelines using SQL, which are compiled into physical plans executed across a cluster of workers. The system supports stateful operations (windows, joins, aggregations), exactly-once semantics via checkpointing, and a wide variety of connectors (Kafka, Kinesis, MQTT, Redis, filesystems, Iceberg, etc.). It includes a web UI for managing pipelines, connections, and UDFs, as well as a REST API and Kubernetes-native deployment. The architecture separates concerns into an API server, controller, worker, and compiler service, with gRPC communication. The codebase demonstrates high engineering effort with custom extensions to Apache DataFusion for streaming SQL planning, a rigorous checkpoint protocol, and a pluggable connector framework. Notable craftsmanship includes the state protocol for generation-based checkpointing, the ArrowOperator abstraction, and the two-phase commit sink pattern.
DeepLAndroid is an unofficial Android wrapper for DeepL's web translation service. It uses WebView to embed the DeepL website, stripping away non-essential UI elements via JavaScript injection to deliver a native-app feel. The app supports dark mode, text selection integration (popup or fullscreen), language state persistence, and cookie management. It is built with Kotlin and AndroidX, targeting Android SDK 36, and includes comprehensive CI/CD pipelines for building, screenshot regression testing, and deployment via Fastlane. Architecturally, the app is a monolithic Android application with a single main activity that hosts a WebView. Custom WebViewClient and WebChromeClient classes control navigation, error handling, and JavaScript injection. A notable custom component is NestedScrollWebView, which implements nested scrolling for the popup translation mode. State is persisted via SharedPreferences, and a JavaScript bridge (WebAppInterface) enables two-way communication between the WebView and Android runtime. The codebase is well-structured, includes unit and integration tests, and is localized into over a dozen languages. Key reusable components include the URL helper for constructing DeepL URLs, the cookie manager helper, and the branding asset generation pipeline. The project demonstrates solid Android engineering practices with attention to edge cases, API version compatibility, and automated quality assurance.
This repository hosts the documentation website for the Home Assistant Community Store (HACS), built with mkdocs-material. It is a static site generator project, not a runtime application. The site is built from Markdown files with custom Python hooks for HTML tag modification, Plausible analytics integration, and shortcode processing. It includes a CI pipeline for linting and building, and uses dependabot for dependency updates. The codebase is well-structured for a documentation project, with clean, reusable hooks and thoughtful theme overrides. While it does not contain application logic or data pipelines, it demonstrates good software engineering practices in the context of documentation generation.
VisualPinball.Engine is a Unity-based virtual pinball engine and editor. It reads legacy Visual Pinball .vpx tables through attribute-driven BIFF binary serialization, reconstructs playfields as Unity scenes, and runs a custom Burst-compatible physics simulation for balls, flippers, colliders, and mechs. It also packages tables into .vpe archives, provides extensive editor tooling, and includes a plugin system for game-logic engines and hardware resources. This is an application/engine project, not a data-research or analytics repository, though it contains deep domain-modeling and content-pipeline code.
Aspia is a comprehensive, cross-platform remote desktop and system administration suite. The codebase is decomposed into four primary components: a **host** (the machine being controlled), a **client** (the controlling machine), a **router** (session brokering and NAT traversal), and a **relay** (traffic forwarding). It supports Windows, Linux, macOS, and Android, with platform-specific implementations for screen capture (DXGI, X11, Wayland/PipeWire, KMS/DRM, Android MediaProjection), audio (WASAPI, PulseAudio, Oboe), input injection, and clipboard integration. The system uses encrypted communication with SRP authentication, X25519 key exchange, and AEAD ciphers (AES-256-GCM, ChaCha20-Poly1305) with key ratcheting. Beyond desktop sharing, it provides file transfer, text chat, remote terminal, task manager, system information collection, and video recording. The client features both a Qt-based desktop GUI and a custom Android UI built with native widgets. The router manages host discovery, two-factor authentication (TOTP), and relay session keys, while the relay handles peer-to-peer forwarding. The codebase is built with CMake, uses protobuf for messaging, and relies on libraries like asio, OpenSSL, libvpx, libyuv, and zstd.
This is a Go library that provides a Prometheus metrics middleware for the Gin web framework. It automatically collects and exposes standard HTTP metrics such as request count, request duration, response size, and request size via a `/metrics` endpoint. The library supports custom labels, a URL label mapping function to control cardinality, optional push gateway integration, and the ability to disable request body reading for performance. The architecture is a single package (`ginprometheus`) with a clean configuration API (`NewWithConfig`) and backward-compatible constructors. The middleware is applied to a Gin engine via `Use()` or `UseWithAuth()`. External dependencies are limited to Gin, the Prometheus client_golang library, and logrus for logging. The code is well-structured, idiomatic Go, with unit tests and CI.
spank is a macOS CLI tool that detects physical hits/slaps on Apple Silicon MacBooks via the accelerometer and plays audio responses. It requires sudo for IOKit HID access to the accelerometer and is built as a single-file Go application. The tool reads raw accelerometer data, runs vibration detection algorithms (STA/LTA, CUSUM, kurtosis, peak/MAD), and triggers audio playback when impacts exceed a configurable amplitude threshold. It offers multiple modes: pain (random 'ow!' sounds), sexy (escalating responses based on slap frequency), halo (Halo death sounds), lizard (similar to sexy but with lizard sounds), and custom (user-specified MP3 directory). Audio playback uses the beep package with resampling to a fixed sample rate, optional volume scaling based on impact force, and adjustable playback speed. The application uses Cobra for CLI parsing and Fang for command execution, with audio assets embedded via go:embed. Key reusable components include the audio resampling function that handles sample rate conversion and speed adjustment, and the amplitude-to-volume mapping function that applies a logarithmic curve for natural volume scaling.
This repository is a curated collection of .gitignore file templates for a wide range of programming languages, frameworks, editors, and operating systems. It serves as the source for GitHub's built-in .gitignore template chooser when creating new repositories. The repository is organized into root-level templates for common technologies, a Global/ directory for editor/OS-specific rules, and a community/ directory for specialized or versioned templates. Each file is a self-contained list of file patterns to exclude from version control, following best practices for the respective technology. The templates are maintained through community contributions and a stale PR workflow. While the repository contains no executable code, its value lies in the curated, accurate, and up-to-date ignore rules that help developers avoid committing unnecessary or sensitive files.
This repository is a collection of Claude/Anthropic skills and platform documentation rather than a standalone application. It contains skill definitions (SKILL.md files), MCP server evaluation guidance, managed-agents documentation, and supporting tooling such as schema definitions and build scripts. The dominant character is developer-facing content and reusable patterns for building LLM agents, with some executable scripts for validation and report generation. It provides structured output schemas for evaluation pipelines (grading, benchmark, comparison, analysis), a validator hierarchy for XML/XSD-based skill files, and a security-conscious file I/O example in build-report-lite.mjs. It also documents managed agents, platform availability, and MCP best practices. The repository is not a data research project; there are no notebooks, data pipelines, or model training scripts. Maintenance is active, but technical drift is medium due to version-sensitive SDK references, manually maintained platform availability tables, and multiple language-specific examples that must be kept in sync. The code and schemas are generally well-structured and reusable, though some paths are hardcoded and some documentation is tightly coupled to generator scripts.
This repository is the Notes app for ownCloud Server, a distraction-free note-taking plugin that stores notes as plain text files in the user's cloud storage. It provides a web-based editor with markdown support (via mdEdit) and syntax highlighting (via Prism), along with a RESTful API (v0.2) for third-party integration. The backend is PHP 8.3 following ownCloud's app framework: controllers handle HTTP requests, services contain business logic, and a simple entity layer maps files to Note objects. The frontend is an AngularJS 1.8 single-page application using Restangular for API communication, with custom directives for autofocus, debounced saving, and editor integration. Notes are persisted as .txt, .md, .org, or .note files in a per-user 'Notes' folder, with filename collision resolution and directory traversal prevention. The app supports favoriting via ownCloud's tag system and remembers the last viewed note across sessions. The codebase is well-structured with unit tests for both PHP and JavaScript, acceptance tests, and CI/CD pipelines. It has been actively maintained with recent security updates (patched AngularJS, underscore, Prism) and a move to in-repo translations. While the architecture is standard for ownCloud plugins and the frontend uses an older AngularJS version, the implementation is clean, the business logic is robust, and there are a few reusable patterns like the async save queue and a Python duplicate-key checker for translation files.
Conky is a free, lightweight system monitor for X11, Wayland, and macOS that displays system information on the desktop or in alternative output modes (console, file, HTTP). It collects data from /proc, /sys, sysctl, and various APIs to report CPU, memory, disk, network, processes, sensors, audio players, mail, RSS, and more. The architecture is modular: data sources are registered as text objects with scan/print/free callbacks, output backends are selected at runtime (X11, Wayland, ncurses, console, file, HTTP), and Lua scripting provides configuration and extensibility via tolua++ generated bindings. A callback system handles periodic data fetching with deduplication and thread safety, and a priority queue supports top process sorting. The codebase is written in C++ with some C, uses CMake build system, and includes a comprehensive test suite using Catch2. It supports Linux, BSDs, Haiku, Solaris, and macOS with platform-specific backends. The project demonstrates several well-crafted reusable components: a generic priority queue, a callback system for periodic tasks, a typed configuration settings framework with Lua integration, a structured logging wrapper around spdlog, and a macro-generated X11 event variant pattern. These components exhibit non-obvious skill and can be extracted for use in other C++ projects. However, the codebase also shows signs of technical drift with bundled third-party libraries (Vc, tolua++, spdlog) that may lag behind upstream, and some platform-specific backends have incomplete implementations.
This repository implements a dual-console emulator targeting PlayStation 3 (RPCS3) and PlayStation 4 (RPCSX/Orbis). The codebase is a large C++ project with a modular architecture: kernel emulation layers for both consoles (syscalls, threads, memory management), CPU emulation (PPU/SPU for PS3, GCN for PS4), GPU emulation (RSX for PS3 with OpenGL/Vulkan backends, GCN shader compiler for PS4), audio backends (Cubeb, FAudio, ALSA), input handlers (DS3, DS4, XInput, PS Move, etc.), network emulation (RPCN, UPnP), and a custom overlay UI system. The project is under active development with frequent commits, though many PS3 firmware modules remain as stubs or placeholders. The architecture separates PS3 and PS4 emulation into distinct directories (`rpcs3/` and `rpcsx/`), sharing a common utility library (`rx/`) that provides synchronization primitives, memory management, and debugging tools. The GPU emulation is particularly sophisticated, featuring a custom shader intermediate representation (IR) for AMD GCN instructions with optimization passes and SPIR-V/GLSL backends. The codebase also includes a comprehensive serialization framework for savestates, a YAML-based configuration system, and a texture cache predictor for GPU performance. Key entry points include the main emulator executables (built from `rpcs3/` and `rpcsx/`), the kernel syscall handlers in `kernel/orbis/` and `kernel/cellos/`, the GPU renderers in `rpcs3/Emu/RSX/` and `rpcsx/gpu/`, and the PS3 firmware HLE modules in `ps3fw/`. External dependencies include Vulkan, OpenGL, FFmpeg, WolfSSL, SDL2, libusb, and several audio libraries. The project is primarily a software application for console emulation, with significant reverse-engineering and research components.
This repository contains the formal LaTeX specification of the JAM (Join-Accumulate Machine) protocol, a proposed blockchain system by Dr. Gavin Wood. It is not a software application but a reference document defining the protocol's state transitions, cryptographic primitives, virtual machine (PVM), consensus mechanism (Safrole), and accumulation pipeline. The codebase consists entirely of LaTeX source files, a bibliography, build scripts, and assets for generating a PDF. The specification is mathematically rigorous and structured for formal verification or implementation. While not a runnable system, it demonstrates high craftsmanship in consistent notation, modular sectioning, and automated build processes. The project is actively maintained with versioning and spell-checking, but lacks automated testing or CI for the specification itself.
This repository is a full-stack application for building knowledge graphs from unstructured data using Large Language Models (LLMs). The backend, built with FastAPI and LangChain, ingests documents from multiple sources (local files, web pages, YouTube, Wikipedia, S3, GCS), chunks them, and uses an LLM to extract entities and relationships, which are stored in a Neo4j graph database. The frontend, a React/TypeScript application, provides a user interface for uploading files, configuring extraction (schema, LLM model, chunking), visualizing the resulting graph, and interacting with the data through a retrieval-augmented generation (RAG) chatbot with multiple retrieval modes (vector, graph, fulltext, hybrid). The system includes post-processing features like community detection, deduplication, and orphan node cleanup, as well as token usage tracking and evaluation metrics (RAGAS). While primarily an application with a web UI, it also contains experimental notebooks (GraphRAG, chunk size evaluation) that serve a data research purpose, making it a hybrid codebase with a dominant application character.
picom is an X11 compositor that provides desktop visual effects such as window shadows, fading, blur, rounded corners, and animations. It is a fork of Compton and serves as a lightweight compositing manager for X11 window managers. The system is built around a modular architecture with pluggable rendering backends (XRender and OpenGL), a damage-based incremental renderer, a window tree manager, and a custom animation scripting engine. Key entry points include the main session initialization in `src/picom.c`, the event loop driven by libev, and the backend initialization. Data flows begin with X11 events (e.g., window creation, property changes) processed by the event handler, which updates the window tree and triggers damage computation. The renderer then builds a list of backend commands from window layers, applies damage culling, and presents the final image via the selected backend. External dependencies include X11 libraries (xcb, xlib, xrender, xdamage, xcomposite, xpresent, xrandr), libconfig for configuration, libev for event handling, pixman for region operations, and optional OpenGL, dbus, and pcre2. The project is actively maintained with a comprehensive test suite and CI/CD pipelines.
Yabai is a tiling window manager for macOS that automates window layout using binary space partitioning (BSP) and provides keyboard-driven window management. It operates as a background daemon, managing spaces, windows, and displays through a combination of public macOS accessibility APIs and private frameworks (notably SkyLight). The application features an event-driven architecture that reacts to system events (window creation, focus changes, space transitions) and applies user-defined rules to control window behavior. The codebase is structured around several managers (display, space, window, view, process) and a central event loop. A scripting addition (OSAX) is injected into the Dock.app to perform privileged operations via private APIs, communicating with the main yabai process over a Unix socket. Configuration and control are exposed through a command-line interface (yabai) and can be integrated with hotkey daemons like skhd. While the core functionality is well-implemented, the project faces significant maintenance challenges due to its reliance on undocumented private macOS APIs, which require frequent updates to remain compatible with new macOS releases. The codebase includes version-specific workarounds and architecture-specific implementations (for x86_64, arm64, and arm64e) to address these challenges. Despite these complexities, yabai remains a popular and actively maintained tool for macOS window management. Reusable components include low-level utilities such as a generic hash table, memory pool, dynamic string buffer, and logging system, which are decoupled from yabai-specific logic and could be extracted for use in other C projects.
pysheeet is a comprehensive Python cheat sheet and reference repository. Although it is classified as an application because it contains a Flask web server and operational scripts, its dominant character is educational reference content: a Sphinx-built documentation site with runnable, tested code examples under `src/basic/`, covering core Python, asyncio, concurrency, networking, security, databases, C/C++ extensions, and more recent LLM/HPC topics. The repository also ships a Claude Code plugin that exposes the cheat sheets as AI skills. Beyond documentation, the repo contains real operational artifacts for distributed LLM work: Slurm/Docker launch scripts for vLLM, SGLang, and TensorRT-LLM, Megatron training recipes, NCCL broadcast benchmarks, and Ray-on-Slurm patterns. These scripts demonstrate practical HPC skills such as EFA/NCCL tuning, multi-node container orchestration, and profiling with nsys/VizTracer. The code quality is solid overall: examples are well-structured, many have pytest coverage, and the Flask serving layer is security-conscious. The main weaknesses are duplication across LLM vendor scripts, hardcoded cluster-specific paths, and documentation that occasionally references older Python or library versions, which creates moderate technical drift.