PEP 541 Request: `pip-licenses`

[reactive-firewall]

Project to be claimed

pip-licenses: https://pypi.org/project/pip-licenses

Your PyPI username

reactive-firewall: https://pypi.org/user/reactive-firewall

Reasons for the request

Initiating a request for name transfer of pip-licenses. I believe the original package Repo is abandoned as it has not been updated in over a year, and the community is interested in a new consortium to maintain the project.

I would like to get multiple co-maintainers to take-over maintaining the project.

Maintenance or replacement?

Maintenance

Source code repositories URLs

Current Project Source URL: https://github.com/raimon49/pip-licenses

Intended Organization Project Source URL: https://github.com/reactive-firewall-org/pip-licenses

Contact and additional research

Additional details:

• Current Project has "no releases within the past twelve months; and" (circa august 2025)
• Current Project has "no activity from the owner on the project’s home page (or no home page listed)."
• Attempts to contact current owner are unsuccessful:
  • Current Project source on GitHub: https://pypi.org/project/pip-licenses/ has no recent activity from owner in about a year (last release/change was Jul 24, 2024 by owner)
  • Current Project was last updated in July 2024, and @raimon49 is no-longer responding on the project home page, despite multiple requests for comment on open pull-requests
  • Current owner has not responded to my, nor other community members regarding the project (to my knowledge)
  • No comment from the owner on active GHI issue discussing how community can proceed. (see GHI #227)

---

• "the candidate is able to demonstrate improvements made on the candidate’s own fork of the project;" (This requirement is still a work in progress at the moment)

AND

---

• Package index maintainers able to contact current owner ( Requested by this issue )
  Or
• Current Package is determined to be abandoned (by PEP 451 DIFFERENTIAL DIAGNOSIS)

AND

• "Final determination regarding project ownership" (AWAITING Package Index Admins standard process)

---

• it is after 24 January 2026, and no activity from project. (6 more months from opening this issue)
• "the maintainers of the Package Index don’t have any additional reservations"(AWAITING feedback from maintainers of the Package Index, if any)

---

Additional Best-effort tasks

• Other members of the relevant community have responded to requests for comment regarding "best interest of the community as a whole" (see GHI #227)

AND

• at least one co-maintainer confirmed (This is part of @reactive-firewalls' attempt to satisfy: "the candidate is able to demonstrate why a fork under a different name is not an acceptable workaround" of the PEP-541 requirements)

Code of Conduct

• I agree to follow the PSF Code of Conduct