Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed App Store pricing workflow that uses MetaRun and requires user review before applying price changes.
Install only if you trust MetaRun and are comfortable letting it access and change App Store pricing. Review every preview carefully before approving an apply step, and prefer a pinned or preinstalled MetaRun CLI in controlled environments.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
envVars:
- name: METARUN_TOKEN
required: false
description: MetaRun personal access token (Settings, MCP). Not needed after `npx metarun login`, which stores it in ~/.metarun/config.json.
requires:
anyBins:
- npx
The skill instructs use of npx metarun without a pinned package version, which means the agent may fetch and execute whatever version is current at runtime. In an agent context that can access app-pricing tools and credentials, a compromised or malicious upstream package version could execute arbitrary code or alter pricing operations unexpectedly.
This unpinned npx metarun invocation creates a supply-chain execution risk because the resolved package can change over time and is not fixed by the skill. Since the skill is designed to perform pricing previews and applies against Apple-related resources, compromise of the fetched package could lead to code execution, credential theft, or unauthorized pricing changes.
The instruction to fetch schemas via npx metarun tools ... also relies on an unpinned remote package resolution path. Even read-oriented operations are dangerous here because package install/execution happens first, so an attacker controlling the package release chain could run arbitrary code in the agent environment.
The discovery command uses unversioned npx metarun, again introducing a supply-chain risk from runtime package resolution. Although this line is framed as exploratory tooling, execution still occurs in the same trust boundary and could expose local files, config, or tokens if the package is malicious.
No suspicious patterns detected.