Hy-Memory-30B-A3B vs Qwen3.5-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.

Qwen3.5-4B 34

The card covers five of the seven items and misses limitations and a cut-off (14). Training data is a general description without a cut-off (5). The files last changed on 2 March 2026, 245 days before 2 November, which is within a year (5). No Qwen member has answered any of the 21 discussions that aren't pull requests, four of them opened since 21 October (0), and the GitHub issues couldn't be counted. Earlier 4B models stay in their own repositories without dated notes (5), and two pull requests fixing the template and adding generation_config.json wait unanswered (5). 14 + 5 + 5 + 0 + 5 + 5 = 34.

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.

Qwen3.5-4B 55

Safetensors only with no remote code gives file safety its 25, and files in the Qwen organisation the publisher's GitHub links to, each with a hash on the Hub, give provenance 15. The Apache 2.0 licence carries none of the deductions, so licence risk keeps 15. Safety evaluation, agent guidance and a security programme score 0, since the card has no safety results or cautions and no reporting route was found. The Qwen3.5 blog and Alibaba's security response centre couldn't be read, so those two are scored as absent and left open.

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.

Qwen3.5-4B 70

The template ships in the repository (20) and the model was trained for tool use with several calls per turn in the template (20). Tool-calling format gets 10, because the card names the qwen3_coder parser but leaves the declaration and call format to the template. Thinking turns off per request and comes back in think tags split by the qwen3 parser (10), and 262,144 tokens is native (10). Structured output scores 0, as nothing documents JSON output for the model.