Auto vs nFPM
Auto
intuit.github.ionFPM
nfpm.goreleaser.comSide by side
| Figure | Auto | nFPM |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 0 | 1 |
| Spec score · Release automation tools | 7.7 (#10) | 7.8 (#8) |
| Integrations | The documented plugins include Jira, Slack, Microsoft Teams, Amazon S3, GitHub Pages, npm, Homebrew, Docker, and VS Code. | GoReleaser can use nFPM to generate and publish Linux packages and Windows MSIX packages. |
| License | The Auto repository is distributed under the MIT License. | The repository identifies its license as MIT. |
| Purpose | Auto automates project releases and pull request interactions, using pull request labels to calculate releases. | nFPM is a Go tool for creating deb, rpm, apk, ipk, Arch Linux, and MSIX packages. |
| Support | The repository invites users to file an issue or open a pull request for help and contributions. | The repository directs users with questions or support needs to the GoReleaser community. |
Plans
In their own words
nFPM
nFPM is a free Go tool for creating DEB, RPM, APK, IPK, Arch Linux, and MSIX software packages. It can be run from the command line or used as a Go library, and the project describes it as a single binary without external runtime dependencies. Package definitions use YAML and can specify metadata, files, dependencies, scripts, and format-specific overrides. Installation options include package managers, prebuilt archives, Docker, Go install, or building from source; documented package managers include Homebrew, Scoop, APT, Yum, Winget, and NPM. GoReleaser can use nFPM to generate and publish Linux packages and Windows MSIX packages. The project lists Linux, macOS, and Windows as target platforms and identifies its license as MIT. The install guide says release artifacts are checksummed and the checksum is signed with cosign; Docker images are also signed with cosign. MSIX support is described as experimental, and symlinks are skipped. The project presents nFPM as an option for users who want package creation without dependencies such as Ruby and tar.