registry  /  @midwess/worldant  /  1.0.3

@midwess/worldant@1.0.3

Worldant CLI — thin verified installer for the Worldant runtime. Downloads, cryptographically verifies, and runs official signed release binaries.

AI Security Review

scanned 15m ago · by lpm-firewall-ai

Install-time code downloads a signed external runtime, writes it under the package-owned `~/.worldant` directory, and the explicit CLI command executes it. No credential harvesting, exfiltration, AI-agent configuration mutation, or destructive behavior beyond package-owned paths was found.

Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall downloads the runtime; `worldant` explicitly launches it.
Impact
A remote binary outside the npm tarball becomes executable after installation, subject to the package's signature and digest checks.
Mechanism
verified remote binary bootstrap and launcher
Rationale
The package is not demonstrably malicious, but its postinstall lifecycle hook retrieves an external executable that is later launched. Treat this as a warning-level staged payload carrier despite the implemented verification controls.
Evidence
package.jsoninstall.jsdownload.mjsverify-manifest.mjsinstaller-core.mjstrust-policy.jsonbin/worldant.jsuninstall.js~/.worldant/versions~/.worldant/current~/.worldant/installed.json
Network endpoints4
github.com/Midwess/worldant/releases/downloadgithub.comobjects.githubusercontent.comrelease-assets.githubusercontent.com

Decision evidence

public snapshot
AI called this Suspicious at 82.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
  • `package.json` runs `node install.js` as `postinstall`.
  • `install.js` downloads and extracts a platform binary into `~/.worldant`.
  • `bin/worldant.js` executes the downloaded binary via `spawnSync`.
  • `WORLDANT_RELEASE_BASE` changes release paths, though hosts remain allowlisted.
Evidence against
  • `install.js` requires the manifest version to equal package version.
  • `verify-manifest.mjs` verifies Sigstore identity against shipped policy.
  • `installer-core.mjs` checks SHA-256 and rejects unsafe archive paths.
  • `download.mjs` limits requests to HTTPS allowlisted hosts and redirects.
Behavioral surface
Source
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Supply chain
UrlStrings
ManifestNo manifest risk signals triggered.
scanned 6 file(s), 13.8 KB of source, external domains: 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 High3 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowUrl Strings