AI Security Review
scanned 4h ago · by lpm-firewall-aiThe npm wrapper performs install-time and first-run setup of a Python package named utim-cli. This creates real remote package execution/supply-chain risk, but source inspection shows package-aligned behavior rather than a confirmed malicious chain.
Decision evidence
public snapshot- package.json defines postinstall: node scripts/postinstall.js
- scripts/postinstall.js runs python -m pip install --upgrade --quiet utim-cli during npm install when Python exists
- bin/utim.js auto-installs utim-cli on first run and can run curl | bash on Termux for pydantic-core setup
- bin/utim.js launches python -m utim_cli.utim with user CLI args
- Postinstall is described as best-effort prewarm and exits 0 on failure
- No credential/env harvesting, npm token reads, or exfiltration code found in package files
- Network/install activity is package-aligned with installing the documented Python engine
- No AI-agent config files or foreign control surfaces are modified by the npm package
- No obfuscation, eval/vm/Function, native binary loading, or persistence logic found
Source & flagged code
3 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 unpkgThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
bin/utim.jsView on unpkg