talking-stick@0.18.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 13d ago · by lpm-firewall-aiThe lifecycle hook performs an automatic user-level binary installation, creating a guarded first-party extension lifecycle risk. The source does not establish a malicious payload or other concrete attack, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The npm postinstall hook launches the Skiller bootstrap for installed copies of this package.
- The bootstrap downloads a platform archive from a configurable GitHub release URL, checks its checksum, and installs an executable in the user's bin directory.
- The package can invoke Skiller as a runtime adapter, so the downloaded executable is an active companion tool rather than an inert archive.
- The bootstrap can be disabled with environment variables and skips downloading when a sufficiently recent Skiller binary is already available.
- The default release repository is the package author's Skiller project, and the archive is checked against a downloaded checksum before installation.
Source & flagged code
15 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.18.0.
See all versions of talking-stick for other recorded verdicts.
- Review the evidence and your use of talking-stick@0.18.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.