Project

Reverse Dependencies for rdoc

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

0.1
No release in over a year
ethname - light-weight crowd-sourced "off-chain" ethereum name to (contract) address service / helper (incl. punks v1,v2,v3,v4; phunks v1,v2, synth punks, punk blocks, nouns, nouns descriptor, synth nouns, etc.) - yes, you can! - add more names / contracts via git ;-)
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.1
The project is in a healthy, maintained state
football-sources - get football match data (leagues, cups & more) via web pages or web api (json) calls
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.1
Low commit activity in last 3 years
No release in over a year
KPeg is a simple PEG library for Ruby. It provides an API as well as native grammar to build the grammar. KPeg strives to provide a simple, powerful API without being too exotic. KPeg supports direct left recursion of rules via the {OMeta memoization}[http://www.vpri.org/pdf/tr2008003_experimenting.pdf] trick.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.1
No release in over 3 years
Low commit activity in last 3 years
This gem automatically handles creation, renewal, and applying SSL certificates from LetsEncrypt to your Heroku account.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.1
No release in over 3 years
merkletree - build your own crypto hash trees; named after Ralph Merkle who patented hash trees in 1979; grow your own money on trees
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.1
Low commit activity in last 3 years
No release in over a year
Hunting down random test failures can be very very difficult, sometimes impossible, but minitest-bisect makes it easy. minitest-bisect helps you isolate and debug random test failures. If your tests only fail randomly, you can reproduce the error consistently by using `--seed <num>`, but what then? How do you figure out which combination of tests out of hundreds are responsible for the failure? You know which test is failing, but what others are causing it to fail or were helping it succeed in a different order? That's what minitest-bisect does best.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.1
No release in over a year
rlp-lite - light-weight machinery to serialize / deserialze via rlp (recursive length prefix)
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.1
No commit activity in last 3 years
No release in over 3 years
There's a lot of open issues
A set of Ruby classes supporting the ActiveRecord lifecycle for the Zoho CRM API.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.1
The project is in a healthy, maintained state
score-formats - read / parse and print sports match scores (incl. half time, full time, extra time, penalties and more)
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.1
The project is in a healthy, maintained state
sportdb-catalogs - sport.db (search 'n' find) catalogs for countries, leagues, clubs, national teams, and more
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.1
No release in over 3 years
sportdb-importers - tools 'n' scripts for importing sports (football) data in alternate (text) formats incl. comma-separated values (csv) format
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024