ryanmcdermott/clean-code-javascript
Clean Code concepts adapted for JavaScript
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
The project lists 105 contributors on GitHub.
Peaked at #21 in the weekly ranking the week of Jun 28, its best in the past year.
Use Cases & Benefits
- Adapts Clean Code principles specifically for writing readable, reusable, and maintainable JavaScript code.
- Provides practical guidelines and examples to improve code quality beyond style, focusing on architecture and best practices.
- Use for improving JavaScript code readability and maintainability in existing projects through refactoring.
- Use for educating developers on clean coding standards and principles tailored to JavaScript language features.
- Use for establishing team-wide coding conventions that emphasize single-responsibility functions and avoiding side effects.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
MIT
Permissive: commercial use, modification and redistribution are allowed with attribution.
Community files
- README: present
Watch-outs
- Warning: No commits in over a year (last push Jul 2024).
- No GitHub releases; pin a commit or tag instead of a release.
General guidance from repository metadata, not legal advice. How we score
From the README
Software engineering principles, from Robert C. Martin's book Clean Code, adapted for JavaScript. This is not a style guide. It's a guide to producing readable, reusable, and refactorable software in JavaScript.
Not every principle herein has to be strictly followed, and even fewer will be universally agreed upon. These are guidelines and nothing more, but they are ones codified over many years of collective experience by the authors of Clean Code.
Our craft of software engineering is just a bit over 50 years old, and we are still learning a lot. When software architecture is as old as architecture itself, maybe then we will have harder rules to follow. For now, let these guidelines serve as a touchstone by which to assess the quality of the JavaScript code that you and your team produce.
One more thing: knowing these won't immediately make you a better software developer, and working with them for many years doesn't mean you won't make mistakes. Every piece of code starts as a first draft, like wet clay getting shaped into its final form. Finally, we chisel away the imperfections when we review it with our peers. Don't beat yourself up for first drafts that need improvement. Beat up the code instead!
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
Forks
12.6K+30
Open issues
124+1
Compared with peers in Web
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 8, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| pingdotgg/t3code | 55.7K | +12.2K | 75 | today |
| pbakaus/impeccable | 107.6K | +6.1K | 75 | 1 day ago |
| meta/astryx | 22.8K | +4.8K | 75 | today |
| Renhuai123/ziwei-doushu | 17.5K | +3.7K | 75 | 26 days ago |
| ranxianglei/billion-context | 6.3K | +2.4K | 75 | 3 days ago |
| ryanmcdermott/clean-code-javascript | 94.7K | — | 35 | — |
| Category median | 22.8K | +4.8K | 75 | — |
Discover Repositories
Search across tracked repositories by name or description
