starred/json

0 Fork 0

mirror of https://github.com/nlohmann/json.git synced 2026-11-14 03:18:20 +00:00

Files

T

Niels Lohmann c9d30bf924 Correct the UTF-8 claims for binary input in the security guide

untrusted_input.md said that a string that is not valid UTF-8 in a
binary format is a parse_error.113. By default the readers keep the
bytes unchanged (error_handler_t::keep); only error_handler_t::strict
gives parse_error.113, and BON8 always validates and reports
parse_error.112. Checked with from_cbor, from_msgpack, from_ubjson,
from_bjdata and from_bson (strings and keys), default and strict, and
with from_bon8: default accepts the bytes, strict gives 113, BON8 gives
112 (as in tests/src/unit-bon8.cpp).

Changes:
- the Strings section says so, and its lead-in is limited to JSON text;
- the sentence that named JSON_STRICT_NUL_HANDLING as a source of
  unvalidated strings (unrelated to the binary readers) now names the
  default error_handler_t::keep;
- the checklist tells the reader to pass error_handler_t::strict to the
  from_* function for untrusted binary input;
- json_strict_binary_utf8.md listed from_cbor as "also affected" although
  the same page says the binary readers behave independent of the macro,
  which is what the code does (verified with the macro defined to 1:
  from_cbor, from_msgpack and from_ubjson still accept 0xFF).

Documentation only.

Signed-off-by: Niels Lohmann <mail@nlohmann.me>

2026-11-11 09:18:56 +01:00

docset

Fix Semgrep findings in Python tooling (#5899 )

2026-10-23 07:11:17 +02:00

mkdocs

Correct the UTF-8 claims for binary input in the security guide

2026-11-11 09:18:56 +01:00

avatars.png

🔖 set version to 3.12.0 (#4727 )

2025-04-11 10:41:14 +02:00

Makefile

Review and extend the documentation, and check it in CI (#5638 )

2026-10-02 11:32:15 +02:00

README.md

Clean up non-code files (#5801 )

2026-10-11 08:21:51 +02:00

README.md

Documentation

Generate documentation

Note on documentation: The source files contain links to the online documentation at https://json.nlohmann.me.
This URL provides the most recent documentation and also applies to previous versions. Documentation for deprecated functions is not removed; instead, it is marked as deprecated.

If you want to view the documentation for a specific tag or commit hash, you can generate it locally as follows (example using tag v3.12.0):

git clone https://github.com/nlohmann/json.git
cd json
git checkout v3.12.0
make install_venv serve -C docs/mkdocs

Open http://127.0.0.1:8000/ in your browser. Replace any URL in the source code that points to https://json.nlohmann.me with http://127.0.0.1:8000 to view the documentation for the selected tag or commit hash.