Licensing clarification for a public derived crates.io index metadata dataset

[37RaptorRed]

Hello crates.io team,

I maintain CratesDataset, a deterministic local pipeline that transforms
immutable monthly snapshots of crates.io registry index metadata into eight
analytical tables covering versions, crate lifecycles, dependency and feature
edges, adjacent release transitions, yanked-version context, candidate
replacement releases, and reproducible manifest-pattern signals.

The proposed public release would:

• contain registry index metadata and deterministic fields derived from it;
• contain no .crate archives or crate source files;
• publish monthly Parquet and JSONL-Zstandard snapshots on Hugging Face;
• preserve source snapshot hashes, provenance, schemas, attribution to crates.io
  and the registry index, and clear limitations;
• describe yank replacements only as deterministic candidates, not
  maintainer-confirmed replacements; and
• avoid implying endorsement by the crates.io team, Rust project, Rust
  Foundation, or crate authors.

The July 2026 release is approximately 1.3 GiB across both formats. Later
monthly snapshots would be preserved as immutable repository tags.

The crates.io Data Access Policy explicitly supports using the Git index for
projects that need most or all crate metadata, but I could not find a license
file in rust-lang/crates.io-index or language that expressly covers public
redistribution of an aggregate derived dataset.

Could you please clarify:

1. Whether public redistribution of this derived aggregate of crates.io index
   metadata is permitted.
2. What license or other terms should be stated for the dataset contents.
3. What attribution, notice, opt-out, or takedown procedure you would like
   included.
4. Whether license: other with a linked permission record is appropriate on
   Hugging Face if no standard SPDX license applies.

I will keep the public upload blocked until an authoritative basis is recorded.

Thank you,

Herb
Aptlantis / CratesDataset