Supply Chain

cyberplace has two independent delivery surfaces:

Surface	Source	Pinning
Skills (SKILL.md files)	GitHub — cyberuni/cyberplace repo	skills-lock.json or pnpm add -D cyberplace
CLI (cyberplace binary)	npm — cyberplace package	npx cyberplace@<exact-version>

A malicious or accidental change to either surface can affect agent behavior. Treat them separately.

Trust tiers

Solo / quick start

npx skills add cyberuni/cyberplace --skill init -g

Pulls from the live default branch. Convenient; no lock file. Acceptable for personal use where you trust the repo directly.

Teams (recommended)

# Install project-scoped
npx skills add cyberuni/cyberplace --skill init --skill init-commit-discipline

# Commit the lock file
git add skills-lock.json && git commit -m "chore: pin cyberplace skill versions"

# Restore from lock on CI or a fresh clone
npx skills ci
# or
npx skills experimental_install

skills-lock.json records the exact commit SHA each skill was installed from. Anyone who runs npx skills ci gets the same files you reviewed.

Strongest coupling

pnpm add -D cyberplace
npx skills add ./node_modules/cyberplace --skill init --skill init-commit-discipline

Skill files and the CLI come from the same npm release. The package.json version is your lock. Use this when you want a single audit surface.

CLI pinning

Never use @latest in hooks or CI — it resolves at runtime and can pull in breaking changes:

# Bad — resolves to whatever is latest at run time
npx cyberplace@latest hook run …

# Good — resolves once, stored in the hook registration
npx cyberplace@0.2.1 hook run …

The init-commit-discipline skill resolves the current npm version and writes it into the hook. Re-run the skill after upgrading to bump the pin.

Threat model

The full supply chain threat model is documented in .research/supply-chain-threat-model/ in the source repository.