rakumux@0.1.42
Terminal session manager for coding agents, with a fast TUI, a background session daemon and an MCP server
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe postinstall hook copies packaged scripts and platform binaries into dist without launching them. The reviewed JavaScript and shell code supports the stated terminal session manager purpose, and showed no credential collection or unrelated transmission; the native binaries remain incompletely analyzed.
Static reason
One or more suspicious static signals were detected.
Trigger
The postinstall hook prepares assets; CLI commands launch the corresponding script or binary. The shell history hook must be sourced and runs only inside an interactive Rakumux session.
Impact
Expected installation and terminal session management behavior; no malicious impact was identified in the reviewed source.
Mechanism
Install copies scripts and binaries to dist. Runtime launchers pass user arguments to those assets. The shell hook appends session commands to local history files.
AI rationale
The postinstall hook copies packaged scripts and platform binaries into dist without launching them. The reviewed JavaScript and shell code supports the stated terminal session manager purpose, and showed no credential collection or unrelated transmission; the native binaries remain incompletely analyzed.
Evidence
dist/~/.cache/rakumux/last_update_check${RAKUMUX_HOME:-$HOME/.rakumux}/history/<session id>.log
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook calls install.js.
- Install setup copies launcher scripts and platform binaries into the package's dist directory.
- The install path does not launch the copied binaries; command launchers invoke them when a CLI command runs.
- The package describes itself as a terminal session manager with a background session daemon.
- The optional shell history hook logs commands only in interactive shells inside a Rakumux session.
Evidence against
- The reviewed install and launcher source showed no credential collection or unrelated network transmission.
- The shipped native binaries could not be fully analyzed, but their installation and invocation match the package's stated purpose.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
UrlStrings
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = node install.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node install.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg45"postinstall": "node install.js"
},
"engines": {
"node": ">=14.0.0"
},
"os": [
"darwin",
"linux"
],
"cpu": [
"x64",
"arm64"
]
}
Low
install.jsView file
Findings
2 High5 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSandbox Evasion Gated Capabilityinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Native Binaryresources/prebuilt/macos-intel/rakumux-ptyd
MediumShips Build Helperresources/scripts/rakumux.sh
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidenceinstall.js
Affected versions and remediation
This report applies to rakumux@0.1.42.
See all versions of rakumux for other recorded verdicts.
- Review the evidence and your use of rakumux@0.1.42 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.