NPM LIBRARY
is-my-json-valid
Official package-registry history. This page does not infer support or EOL from release activity.
- Versions indexed
- 64
- Latest version activity
- 2.20.6
- Latest registry signal
- Published
- Last synchronized
- 25 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 |
|---|---|---|---|---|
| 2.20.6 | 10 Nov 2021 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.20.5 | 22 Jul 2020 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.20.4 | 29 Jun 2020 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.20.3 | 29 Jun 2020 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.20.2 | 29 Jun 2020 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.20.1 | 26 Jun 2020 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.20.0 | 7 May 2019 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.19.0 | 13 Aug 2018 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.18.0 | 9 Aug 2018 | PUBLISHED | Not checked yet | Official event ↗ |
| 1.4.2 | 14 Feb 2018 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.17.2 | 14 Feb 2018 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.17.1 | 18 Dec 2017 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.17.0 | 18 Dec 2017 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.16.1 | 23 Aug 2017 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.16.0 | 26 Feb 2017 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.15.0 | 2 Oct 2016 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.14.0 | 19 Sep 2016 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.13.1 | 22 Feb 2016 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.13.0 | 18 Feb 2016 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.12.4 | 17 Jan 2016 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.12.3 | 6 Nov 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.12.2 | 28 Aug 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.12.1 | 26 Jul 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.12.0 | 15 May 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.11.0 | 10 May 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.10.1 | 8 Apr 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.10.0 | 12 Mar 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.9.4 | 25 Feb 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.9.3 | 23 Feb 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.9.2 | 23 Feb 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.9.1 | 19 Feb 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.9.0 | 18 Feb 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.8.0 | 16 Feb 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.7.0 | 13 Feb 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.6.0 | 13 Feb 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.5.0 | 12 Feb 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.4.1 | 10 Feb 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.4.0 | 9 Feb 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.3.1 | 4 Feb 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.3.0 | 29 Jan 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.2.1 | 29 Jan 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.2.0 | 28 Jan 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.1.0 | 28 Jan 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.0.3 | 23 Jan 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.0.2 | 22 Jan 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.0.1 | 22 Jan 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 2.0.0 | 22 Jan 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.4.1 | 11 Jan 2015 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.4.0 | 22 Oct 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.3.9 | 22 Oct 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.3.8 | 2 Oct 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.3.7 | 21 Aug 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.3.6 | 4 Aug 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.3.5 | 4 Aug 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.3.4 | 4 Aug 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.3.3 | 2 Aug 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.3.2 | 2 Aug 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.3.1 | 2 Aug 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.3.0 | 1 Aug 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.2.0 | 31 Jul 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.1.0 | 31 Jul 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.0.1 | 31 Jul 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 1.0.0 | 31 Jul 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 as soon as possible | Not checked yet | Official event ↗ |
| 0.0.0 | 31 Jul 2014 | DEPRECATEDcatastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 1.4.2 or 2.17.2 as soon as possible | Not checked yet | Official event ↗ |