Is @types/bcryptjs still maintained?

deprecated as of 2026-10-17 — deprecated

As of 2026-10-17, the npm package @types/bcryptjs is recorded deprecated: the package's latest version carries an npm deprecation notice set by its publisher. Latest published version dated 2025-03-14. An npm deprecation notice was first read on 2026-08-01. 73 dated observation(s) on record since 2026-08-01; 162 dependent package(s) read 2026-10-17.

npm package @types/bcryptjs is recorded as deprecated in the lastseen.dev component-maintenance dataset as of 2026-10-17. Definition: the package's latest version carries an npm deprecation notice set by its publisher. Adoption at the latest read: 162 dependent packages (read 2026-10-17). The page carries 73 dated observations from 2026-08-01 onward. The recorded state did not change across the series. An npm deprecation notice was first read on 2026-08-01. 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":"@types/bcryptjs","kind":"npm"}]}' — add ?as_of=2026-10-17 for a point-in-time read. See /api/v1/docs.

State (latest)

deprecated — the package's latest version carries an npm deprecation notice set by its publisher

Latest published version

2025-03-14

npm deprecation notice

recorded (first read 2026-08-01)

Dated observations

73, from 2026-08-01 to 2026-10-17

State changes

0 across the series

Adoption (latest read 2026-10-17)

162 dependent package(s)

Method

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

Source / evidence

npmjs.com/package/@types/bcryptjs

Observed as of

2026-10-17

Registry

npm

Interval-censoring. Observation window from 2026-08-01 to 2026-10-17, with 73 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-10-17). 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 73 dated observations from 2026-08-01 to 2026-10-17, the recorded state did not change: it remained deprecated throughout the observed window.

An npm deprecation notice was recorded on 2026-08-01 and is a publisher-set flag on the package's latest version.

When was it last published?

The latest published version read for @types/bcryptjs was dated 2025-03-14. State deprecated reflects a publisher-set npm deprecation notice on that version.

What is its recorded state?

State deprecated: the package's latest version carries an npm deprecation notice set by its publisher, read on the observation date 2026-10-17.

What does that mean for projects depending on it?

At the latest adoption read (2026-10-17) the npm registry listed 162 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: 73 observations from 2026-08-01 to 2026-10-17, each with a state and the latest-published date, plus 0 state change(s) and a deprecation flag. A dispute re-reads the public npm metadata and issues a dated correction on this page.

Other packages under this scope

• nodealive2026-10-17
• reactalive2026-10-17
• jestalive2026-10-17
• react-domalive2026-10-17
• expressalive2026-10-17