Request
Please explicitly choose and publish the repository's license, then align the package metadata:
- add a root
LICENSE (and NOTICE if the chosen license requires it);
- add
license or license-file to the workspace/crate Cargo metadata;
- add
license to the npm workspace/package metadata;
- optionally add SPDX identifiers where appropriate.
Current observation
The repository currently has no LICENSE, COPYING, or NOTICE file, and its Cargo/npm metadata does not declare a license. Dependency licenses do not grant permission to redistribute ctxmux's own source or binaries.
Why this blocks DevFleet
DevFleet needs an explicit redistribution grant before it can package or distribute ctxmux/ctxmuxd as signed managed artifacts. Until the repository owner selects and records a license, the integration must fail closed even when the binaries build and pass technical validation.
This issue deliberately does not propose or assume a particular license; that choice belongs to the repository owner.
Request
Please explicitly choose and publish the repository's license, then align the package metadata:
LICENSE(andNOTICEif the chosen license requires it);licenseorlicense-fileto the workspace/crate Cargo metadata;licenseto the npm workspace/package metadata;Current observation
The repository currently has no
LICENSE,COPYING, orNOTICEfile, and its Cargo/npm metadata does not declare a license. Dependency licenses do not grant permission to redistribute ctxmux's own source or binaries.Why this blocks DevFleet
DevFleet needs an explicit redistribution grant before it can package or distribute
ctxmux/ctxmuxdas signed managed artifacts. Until the repository owner selects and records a license, the integration must fail closed even when the binaries build and pass technical validation.This issue deliberately does not propose or assume a particular license; that choice belongs to the repository owner.