Data
The open dataset behind unrom: device–ROM compatibility, available as JSON, SQLite, and a REST API.
Catalogue
- Devices
- 9,110
- Brands
- 70
- ROMs
- 277
Coverage
- Devices with ROM data
- 94010% of devices
- ROMs with device data
- 5620% of ROMs
Downloads
No key and no authentication. Device lists paginate with limit and offset (maximum 200) and return the total in x-total-count. Response shapes are frozen in contract/.
- GET
/api/health - GET
/api/openapi.json - GET
/api/meta - GET
/api/summary - GET
/api/devices?q=&vendor=&letter=&limit=&offset=&all= - GET
/api/devices/letters - GET
/api/brands - GET
/api/devices/:vendor/:codename - GET
/api/search?q= - GET
/api/registry?q=&vendor= - GET
/api/roms - GET
/api/roms/:id - GET
/api/data - GET
/api/export/json - GET
/api/export/sqlite
What is in the dataset
Entities
- Vendors and their devices.
- Devices with codenames, model names, and aliases.
- ROMs and their status.
- Device–ROM mappings with a source URL.
Fields
- Names, codenames, aliases, and build groups.
- ROM status and per-device build references.
- Name confidence and the sources behind it.
Not included: ROM downloads, device specifications, or install instructions. Catalogue-only ROMs have no device data yet.
Provenance and license
Each mapping keeps the source URL it came from. Device lists are read from ROM projects' own sources, with catalogue coverage from ROMDB.tel, Customrombay, and the awesome list. Raw snapshots live in data/.
Data is ODbL-1.0 and code is AGPL-3.0-only. Android is a trademark of Google LLC. Other names belong to their owners and are used for identification only.
Freshness
The dataset is rebuilt from the snapshots in data/. The content hash changes when the data changes.
- Last built
- Content hash
fdfb77c9d4528991
Corrections
Found a wrong mapping or a missing device? Open an issue or read the contribution guide. Changes require a DCO sign-off.