talking-stick@0.14.1
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 13d ago · by lpm-firewall-aiThe automatic lifecycle stages a remotely obtained executable that can later perform agent skill operations. The inspected source supports a staged-payload warning, but does not establish concrete malicious behavior or unconsented broad agent-control mutation.
Decision evidence
public snapshot- The npm postinstall hook runs the bootstrap script automatically.
- The bootstrap downloads a platform binary from GitHub releases and installs it in the user’s local binary directory.
- A later explicit install command can run that binary to manage agent skills.
- The install module maps agent configuration directories, including the Claude Code settings directory.
- The bootstrap checks the downloaded archive against a checksum file and checks the installed binary’s version.
- The postinstall sync targets installed skills and instructions; the inspected code does not establish credential theft or a broader agent-control mutation.
Source & flagged code
14 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.14.1.
See all versions of talking-stick for other recorded verdicts.
- Review the evidence and your use of talking-stick@0.14.1 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.