Project

Reverse Dependencies for m

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

12.04
A long-lived project that still receives updates
Sprockets is a Rack-based asset packaging system that concatenates and serves JavaScript, CoffeeScript, CSS, Sass, and SCSS.
2019
2020
2021
2022
2023
2024
1.98
The project is in a healthy, maintained state
A framework for building reusable, testable & encapsulated view components in Ruby on Rails.
2019
2020
2021
2022
2023
2024
1.51
Low commit activity in last 3 years
A long-lived project that still receives updates
Rails I18n de-facto standard library for ActiveRecord model/data translation.
2019
2020
2021
2022
2023
2024
1.1
A long-lived project that still receives updates
Rack middleware to measure production code usage (LOC runtime usage)
2019
2020
2021
2022
2023
2024
0.7
No release in over a year
Intercom (https://www.intercom.io) is a customer relationship management and messaging tool for web app owners. This library wraps the api provided by Intercom. See http://docs.intercom.io/api for more details.
2019
2020
2021
2022
2023
2024
0.64
There's a lot of open issues
A long-lived project that still receives updates
Prometheus metric collector and exporter for Ruby
2019
2020
2021
2022
2023
2024
0.62
The project is in a healthy, maintained state
Use Vite in Ruby and bring joy to your JavaScript experience
2019
2020
2021
2022
2023
2024
0.61
No release in over 3 years
Low commit activity in last 3 years
It makes histograms out of Ruby data. How cool is that!? Pretty cool if you ask me.
2019
2020
2021
2022
2023
2024
0.6
A long-lived project that still receives updates
Monitors Ruby apps and reports detailed metrics on performance to Scout.
2019
2020
2021
2022
2023
2024
0.33
A long-lived project that still receives updates
A library for specifying, quering, and enumerating recurring events for calendars in Ruby.
2019
2020
2021
2022
2023
2024
0.21
No commit activity in last 3 years
No release in over 3 years
Auto-submit Rails exceptions as new issues on GitHub
2019
2020
2021
2022
2023
2024
0.2
Low commit activity in last 3 years
No release in over a year
Best practice is to send text/plain && text/html markdown works great for both, so why write your templates twices?
2019
2020
2021
2022
2023
2024