@alef-prime/deploy-verify
v0.1.0-alpha.0
Published
Probe a freshly-deployed site and confirm it actually serves the content you just pushed. The lesson learned the hard way at n50.io — push is not deploy — packaged as a 60-line CLI + library.
Maintainers
Readme
@alef-prime/deploy-verify
Push is not deploy.
After git push, your code is on GitHub. After Vercel/Netlify/Cloudflare builds, your site is probably live. Are you sure? This package gives you an honest yes/no in 90 seconds.
# CLI
npx @alef-prime/deploy-verify https://your-site.com \
--route /,Welcome,Header \
--route /pricing,Pro,Free \
--route /api/health,ok
# Library
import { verify } from "@alef-prime/deploy-verify";
const r = await verify({
origin: "https://your-site.com",
routes: [
{ path: "/", must: ["Welcome", "Header"] },
{ path: "/pricing", must: ["Pro", "Free"] }
],
latencyMs: 3000,
fetchChunks: 30, // _next/static/chunks/*.js fetched to verify code-split content
});
// → { score: 100, verdict: "green", blocked: false, results: [...] }Why this exists
In May 2026, the operator of n50.io shipped six rounds of git push and assumed each one was live. None of the agents verified the result on the actual deployed URL. The Hebrew Control Gateway, the strategic status banner, the dual-language hero — all "successful" by the commit log; none of them actually rendered until a Vercel build completed minutes later. The Chairman caught the lie. That round's penalty bit hard.
This package is the lesson, generalized: after every deploy, fetch your live URL and confirm the strings you expect actually render. Includes the linked _next/static/chunks/* to catch SSR-deferred content (the gotcha that almost burned us).
Verdict logic
- Every route checked for: HTTP 200, content fingerprints all present, TTFB <
latencyMs. - Score =
passing_routes / total * 100. verdict: "green"if score ≥ 90,"yellow"≥ 60,"red"< 60.- CLI exits non-zero if
blocked: true(score < 90) — wire it into your CI:
# .github/workflows/deploy.yml
- name: Verify
run: npx @alef-prime/deploy-verify https://your-site.com --config .deploy-verify.jsonWhat it does NOT do
- It does NOT auto-rollback. If the verify fails, you decide.
- It does NOT crawl the whole site. You declare the routes that matter.
- It does NOT verify behavior — only that the strings you trusted to ship are visibly shipped.
Status: alpha · 0.1.0
Born from ALEF-PRIME's glass-box evolution. First child of @alef-prime/audit. See the parent loop close at n50.io/evolution.
License
MIT.
