BlackTreeLifecycle intelligence
Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT

NPM LIBRARY

@majikah/majik-signature

Official package-registry history. This page does not infer support or EOL from release activity.

Versions indexed
51
Latest version activity
0.9.0
Latest registry signal
Published
Last synchronized
5 Oct 2026
Authoritative registry

Version entries link to the official registry catalogue event that supplied the record.

Open package on npm ↗
Lifecycle interpretation

Publication or deletion in a package registry is a distribution signal, not a promise of maintenance or security support. Any verified publisher EOL boundary remains in the main lifecycle catalogue.

Package-version activity

Newest official registry events first.

51 records
VersionRegistry eventSignalRelease notesEvidence
0.9.05 Oct 2026PUBLISHEDChecked, none publishedOfficial event ↗
0.8.34 Oct 2026PUBLISHEDChecked, none publishedOfficial event ↗
0.8.24 Oct 2026PUBLISHEDChecked, none publishedOfficial event ↗
0.8.14 Oct 2026PUBLISHEDChecked, none publishedOfficial event ↗
0.8.04 Oct 2026PUBLISHEDChecked, none publishedOfficial event ↗
0.7.22 Oct 2026PUBLISHEDChecked, none publishedOfficial event ↗
0.7.126 Sep 2026PUBLISHEDChecked, none publishedOfficial event ↗
0.7.022 Sep 2026PUBLISHEDChecked, none publishedOfficial event ↗
0.6.019 Sep 2026PUBLISHEDChecked, none publishedOfficial event ↗
0.5.119 Sep 2026PUBLISHEDChecked, none publishedOfficial event ↗
0.5.019 Sep 2026PUBLISHEDChecked, none publishedOfficial event ↗
0.4.12 Sep 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.4.01 Sep 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.3.015 Aug 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.2.915 Aug 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.2.86 Aug 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.2.73 Aug 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.2.62 Aug 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.2.52 Aug 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.2.41 Aug 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.2.31 Aug 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.2.231 Jul 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.2.126 Jul 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.2.015 Jul 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.1.011 Jul 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.3211 Jul 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.3111 Jul 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.307 Jul 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.2929 Jun 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.2826 Jun 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.2623 Jun 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.2521 Jun 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.1921 Jun 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.1821 Jun 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.1714 Apr 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.163 Apr 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.1526 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.1425 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.1325 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.1225 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.1125 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.1022 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.919 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.819 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.719 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.618 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.518 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.418 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.316 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.215 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗
0.0.115 Mar 2026DEPRECATEDSecurity vulnerability: verification could accept files with content appended after the signature block. Upgrade to @majikah/majik-signature@0.5.0 or later.Checked, none publishedOfficial event ↗