# Installer standard avec Homebrew Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de standard pour les workflows d'agents IA. ## installation ```sh sudo av install brew:standard ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install standard ``` Preuve: local Homebrew formula metadata ## Faits du paquet - **Clé du paquet:** brew:standard - **Gestionnaire de paquets:** Homebrew - **Page du gestionnaire de paquets:** - **Version:** 17.1.2 - **Résumé source:** JavaScript Style Guide, with linter & automatic code fixer - **Page d'accueil:** - **Dépôt:** - **Docs amont:** - **Licence:** MIT - **Archive source:** - **Généré:** 2026-08-04T22:13:35+00:00 ## exécutables - standard (cli) - standard (alias) ## Dépendances - node ## Comportement d'installation - hook post-installation: non défini - Bouteille: disponible sur all ## Version et fraîcheur - page générée: 2026-08-04 - version du gestionnaire: 17.1.2 - données locales: OK - dépôt amont: https://standardjs.com/ - info: No package-manager update timestamp was available. - info: Release/tag comparison is only available for GitHub repositories. ## Historique du projet et usages StandardJS, distributed by the `standard` CLI, packages a JavaScript style guide together with linting and automatic fixing. Its appeal in CLI and package-manager culture is that a project can install one package and run one command instead of maintaining a separate ESLint configuration. ### Historique du projet The project presents itself as a JavaScript style guide, linter, and formatter. Its own changelog records version 4.0.0 in May 2015, and later major releases track the underlying ESLint ecosystem, including the 2022 `standard` 17 release built around ESLint 8 compatibility. ### Historique d'adoption Adoption grew around the promise of no `.eslintrc` files and a repeatable `standard` command. The README explicitly encourages adding `standard` to `package.json` and wiring it into `npm test`, which made it fit the everyday workflow of npm packages, CI, and pull-request review. ### Modes d'utilisation Typical use is installing `standard` globally or as a development dependency, then running `standard`, `npx standard`, or `standard --fix`. Configuration, when needed, is stored under the `standard` key in `package.json` rather than in a separate dotfile. ### Pourquoi les passionnés de paquets s'y intéressent Package maintainers care about StandardJS because it made style enforcement feel like a dependency choice rather than a configuration project. It also demonstrates the tradeoff package ecosystems often debate: convention and speed over local bikeshedding. ### Chronologie - 2015: Changelog records StandardJS 4.0.0. - 2016: Version 8.0.0 adds the built-in `--fix` workflow. - 2022: Version 17 aligns StandardJS with ESLint 8. ### Related projects - StandardJS is built around ESLint-related packages such as `eslint-config-standard`, `eslint-config-standard-jsx`, `standard-engine`, and ESLint plugins for import, promise, React, and Node rules. ### Sources - - - ## Notes de sécurité narrow executable package without higher-risk signals. - **Risque Geiger:** vert / faible - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: package.json ## Détails de la base source - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** standard - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Liens liés - [Terminal utility packages](https://pkg.so/fr/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://pkg.so/fr/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://pkg.so/fr/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [Language runtime packages](https://pkg.so/fr/language-runtime-packages/) - Matched language runtime, compiler, or interpreter metadata. - [node](https://pkg.so/fr/brew/node/) - Runtime dependency declared by Homebrew. - [protolint](https://pkg.so/fr/brew/protolint/) - Shares pkgdb curated category or tags: cli, developer-tools, formatter, linter, style-guide. - [eslint_d](https://pkg.so/fr/brew/eslint-d/) - Shares pkgdb curated category or tags: cli, developer-tools, eslint, javascript, linter. - [biome](https://pkg.so/fr/brew/biome/) - Shares pkgdb curated category or tags: cli, developer-tools, formatter, linter. - [prettier](https://pkg.so/fr/brew/prettier/) - Shares pkgdb curated category or tags: cli, developer-tools, formatter, javascript. - [eslint](https://pkg.so/fr/brew/eslint/) - Shares pkgdb curated category or tags: cli, developer-tools, javascript, linter. - [rumdl](https://pkg.so/fr/brew/rumdl/) - Shares pkgdb curated category or tags: cli, developer-tools, formatter, linter. - [ktlint](https://pkg.so/fr/brew/ktlint/) - Shares pkgdb curated category or tags: cli, developer-tools, formatter, linter. - [sqlfluff](https://pkg.so/fr/brew/sqlfluff/) - Shares pkgdb curated category or tags: cli, developer-tools, formatter, linter. - [standard](https://pkg.so/fr/npm/standard/) - Same normalized package name appears in another local ecosystem. Shared terms: cli, code, developer, developer-tools, eslint. - [standard](https://pkg.so/fr/npm/standard/) - Same normalized package name in another local ecosystem. ## Combined YAML source View the package source record on GitHub. [combined/standard.yml](https://github.com/mxcl/pkgdb/blob/main/combined/standard.yml) ## Sources - pkg.so package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - pkgdb category and tag curation - package relationship graph - cross-ecosystem install command graph