Prompty is pre-1.0, and only the latest release is supported. Fixes land in a new release rather than being backported, so if you're on an older tag, upgrading is the fix.

Please don't open a public issue for a security problem.

Use GitHub's private reporting instead - go to the Security tab and choose "Report a vulnerability". That opens a private thread visible only to the maintainers. If that isn't available to you, email alex@drevops.com.

Helpful things to include:

• What the issue is, and which file or function it's in.
• The version or commit you're on.
• Steps to reproduce, ideally as a short script.
• What an attacker could actually do with it.

You'll get an acknowledgement within a few days. If the report is confirmed, we'll agree a disclosure timeline with you and credit you in the advisory unless you'd rather stay anonymous.

Every release ships a SHA256SUMS file covering all assets, plus a detached GPG signature SHA256SUMS.asc. The signing key's public half is PUBLIC_KEY.asc in this repository, and its fingerprint is:

755E 824E 80F8 4913 5F5F  4043 E71E DB25 C4F6 D89D

Because Prompty is designed to be copied or embedded directly into your own script, verifying the download before you paste it in is worth the 20 seconds:

BASE=https://github.com/AlexSkrypnyk/prompty/releases/latest/download
RAW=https://raw.githubusercontent.com/AlexSkrypnyk/prompty/main

curl -LO $BASE/Prompty.php
curl -LO $BASE/SHA256SUMS
curl -LO $BASE/SHA256SUMS.asc
curl -LO $RAW/PUBLIC_KEY.asc

# Check the fingerprint against the one above before trusting the key.
gpg --show-keys --with-fingerprint PUBLIC_KEY.asc

gpg --import PUBLIC_KEY.asc
gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum --ignore-missing -c SHA256SUMS

--ignore-missing lets the check pass when you've only downloaded some of the assets. Drop it if you've pulled all of them.

The release workflow performs this same verification itself after uploading, so a release that fails it never ships.

A passing check proves 2 things: the files you downloaded match the checksums that were signed, and the signature was made with the key whose public half is in this repository. It doesn't prove that key belongs to the maintainer. The key, its fingerprint and this page all live in the same repository, so anyone who took over the repository or the maintainer's account could replace all 3 at once, and a first-time download would verify just fine.

What the check does defend against is a key swap after you've already trusted the key. Record the fingerprint the first time you download Prompty and compare it on every download after that. If it changes without a note in the release notes, treat that release as suspect and get in touch before running anything from it.

Prompty reads keystrokes from a stream and writes ANSI escape sequences to stdout. It runs stty through the shell to put the terminal into raw mode and to restore it afterwards, using only values it read back from stty -g itself - never anything supplied by a caller or an environment variable.

The library performs no network access, writes no files, and evaluates no user input as code.

embed.php is a build-time tool with a wider footprint. It reads a class file, rewrites it, writes the result to a path you name, and then shells out: to Rector if it's installed, to php -l to check the output parses, and to php <your-script> to confirm the embedded result actually runs. That last step executes the target script, so only point embed.php at scripts you trust. The run is guarded by the kill switch: embed.php only runs a script that has one, and the kill switch returns before the script's real work unless SHOULD_PROCEED is set.

Everything under .util/ is maintainer tooling, not part of the library: the drift check that composer lint runs against the embedded playground demo, and the scripts that record and render the README demos. It's marked export-ignore in .gitattributes, so it's left out of source archives and of the dist installs Composer does by default; a --prefer-source install clones the whole repository and gets it too. These scripts shell out too - to php, and for the recordings to asciinema, expect and node - but only with paths derived from their own location and job names checked against a fixed list, each passed through escapeshellarg().