connect-history-api-fallback
/All repositories
Overview
HEALTH SCORE
Concerning
33out of 100
Development cadence is the lead risk. Security posture and maintainer coverage are present but not enough to offset the structural risk.
LIFECYCLE
Active
Consistent commits, responsive maintainers, regular releases, and healthy issue triage.
Health breakdown
Concerning(33/100)
Maintainer availability, known risks and supply chain posture, and whether the project is actively developed or appropriately stable.
Maintainer responsiveness
No PRs or issues were opened in the review window, so response time could not be measured.
Bus factor
No data available. Repository has not been indexed for bus factor.
Organization Diversity
Contributors span 3 organizations.
Project Achievements
Leaderboards
About
A Node.js middleware that provides a fallback for single-page applications using HTML5 History API routing, allowing the server to return the main index.html file for client-side routes instead of 404 errors
First commit
Software value
$19K
License(s)
MIT
Data sources
Git
GitHub