Project

Reverse Dependencies for yard

The projects listed here declare yard as a runtime or development dependency

0.0
No commit activity in last 3 years
No release in over 3 years
Parses PokéPastes into an object that you can easily read/manipulate/save.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No release in over a year
A comprehensive Ruby SDK for Polar.sh, providing easy integration with their payment infrastructure, subscription management, and merchant services.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
This is a search library for searching terms in documents
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No release in over 3 years
Set of tools used when developing Ruby based apps
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Popularity
0.0
No commit activity in last 3 years
No release in over 3 years
A ruby interface to POLITICO RSS feeds. Includes feed contents and metadata.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
Polygon provides a framework with strong separation of concerns between clients, developers and web designers
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
hacks paperclip to have a single repo of attachments
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
Pombo is a gem that allows the use of webservices the Correios (Brazilian Post Service) of sending packets to check price, delivery time and progress of service
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
A command line pomodoro timer
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
Repository is gone
No release in over 3 years
A ruby bridge library for shared garcon/soleil code
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Popularity
0.0
No commit activity in last 3 years
No release in over 3 years
An alternative to DatabaseCleaner for automatically ensuring that objects created during tests are removed from the database.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No release in over 3 years
Friendship gem for Rails/ActiveRecord. Popular saves time when developing social apps
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Popularity
0.0
The project is in a healthy, maintained state
Ships the `portage` executable. `portage buy <url>` tries native UCP discovery first (zero credentials, works on any store that's opted in), falls back to a portage-ucp-* platform adapter only when this process already has that platform's own credentials in env (i.e. it's your own store or one you're integrated with), and otherwise says so plainly — never scrapes or session-hijacks as an anonymous shopper. `portage find` covers the no-URL case: ask an allowlist, DuckDuckGo, Brave, or a Google Programmable Search engine which stores might sell something, keep the ones answering /.well-known/ucp, and search their catalogs — documented APIs only, no SERP scraping. Depends on portage-ucp (for platform detection via Resolver), portage-ucp-client (for the actual buy calls), and portage-ucp-journal (for `portage-console`'s read-only view of local purchase/transaction/order state); no single adapter gem is a hard dependency. Ranking, escalation and the spend-policy check use portage-ucp core's rules; portage-ucp-decision is optional and only the opt-in confidence gate needs it.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
Protocol-only core gem: Adapter contract, capability registry, manifest builder, and an MCP server wrapper. No commerce-backend deps.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
Implements Portage::Ucp::Adapter against a BigCommerce store's v3 Catalog/Carts/Checkouts APIs and v2 Orders API. Generic only — no merchant-specific business logic. Plain Net::HTTP, no bigcommerce/api runtime dependency.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
Every other portage-ucp gem lets a Ruby program expose a commerce backend to agents (server side). This gem is the other direction: connect to somebody else's /.well-known/ucp manifest, or drive your own Adapter directly, and place an order as the client. Three transports behind one interface (loopback over an in-process Adapter, stdio, Streamable HTTP) — callers never know which they got. Depends only on portage-ucp, the mcp gem's client half, and faraday (the HTTP transport's backend); no adapter gem is a dependency.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
The judgment calls between the agent loop and the Adapter/client layer, as typed, inspectable decisions instead of control flow scattered across skill instructions and the CLI: which offer to pick (OfferRanking), hand off vs. keep going (EscalationPolicy), whether a result is confident enough to act on unattended (ConfidenceGate), and a typed wrapper around Portage::Ucp::PolicyGuard (PolicyCheck). See docs/plans/system-one-decision-layer.md.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
Implements Portage::Ucp::Adapter against Etsy's Open API v3. Catalog and order are real; checkout is redirect-link only (links to etsy.com) since Etsy's public API has no cart/checkout endpoint. Generic only — no merchant-specific business logic. Plain Net::HTTP, no Etsy SDK runtime dependency.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
Implements Portage::Ucp::Adapter against Meta's Graph API Commerce Catalog. Catalog is real; checkout is redirect-link only (to each product's own merchant-hosted URL) since Meta's public API has no cart/checkout endpoint for website-checkout catalogs, and none at all for native Instagram/Facebook checkout. Generic only — no merchant-specific business logic. Plain Net::HTTP, no Facebook SDK runtime dependency.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
An append-only, consumer-swappable record of every purchase a Dispatcher completes (store origin, source, product, amount in minor units, order id, idempotency key), built on a small Store interface in the rate_limiter/authenticator mold — the shared persistence seam design-log §22 asks for so a future console or scheduler gem doesn't each grow an incompatible one. Zero runtime dependency on portage-ucp itself; wires in via Dispatcher's optional journal: argument.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026