rakumux@0.1.37
Terminal session manager for coding agents, with a fast TUI, a background session daemon and an MCP server
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s install hook sets up its own launchers and binaries, consistent with its stated purpose. However, TUI startup triggers an undisclosed, daily background request for the latest package version, so this is suspicious runtime telemetry.
Decision evidence
public snapshot- Opening the TUI starts a silent background update check; subcommands skip it.
- The check runs at most once per day and stores its timestamp under ~/.cache/rakumux/last_update_check.
- The update check queries npm for the latest rakumux version; this runtime network activity is not disclosed in the README.
- The postinstall hook sets up the package’s own scripts and platform binaries in dist/.
- The package describes itself as a terminal session manager and documents its launcher commands.
- The inspected update check requests a package version and does not show collection of credentials or machine details.
Source & flagged code
7 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to rakumux@0.1.37.
See all versions of rakumux for other recorded verdicts.
- Review the evidence and your use of rakumux@0.1.37 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.