Is @paulnsorensen/hallouminate-nightly safe?
- Node.js shell/command execution
- npm install-time lifecycle hook
@paulnsorensen/hallouminate-nightly is an AI npm_package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 2 risky constructs are reported for review. It can: install time execution and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).
@paulnsorensen/hallouminate-nightly 0.0.0-experimental.243.1
Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of @paulnsorensen/hallouminate-nightly's authors. Report a false positive.
Behavioral traits
How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.
Findings (2)
package.json runs scripts automatically when the package is installed.
"postinstall": "node install.js"
Why it matters: Install scripts are a favorite supply-chain foothold — they execute on every machine that installs the package.
Fix: Inspect the hook command. Install-time scripts are a common supply chain execution vector; ensure they do nothing beyond a documented build step.
The component can run operating-system commands or spawn processes.
const { spawn } = require("child_process");const tar = spawn(
const { spawn } = require("child_process");const child = spawn(bin, process.argv.slice(2), { stdio: "inherit" });Why it matters: Powerful and often legitimate — confirm the commands aren't built from untrusted input.
Fix: Confirm the command and its arguments are fully controlled and not derived from untrusted input; prefer execFile with an argument array.
Check your own component
Run the same evidence-backed scan on any MCP server, agent skill, or package.
Scan your own componentHow we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →