Contact.

PEP/NEWS uses GitHub Issues as its public contact channel. No email, no phone — but every issue is read and answered, and the conversation is auditable by anyone.

Tips and story leads.

Got a peptide-research paper, a clinical-trial readout, or a physician-researcher video we should be covering? Open a tip issue on GitHub. Include the URL and a one-sentence reason it matters.

Corrections.

Spotted a factual error in a brief or a misattribution? File a correction issue and we'll update the relevant brief and link to the correction. Past archive briefs are immutable URLs — corrections are append-only.

Accessibility barriers.

If something on PEP/NEWS isn't accessible to you, open an accessibility issue. Include the URL, what you were trying to do, and what assistive technology you were using. We aim to respond within seven days. See also our accessibility statement.

Licensing questions.

The brief itself is CC-BY 4.0 — you can quote, mirror, or train an LLM on it as long as you attribute "PEP/NEWS, https://pep.news/." For anything outside CC-BY 4.0 (commercial syndication, derivative products, attribution-waiver requests), open a licensing issue.

Why GitHub.not email

Open issues are public. Public issues are auditable. We're a small operation; running a separate inbound mail service introduces spam-filtering, deliverability, and privacy headaches that GitHub already solves. If you don't have a GitHub account, signing up is free and the only personal data they require is an email address you control.

Last updated: 2026-05-09