registry  /  @star-setup/star-setup  /  0.4.4

@star-setup/star-setup@0.4.4

Lightweight CLI to clone, configure, and wire single or multi-repo ecosystems

AI Security Review

scanned 17h ago · by lpm-firewall-ai

Install-time code downloads and unpacks a platform native executable from GitHub releases into the package directory. This is package-aligned but leaves the reviewed npm source as a binary downloader rather than the full executable payload.

Static reason
One or more suspicious static signals were detected.
Trigger
npm install postinstall; later star-setup CLI invocation
Impact
Unreviewed release binary executes with user privileges when the CLI is run; install-time network fetch occurs during npm lifecycle.
Mechanism
platform binary download, archive extraction, and native executable launch
Attack narrative
On install, package.json postinstall runs install.js, which selects a platform artifact URL under the package's GitHub release, downloads it with axios, and extracts it into node_modules/.bin_real. The bin wrapper later spawns that downloaded executable with inherited stdio and current working directory.
Rationale
The source shows a package-aligned native binary installer, not concrete malware, exfiltration, persistence, or AI-agent hijacking. Because the npm package fetches and executes an external binary payload at lifecycle/runtime that is not inspectable in the package source, a warning is appropriate.
Evidence
package.jsoninstall.jsbinary.jsbinary-install.jsrun-star-setup.jsnode_modules/.bin_realOS temp archive path
Network endpoints1
github.com/star-setup/core/releases/download/v0.4.4

Decision evidence

public snapshot
AI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
  • package.json defines postinstall: node ./install.js
  • install.js calls install(false) during npm lifecycle
  • binary-install.js downloads a platform archive with axios and extracts it
  • binary-install.js runs downloaded bin from node_modules/.bin_real on CLI invocation
Evidence against
  • Download URL is package-aligned GitHub release path for star-setup/core v0.4.4
  • No credential, env, or sensitive file harvesting found in JS sources
  • No AI-agent config/control-surface writes found
  • No persistence outside package install directory found
Behavioral surface
Source
ChildProcessFilesystemNetwork
Supply chain
UrlStrings
Manifest
NoLicense
scanned 4 file(s), 10.0 KB of source, external domains: example.com

Source & flagged code

2 flagged · loading source
package.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 unpkg

Findings

1 High2 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
LowScripts Present
LowFilesystem
LowUrl Strings
LowNo License