Chandra OCR 2 vs DeepSeek-OCR 2

Chandra OCR 2 70

Chat template 20, chat_template.jinja in the repository (7,622 characters), Qwen 3.5's template, with a copy in tokenizer_config.json. Tool-calling format 25, Read for a document parser as what it takes and returns. Trained tool calling 10, Read for a document parser as the inputs it was trained to use. Structured output 15, Read for a document parser as typed outputs. Reasoning control 0, A document parser run without reasoning. Context 0, Datalab states no context length for it. 20 + 25 + 10 + 15 + 0 + 0 = 70.

DeepSeek-OCR 2 35

Chat template 10, no Jinja template in the repository and none in tokenizer_config.json. Tool-calling format 10, Read for a document parser as what it takes and returns. Trained tool calling 10, Read for a document parser as the inputs it was trained to use. Structured output 5, Read for a document parser as typed outputs. Reasoning control 0, A document parser with no reasoning. Context 0, config.json gives 8,192 positions, below the 32K band. 10 + 10 + 10 + 5 + 0 + 0 = 35.

Chandra OCR 2 33

Model card 8, Intended use and the languages (over 90) are on the card. Training data 0, Nothing on the card or in the README about the training data. Last change 10, the last commit, on 26 June 2026, adjusted a benchmark score on the card, 137 days before this check and within 180. Responsiveness 0, none of the 8 discussions that aren't pull requests (8 April to 23 September 2026) has a reply from a datalab-to member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, Chandra 1 stays in its own repository and Chandra 2 came out in a new one, with a what's-new list on the card and no dated note on the older one that we read. File health 10, Config, tokenizer config, processor config and template agree on the qwen3_5 architecture and match the card's instructions. 8 + 0 + 10 + 0 + 5 + 10 = 33.

DeepSeek-OCR 2 22

Model card 2, Intended use is there, as the two prompts. Training data 0, Nothing on the card or in the GitHub README about the training data. Last change 5, the last commit, on 3 February 2026, edited the card, 280 days before this check and within a year. Responsiveness 0, none of the 21 discussions that aren't pull requests (27 January to 1 October 2026) has a reply from a deepseek-ai member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, the first DeepSeek-OCR stays in its own repository and this one came out in a new one, without a dated note on the older card that we read. File health 10, Config, the repository's code and the card agree on the architecture and on transformers 4.46.3. 2 + 0 + 5 + 0 + 5 + 10 = 22.

Chandra OCR 2 45

File safety 25, one safetensors file, no .bin, .pt or .pth files and no Python in the model repository. Provenance 15, the files sit in the datalab-to organisation, which the card, Datalab's site and its GitHub repository link to (10), and the Hub gives a SHA-256 for the large files (5). Safety evaluation 0, no safety results on the card or in the README. Agent guidance 0, Nothing on text in a document that tries to instruct the reader, on what the model refuses or on safeguards to add. Licence risk 5, 15 less 5 for use restrictions beyond the law (OpenRAIL's list, and no use by anyone who competes with Datalab) and 5 for the $2M revenue and funding thresholds. Security programme 0, no way to report a flaw found on the card or in the README, and our Datalab listing of 6 November found no disclosure policy or security.txt. 25 + 15 + 0 + 0 + 5 + 0 = 45.

DeepSeek-OCR 2 50

File safety 15, safetensors only, no .bin, .pt or .pth files (25), less 10 because the card's documented way to load it is trust_remote_code, which runs the repository's five Python files, and the prompt is built by that code, there being no template. Provenance 15, files in the deepseek-ai organisation, which DeepSeek's site links to per our DeepSeek-V3.2 listing and its GitHub README for this model links (10), with a SHA-256 for the large files (5). Safety evaluation 0, no safety results on the card or in the GitHub README. Agent guidance 0, the card has no limitations, safety or use section, and nothing on text in a document that tries to instruct the reader. Licence risk 15, Apache 2.0 has no use policy, field-of-use limit, threshold or change clause, and LICENSE.txt is in the repository. Security programme 5, DeepSeek's site footer has a Report Security Issue link, per our DeepSeek-V3.2 listing (5). 15 + 15 + 0 + 0 + 15 + 5 = 50.