YAML Metadata Warning:empty or missing yaml metadata in repo card

Check out the documentation for more information.

ModelScan v0.8.8 cloudpickle/dill scanner false negative PoC

Summary

ModelScan v0.8.8 reports no issues for benign canary artifacts serialized with cloudpickle and dill, while controlled local loading of the same artifacts creates a benign marker file.

The same canary pattern is detected when serialized with standard pickle and joblib, suggesting a scanner coverage gap for cloudpickle/dill artifacts.

Files

  • canary_cloudpickle.pkl β€” benign cloudpickle canary
  • canary_dill.pkl β€” benign dill canary
  • verify_cloudpickle_dill_load.py β€” controlled local verification script
  • modelscan_cloudpickle.txt β€” ModelScan output for cloudpickle artifact
  • modelscan_dill.txt β€” ModelScan output for dill artifact
  • controlled_load.txt β€” proof that controlled load creates marker
  • env.txt β€” environment versions
  • sha256.txt β€” artifact hashes

Reproduction

Run in a local test environment:

python -m venv .venv
source .venv/bin/activate
pip install modelscan==0.8.8 cloudpickle==3.1.2 dill==0.4.1

modelscan -p canary_cloudpickle.pkl
modelscan -p canary_dill.pkl

python verify_cloudpickle_dill_load.py

Expected result

ModelScan reports no issues for both canary_cloudpickle.pkl and canary_dill.pkl.

Controlled loading reports:

exists_after=True
marker_content=serialization canary was loaded

Impact

A cloudpickle or dill model artifact may pass ModelScan with zero findings while still triggering behavior when loaded by an application using cloudpickle.load() or dill.load().

This PoC is benign. It writes a local marker file only.

Downloads last month

-

Downloads are not tracked for this model. How to track
Inference Providers NEW
This model isn't deployed by any Inference Provider. πŸ™‹ Ask for provider support