libsignal versions and release history

Inspect a published release before upgrading or adding a dependency. Each version reference keeps its metadata and provider measurements pinned to that exact npm version.

Published versions14
Stable versions14
Prereleases0
Releases published in the last 90 days0
Deprecated releases13
Latest npm dist-tag6.0.0

All available releases

VersionPublishedRuntime dependenciesTypesStatus
6.0.02026-05-13T08:11:23.790Z2Bundledlatest
2.0.12019-01-11T17:55:57.822Z1Not declaredUnstable and contains protocol/security bugs. Use libsignal@>=6.0.0.
2.0.02018-08-14T00:26:18.645Z1Not declaredUnstable and contains protocol/security bugs. Use libsignal@>=6.0.0.
1.2.22018-04-04T22:58:25.986Z1Not declaredUnstable and contains protocol/security bugs. Use libsignal@>=6.0.0.
1.2.12018-01-14T21:18:44.498Z1Not declaredUnstable and contains protocol/security bugs. Use libsignal@>=6.0.0.
1.2.02018-01-13T00:58:00.712Z1Not declaredUnstable and contains protocol/security bugs. Use libsignal@>=6.0.0.
1.0.72017-11-15T23:58:03.353Z1Not declaredUnstable and contains protocol/security bugs. Use libsignal@>=6.0.0.
1.0.62017-10-16T23:24:22.226Z1Not declaredUnstable and contains protocol/security bugs. Use libsignal@>=6.0.0.
1.0.52017-10-16T21:03:05.625Z1Not declaredUnstable and contains protocol/security bugs. Use libsignal@>=6.0.0.
1.0.42017-10-16T06:29:08.124Z1Not declaredUnstable and contains protocol/security bugs. Use libsignal@>=6.0.0.
1.0.32017-10-15T20:50:24.128Z1Not declaredUnstable and contains protocol/security bugs. Use libsignal@>=6.0.0.
1.0.22017-10-15T20:23:46.409Z1Not declaredUnstable and contains protocol/security bugs. Use libsignal@>=6.0.0.
1.0.12017-10-15T20:14:09.245Z1Not declaredUnstable and contains protocol/security bugs. Use libsignal@>=6.0.0.
1.0.02017-10-15T20:11:05.903Z1Not declaredUnstable and contains protocol/security bugs. Use libsignal@>=6.0.0.

Choosing a version

The latest tag is selected by the publisher and is not a guarantee of compatibility. Prerelease and deprecated status remain visible. Check your Node.js range and peer requirements on the exact version page, then review the maintainer’s release notes before upgrading.

Removed or unpublished versions may be absent. Historical download charts cover all package versions and do not show adoption of an individual release.

npm release-history source — retrieved 2026-10-29T12:16:59.769Z