Is bower healthy, maintained, and safe?

The verdict

OSPulse scores bower at 20/100 (high risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. No — bower looks abandoned and still has open security advisories.

The last sign of life was 14 March 2022, more than 4 years ago (1596 days); by any practical measure the package looks abandoned. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. Two maintainers are listed; better than a lone author, but still a thin bench if one steps away.

OSV lists 1 known advisory for bower, including 1 high. Review whether your version is in the affected range and whether a fixed release is available before depending on it. Each advisory is listed with its OSV/GHSA identifier below.

Treat bower as a liability to manage: review the evidence above, pin or patch, and evaluate alternatives. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.