Is @tiptap/extension-code-block still maintained?

alive as of 2026-09-11 — alive

As of 2026-09-11, the npm package @tiptap/extension-code-block is recorded alive: the package's latest published version on npm was within 180 days of the observation. Latest published version dated 2026-09-04. 40 dated observation(s) on record since 2026-08-01; 101 dependent package(s) read 2026-09-11.

npm package @tiptap/extension-code-block is recorded as alive in the lastseen.dev component-maintenance dataset as of 2026-09-11. Definition: the package's latest published version on npm was within 180 days of the observation. Adoption at the latest read: 101 dependent packages (read 2026-09-11). The page carries 40 dated observations from 2026-08-01 onward. The recorded state did not change across the series. Method: read from the public npm registry metadata — the latest-published timestamp and the deprecation flag (authoritative). This is a dated factual observation series about one npm package, not advice about any named party.

API (npm is POST-only): curl -X POST https://lastseen.dev/api/v1/manifest -H 'Content-Type: application/json' -d '{"components":[{"name":"@tiptap/extension-code-block","kind":"npm"}]}' — add ?as_of=2026-09-11 for a point-in-time read. See /api/v1/docs.

State (latest)

alive — the package's latest published version on npm was within 180 days of the observation

Latest published version

2026-09-04

npm deprecation notice

none on record

Dated observations

40, from 2026-08-01 to 2026-09-11

State changes

0 across the series

Adoption (latest read 2026-09-11)

101 dependent package(s)

Method

npm registry metadata — latest-published timestamp + deprecation flag (authoritative)

Source / evidence

npmjs.com/package/@tiptap/extension-code-block

Observed as of

2026-09-11

Registry

npm

Interval-censoring. Observation window from 2026-08-01 to 2026-09-11, with 40 dated observations. A state transition inside an unobserved span is dated to that interval, not to a single day. The dependent count is the value carried with the latest census (2026-09-11). Absence of an observation on a date is recorded as not observed, never as a state.

A dated observation series, not advice. Data under CC-BY-4.0. Check every dependency in one place: check your whole organization.

Dated observation series

State-mutation history

Across 40 dated observations from 2026-08-01 to 2026-09-11, the recorded state did not change: it remained alive throughout the observed window.

When was it last published?

The latest published version read for this package was dated 2026-09-04. State alive reflects the package's latest published version on npm was within 180 days of the observation.

What is its recorded state?

State alive is derived from the public npm registry metadata read on each observation date: the package's latest published version on npm was within 180 days of the observation.

What does that mean for projects depending on it?

At the latest adoption read (2026-09-11) the npm registry listed 101 dependent package(s) on this package — the adoption signal that qualifies it for a page. A project that lists this package as a dependency continues to install its last published version; a caret or tilde version range has no newer release to resolve to. This is a dated observation, not advice about any named party.

What is the observation record?

The record is the dated series above: 40 observations from 2026-08-01 to 2026-09-11, each with a state and the latest-published date, plus 0 state change(s). A dispute re-reads the public npm metadata and issues a dated correction on this page.

Other packages under this scope

• corealive2026-09-11
• corealive2026-09-11
• corealive2026-09-11
• corealive2026-09-11
• corealive2026-09-11