NPM LIBRARY
@kozojs/cli
Official package-registry history. This page does not infer support or EOL from release activity.
- Versions indexed
- 50
- Latest version activity
- 0.7.1
- Latest registry signal
- Published
- Last synchronized
- 26 Sep 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.
| Version | Registry event | Signal | Release notes | Evidence |
|---|---|---|---|---|
| 0.7.1 | 10 Aug 2026 | PUBLISHED | Not checked yet | Official event ↗ |
| 0.7.0 | 27 Jul 2026 | PUBLISHED | Not checked yet | Official event ↗ |
| 0.6.1 | 25 Jul 2026 | PUBLISHED | Not checked yet | Official event ↗ |
| 0.6.0 | 25 Jul 2026 | PUBLISHED | Not checked yet | Official event ↗ |
| 0.5.23 | 25 Jul 2026 | PUBLISHED | Not checked yet | Official event ↗ |
| 0.5.22 | 24 Jul 2026 | PUBLISHED | Not checked yet | Official event ↗ |
| 0.5.20 | 13 Jul 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.5.17 | 17 Jun 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.5.16 | 11 Jun 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.5.13 | 11 Jun 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.5.12 | 11 Jun 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.5.11 | 10 Jun 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.5.10 | 3 Jun 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.5.9 | 31 May 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.5.2 | 30 May 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.5.1 | 30 May 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.5.0 | 30 May 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.4.1 | 29 May 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.4.0 | 29 May 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.34 | 2 Apr 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.33 | 7 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.32 | 7 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.31 | 5 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.30 | 4 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.29 | 4 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.28 | 4 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.27 | 4 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.26 | 4 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.25 | 4 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.24 | 4 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.23 | 4 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.22 | 4 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.21 | 4 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.20 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.19 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.18 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.17 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.16 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.15 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.14 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.13 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.12 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.11 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.10 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.9 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.8 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.7 | 3 Mar 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.6 | 1 Feb 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.5 | 1 Feb 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |
| 0.1.4 | 10 Jan 2026 | DEPRECATEDSecurity: generated projects sign JWTs with a publicly-known default secret. Upgrade to >=0.5.22 AND rotate JWT_SECRET — upgrading alone does not fix an already-deployed app. | Not checked yet | Official event ↗ |