This repository contains the Ruff Python linter and formatter, along with the Ty Python type checker, both written in Rust. It is a monolith of several dozen crates assembled into a workspace, delivering a CLI tool, a Language Server Protocol (LSP) server, and a web playground. In production, Ruff analyzes Python source files against hundreds of lint rules from flake8, pylint, pyupgrade, and other plugins, formats code to be compatible with Black, and provides IDE features via LSP. Ty adds type checking and advanced IDE features like goto-definition and workspace symbols. The architecture is modular: a parser produces an AST, semantic analysis operates on that AST, lint rules are checked via pluggable visitors, formatting is done through an IR-based printer, and diagnostics are rendered in multiple formats (JSON, JUnit, SARIF, etc.). The LSP server reuses many of these components through a Salsa-based incremental database for caching. The repository is a model of how to structure a high-performance developer tool in Rust, with extensive test fixtures, fuzzing, and benchmarks. While primarily an application, it includes some data-like assets (test fixture corpora, ecosystem check scripts) but nothing that would classify it as a data research project.
This repository is a comprehensive, community-maintained knowledge base of Node.js best practices — not a runnable application or data pipeline. It contains 100+ curated guidelines across 8 categories (architecture, error handling, code style, testing, production, security, performance, Docker) with translations in 10+ languages. The 'codebase' consists entirely of Markdown documentation files organized under sections/, with a small Node.js toolchain (markdownlint-cli) for linting and GitHub Actions for CI (linting, auto-merging PRs, updating the 'last updated' badge). There are no runtime entry points, APIs, or data flows. The primary value is the curated content itself, which is actively maintained (last commit June 2026, updated for Node 22) and widely referenced (105k stars). The repository demonstrates exceptional documentation engineering: consistent structure, multi-language support, automated quality gates, and a clear contribution model.
This repository is SAP's official, community-driven collection of coding style guides, focused on ABAP development within the SAP ecosystem. The centerpiece is Clean ABAP (clean-abap/CleanABAP.md), a comprehensive adaptation of Robert C. Martin's Clean Code for the ABAP language, covering naming conventions, language constructs, variables, internal tables, conditions, classes, methods, error handling, comments, formatting, and testing - with each rule paired as good and anti-pattern code examples. A companion guide (abap-code-review/ABAPCodeReview.md) defines a pragmatic, checklist-based ABAP code-review process tied to the Clean ABAP rules. The repo is documentation-only; it is not a runnable application, service, or data pipeline. Its only executable surface is a GitHub Actions workflow (build.yml) that validates markdown links via markdown-link-check, plus an automated issue labeler. Content is organized as a single large primary document (~10,000+ lines) with modular deep-dive sub-sections (clean-abap/sub-sections/), a print-optimized cheat sheet, and full translations into eight languages (English, Chinese, German, Spanish, French, Japanese, Korean, Russian). The project is actively maintained - last commit April 2026, 79 open issues triaged through structured templates (propose new rule, clarification, adjust existing rule) - and uses a formal governance model requiring consensus and quarterly review for significant changes. The guides are opinionated by design and openly acknowledge tensions with legacy code, performance, and official SAP guidelines; enforcement is delegated to companion tools such as abaplint and code pal for ABAP. Primary drift risk is translation lag - several translations are based on English versions from 2019-2022 - and evolution of the ABAP language beyond the NetWeaver releases referenced in the text.
This repository is an opinionated Angular style guide by John Papa, primarily targeting AngularJS (1.x). It is not a runnable application but a comprehensive documentation resource prescribing coding conventions, architecture patterns (LIFT, modularity, folder-by-feature), and best practices for building Angular 1 applications. The repo contains the full guide in English and 12+ community-translated versions, along with editor snippets for various IDEs. While no executable code exists, the guide itself serves as a reference for legacy Angular projects and continues to receive maintenance (last commit 2026-04-30). The companion guide for Angular 2+ is largely a stub pointing to official documentation.
This repository hosts Google's official coding style guides for multiple programming languages (C++, Java, Python, Go, JavaScript, TypeScript, etc.) as well as supporting technologies (HTML/CSS, JSON, Lisp, Vimscript, etc.). It is a static documentation site with auxiliary tooling: JavaScript for dynamic table-of-contents generation and code block formatting, XSLT for transforming XML-based guides into interactive HTML pages, and editor configuration files (Emacs, Vim, Eclipse, IntelliJ). The repository contains no application runtime, API endpoints, or data processing pipelines. While the style guides themselves are the primary value, the code artifacts are simple, well-structured rendering helpers that can be adapted for other documentation projects. External contributions are not accepted, and some guides (e.g., the JavaScript guide) are explicitly deprecated, reflecting a maintenance model driven entirely by internal updates.
This repository is a PHP-based living style guide boilerplate that generates a web-based style guide from HTML markup snippets and Markdown documentation. The system scans directories of markup files, renders them with syntax highlighting (Prism.js), and provides a navigable interface with color swatches, font stacks, and documentation sections. It is a simple, monolithic PHP application with a single entry point (index.php) and a helper functions file (functions.php). While the code is clean and well-commented, it relies on outdated practices (no dependency management, no modern PHP, legacy CSS vendor prefixes) and has not been updated since 2018. The repository serves as a starting point for teams to create custom style guides, but it requires significant modernization to be used effectively in contemporary front-end workflows.