Permission to distribute act as a Snap package

[Ignacio-Trottaa]

Hi, I really like act and would like to make it available as a Snap package for easier installation.
I know it’s MIT licensed, but I wanted to check with you first if you’re okay with it being published in Snap Store.

[wellkilo]

From the license side, yes: act is MIT-licensed, and the license explicitly permits using, copying, modifying, publishing, distributing, sublicensing, and selling copies. A Snap package is therefore allowed as long as the copyright notice and MIT permission notice are included in the distributed package or other substantial portions.

The practical packaging checklist would be:

1. Include the upstream MIT LICENSE in the Snap copyright/legal metadata.
2. Make the Snap description clear that it packages upstream nektos/act; do not imply that it is an official upstream distribution unless maintainers agree to maintain or endorse it.
3. Track upstream releases/security updates and expose the upstream version accurately.
4. Test Docker socket access and confinement. act needs Docker access, so strict confinement may require an appropriate interface or a documented setup step.
5. Publish the snapcraft recipe so users can audit how the binary is obtained and verify architecture/checksums.

No extra copyright permission is required by the MIT license, but maintainers may still have preferences about the package name, verified publisher status, and whether it is listed as an official installation method. Asking here before using official-looking branding is the right thing to do.

If this answers the legal/package boundary, please mark it as accepted; a maintainer can separately confirm branding and official-support expectations.