A project can have passing tests and still leave a new contributor stuck at setup. FreshClone checks that path. You mark the shell blocks in your README that a newcomer should run, select them in .freshclone.yml, and define the expected HTTP response. FreshClone copies Git-tracked working files into a temporary directory, runs those commands in a disposable Linux Docker container, starts the app, and checks its endpoint. This is an early MIT-licensed source release, v0.1.0, for Node.js/npm projects in Linux containers. It is not yet published to npm. You can preview commands without Docker using plan; running the app check requires Docker. We are looking for contributors and maintainers willing to try it on real repositories. Contributor priorities are tracked here; check current assignments and coordinate in the issue before starting: 1. Troubleshooting guide: https://github.com/ergishasani/f... 2. Nested application example: https://github.com/ergishasani/f... 3. GitHub Actions job summary: https://github.com/ergishasani/f... Start here: https://github.com/ergishasani/f... Bug reports, docs, clearer diagnostics, and failure tests are welcome too. What undocumented setup step has cost you the most time?

FreshClone

Check whether your README can actually start your app

Check whether your README can actually start your app