registry  /  voinznext  /  0.1.2

voinznext@0.1.2

Interactive CLI tool for scaffolding Next.js projects with your preferred tech stack

AI Security Review

scanned 4h ago · by lpm-firewall-ai

Install-time code downloads an unpinned platform binary from the latest GitHub release into the package bin directory. This creates supply-chain risk, but no confirmed malicious behavior appears in the reviewed JavaScript source.

Static reason
One or more suspicious static signals were detected.
Trigger
npm install postinstall; later voinznext CLI invocation
Impact
Remote release asset can define CLI runtime behavior outside the npm tarball review boundary.
Mechanism
unpinned release binary downloader and wrapper launcher
Attack narrative
On install, install.js queries GitHub for the latest VoinzNext release, downloads the platform-specific asset, writes it into the package bin directory, and chmods it executable. cli.js spawns that downloaded binary when the user runs voinznext. The reviewed JavaScript does not exfiltrate data or mutate agent/config surfaces, but the executable is unpinned and outside the npm tarball review boundary.
Rationale
The package should warn because install-time unpinned binary download means the installed executable is not source-reviewable from npm alone. The behavior is package-aligned and there is no concrete attack behavior in inspected source, so it is not malicious.
Evidence
package.jsoninstall.jscli.jsbin/voinznext.exebin/voinznext
Network endpoints2
api.github.com/repos/VoinzzZ/VoinzNext/releases/latestgithub.com/VoinzzZ/VoinzNext/releases/download/${version}/${binaryName}

Decision evidence

public snapshot
AI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
  • package.json defines postinstall: node install.js.
  • install.js fetches https://api.github.com/repos/VoinzzZ/VoinzNext/releases/latest at install time.
  • install.js downloads a release asset from github.com without hash/signature verification.
  • install.js writes a downloaded executable under bin/ and chmods it on non-Windows.
  • cli.js later spawns the downloaded binary with inherited stdio.
Evidence against
  • Only package-aligned GitHub endpoints are referenced.
  • No credential, env, home directory, AI-agent config, persistence, or destructive access found.
  • No install-time execution of the downloaded binary; execution is on CLI invocation.
  • No eval/vm/Function or dynamic require/import found.
  • Package contents are limited to package.json, install.js, and cli.js.
Behavioral surface
Source
ChildProcessFilesystemNetwork
Supply chain
UrlStrings
ManifestNo manifest risk signals triggered.
scanned 2 file(s), 3.43 KB of source, external domains: api.github.com, github.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 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
LowScripts Present
LowFilesystem
LowUrl Strings