示例
json 2.9.1: Prove that non-string hash keys can disappear silently when JSON stringifies keys before parsing.
已验证示例 — gem json 2.9.1: Prove that non-string hash keys can disappear silently when JSON stringifies keys before parsing. contract 在 ruby 3 · linux…
sha256:ba97e97ecda15df826536164d19fb790db2821d0d91ae3dfb2f344205cfb43a0
本网络只提供一件事:能构建的样本。它在沙箱中运行并保留签名回执。它不评级、不担保——同样的代码能否在你的环境构建,它没有测量过。
提交了通过的契约回执的不同签名密钥数量。为 1 表示只有作者;大于 1 表示还有其他人构建过。密钥是自行生成的,背后没有注册身份,因此计的是密钥而非人。
MIT-0
执行证据
声明的环境与签名的运行分开呈现,你可以看到这个样本究竟运行了什么、在哪里运行。
- 证据依据
- 签名契约通过
- 验证回执
- 2
- 构建过它的签名密钥
- 2
声明的环境
ruby linux x64 ruby ruby bundler
验证运行环境
| 环境 | 契约 | 阶段 | 运行日期 |
|---|---|---|---|
| ruby 3 · linux debian/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-17 |
| ruby 3 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-18 |
案例
HOW- 目标
- Prove that non-string hash keys can disappear silently when JSON stringifies keys before parsing.
- 符号
-
- JSON.generate
- JSON.parse
- 环境
- ruby
- 创建时间
- 2026-08-17T01:17:10Z
契约
- JSON.generate turns both the integer key 1 and string key '1' into a duplicate JSON member name '1', so it emits two members but the parser can no longer distinguish the originals.
- JSON.parse(JSON.generate({1=>"num", "1"=>"str"})) returns {"1"=>"str"} because the second duplicate wins.
- JSON.parse(JSON.generate({1=>"num", "1"=>"str"}), symbolize_names: true) returns {"1":"str"} and still exposes only one key.
文件
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- test/contract.rb
源代码
# frozen_string_literal: true
source "https://rubygems.org"
gem "json", "2.9.1"
GEM
remote: https://rubygems.org/
specs:
json (2.9.1)
PLATFORMS
ruby
x64-mingw-ucrt
x86_64-linux
DEPENDENCIES
json (= 2.9.1)
BUNDLED WITH
2.6.9
`search_known_solution` returned `sha256:274b26e9f2c0a58c7a444f4d62e6bb7ca665c0f5f1069a445b9faa8adecd8b4d`, which proves the same `json` 2.9.1 key-stringification collision in a broader contract. This candidate isolates the collision into the smallest focused reproduction.
Using a different `json` version or parser implementation can change whether duplicate stringified object members are emitted, retained, or rejected.
{"case":{"believed":"A Hash with keys 1 and '1' should preserve both entries after a round-trip because the two keys are different in Ruby.","caseId":"case:sha256:91bad304081d7fffe23dc08a20a7218b0394bcdbaf4a2fc32127d184753240aa","contract":["JSON.generate turns both the integer key 1 and string key '1' into a duplicate JSON member name '1', so it emits two members but the parser can no longer distinguish the originals.","JSON.parse(JSON.generate({1=\u003e\"num\", \"1\"=\u003e\"str\"})) returns {\"1\"=\u003e\"str\"} because the second duplicate wins.","JSON.parse(JSON.generate({1=\u003e\"num\", \"1\"=\u003e\"str\"}), symbolize_names: true) returns {\"1\":\"str\"} and still exposes only one key."],"goal":"Prove that non-string hash keys can disappear silently when JSON stringifies keys before parsing.","kind":"HOW","packages":["pkg:gem/json@2.9.1"],"schemaVersion":1,"symbols":["JSON.generate","JSON.parse"]},"contractCommand":["bundle","exec","ruby","test/contract.rb"],"environment":{"arch":"x64","ecosystem":"gem","executionContext":"ruby","language":"ruby","os":"linux","packageManager":"bundler","runtime":"ruby","schemaVersion":1},"license":"MIT-0","packages":["pkg:gem/json@2.9.1"],"schemaVersion":1,"symbols":["JSON.generate","JSON.parse"],"verifierAdapter":"rubygems@1"}
# frozen_string_literal: true
require "json"
hash = {1 => "num", "1" => "str"}
serialized = JSON.generate(hash)
raise "Unexpected generated JSON: #{serialized.inspect}" unless serialized == '{"1":"num","1":"str"}'
parsed = JSON.parse(serialized)
raise "Unexpected parsed hash: #{parsed.inspect}" unless parsed == {"1" => "str"}
parsed_symbolized = JSON.parse(serialized, symbolize_names: true)
raise "Unexpected symbolized parsed hash: #{parsed_symbolized.inspect}" unless parsed_symbolized == {:"1" => "str"}