thehardwarestore.ai

Foundry is an opinionated toolkit that centralizes and automates the configuration of code quality tools for JavaScript/TypeScript projects. It bundles and exposes composable ESLint flat configs, Biome configuration, Stylelint configuration, Husky hooks, and lint-staged setup. The CLI (`foundry init`) detects installed frameworks and dependencies (React, Next.js, Jest, etc.), generates tailored config files, and updates package.json scripts. The package primarily serves as a shared, versioned dependency that enforces consistent linting and formatting across multiple projects within an organization. The architecture is a library of configuration objects combined with a thin CLI wrapper, and the code is well-structured, modular, and thoroughly tested.

This repository is a PHPStan extension that detects banned code patterns in PHP projects. It provides two main rules: BannedNodesRule to forbid specific function calls and language constructs (like var_dump, exit, echo), and BannedUseTestRule to prevent the use of test namespaces in non-test files. The extension is configured via PHPStan's neon configuration and integrates seamlessly into the PHPStan analysis process. The architecture is straightforward, with each rule implemented as a separate class that processes AST nodes and reports violations. The project demonstrates good practices in PHPStan extension development, including configurable rules, proper error building with non-ignorable options, and thorough unit testing.

Globstar is a static analysis toolkit that enables developers to write custom checkers in YAML or Go and run them via a single portable binary. It uses tree-sitter for AST-based analysis, supporting multiple languages (Go, Java, JavaScript, Python, Ruby, etc.). The tool is designed to be fast, dependency-free, and CI-friendly, with a focus on enforcing learned patterns such as security vulnerabilities and code quality issues. The architecture consists of a CLI layer, an analysis engine for parsing and scope resolution, and a checker system with built-in and custom checker support.

This repository is a curated 'awesome list' for ESLint, not a software application or data pipeline. Its core is a single, extensively organized README.md that catalogs ESLint configurations, plugins, parsers, formatters, globals, tools, tutorials, and setup resources. The only functional code is a package.json declaring the `awesome-lint` dev dependency and a GitHub Actions workflow that runs this linter against the README on every push and pull request to ensure list quality and formatting consistency. The architecture is intentionally static—no runtime services, APIs, or data processing exist. The repo's production value is purely informational: it serves as the de facto community reference for discovering and choosing ESLint-related tooling. It is actively maintained with recent commits, high visibility, and a clear contribution guide. Technical drift is limited to outdated CI details (e.g., actions/checkout@v3) and a broad dev-dependency range, but the content itself stays current with the ESLint ecosystem. While not a codebase in the traditional sense, the curation quality, categorization, and maintenance discipline are strong, making it a reliable resource for developers evaluating ESLint tools.

coca is a static code analysis and refactoring CLI tool written in Go, designed to assess code quality, detect bad smells, analyze dependencies, and support migration tasks (specifically Spring MVC to Spring Boot). It operates as a monolithic command-line application using the Clean Architecture pattern, with distinct layers for domain models, application logic, and infrastructure. The tool supports multiple languages including Java, Go, Python, JavaScript, TypeScript, and Groovy, leveraging ANTLR for parsing and generating ASTs for analysis. The system's primary function is to scan codebases for technical debt, architectural issues, and API definitions, outputting results in various formats (JSON, CSV, Graphviz). It includes features for bad smell detection (e.g., Long Method, Large Class), test smell analysis, and dependency usage evaluation. The architecture is modular, allowing individual analysis features to be executed independently, though the tool itself is a single binary. While the codebase demonstrates solid engineering practices with a clean separation of concerns and reusable domain models, it exhibits technical drift in its dependency ecosystem. The Go version specified (1.23) is ahead of current stable releases, and several core dependencies (e.g., spf13/cobra, gomega) are significantly outdated, creating a mismatch between the code's stated requirements and the available ecosystem versions. This suggests the project is either in a transitional state or relies on specific, potentially unstable, dependency versions.

This is a monorepo (Yarn Berry workspaces) serving as a comprehensive educational resource for frontend fundamentals, maintained by the Korean fintech company Viva Republica (Toss). It comprises multiple VitePress documentation sites covering code quality, accessibility, debugging, and bundling, along with a real React application ('today-i-learned') that demonstrates the principles by using GitHub Discussions as a backend for a community TIL blog. The repository also includes a Claude Code plugin (frontend-fundamentals-plugin) that evaluates code against these principles using automated grading tasks. The architecture is documentation-centric with a shared navigation component, multi-language support (Korean, English, Japanese, Chinese), and Vercel serverless functions for GitHub OAuth and GraphQL API proxying. The TIL app is a production-grade React SPA (Vite, React Query, Panda CSS, Radix UI) that features post creation, comments, reactions, streaks, and weekly challenges. While the code is well-structured and the educational content is high-quality, much of the code is tightly coupled to the documentation context or the TIL app's specific domain, limiting broad reuse. The repository is actively maintained with recent commits and responsive issue management.

This repository is an ESLint plugin (`@factory/eslint-plugin`) developed by Factory AI. It provides a suite of custom lint rules and shared configurations designed to enforce strict code organization, testing, and logging conventions. The codebase is fully AI-generated and explicitly unmaintained, intended for inspiration rather than direct import. It demonstrates high craftsmanship in AST manipulation (e.g., `jest-mock-require-actual`, `structured-logging` rules with auto-fix) and complex configuration curation (e.g., `frontend.js` config with extensive `no-restricted-syntax` selectors banning specific React/Next.js patterns). The rules enforce a highly opinionated architecture, including specific file naming conventions (`.page.tsx`, `.module.tsx`), mandatory middleware in route handlers, and structured logging over template literals. While the code quality and test coverage are strong, the plugin is technically drifted (ESLint 8.x API, TypeScript 5.x) and relies on outdated dependencies, limiting its direct applicability without significant modernization.