cli@0.3.0-beta.2
CAUTION· install onlyPublisher claims: "Sandscape CLI — connect browser and Unreal projects, generate and sync source assets, and install managed game-development skill packs." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 1 of 1 bundled script run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What changed since 0.2.0-beta.8
vet-skills diff cli 0.2.0-beta.8 0.3.0-beta.2This version reaches for something 0.2.0-beta.8 did not: 2 new hosts (evil.example, sandscape.app). Compared from the two recorded runs, not from source.
- New hosts
- evil.example, sandscape.app
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 79/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
…rent state. `asset save-state <id> --editor <kind> --params-file <complete-state.json>` uses the existing replacement save. It does not render a baked file or publish new source bytes. For an actual rendered PNG/WAV, `asset bake <id> --edi…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.return (0, output_1.commandError)(opts.json, "upload_failed", outcome.detail ?? "Upload failed.");Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.return (0, output_1.commandError)(opts.json, "already_initialized", `Already a Sandscape project: ${srcDir}. Run \`sandscape push\` to upload changes.`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.return (0, output_1.commandError)(opts.json, "upload_rejected", begun.rejected_reason || "Upload rejected: the import session diverged.");Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.`npx -y @sandscape/cli@latest …` unless a real `sandscape` is on PATH (they'reFix: Pin versions and sources; vendor anything fetched at install time.return (0, output_1.commandError)(opts.json, "upload_failed", outcome.detail ?? "Upload failed.");Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.* `.netrc`, and `credentials.json`. The secret rules are applied BEFORE anyFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return (0, output_1.commandError)(opts.json, "usage", `sandscape generate ${kind} needs --in <file> (${INPUT_EXTENSIONS[spec.input].join(", ")}).`, 2);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.allowed-tools: Bash(sandscape *), Bash(npx @sandscape/cli *)Fix: Pin versions and sources; vendor anything fetched at install time.return (0, output_1.commandError)(opts.json, "commit_rejected", synced.rejected_reason || "Upload rejected: the import session diverged.");Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.".env.template",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// bundle. Split into exact names, extension globs, and the `.env.*` family.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// generation.json that the next push uploads; the `done` event carries it.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.`sandscape …` for brevity; read that as `npx -y @sandscape/cli@latest …` (or aFix: Pin versions and sources; vendor anything fetched at install time.* install. The other half is the public `skills`-CLI repo (npx skills add …).Fix: Pin versions and sources; vendor anything fetched at install time.* and taken over, so a holder that never released (crash, kill -9) cannot blockFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.… ## Edit existing registered images Use `asset edit-image <asset_id> --prompt <instruction> --max-coins <authorized-ceiling> --json` when the output should become a new ve…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.allowed-tools: Bash(sandscape *), Bash(npx @sandscape/cli *)Fix: Pin versions and sources; vendor anything fetched at install time.return (0, output_1.commandError)(opts.json, "banner_upload_failed", `Banner upload failed: ${resp.error || "unknown error"}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.".env.sample",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log("Media uploaded. Add --title to publish, or --prepare to stage a draft for review.");Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.So `sandscape pull` means `npx -y @sandscape/cli@latest pull`. Having this skillFix: Pin versions and sources; vendor anything fetched at install time./* best effort on platforms without chmod */Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.console.log("(Optional: `npm i -g @sandscape/cli` to also put `sandscape` on your PATH.)");Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(` npx -y @sandscape/cli@${managed_1.BUNDLE_VERSION} login --json`);Fix: Pin versions and sources; vendor anything fetched at install time.* `.env`(+`.env.*`), `*.pem`/`*.key`/`*.p12`/`*.pfx`, ssh keys, `.npmrc`,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log(`on demand via npx — installed from CLI ${managed_1.BUNDLE_VERSION}. No global binary is needed.`);Fix: Pin versions and sources; vendor anything fetched at install time.".env.example",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return (0, output_1.commandError)(opts.json, "invalid_arguments", "--asset needs --out <dir> inside the game tree — the default output dir " +Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.npx -y @sandscape/cli@latest list --json 2>&1 | head -1Fix: Pin versions and sources; vendor anything fetched at install time.npx -y @sandscape/cli@latest login --json > "$LOG" 2>&1 &Fix: Pin versions and sources; vendor anything fetched at install time.…by this project. `sandscape pull` refreshes those sources and `.sandscape/design.json`; `push` uploads only that selection and returns asset review links. Existing project instructi…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.* Write AGENTS.md as a POSIX symlink to CLAUDE.md, falling back to a smallFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for @sandscape/cli@0.3.0-beta.2 as of 21 min ago. This is the package itself, not its dependencies.
What would make this Verified
1 point to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim sandscape: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.