T08 · Insecure Dependencies
- Location
references/SETUP.md:17- Finding
Unpinned Third-Party CLI Installation and Remote Execution
- Content
View full analysis
Vulnerability Details
File Location:
references/SETUP.md, lines 17–28
Vulnerability Type: Unpinned third-party dependency and mutable remote package execution
Risk Level: MediumVulnerable Code
markdown ### Option 1: Install globally via npm ```bash npm install -g tandoor-cliAfter the global install, the
tandoorcommand becomes available system-wide.Option 2: Run without installing
bash npx tandoor-cli <command>No global install is required.
npxdownloads and runs the CLI on demand.text Additional unpinned fallback commands appear at `references/SETUP.md:231-232`: ```markdown - Try `npx tandoor-cli` instead - Reinstall: `npm install -g tandoor-cli`The documentation also makes an inaccurate version-pinning assertion at
SECURITY.md:34:markdown - **Version Pinning:** The skill explicitly uses `npx tandoor-cli@0.3.1` to pin to a known versionNo corresponding pinned command appears in the reviewed setup instructions. In addition,
SKILL.md:5declares version1.5.0, making the0.3.1security assertion inconsistent with the documented skill version.Technical Analysis
Both
npm install -g tandoor-cliandnpx tandoor-cli <command>resolve a mutable package version from the npm registry. Thenpxcommand may download and execute package code on demand without constraining it to a previously reviewed release.The executable implementation of
tandoor-cliis not included in the audited artifact. Consequently, the runtime behavior of the downloaded package cannot be verified by this audit. Verification links and recommendations to pin a version do not technically enforce package identity, version, or integrity.This creates a supply-chain boundary in which the effective executable can change after the skill itself has been reviewed. A compromised maintainer account, malicious package release, registry compromise, or unexpected incompatible update could cause arbitrary pa ...[truncated 1778 chars]
- Remediation
View remediation
Remediation Suggestions
-
Replace every unpinned installation and execution command with the exact reviewed version matching the skill metadata, for example:
bash npm install -g tandoor-cli@1.5.0 npx --yes tandoor-cli@1.5.0 <command> -
Update the fallback commands at
references/SETUP.md:231-232so they also specify the exact version. -
Correct or remove the inaccurate assertion in
SECURITY.md:34. The security documentation, setup guide, andSKILL.mdmetadata must identify the same reviewed version. -
Prefer a project-local dependency managed by a committed lockfile rather than a global installation or unconstrained on-demand execution.
-
Verify package integrity and provenance before execution. Where supported, use npm integrity metadata, package signatures or attestations, and a trusted internal registry or approved package mirror.
-
Review the exact CLI release and its transitive dependency tree before granting it Tandoor credentials, especially administrative or space-owner credentials.
-
Run the CLI under a restricted operating-system account or isolated environment with access only to the minimum required files and environment variables.
-
Supply short-lived, least-privileged Tandoor tokens only for the duration of the required operation. Do not expose administrative credentials during ordinary recipe or shopping-list tasks.
-
