talking-stick@0.21.0
Talking Stick now ships as a standalone binary. Install with: curl -fsSL https://raw.githubusercontent.com/mostlydev/talking-stick/master/scripts/install.sh | sh Put ~/.local/bin first on PATH, then remove the npm copy. Existing installs remain functional; future updates ship on GitHub.
CLI coordination tool for path-scoped agent handoffs.
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource confirms that npm postinstall can install and execute a companion binary and synchronize existing agent assets. The behavior is package-aligned and does not establish a concrete attack, but automatic executable installation and agent setup leave residual lifecycle risk.
Decision evidence
public snapshot- The npm postinstall runs a bootstrap script and a separate sync script automatically.
- The bootstrap downloads a Skiller release from the configured GitHub release base and checks it against a checksum file from that base.
- It installs the downloaded binary in the user's local bin directory and executes it to check its version.
- The sync step updates existing Talking Stick skills and only replaces unedited managed instructions; customized skill content is preserved.
- The package targets agent configuration directories including Claude, Codex, and shared agent settings.
Source & flagged code
11 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 source references child process execution.
dist/process-utils.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to talking-stick@0.21.0.
See all versions of talking-stick for other recorded verdicts.
- Review the evidence and your use of talking-stick@0.21.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.