A publish-subscribe (broadcast-listen) layer for same-origin inter-window communication
SDK for Net Bazaar - a decentralized bazaar storing all orders onchain via Seaport
Helps to create starter kit from Bazaar template
VDOM Library for Bazaar Project
The Bazaar SDK. Conveniently use Bazaar with your app in the browser.
AJAX Module for Bazaar Project
Elements for the bazaar
MCP server adapter for Agent Bazaar — connects any LLM agent to the marketplace via OAuth
cafe bazaar billing feature for react native application
Mock server to locally test Bazaar apps
Bazaar Design System Styles
AJAX validation for Bazaar Project
CLI for x402 Bazaar — AI Agent Marketplace. Browse, call, and auto-pay APIs with USDC on Base. One command to connect your agent.
Component library and supporting frontend utils for CA DMV projects by Digital Bazaar.
Tool to maintain ipfs cache of Subutai Bazaar Templates
MCP server for the OpSpawn x402 Bazaar — screenshot capture, AI analysis, PDF/HTML generation, code security scanning, and dependency auditing via x402 micropayments
Armory x402 SDK — Protocol extensions for x402 payments. Add SIWX, payment ID, Bazaar discovery, and custom extensions.
No description provided.
Subutai Bazaar Node API
Command line tool for Open Bazaar
No description provided.
This package contains various functions that can be used in any JavaScript project. It also has some Vue-specific code.
AP2-native x402 + MPP middleware for Express. Dual-rail by default (USDC on Base + Stripe fiat). Auto-discoverable on CDP Bazaar, MPPScan, and Delegare Market in one call. Agents pay against bounded SD-JWT-VC mandates — no keys, no card details. Settlemen
A forked bridge package between capacitor app and bazaar poolakey sdk from 'capacitor-poolakey'
Rust implementation of the Bazaar formats and protocols
Bazaar pallet for the Encointer blockchain runtime
A model code generator from database table using rustorm ORM
The chk_map format used by Bazaar
The dirstate format used by Bazaar
The groupcompress format used by Bazaar
Bazaar rpc for the Encointer blockchain runtime
Bazaar rpc runtime API for the Encointer blockchain runtime
A place to find tools for building your Rust application
A place to find tools for building your Rust application (Core)
A more user-friendly CLI for Git repositories
Like `aligned` but better. Newtype whose alignment is constrained not only by the inherent alignment requirements of the underlying type but also by the alignment requirements of the "alignment constraint archetype"
Random item and Heroku-ish name generator.
Bazaar Sources
Talk to Bazzar Voice API's with this handy gem
A Berkshelf plugin that adds support for downloading Chef cookbooks from Bazaar locations.
Wrapper for bazaar-vcs to extract information of bazaar-branches / see: http://bazaar-vcs.org
A Ruby implementation of the Patience diff algorithm. Patience Diff creates more readable diffs than other algorithms in some cases, particularly when much of the content has changed between the documents being compared. There's a great explanation and example [here][example]. Patience diff was originally written by Bram Cohen and is used in the [Bazaar][bazaar] version control system. This version is loosely based off the Python implementation in Bazaar. [example]: http://alfedenzo.livejournal.com/170301.html [bazaar]: http://bazaar.canonical.com/
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.
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.
No description provided.
No description provided.