JHipster

JHipster is a development tool used to quickly build modern web applications and services.

  • Development
  • Tools & Utilities
JHipster is a development tool used to quickly build modern web applications and services. It provides a pre-configured blueprint that combines several technologies, saving time by automatically creating the underlying structure. It is commonly used by developers to launch high-quality software projects with minimal manual setup.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

79/100 Good

Maintained
100last commit 3 days ago
Popular
8722,462 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
22,462
Open issues
62
Last commit
2026-11-18
Latest release
v9.4.0
License
Apache-2.0
Activity
steady

Checked 3 days ago - source: GitHub (jhipster/generator-jhipster)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set up your domain and HTTPS Install Apache and Certbot, then run the certbot command with your real domain name and email, and add the provided renewal line to cron (the system's scheduled task list). This gives the app a trusted HTTPS address and keeps it from showing certificate errors after the certificate expires. source
  • Install the app's packages first Run npm install inside the app folder before starting anything; npm is the package manager that downloads missing files. This prevents failed starts and 'module not found' errors caused by missing pieces. source
  • Start Keycloak if you use login If your JHipster app is configured for Keycloak, run npm run docker:keycloak:up before signing in. Keycloak is the login/security service, and without it the app may not be able to create or verify user accounts. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What should I check before running JHipster on a project I did not author?

Check the .yo-rc.json trust model before running the generator. Its properties become part of the generated application, and blueprints declared there are executed on your machine.

What should I do if the app uses Keycloak for login?

Run npm run docker:keycloak:up before signing in. Without that login service running, the app may not be able to create or verify user accounts.

How do I set up HTTPS for a production JHipster deployment?

Install Apache and Certbot, run Certbot with your real domain name and email, then add the provided renewal line to cron. That gives the app a trusted HTTPS address and avoids certificate errors after the certificate expires.

What should I expect when upgrading an existing JHipster app?

An existing app may need updates merged in when moving to a newer JHipster version. The project updates dependencies and may change or rewrite code to keep up with best practices and security.

Answers sourced from github.com, github.com, github.com, www.reddit.com

Community

Collected 48 days ago - public community threads