Is portal-cli-deps safe to install?

SaferSkills independently audited portal-cli-deps (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.agents/skills/portal-cli-deps/SKILL.md · 1 file

.agents/skills/portal-cli-deps/SKILL.md1.3 KB · Markdown

name: portal-cli-deps

description: RiskModels_API — Next.js root build typechecks cli/; mirror CLI deps in root package.json for Vercel, or exclude cli from tsconfig. Use when Vercel/CI fails on missing modules in cli/src or when editing cli/package.json.

Portal + CLI dependency layout (RiskModels_API)

Problem

next build at the repo root typechecks `cli/src` (root tsconfig includes **/*.ts).
Vercel only runs `npm ci` at the root; `cli/package.json` is not installed unless you add a separate step.

So imports like inquirer that exist only in cli/package.json can work in a mixed local setup but fail on Vercel with “Cannot find module”.

Fix (pick one)

Mirror deps on the root — Add the same runtime packages to root package.json as in cli/package.json, add @types/* to root devDependencies if needed, run npm install, commit package-lock.json.
Stop typechecking CLI from Next — exclude: ["cli"] (or narrow include) in root tsconfig.json, and typecheck the CLI only via cli/’s own npm run build in CI.

Commander typing

Do not use cmd.optsWithGlobals<{…}>() under strict TS; cast: (cmd.optsWithGlobals() as { json?: boolean }).

Canonical write-up

See “Next.js portal + cli/ (Vercel builds)” in AGENTS.md.

portal-cli-deps— agent skill

Is portal-cli-deps safe to install?

Portal + CLI dependency layout (RiskModels_API)

Problem

Fix (pick one)

Commander typing

Canonical write-up

Audit the pieces. Scan the whole. Decide.