agentOps · tooling

GitHub Actions

12 production projects and 0 rule sets built with GitHub Actions.

Production projects

Headless CSV Ingestion Engine Classic elekcsv Keeping parsing, compiled-validator generation, fuzzy column mapping and bitmap error tracking in one dependency-free core package lets every UI framework reuse identical import logic instead of six separate implementations.
Agentic Development Environment for Parallel Coding Agents Hybrid Orca Agent CLIs stay the user's own. Orca adds the orchestration layer around them: isolated git worktrees, a PTY daemon that outlives the UI, and a relay for mobile steering. It can support new agents without bundling them.
Rust Web Framework Classic Axum Axum skips a custom middleware system and treats every route and layer as a Tower service, so it inherits timeouts, tracing, compression and auth from tower-http and shares middleware with Hyper and tonic code.
Full-Stack Rust Web Framework Classic Leptos Leptos separates its reactive graph, renderer and server-function RPC into independent crates and keeps the core server-agnostic, so the same components run as SSR HTML or WebAssembly, and Axum or Actix Web plug in through thin integration crates.
Cross-Platform Rust App Framework Classic Dioxus Dioxus keeps one virtual DOM and component model and swaps renderers per platform (WebAssembly, WebView, SSR, LiveView, native), while its own dx CLI handles hot-patching, asset bundling and packaging for every target.
Rust Web Framework Classic Actix Web Actix Web owns its HTTP stack in actix-http and keeps router, codegen, files, multipart, test utilities and the awc client in one workspace, so the whole request path, TLS options and public API are versioned and semver-checked together.
Rails-Style Rust Web Framework Classic Loco Loco assembles proven crates (Axum, SeaORM, Tera, Lettre, OpenDAL) behind Rails-style conventions and generators, uses feature flags to keep infrastructure optional, and ships an AGENTS.md, an agent skill and evals so agents can build on it.
Browser Automation Bridge for AI Agents Classic BrowserSkill The agent keeps the browser's real login state and the user can watch and take over, because the design pairs a small native Rust daemon (callable from any agent's shell) with a WXT extension, instead of running a separate headless browser. A shared protocol crate keeps both sides in sync.
Browser-Based 3D Geospatial Intelligence Simulator Hybrid God's Eye View All rendering runs client-side on Cesium with plain JavaScript modules, while a thin localhost Node proxy per data provider keeps keys out of the browser, so the whole product installs and runs locally with no hosted backend or database.
Hybrid Deterministic + LLM Agent Code Review Tool Hybrid Open Code Review A single static Go binary keeps the review engine fast and easy to distribute through npm, CI and IDE plugins. Putting deterministic diff/context analysis before a narrow LLM loop keeps reviews precise and cheap in tokens compared with general-purpose agents.
Native macOS Launcher & Clipboard Manager Hybrid Tinycast Staying native with zero third-party dependencies and delegating search to Spotlight and system services keeps memory use low. A small embedded JavaScriptCore runtime adds Raycast extension compatibility without pulling in Electron.
High-Performance Python Web API Framework Classic FastAPI FastAPI keeps its own dependency surface to Starlette and Pydantic and pushes servers, CLI, templating, forms and settings into an optional 'standard' extra, so a bare install stays minimal while typical apps opt into one bundle instead of assembling it dependency by dependency.

Often used with GitHub Actions

Questions about GitHub Actions

How many production projects use GitHub Actions?

12 verified production projects in the STACK IT FAST directory use GitHub Actions, each with a full architecture breakdown.

What is GitHub Actions most often used with?

Across projects in the directory, GitHub Actions is most commonly paired with Rust, Tokio, React.