You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you're looking for a pup that will be actively updated for the foreseeable future, try my fork. I've already incorporated some of the PRs-in-waiting, and will be addressing outstanding issues as I see fit. I've also:
improved the existing test suite, supporting pup command line options during testing
added formatting modifiers for text{}, viz. trim, upper and lower
I'm also building release binaries for all major Golang OS platforms via GoReleaser, and host a custom Homebrew tap that tracks my releases. The current Homebrew core pup formula has been disabled for non-maintenance, and I can only replace it with my fork when:-
@ericchiang puts a note in his project's README, pointing to my project as a "blessed fork", or
at least one year elapses after the disabling, so 24 Feb 2026 at the earliest.
Do file issues and/or PRs at my fork, and I'll see what I can do to address them. Thanks much!
Reacted by danielwerg, Chris Blake, Jakob Miksch, Emmanuel FEDERBUSCH, fenchu, hexagonwin, Michael Steinbaugh, simon-liebehenschel, Huy Z, Dan Strokirk and 4 more
@ericchiang, pup is distributed by many package repositories https://repology.org/project/pup/versions, and we now have two PRs in nixpkgs proposing to change pup upstream to the fork mentioned in this issue. Is distributing the fork under the name pup alright with you, or would you prefer we distribute the fork under a different name?
A malicious actor doing a soft takeover of a popular tool to serve their own agenda?
I have no reason to distrust @gromgit, and as a user I would certainly like maintenance of this great tool to continue, but in the modern age of increased supply chain attacks, giving a random person the same privileges to push software to an existing user base without considering the risks doesn't seem wise to me. It would be safer to at least do this transition gradually, and preferably under a new package namespace, so that the community has time to vet and audit the new changes. Trust is earned over time, not automatically awarded.
Reacted by Huy Z, laur89, Peder Bergebakken Sundt, Andrew Gerst, qadzek, jxu and Kirin Etheridge
If I may offer my two cents, I suggest that any fork be distributed, for example, as <project-name>2 (or <project-name>-fork, etc.) until the author of the original repository:
archives their repository, or
explicitly approves in the comments the distribution of the fork with the same name.
In any case, I appreciate the effort that was put into maintaining any forks.
Reacted by Ivan Mirić, Ernie Hershey and Johannes Wülk
Activity
limaceous-bushwhacker commentedon Sep 23, 2025
Thank you!
Gerst20051 commentedon Feb 27, 2026
@gromgit i noticed that
puphas been removed from Homebrew today 26 Feb 2026 as you mentionedand the formulae page no longer loads (404) https://formulae.brew.sh/formula/pup
@ericchiang it seems like now is the time to support the actively maintained fork
pbsds commentedon Apr 10, 2026
@ericchiang, pup is distributed by many package repositories https://repology.org/project/pup/versions, and we now have two PRs in nixpkgs proposing to change pup upstream to the fork mentioned in this issue. Is distributing the fork under the name
pupalright with you, or would you prefer we distribute the fork under a different name?Gerst20051 commentedon Apr 11, 2026
That seems reasonable and safe to me. What's the risk? I'm not aware of any backwards-incompatible changes.
imiric commentedon Apr 11, 2026
A malicious actor doing a soft takeover of a popular tool to serve their own agenda?
I have no reason to distrust @gromgit, and as a user I would certainly like maintenance of this great tool to continue, but in the modern age of increased supply chain attacks, giving a random person the same privileges to push software to an existing user base without considering the risks doesn't seem wise to me. It would be safer to at least do this transition gradually, and preferably under a new package namespace, so that the community has time to vet and audit the new changes. Trust is earned over time, not automatically awarded.
simon-liebehenschel commentedon Apr 11, 2026
If I may offer my two cents, I suggest that any fork be distributed, for example, as
<project-name>2(or<project-name>-fork, etc.) until the author of the original repository:In any case, I appreciate the effort that was put into maintaining any forks.
jxu commentedon Aug 27, 2026
Alternative to fork, similar program: https://github.com/mgdm/htmlq