Hy-Memory-30B-A3B vs Spark-X2.6-4B

Hy-Memory-30B-A3B 68

Model card 8, Intended use (the write path of Mem0, MemOS and Hy-Memory), parameters (30B, about 3B active) and languages (English and Chinese, in the metadata) are there. Training data 5, A general description of the two training stages inside the harnesses, with no datasets, sizes or cut-off. Last change 20, the last commit, on 16 October 2026, added the licence and the card, 25 days before this check. Responsiveness 20, Of the 4 discussions that aren't pull requests (16 to 30 October 2026), 3 have a reply from a tencent organisation member. Version policy 5, A first release, with nothing replaced. File health 10, Config, tokenizer and template agree on the architecture, the context and the thinking levels. 8 + 5 + 20 + 20 + 5 + 10 = 68.

Spark-X2.6-4B 51

Model card 11 of 20, intended use, parameters, context and languages, with no limitations, cut-off or architecture description of its own. Training data 0, the X2.6 card describes none. Last change 20, the card changed on 1 November 2026. Responsiveness 10, SparkLLM members answered 11 of 40 discussions. Version policy 5, X2.5 stays in place with no note. File health 5, the tokenizer config's 131,072 disagrees with the 1M context.

Hy-Memory-30B-A3B 60

File safety 25, 51 safetensors shards and no pickle or Python files. Provenance 15, files in the tencent organisation that the card's own resource list links to (10), with a SHA-256 listed for all 53 large files (5). Safety evaluation 0, no safety results on the card. Agent guidance 0, no prompt-injection guidance, instruction hierarchy, account of trained refusals or general cautions on the card. Licence risk 15, Apache 2.0 with no use policy, no field-of-use limit, no threshold and no clause letting Tencent change the terms. Security programme 5, Tencent's Security Response Center takes vulnerability reports company-wide with published reward rules, as the Hy3 listing records (5). 25 + 15 + 0 + 0 + 15 + 5 = 60.

Spark-X2.6-4B 50

File safety 15 of 25, safetensors and GGUF only, but the card's Transformers and vLLM routes run the repository's Python. Provenance 15, the files are in SparkLLM's own Hub organisation, which its GitHub docs name, and every file has a checksum, though neither organisation is verified and no company site was found. Safety evaluation 0 and agent guidance 0, none published. Licence risk 15, plain Apache 2.0 that hasn't changed. Security programme 5 of 10, a private reporting route and email in SparkLLM's community repository, with no public advisories.

Hy-Memory-30B-A3B 65

Chat template 20, chat_template.jinja in the repository. Tool-calling format 10, the card doesn't mention tools. Trained tool calling 10, the template can render tool calls, but the card presents the model as a memory writer that returns memories as text or JSON and says nothing of calling tools. Structured output 5, the card's quickstart asks for a JSON object with a memories list in the system prompt and shows nothing else, no response_format and no schema, so JSON output is shown by example without a documented way to constrain it. Reasoning control 10, the card passes reasoning_effort as no_think per request through chat_template_kwargs, and the template takes high, low or no_think. Context 10, 262,144 tokens native (max_position_embeddings in config.json). 20 + 10 + 10 + 5 + 10 + 10 = 65.

Spark-X2.6-4B 70

Chat template 20, a Jinja file in the repository. Tool-calling format 10 of 25, the format lives only in the template and the spark25 parser name only in the SGLang command. Trained tool calling 20, the template renders several calls in one turn. Structured output 0, not documented. Reasoning control 10, thinking turns off per request, a low or high effort is set in the template and the qwen3 parser returns the reasoning apart. Context 10, 1,048,576 tokens with no scaling.