Show HN: BootProof – Cryptographically prove any GitHub repo boots locally
BootProof is a tool that verifies whether a GitHub repository can successfully boot by executing only justified steps and generating a signed attestation of the outcome. It inspects repository requirements, runs dependency installation when appropriate, and confirms health by observing reachable endpoints rather than relying on command exit codes or Docker status. The tool can be used locally or in CI pipelines, supports remote repository inspection, and provides explanations for verification failures such as version mismatches or blocked remote code execution.
- ▪BootProof separates activity from evidence, executing only actions it can justify and recording health observations in a signed attestation file.
- ▪The tool refuses to run when environment constraints, such as a mismatched package manager version, are detected, prompting the user to correct the setup before retrying.
- ▪Remote repositories are treated as untrusted code; BootProof requires explicit consent before executing any code from them and will block execution by default.
- ▪A successful boot is marked only after BootProof observes an HTTP 200 response from the application’s health endpoint, not merely after a process starts or dependencies install.
- ▪Users can run BootProof via npx commands, obtain human‑readable diagnostics, and verify or explain attestation files using provided CLI options.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/bootproof/bootproof |
| Publication time | Sun, 14 Jun 2026 22:28:30 +0000 |
| Retrieval time | 2026-06-14T22:37:33.112Z |
| Last seen | 2026-06-14T22:37:33.112Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | thufHu8rIGGs |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
BootProof The honest run button for GitHub repos. Proof, not vibes. BootProof answers one question: Did this repository actually boot? Not “did a command run?” Not “did Docker say containers are up?” Not “did an AI agent say it worked?” Not “did the README look plausible?” BootProof inspects a repo, builds an evidence-based run plan, executes only what it can justify, observes real health, and writes a signed attestation for success or failure. No proof, no green check. Why BootProof exists Every developer knows this loop: git clone some/repo npm install npm run dev Then reality appears. Wrong Node version. Wrong pnpm version. Missing Java. Missing Clojure. Docker is running but the service is not healthy. Postgres exists but the role does not. Redis is missing. A migration fails.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.