The symbolgraph binary bson files captured during swiftinit builds could be quite useful for third-party analysis.

With the unidoc tool, folks can compile them independently, but making the binaries publicly available would relieve said third parties from that hard work.

If/since the binaries are stored per-package and referenced on each package page, each could be linked from there for manual download.

My own goal is scaling analysis for many packages, so it would be nice to have an officially permitted way to get e.g., 100 or 1000+ packages at a time. I believe the consumer would be responsible for aligning both package and bson versions and comply with size/frequency throttling to avoid egress costs. Because batching could be a bit of work with a different cost/benefit profile, it can be split off as another issue. My own foreseeable need is only for one big batch.

Batch and package users might both need some way to avoid comparing across versions. Each file includes the symbol graph ABI version as a bson field, and the metadata for each package dependency seems to include a version. For the package itself, direct users are typically clicking on a versioned link, but batch users might need a version for the package represented in the bson file (perhaps encoded in the file name?).

For context, please see
https://forums.swift.org/t/documentation-workgroup-meeting-september-9th-2024/74420/7