Ross ROSS = Recommend OSS · open-source software intelligence for agents

browserstate/history.js

History.js gracefully supports the HTML5 History/State APIs (pushState, replaceState, onPopState) in all browsers. Including continued support for data, titles, replaceState. Supports jQuery, MooTools and Prototype. For HTML5 browsers this means that you can modify the URL directly, without needing to use hashes anymore. For HTML4 browsers it will revert back to using the old onhashchange functionality. observed · 2026-08-28

github.com/browserstate/history.js · homepage · JavaScript · NOASSERTION (other) observed · 2026-08-28

Health v2 · maintenance only

32/100

  • Activity 0
  • Release rhythm 35
  • Longevity 100

Flags: no_releases no_license

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 5704
  • days_rel: n/a
  • days_push: 1663
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

10654 stars · 1302 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

History.js is a JavaScript library that provides a normalized wrapper around the HTML5 History/State APIs (pushState, replaceState, onPopState) across all browsers, falling back to hashchange-based behavior in HTML4 browsers. It supports adapters for jQuery, MooTools, and Prototype and is now maintained only in a legacy/archival condition.

Use cases

  • normalize browser history APIs across browsers
  • support pushState in legacy HTML4 browsers
  • manage client-side routing state without page reloads
  • handle back/forward button navigation in single-page apps
  • modify the URL without hashes in older browsers

When to choose

  • you must support legacy HTML4 browsers that lack native pushState
  • you need consistent history behavior across very old browser versions
  • you are maintaining an existing codebase already built on History.js

When to avoid

  • you target only modern browsers - use the native HTML5 History API instead
  • you need an actively maintained library with ongoing bug fixes
  • you are starting a new single-page application - modern frameworks have built-in routing

Facets

library · maturity abandoned

routing state-management middleware web-development frontend browser-extensions browser cross-platform polyfill html5-history-api pushstate hashchange jquery-plugin legacy-browser-support javascript

1 source

Member repositories

RepositoryRoleHealth v2
browserstate/history.jsmain32

For agents

markdown · JSON · MCP: product_card(name="browserstate/history.js")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem