recess-cli@3.24.0
Safe Recess administration and family AI tools from the command line.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe install hook automatically replaces first-party guidance in user-level agent skill directories, creating a limited agent extension lifecycle risk. The shipped guidance contains permission-scope and confirmation safeguards, and the indicated apps.js write occurs only through an explicit CLI scaffold command.
Decision evidence
public snapshot- package.json defines a postinstall hook that runs scripts/postinstall.mjs.
- The postinstall hook imports the setup module and calls installSkill for published installs when the checkout guard does not apply.
- installSkill targets skill directories under the user’s Codex and Claude homes, replacing the current recess-cli skill and removing the superseded recess-admin directory.
- The shipped skill routes agents through scope checks and requires previews and explicit approval before writes.
- The indicated apps.js location writes AGENTS.md as part of the explicit apps init command.
- The installed skill is first-party guidance for the recess command and describes permission-scoped access and confirmation steps.
- The apps init behavior is an explicit CLI scaffold action, not an install-time write.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage contains a possible secret pattern.
dist/commands/onboarding.jsView on unpkg · L576Findings
Affected versions and remediation
This report applies to recess-cli@3.24.0.
See all versions of recess-cli for other recorded verdicts.
- Review the evidence and your use of recess-cli@3.24.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.