npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@limetry/shopify

v1.2.61

Published

Shopify Admin API mutation firewall gated by Limetry ActionIntent evaluate

Downloads

1,364

Readme

@limetry/shopify

[!NOTE] Origin: A design partner's support agent issued fourteen refunds totaling $3,200 in two minutes — each individually valid, none approved by a human. Prompt-level limits are advisory, so @limetry/shopify holds the Admin token in the runtime and evaluates every mutation before Shopify sees it. Limetry evaluates; Shopify still performs the mutation.

Admin API mutation firewall that holds SHOPIFY_ADMIN_TOKEN and only refunds, discounts, or inventory updates after Limetry returns allow.

This is a library in your agent runtime, not a Shopify App or Admin/Checkout extension. Merchants do not install Limetry from the Shopify App Store. Your backend (or MCP host) already holds the Admin token; Limetry decides whether that process may mutate.

Live demo in this repo

.github/workflows/limetry-shopify-gate.yml starts a Limetry node in the job, applies policies/refunds.json, then:

  1. Evaluates a $10 shopify.refund — must allow (dry-run; Admin API is never called).
  2. Evaluates a $500 refund — must deny (max_cost_minor is $25.00).
  3. Evaluates shopify.inventory set to 0 — must deny (shopify.inventory is in denied_action_types).

No Shopify Partner app, store, or SHOPIFY_ADMIN_TOKEN is required for that check. A later optional step is a Partner development store with a token in GitHub secrets on trusted push only, still using this same firewall with dryRun: false.

Install

npm install @limetry/shopify @limetry/sdk

Use the package manager you prefer; the equivalent Yarn or pnpm command works the same way.

Usage

import { ShopifyActionFirewall, createShopifyActionPolicy } from "@limetry/shopify"

const firewall = new ShopifyActionFirewall({
  shopDomain: "acme.myshopify.com",
  adminToken: process.env.SHOPIFY_ADMIN_TOKEN!,
  apiKey: process.env.LIMETRY_API_KEY!,
  policyId: process.env.LIMETRY_POLICY_ID!,
  dryRun: true,
})

const result = await firewall.createRefund({
  orderId: "5678",
  amountMinor: 2500,
})

if (result.evaluation.decision === "approval_required") {
  // Pause until POST /v1/approvals/:id/approve with the same intent payload hash
}

createShopifyActionPolicy ships a broader template: it allows shopify.inventory and routes shopify.refund to approval via require_approval_action_types. The CI demo policy (policies/refunds.json) is stricter — it denies inventory outright. Pick one deliberately rather than assuming they match. Approvals resolve through POST /v1/approvals/:id/approve on your Limetry server.

Apply the repo policy on your evaluation server

limetry setup
limetry policy apply --file packages/shopify/policies/refunds.json