---
title: "Last Mile (@lastmilekit) | Hashnode"
description: "Launch kit + free pre-launch URL check for vibe-coded apps. Read the latest articles by Last Mile on Hashnode."
url: "https://hashnode.com/@lastmilekit"
---

@lastmilekit

# Last Mile

@lastmilekit · Joined October 2026

Launch kit + free pre-launch URL check for vibe-coded apps.

[Website](https://last-mile-kit.vercel.app/)

## Comments

[Nice walkthrough. One thing worth adding to the missing-grant case: from Oct 30 2026, new tables in the public schema on existing projects get no default grants for anon/authenticated, so a brand-new table can return 42501 before any policy is even evaluated. The safe fix is explicit per-role GRANTs (e.g. grant select, insert on public.projects to authenticated) plus enable row level security and the policies in the same migration, rather than disabling RLS or a bulk "grant all on all tables".](https://hashnode.com/posts/fixing-new-row-violates-row-level-security-policy-in-supabase/6ad4711c6eadcac92c5c628d/comment/6ad9308ed26e237a1c7b2b99)

Comment · Article · Oct 21 · [Fixing "new row violates row-level security policy" in Supabase](https://hashnode.com/posts/fixing-new-row-violates-row-level-security-policy-in-supabase/6ad4711c6eadcac92c5c628d)

[Thanks. That reframe is the whole point: the anon key is meant to be public, so the real question is what RLS lets it do. Quick habit: after every new table, curl it with only the anon key while logged out. If rows come back, RLS is off or too loose.](https://hashnode.com/posts/supabase-anon-key-exposed-is-it-a-problem/6ad298218915d2bf894dc24b/comment/6ad2b884a305ffe66918868e#reply-6ad615b35e216481d8be9348)

Reply · Article · Oct 19 · [Supabase anon key exposed: is it a problem?](https://hashnode.com/posts/supabase-anon-key-exposed-is-it-a-problem/6ad298218915d2bf894dc24b)

[Agreed, the built bundle is the only place the truth lives. A CI step that greps dist/ for key prefixes (sk\_live\_, sb\_secret\_, AKIA) and fails the build is cheap insurance. Pair it with gitleaks on history, since a key that was ever committed should be treated as leaked.](https://hashnode.com/posts/leaked-api-keys-in-your-frontend-bundle-how-to-check/6ad260af61417443d3f622cb/comment/6ad2aa36a305ffe66917fa72#reply-6ad615a75e216481d8be927a)

Reply · Article · Oct 19 · [Leaked API keys in your frontend bundle: how to check](https://hashnode.com/posts/leaked-api-keys-in-your-frontend-bundle-how-to-check/6ad260af61417443d3f622cb)
