# blockprotocol/blockprotocol

✨ The open-source standard for blocks. From @hashintel

Repository: https://github.com/blockprotocol/blockprotocol
Canonical: https://ross.abutalabs.com/products/blockprotocol
Homepage: https://blockprotocol.org
Language: TypeScript
License: NOASSERTION
License Family: other
Topics: blocks, block-protocol
Last push: 2026-08-12T02:27:28+00:00

## Health v2 (maintenance only)
Score: 66/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 97, release rhythm 8, longevity 100
- inputs: {"age_days": 1963, "days_push": 22, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1437, forks 48 (observed 2026-08-28T04:04:43.714563+00:00)

## What it is
Block Protocol is an open standard (with a TypeScript monorepo of libraries and tooling) defining how data-driven, interoperable frontend components called 'blocks' communicate with the applications that embed them. It includes a core specification, module specs, developer libraries, a CLI, and a public hub registry of blocks and services.

## Use cases
- build interoperable embeddable ui blocks
- add a block plugin system to my web app
- publish reusable frontend components to a registry
- embed structured data blocks in wordpress gutenberg
- standardize communication between app and embedded components
- create a react block with typed entity data

## When to choose
- you want blocks that work across multiple conforming applications without per-app integration
- you're building an app that should be infinitely extensible with third-party components
- you want typed, semantic data structures in editable content blocks

## When to avoid
- you need a mature, actively developed standard - work on version 0.4 has been paused
- you only need blocks within a single app with no interoperability goals
- you need environments beyond WordPress/HASH, like Figma, which are not yet supported

## Facets
- artifact type: framework
- maturity: maintenance
- function: ui-components, frontend-framework, plugin-system, sdk, developer-tools
- domain: web-development, frontend, developer-tools, apis
- platform: cross-platform
- tags: block-protocol, interoperable-blocks, embeddable-components, open-standard, specification, monorepo, wordpress-plugin, react, web-server, nodejs, typescript

## Member repositories
- blockprotocol/blockprotocol (main) score 66

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:43.714563+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:36:43.433002+00:00, confidence not recorded.
  - readme: https://github.com/blockprotocol/blockprotocol (fetched 2026-08-28T04:04:43.714563+00:00, sha 1d7d93511d0b)
  - homepage: https://blockprotocol.org (fetched 2026-08-29T11:47:52.290875+00:00, sha cc1d955cbd19)
  - site_page: https://blockprotocol.org/docs/blocks/environments (fetched 2026-08-29T11:47:52.293418+00:00, sha cf639c9619d8)
  - site_page: https://blockprotocol.org/docs/blocks/develop (fetched 2026-08-29T11:47:52.295178+00:00, sha 9602869c1e4f)
  - site_page: https://blockprotocol.org/docs (fetched 2026-08-29T11:47:52.299534+00:00, sha 1555db69d283)
  - registry_npm: https://registry.npmjs.org/blockprotocol (fetched 2026-08-29T11:47:52.301049+00:00, sha 2d9d6ff316bd)
  - site_page: https://blockprotocol.org/@hash/blocks/faq (fetched 2026-08-29T11:47:52.297943+00:00, sha dd6c8ba197b4)
- Data as of 2026-08-30T08:39:29.467469+00:00.