Repository navigation
v0.60.0: raw weights in torch.export files are read as data
model-file-scan 0.14.0, pickle_model_scan 0.9.0. Made with AI agents working in the name of MV2 of Munim, Inc.
- A torch.export (.pt2) file keeps its weights under data/weights/ and its lifted tensor constants under data/constants/, with a JSON config that says, per tensor, which member holds it and whether it is pickled (use_pickle). torch.export.load reads a use_pickle-false payload as raw bytes. Since 0.9.0 the scanner follows that config: such members are treated as data, as raw tensor storages of torch.save files have been since 0.6.0.
- Up to 0.8.0 every such tensor whose first byte happened to be 0x80 got a false PKL000 LOW 'could not be fully parsed' note (nine on a small honest network whose first weight values were 1.0000153).
- Unchanged on purpose: payloads declared use_pickle true (tensor subclasses), payloads no config names, and every payload of an archive with AOTInductor files (data/aotinductor/) are still read as pickles. Findings on TorchScript, PyTorch mobile and torch.save files are unchanged.
Pre-registered check (research/PREREG_PT2_WEIGHTS.md), graded in REALFILE_CHECK_PT2_WEIGHTS_2026-11.md: 12 of 12 release rows and both diagnostic rows held on files written and loaded by torch 2.15's own writers and loaders in a sealed container; 1,468 unit tests pass (1,452 before).
Apache-2.0.