Skip to content

Moving forward with pup #213

Open
Open

Description

@gromgit

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!

Activity

  1. limaceous-bushwhacker commented on Sep 23, 2025

    @limaceous-bushwhacker

    Thank you!

  2. Gerst20051 commented on Feb 27, 2026

    @Gerst20051

    @gromgit i noticed that pup has been removed from Homebrew today 26 Feb 2026 as you mentioned

    Image

    and the formulae page no longer loads (404) https://formulae.brew.sh/formula/pup

    Image

    @ericchiang it seems like now is the time to support the actively maintained fork

  3. pbsds commented on Apr 10, 2026

    @pbsds

    @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?

  4. Gerst20051 commented on Apr 11, 2026

    @Gerst20051

    That seems reasonable and safe to me. What's the risk? I'm not aware of any backwards-incompatible changes.

  5. imiric commented on Apr 11, 2026

    @imiric

    What's the risk?

    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.

  6. simon-liebehenschel commented on Apr 11, 2026

    @simon-liebehenschel

    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.

  7. jxu commented on Aug 27, 2026

    @jxu

    Alternative to fork, similar program: https://github.com/mgdm/htmlq

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions