registry / @imagifly/cli / 0.1.6
@imagifly/cli@0.1.6
Agent-first CLI for the Imagifly image and video API
AI Security Review
scanned 18h ago · by lpm-firewall-aiThe inspected source matches the package's stated purpose: the only lifecycle script builds the CLI, while credential and network operations are tied to explicit Imagifly commands. The flagged child process launches the browser for OAuth login, and credentials are sent to the Imagifly API or stored locally.
Static reason
No blocking static signals were detected.
Trigger
The user runs an Imagifly CLI command; OAuth browser login is explicitly triggered by `imagifly auth login`.
Impact
Normal operation can authenticate to the user's Imagifly account and save its token locally.
Mechanism
The CLI exchanges an OAuth authorization code with Imagifly, sends API credentials to the configured Imagifly API, and stores credentials in the local config file.
AI rationale
The inspected source matches the package's stated purpose: the only lifecycle script builds the CLI, while credential and network operations are tied to explicit Imagifly commands. The flagged child process launches the browser for OAuth login, and credentials are sent to the Imagifly API or stored locally.
Evidence
~/.config/imagifly/config.json (default; configurable via IMAGIFLY_CONFIG_DIR)
Network endpoints1
imagifly.net
Decision evidence
public snapshotAI called this Clean at 98.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package is an agent-first CLI for the Imagifly image and video API, with `dist/cli.js` as its executable entry point.
- Its only lifecycle script is `prepublishOnly`, which runs the build; there is no install hook.
- OAuth login runs only when requested. It obtains an authorization code through a local callback and exchanges it for an Imagifly access token.
- API credentials are sent as bearer tokens in API requests; the default API host is `imagifly.net`.
- The child process use launches the system browser to open the OAuth URL shown to the user.
- Saved credentials are written to the Imagifly config file with restrictive directory and file permissions.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/commands/auth.jsView file
2import { createServer } from "node:http";
L3: import { spawn } from "node:child_process";
L4: import { stdin as input } from "node:process";
High
Child Process
Package source references child process execution.
dist/commands/auth.jsView on unpkg · L21import { createHash, randomBytes } from "node:crypto";
L2: import { createServer } from "node:http";
L3: import { spawn } from "node:child_process";
L4: import { stdin as input } from "node:process";
...
L16: }
L17: if (!input.isTTY && !process.env.IMAGIFLY_ALLOW_DEVICE_LOGIN) {
L18: throw badArgs("Run `imagifly auth login` in a terminal, or pass --key only for CI.");
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/commands/auth.jsView on unpkg · L1package.jsonView file
2"name": "@imagifly/cli",
"version": "0.1.6",
"description": "Agent-first CLI for the Imagifly image and video API",
"type": "module",
"bin": {
"im
Findings
2 High2 Medium8 Low
HighChild Processdist/commands/auth.js
HighSame File Env Network Executiondist/commands/auth.js
MediumNetwork
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowAi Review Evidencepackage.json
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/cli.js
Affected versions and remediation
This report applies to @imagifly/cli@0.1.6.
See all versions of @imagifly/cli for other recorded verdicts.
- Review the evidence and your use of @imagifly/cli@0.1.6 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.