Audit GitHub access before your next Shopify deployment

Daniel Lockyer's 18 November reminder to review GitHub credentials is a timely maintenance task for Shopify app and theme teams. In a follow-up, he reported finding three old applications with broad…

SSophie Harrington2 min read

Daniel Lockyer's 18 November reminder to review GitHub credentials is a timely maintenance task for Shopify app and theme teams. In a follow-up, he reported finding three old applications with broad private-repository access. This is an account-hygiene example, not evidence of a new GitHub breach.

Make an access list before removing dependencies

GitHub recommends reviewing SSH keys, deploy keys and authorized applications. For each entry, record its owner, purpose, repository access and whether a current deployment or integration depends on it. An unfamiliar credential deserves investigation; an unused integration should not retain access indefinitely.

  1. SSH and deploy keys: review account keys and repository-specific deploy keys separately. Identify old machines and abandoned deployment services.
  2. Personal access tokens: check both classic and fine-grained tokens, their permissions and expiry. GitHub's token guidance explains the differences and limitations. Validate compatibility before replacing a working integration.
  3. Apps: review authorized OAuth apps and installed GitHub Apps. Check the developer and requested access, following GitHub's authorization guidance. Include organization installations rather than stopping at personal settings.

Separate routine cleanup from an incident

Removing an old app does not by itself prove that a Shopify credential was stolen. If you discover an exposed secret or suspicious access, investigate the affected repositories and activity, then revoke or rotate the credentials actually at risk. Secrets should not be committed to source repositories.

Consult the GitHub security log when investigating unexpected account activity. Coordinate changes with the person responsible for deployments so cleanup does not silently break a production workflow.

Keep an AI-assisted review read-only

Lockyer used a browser agent to help list authorized apps and scopes. If you use that approach, ask for an inventory first and verify it against GitHub's own settings. Do not paste token values or private source code into a prompt. Review proposed removals yourself before allowing an agent to change access.

For a store owner working through an agency, the useful deliverable is a current access register and a named owner for each integration. Recheck it when contractors leave or projects end, and confirm that legitimate deployments still work after changes.

Related reading: our Shopify app security checklist.

ℹ️
Start with an inventory. Verify dependencies before routine removals; investigate unexpected access and exposed credentials as a separate incident.

Daniel Lockyer’s access-audit reminder, 18 November 2026. Read the original post.

Filed underNews

More from News

See all →