Praxikit

Home / Policy

Listings, reports and removals

Praxikit is run by one maintainer, part-time. This page says what a listing means, how to report a problem and what happens next. It describes how the site is run; it is not legal advice.

What a listing means

  • Kits built by Praxikit are ours. We maintain them and ship fixes as new versions.
  • Listed kits and picks are other people's work. We link to the public repository. We do not host, copy or run it. A pick is a kit the owner has used, with a note on how; a listed kit was scanned and read by a person, and is not necessarily used.
  • A listing means a person read the repository and the automatic result at one commit, which each listing shows. It is not an endorsement and not a safety guarantee. The automatic checks are pattern checks and cannot see everything.
  • The reviewed commit is not what you install. Installs come from the author's repository and follow its latest version, so the code you get can be newer than the code that was reviewed. A daily check marks a listing Changed since review when its repository has moved on, with a link to what changed. That tells you something changed, not whether it is safe; compare before you install.
  • Listing is free. Nothing is listed for payment, and payment never changes a check or a decision.
  • A listing needs a licence that lets others use the work, and the submitter confirms they wrote it or have permission.
  • We can decline or remove any listing. We try to say why.

Report a problem

  • Malicious code or an exposed secret: use the private report. Please do not post details in a public issue.
  • Licence or copyright, a misleading description, an abandoned kit, or an author asking for their own work to be removed: use the report form.

What we will do

  • We aim to reply within 3 days. There is one maintainer and no on-call rota, so this is an aim, not a service level.
  • Malicious code or an exposed secret: once we have read the report and it looks real, we remove the listing first and investigate after. We aim to do that the day we read it, and within 2 days of the report.
  • Everything else: we read the evidence, may ask the listing's author, then correct or remove the listing. We aim to decide within 14 days.
  • A removal takes the entry off the catalogue at the next deploy, a few minutes later. It is recorded in the public removal log with the date, the name, the repository, a reason category and a short note.

Telling people who installed it

We cannot message them: installs go from the author's repository to the user and do not pass through Praxikit. The removal log is the notice. If you installed something that was later removed, check the log and uninstall it.

Limits we are open about

  • There is one maintainer and no second person with admin rights yet. One is planned. Until then, if the maintainer is away, reports wait.
  • For copyright on code hosted elsewhere, also tell the host (GitHub). We will remove our link on a credible request.
  • Last updated 2026-11-15.