# aurelia/aurelia

Aurelia 2, a standards-based, front-end framework designed for high-performing, ambitious applications.

Repository: https://github.com/aurelia/aurelia
Canonical: https://ross.abutalabs.com/products/aurelia
Language: TypeScript
License: MIT
License Family: permissive
Topics: aurelia, typescript, javascript, web, pwa, web-framework, web-performance, html, mobile, spa, framework, single-page-applications, cross-platform, javascript-framework, frontend, electron, cordova
Last push: 2026-08-26T11:56:06+00:00

## Health v2 (maintenance only)
Score: 86/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 60, longevity 100
- inputs: {"age_days": 3121, "days_push": 7, "days_rel": 29, "gap_med": 83.0, "n_releases_24m": 9}
- flags: prerelease_only
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1537, forks 148 (observed 2026-08-28T04:05:00.028740+00:00)

## What it is
Aurelia 2 is a standards-based front-end JavaScript/TypeScript framework for building browser, mobile, and desktop single-page applications with minimal framework intrusion and convention over configuration. This repository is the monorepo containing its core packages, plugins, examples, benchmarks, and documentation.

## Use cases
- build a single-page application with a modern javascript framework
- create a progressive web app with data binding
- develop cross-platform apps for browser, mobile, and desktop from one codebase
- build components from plain typescript classes with html templates
- migrate away from heavier frameworks like angular with less boilerplate
- two-way bind form inputs with debouncing and conditional rendering

## When to choose
- you want a frontend framework that stays close to web standards with vanilla JS/TS classes and HTML templates
- you prefer convention over configuration and minimal framework intrusion
- you need one framework targeting browser, Electron, and Cordova/mobile apps
- you value powerful built-in templating and binding syntax

## When to avoid
- you need a fully stable, long-term-supported framework - Aurelia 2 is still in beta with possible breaking changes
- your team relies on a huge ecosystem of ready-made components and hiring pools like React or Vue
- you want server-side rendering as a first-class built-in feature
- you prefer explicit configuration over conventions

## Facets
- artifact type: framework
- maturity: active
- function: web-framework, frontend-framework, ui-components, state-management, templating, routing
- domain: web-development, frontend, cross-platform, developer-tools
- platform: browser, cross-platform
- tags: spa, typescript, javascript-framework, pwa, convention-over-configuration, data-binding, web-components, monorepo, beta, nodejs, web-server, electron, mobile

## Member repositories
- aurelia/aurelia (main) score 86

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:00.028740+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:31:00.286110+00:00, confidence not recorded.
  - readme: https://github.com/aurelia/aurelia (fetched 2026-08-28T04:05:00.028740+00:00, sha fb55c6a6e51e)
- Data as of 2026-08-30T08:39:29.467469+00:00.
