Two minutes · eight checks

Can a stranger run your first command?

Score the public path from package discovery to the first useful result. Answer from a clean user's point of view—not from a maintainer checkout that already has the right tools and context.

Private by design: this checklist runs entirely in the browser. Answers are not sent or stored.

1. Does the named package or release resolve publicly?

Run the registry lookup or open the release URL while logged out.

2. Does the README show one exact install command?

A new user should not have to combine steps from several sections.

3. Does installation work without a source checkout?

Test from an empty directory with no project-local dependency fallback.

4. Do help and version commands exit cleanly?

They should name the installed tool, public options, and actual version.

5. Does the first documented example produce its promised result?

Check the output, saved file, network result, and process exit—not just terminal text.

6. Do common failures return a useful message and non-zero exit?

Try a missing file, unreachable URL, invalid input, or absent credential.

7. Are runtime, platform, and credential requirements explicit?

Name supported versions before the first command, including platform-only limitations.

8. Does CI test the published artifact as a user installs it?

Source tests can all pass while a registry package is missing or an archive omits files.

Your self-check

Fix these first:
    Request the US$25 clean-environment check See the full scope

    The paid route begins with a public GitHub intake. No payment is collected until the release path and platform are confirmed.