move along nothing to see here.
Business Intelligence API for Azure IoT Happy Path
CodeCheck scope plugin — generates smoke tests (happy path, does-it-run sanity checks)
Fetching done right, not just the happy path.
acture StateAdapter for zustand + zustand/middleware/immer. Phase 1's documented happy path.
MixMake CLI for MCP happy-path workflows
Business Intelligence API for Azure IoT Happy Path
Super Duper Happy Path Logger
A test suite with some basic happy-path checks against a DPop-based WebID-OIDC provider
Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. It includes many web standards from WHATWG DOM and HTML.
A node.js through stream that does basic streaming text search and replace and is chunk boundary friendly
Golden request/response payloads for ACP and UCP (AP2 placeholder — upstream draft). 9 ACP fixtures covering create/update/complete + error envelopes. 4 UCP fixtures covering the discovery profile + shopping create-checkout happy-path + out-of-stock error
Use Happy DOM globally in a Node.js environment for testing.
Use Happy DOM as environment in Jest.
Connect is a family of libraries for building and consuming APIs on different languages and platforms, and [@connectrpc/connect](https://www.npmjs.com/package/@connectrpc/connect) brings type-safe APIs with Protobuf to TypeScript.
XML Lexer
A collection of helpers for Angular and RxJs provided by Happy Path
Connect is a family of libraries for building and consuming APIs on different languages and platforms. [@connectrpc/connect](https://www.npmjs.com/package/@connectrpc/connect) brings type-safe APIs with Protobuf to TypeScript.
Awesome node module
Emoji keyword library.
Creates .d.ts files from CSS Modules .css files
Mobile and Web client for Claude Code and Codex
A higher order component for loading components with promises
Ant Design happy work theme
Write/read SHA-256 commitments to/from Liquid OP_RETURN transactions via Elements JSON-RPC.
Strict, opinionated X.509 chain verifier for the common happy-path case
Interactive document sessions with AI agents
Laravel/AdonisJS-inspired utility helpers for the Rok ecosystem
WSL2 backend integration for ZLayer on Windows
Recursive CellOS-in-CellOS backend — runs CellOS cells as nested supervisors. Used for federated and self-hosting topologies.
Experimental, research-stage post-quantum cluster-threshold encrypted-mempool sealing primitive (ML-KEM-768 + GF(256) Shamir + committing ChaCha20-Poly1305). Unaudited.
Spec-first Rust port of beads_viewer (bv) — graph-aware triage for beads issue trackers (CLI binary: bvr)
Phase 31.1 — fetch + resolve + download + sha256-verify nexo plugin tarballs against the ext-registry index. Building block for `nexo plugin install <id>` (CLI integration in 31.1.c).
Multi-runtime GPU + remote inference as a supervised actor system on atomr. Single-crate rollup that re-exports per-runtime backends behind feature flags.
L402 + DID-signed invoices: agent-to-agent Lightning payments (Rust port of @p-vbordei/agent-pay)
D-dimensional Delaunay triangulations and convex hulls in Rust, with exact predicates, multi-level validation, and bistellar flips
Reroute /first or /last to the endpoint for the model's first or last instance.
Fix is a modern Ruby testing framework built around a key architectural principle: the complete separation between specifications and tests. It allows you to write pure specification documents that define expected behaviors, and then independently challenge any implementation against these specifications.
CrewdPolicies enables conventional Pundit (https://github.com/elabs/pundit) policies to be written using an opinionated pattern based on declarative Create, Read, Execute (optional), Write and Destroy (CREWD) permissions for each resource. Conventional pundit create?, show?, update? and destroy? permissions are automatically derived from these, as well as permitted_attributes/strong parameters.
Library for semantic path configuration to make developers and operators happy.
Prioritize the happy path.
Lean CMS is a Rails Engine that adds in-context content editing, page content management, blog/portfolio, settings, and notifications to any Rails 8 application. Built for marketing sites — SQLite happy path with full Postgres/MySQL compatibility.
# Footman This gem is still growing. ## Installation Depends upon having reprepro tool installed (if debian based) or createrepo installed (if red hat based). Ruby 1.9.+ is required to use this gem. 'createrepo' (rpm) tool does not require any pre-setup to the repository or watched directory. - - - 'reprepro' (deb) tool requires pre-setup. The repository directory for deb files must contain: <pre><code> conf/ conf/distributions conf/options conf/override.precise </pre></code> options file is empty, but needed to make reprepro happy distributions file will contain: <pre><code>Origin: Tyler Label: Tyler's Personal Debs Codename: precise Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.precise DscOverride: override.precise Origin: Tyler Label: Tyler's Personal Debs Codename: lenny Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.lenny DscOverride: override.lenny </code></pre> Note that the code name is for each distribution repository you support. for each distribtuion repository you support there must be an override file. override file can be left empty, footman will fill it out when a new package is added. The watched directory must have sub directorys named after each of the distribution repositories you support. For example my watched directory at /path/ will have two subdirectories: <pre><code>/path/lenny/ /path/precise/</code></pre> Packages must be dropped into the subdirectory that corrosponds with the distribution they were built on. - - - Add this line to your application's Gemfile: gem 'footman' And then execute: $ bundle Or install it yourself as: $ gem install footman Or locally: $ gem build footman.gemspec $ gem install footman --local ## Usage footman path/to/watch path/to/repo ## Contributing 1. Fork it 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create new Pull Request
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.