Standard promises monthly releases and its newest GitHub release is from 2023
Ruby's bikeshed-proof linter and formatter 🚲
At a glance
- What is it?
- standard is an unconfigurable RuboCop-based linter and formatter for Ruby, created and maintained by Test Double. Its README promises a monthly release cadence, its newest GitHub release is v1.31.0 from 2023-08-19 while the last push is 2026-11-01, and its version history runs 1.25.0, then 0.0.36.1, then 1.31.0.
- Who is it for?
- standard is worth trying if your team's real cost is arguing about linter configuration, because the unconfigurable stance is the product and the argument for it is made plainly rather than assumed. Two things to weigh first.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 3 days ago.
- What is it written in?
- Mainly Ruby, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- standardrb/standard2,928 ★ · +3
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| standardrb/standard | 2.9k | 2.9k |
3 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The newest release is 1.31.0 from 2023 and the last push is three days old
Two dates in this repository need to be read together rather than separately. The repository is not archived, and the last push to the default branch is dated 2026-11-01. The newest release tag, meanwhile, is v1.31.0, published on 2023-08-19. So the default branch is being written to while the newest GitHub release is more than three years old. Those two facts are not contradictory; plenty of projects land work on a branch and cut releases on their own schedule. But for a tool whose entire value proposition is that it stays current with the linter it wraps, the gap between the two dates is the number that matters, and it is not a small one.
The version numbers run 1.25.0, then 0.0.36.1, then 1.31.0
Read the three most recent releases in date order rather than version order and the sequence looks wrong. v1.25.0 shipped on 2023-03-16. Then, on 2023-04-05, came v0.0.36.1. Then, on 2023-08-19, v1.31.0. So the project went from the 1.x series back down to a 0.0.x patch and then back up into the 1.x series, in the space of five months. The release title explains the middle one, and it is unusually forthcoming: it calls itself the edition in which someone got the RuboCop version specifier wrong. So the 0.0.36.1 line is a repair, not a new product line, and anyone parsing the version list to work out what is installed, or writing automation against it, has to know that a 0.0.x release can appear between two 1.x releases. The other two titles are bare version numbers.
The README promises monthly releases and the record shows none in three years
The unconfigurable argument in this README is good, and one sentence in it is checkable. The pitch for adopting it includes time saved on argument and upgrades, on the grounds that the maintainers stay on top of each new RuboCop rule and update the configuration on a monthly release cadence. The three most recent GitHub releases are all from 2023 and none is newer, which sits uneasily with that promise. It is worth asking what a RuboCop upgrade costs you in practice, because the whole argument rests on that number staying at zero.
An unconfigurable linter ships a configuration file
The repository root contains a configuration file with the tool's own name on it. That sits oddly beside a section headed by a question, answered in the affirmative, about whether the tool is unconfigurable: but you can't configure Standard Ruby, you can take it or leave it. The rest of that section is the best writing in the file. No two developers will ever agree on what all the rules and format should be; teams have argued about comma placement for decades; some have a tech lead who imposes his favourite way; and the usual outcome is a configuration nobody understands that drifts out of date with changes to the linter and to the language. The readme also has separate sections for ignoring errors and for configuration options. So what the file at the root is still allowed to do is something you have to read in those sections rather than infer from the slogan.
The unconfigurable configuration lives in three repositories
Follow the three links in the middle of that same section and the fixed ruleset is spread across three projects. One points at a base configuration file inside this repository. The second points at a base configuration in a separate repository named for performance. The third points at a base configuration in another one named for custom rules. So the configuration you are told you cannot change is itself distributed across at least three repositories, each on its own default branch, and a change to how your code is linted can arrive because something changed in one of them rather than because a gem version moved. There is an extension point as well, through a plugin mechanism, with two named plugins for Rails and for Sorbet, which is how a genuinely unconfigurable tool stays adjustable at all.
The gem is standard and the executable is standardrb
This one costs people an afternoon. The gem is named standard and the binary it installs is named standardrb, and the reason given is to distinguish it from StandardJS, the JavaScript project it takes its ethos from. So you add gem standard to your Gemfile, and the command you type is not standard. One other invocation path exists and it is named after the gem rather than the binary: a Rake task, available if your Rakefile requires the tool's rake file, run as rake standard. The tool inspects any Ruby files it finds under the current directory tree, reports errors if it finds them, and on a compliant tree exits quietly with code zero.
One fix task uses a colon and the other does not
There are two fix modes, each with a CLI flag and a Rake task, and the names are not consistent. The safe fix is a CLI flag and a Rake task, where the task is namespaced with a colon. The unsafe fix, for rules that can be remedied automatically but might change behaviour, is the pair:
# CLI
$ standardrb --fix-unsafely
# Rake
$ rake standard:fix_unsafelySo the safe task is standard:fix, while the unsafe task is standard:fix_unsafely with an underscore, and the unsafe CLI flag --fix-unsafely uses a hyphen instead. A team that memorises one spelling will not necessarily derive the other. The stance on running them is more interesting than the naming. The safe fix is run with fix enabled all the time, on the grounds that the fixes will not change behaviour, and the unsafe one is defended by pointing out that if the code is in source control and the tests pass it is probably no more error prone than editing the changes by hand.
The editor guide list includes a discontinued editor
The editor section lists ten guides, and one of them is for Atom, an editor that has been discontinued and whose guide points at a wiki page rather than at current documentation. That is the expected decay of a maintained list. Several other entries are hosted away from the project's own wiki: for example the Nova guide lives on a different forge entirely, and the RubyMine guide points at documentation for a different linter with instructions to disable that linter. The rest cover the usual ground, with the emacs, Helix and Zed guides pointing at the editors' own documentation rather than this project's wiki.
Editorial conclusion
standard is worth trying if your team's real cost is arguing about linter configuration, because the unconfigurable stance is the product and the argument for it is made plainly rather than assumed. Two things to weigh first. The README states a monthly release cadence, but the newest GitHub release is from 2023, so check the gem release history before relying on that promise. And check what the configuration file at the repository root is still permitted to do before you rely on it, because a tool that insists it cannot be configured ships one anyway.
Frequently asked questions
What is the standard Ruby gem?
A linter and formatter for Ruby built on RuboCop that brings the ethos of StandardJS to Ruby. It applies an unconfigurable configuration to RuboCop's built-in rules and to those in the performance plugin, supports plugins built with lint_roller such as the Rails and Sorbet ones, and was created and is maintained by the team at Test Double.
Why is standard unconfigurable?
Because the argument is about bikeshedding rather than about rules. The readme's position is that no two developers will agree on what all the rules and format should be, that teams have argued about comma placement for decades, that the usual result is a configuration nobody understands which drifts out of date, and that time spent on it is time wasted. You can take the tool or leave it.
How do I run standard on my code?
Install the gem named standard, then run the binary, which is named standardrb specifically to distinguish it from StandardJS. A Rake task is also available, run as rake standard, if your Rakefile requires the tool's rake file. Both inspect any Ruby files found under the current directory tree and exit quietly with code zero when the code is compliant.
What is the difference between the two standard fix modes?
A majority of the rules can be fixed safely, and the maintainers run with that fix enabled all the time on the grounds that the changes will not alter behaviour. The other rules can be remediated automatically but with a risk of changing behaviour, so they are behind a separate flag and a separate task. Their advice is that if the code is in source control and the tests pass, it is probably no more error prone than editing by hand.
Is standard still being released?
The repository is not archived and the last push to the default branch is dated 2026-11-01, but the newest release tag is v1.31.0 from 2023-08-19. The readme states that the configuration is updated on a monthly release cadence, and the visible release record does not show that since 2023. Note also that one of the three recent releases is a 0.0.x patch between two 1.x releases, titled as a repair to a RuboCop version specifier.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/standardrb-standard)Star history chart for your README
[](https://hysenlabs.com/projects/standardrb-standard)Was this useful?