eirslett/frontend-maven-plugin

"Maven-node-grunt-gulp-npm-node-plugin to end all maven-node-grunt-gulp-npm-plugins." A Maven plugin that downloads/installs Node and NPM locally, runs NPM...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 55 minutes ago
Type:Plugin / ExtensionCategory(s):Build Systems & Package ManagersDeveloper Tools
Added to GitGenius on September 15th, 2026
Created on August 30th, 2013
Open Issues & Pull Requests: 306 (+0)
GitHub issues: Enabled
Number of forks: 870
Total Stargazers: 4,383 (+0)
Total Subscribers: 119 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 38.1 hours
Mean response time: 351.4 days
90th percentile: 745.2 days
Tracked items: 72

Most active contributors

Sign in to see contributor activity.

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 98% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 27
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 872 days
Stale 30+ days: 25
Stale 90+ days: 23

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

frontend-maven-plugin is a Maven plugin that integrates Node.js and frontend build tools into Maven-based Java projects.

The plugin solves the problem of managing Node.js, NPM, and frontend build orchestration within a Maven build lifecycle. Rather than requiring developers to install Node and frontend tools separately on their machines or build servers, the plugin downloads and installs Node and NPM locally as part of the Maven build process. It then executes frontend build tasks through NPM, Grunt, Gulp, and Karma, allowing frontend and backend builds to be unified under a single Maven command.

Teams working on projects that combine Java backends with Node.js-based frontends benefit most from this tool. It suits organizations that have standardized on Maven and want to avoid maintaining separate build systems or installation procedures for different parts of their codebase. The plugin is particularly valuable in continuous integration environments where build servers should not require pre-installed Node.js or frontend tooling, since the plugin handles all necessary downloads and setup automatically.

The project shows consistent maintenance with regular updates addressing compatibility and bug fixes. Pull requests are reviewed and merged steadily, indicating active engagement with contributions. Issues are addressed with reasonable responsiveness, and the maintainer provides clear guidance on usage patterns and troubleshooting. The codebase remains stable with incremental improvements rather than disruptive rewrites, suggesting a pragmatic approach to evolution that respects existing users while incorporating necessary enhancements.