Here are people who have contributed to the development of Jackson JSON processor
core component, version 3.x
(version numbers in brackets indicate release in which the problem was fixed)

(note: for older credits, check out `CREDITS-2.x`)

Tatu Saloranta, tatu.saloranta@iki.fi: author

PJ Fanning (pjfanning@github): co-author (2.15+)

----------------------------------------------------------------------------

Sven Döring (@sdoeringNew)
 * Contributed #680: Allow use of `java.nio.file.Path` as parser source, generator target
  (3.0.0)

@sri-adarsh-kumar
 * Contributed #1288: Add new method like `JsonParser.readText(Writer)` (and
   implementation) for truly non-buffering reads
  (3.1.0)

Nicholas Rayburn (@nrayburn-tech)
 * Contributed #1514: Additional configuration to closer match Jackson 2 behavior
  (3.1.0)

Henri Biström (@hb16)
 * Reported #1527: `TokenStreamFactory.createNonBlockingByteBufferParser()` return type wrong
  (3.1.0)

Afzal Najam (@AfzalivE)
 * Reported #1541: Unexpected Illegal surrogate character when parsing field names
  (3.1.0)

Prabhav Srinath (@sprabhav7)
 * Reported #1553: Max Depth validation not working for `DataInput`-backed `JsonParser`s
   in 3.0
  (3.1.0)

Rohan Nagendra (@rohan-repos)
 * Reported #1553: Max Depth validation not working for `DataInput`-backed `JsonParser`s
   in 3.0
  (3.1.0)

Rob Spoor (@robtimus)
 * Reported #1561: Javadoc for 3.1.0 doesn't work (build with JDK 21)
  (3.1.2)

Revanth Meesala (@revanthmeesala)
 * Contributed #1642: Fix maxDocumentLength bypass in async parser single-feedInput()
   case [GHSA-2c4j-63jj-9fqr]
  (3.1.6)

@tinyb0y
 * Contributed #1643: Enforce maxNameLength incrementally in ReaderBasedJsonParser
   [GHSA-649p-m576-vr99]
  (3.1.6)

Lee Dongnyoung (@DongNyoung)
 * Contributed #1651: Fix object context handling for buffered `INCLUDE_NON_NULL` tokens
  (3.1.6)
 * Contributed #1667: `JsonParser.willInternPropertyNames()` returns `true` even when
   `CANONICALIZE_PROPERTY_NAMES` is disabled
  (3.2.3)
 * Reported, fixed #1703: Validate name length in `UTF8DataInputJsonParser` before
   quad buffer growth
  (3.1.7)
 * Reported, fixed #1711: `File`/`Path` generator targets may be leaked, double-closed
   or truncated when construction fails
  (3.1.7)
 * Reported #1724: Use target exception's original message and type when wrapping
   `InvocationTargetException` with path information
  (3.1.8)

seonwoojung (@seonwooj0810)
 * Contributed #707: Add `JsonReadFeature.ALLOW_HEXADECIMAL_NUMBERS`
   for JSON5-style hexadecimal integer literals
  (3.2.0)

Max Paulus (@maxpaulus43)
 * Contributed #1211: Add `JsonParser.willInternPropertyNames()` to check whether
   property name interning is enabl
  (3.2.0)

Antonin Janec (@xtonik)
 * Contributed #1576: Use Java 17 intrinstics for long multiplication
  (3.2.0)

@hdimitrieski
 * Reported #1668: `WriterBasedJsonGenerator` AIOOBE when a zero-length custom
   escape lands at the output buffer boundary
  (3.1.7)

Burak KALAYCI (@kalayciburak)
 * Contributed #1668: `WriterBasedJsonGenerator` AIOOBE when a zero-length custom
   escape lands at the output buffer boundary
  (3.1.7)
 * Contributed #1718: `File`/`Path` parser sources leak if decorated stream
   `close()` fails on failed construction
  (3.1.7)
 * Contributed #1728: Quote supplementary code points in unexpected-character
   messages
  (3.1.8)

@youdie006
 * Reported #1713: `UTF32Reader` corrupts or drops the low surrogate when a
   supplementary character splits across a `read()` boundary
  (3.1.7)

@CCCLL
 * Contributed #1724: Use target exception's original message and type when wrapping
   `InvocationTargetException` with path information
  (3.1.8)

@bodograumann
 * Reported #1728: Unexpected-character messages drop the high bits of a
   supplementary code point
  (3.1.8)

Elankumaran Srinivasan (@elang2)
 * Contributed #1683: `ReaderBasedJsonParser` should reject JSON-escaped lone
   surrogates in property names (mirror of #1541 fix in `UTF8StreamJsonParser`)
  (3.1.8)

David R. MacIver (@DRMacIver)
 * Reported #1742: Non-blocking parser returns `NOT_AVAILABLE` but does not resume when
   a feed ends inside an escaped surrogate pair in a property name
  (3.1.8)

@ItsDeadlyProgrammer
 * Contributed #1756: Non-blocking parser does not decode multi-byte UTF-8 character
   after backslash escape
  (3.1.8)
