# Installer jhipster avec Homebrew, chocolatey Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de jhipster pour les workflows d'agents IA. ## installation ```sh sudo av install brew:jhipster ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install jhipster ``` Preuve: local Homebrew formula metadata ### Windows - Chocolatey (92%): ```sh choco install jhipster ``` Preuve: Chocolatey community package catalog: jhipster from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='6.928','obs-virtualcam' ## Faits du paquet - **Clé du paquet:** brew:jhipster - **Gestionnaire de paquets:** Homebrew - **Version:** 9.2.0 - **Résumé source:** Generate, develop and deploy Spring Boot + Angular/React applications - **Page d'accueil:** - **Dernière mise à jour:** 2026-07-11T17:52:04Z - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - jhipster (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 9.2.0 ## Historique du projet et usages JHipster is a full-stack application generator that began as a Yeoman generator joining Java server applications with a JavaScript front end. It became a development platform for generating Spring Boot applications, Angular or React clients, microservice systems, deployment descriptors, and project configuration. ### Historique du projet The generator-jhipster repository and npm package were created in October 2013. Early release notes describe the original shape as Yeoman plus Maven plus Spring plus AngularJS in one generator; by the 2.0.0 line in 2015, the public release notes described it as Spring Boot plus AngularJS. JHipster 3.0.0 in 2016 was a major expansion point: the official release notes introduced generation for complete microservices architectures, including microservices, routers, a service registry, monitoring, and distributed-system scaffolding. Later lines broadened the front-end choices, with React moving out of experimental status in JHipster 5.0.0 in 2018. The project grew from a generator into an ecosystem: the website includes release notes, installation and application-creation docs, a module marketplace, JDL Studio, sponsorship through OpenCollective, and daily-build repositories that continuously exercise generated application combinations. ### Historique d'adoption JHipster adoption is tied to its promise of reducing full-stack setup cost. It packages the choices many enterprise Java teams would otherwise assemble manually: Spring Boot, security, database options, build tooling, front-end frameworks, tests, Docker, and deployment targets. The npm registry records the package from October 2013, while the GitHub repository accumulated a large contributor and user community. Homebrew and Chocolatey packaging put the generator into developer workstation package flows outside npm alone. ### Modes d'utilisation Developers use the `jhipster` command to generate monoliths, gateways, microservices, entities, Docker and Kubernetes assets, and application configuration. The `.yo-rc.json` file records generator choices for a project. JHipster is also used as a repeatable architecture template: teams can standardize a stack, regenerate entities, share JDL definitions, and keep generated conventions aligned across services. ### Pourquoi les passionnés de paquets s'y intéressent JHipster matters to package people because it is a package that emits package-managed projects. Installing one CLI fans out into npm, Maven or Gradle, Docker images, Java dependencies, front-end dependencies, and deployment manifests. It is also a durable example of the Yeoman-generator era crossing into Spring Boot and cloud-native Java. The package stayed relevant by changing the generated stack while preserving the one-command generator workflow. ### Chronologie - 2013: The generator-jhipster repository and npm package were created. - 2014: Release 1.1.0 described JHipster as Yeoman plus Maven plus Spring plus AngularJS. - 2015: Release 2.0.0 described the stack as Spring Boot plus AngularJS. - 2016: Release 3.0.0 added complete microservices architecture generation. - 2018: Release 5.0.0 moved React support out of experimental status. - 2026: Release 9.0.0 continued the major-version line after the 8.x series. ### Related projects - Yeoman is the generator framework lineage behind early JHipster. - Spring Boot is the Java application framework at the center of generated server projects. - Angular, React, and Vue are front-end options represented across JHipster release lines and generated applications. - JDL Studio and the JHipster module marketplace are related tools in the JHipster ecosystem. ### 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: ./.yo-rc.json ## Autres enregistrements de gestionnaires de paquets - Chocolatey - jhipster: normalized package name match | Chocolatey community package catalog: jhipster from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='6.928','obs-virtualcam' ## Combined YAML source View the package source record on GitHub. [combined/jhipster.yml](https://github.com/mxcl/pkgdb/blob/main/combined/jhipster.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph