UK Grocery CLI: why it is not safe to use

What we found

Our review did not find hidden instructions, hardcoded secrets, obfuscated code, undisclosed data sinks, or remote code fetching in the inspected repository. The documented behavior was generally clear, and checkout appears to default to `dry_run=true` before order placement, which is a meaningful safeguard.

The main reason this skill did not fully pass is its access level once connected to a grocery account. Based on the repository materials, it can legitimately handle sensitive supermarket credentials or browser sessions and may access order history, favourites, baskets, and checkout on those accounts. That creates a higher privacy and account-safety exposure than skills that work without account access, especially if used on a personal grocery profile.

What to do instead

Use this skill only if you are comfortable granting a third-party tool access to your supermarket account activity and checkout flow. Prefer a dedicated low-risk grocery account where possible, avoid storing more access than needed, and review connected sessions, saved payment methods, order history visibility, and favourites before use. Keep the default dry run behavior in place unless you intend to place an order.