The repo's LICENSE file is Apache-2.0 and has been since the project shipped. The original ask was a dual-license recommendation; that recommendation is walked back. The maintainer's actual choice is Apache-2.0 (matching the orchd repo) and the dossier confirms it.
The remaining gaps are registry-side and crate-name-side, not file-side.
Action
Context
Tracked in the distribution playbook at adiled/distribution. orch and orchd are a coherent pair under one license, not the dual-license mix the prior dossier inferred.
~ distribution team
The repo's
LICENSEfile is Apache-2.0 and has been since the project shipped. The original ask was a dual-license recommendation; that recommendation is walked back. The maintainer's actual choice is Apache-2.0 (matching the orchd repo) and the dossier confirms it.The remaining gaps are registry-side and crate-name-side, not file-side.
Action
licensefield inorch/Cargo.tomlto"Apache-2.0". Currently unset.orchis already taken on crates.io byguywaldman/orch(an LLM orchestration library, ~15k downloads).cargo install orchis impossible. Recommended replacement:orchfile(available on crates.io, doubles as the file format name, lets the binary inside stay namedorch). The repo name and the binary name can stay as is; only the crate'snameinCargo.tomlchanges.cargo publish --dry-runto verify all metadata.Cargo.tomlto depend on the renamed crate (currently a git dep onadiled/orch).Context
Tracked in the distribution playbook at
adiled/distribution. orch and orchd are a coherent pair under one license, not the dual-license mix the prior dossier inferred.~ distribution team