@imagifly/cli@0.1.3
Agent-first CLI for the Imagifly image and video API
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package exposes an Imagifly API CLI with no install hook; its flagged process execution opens the OAuth URL only during a user-run login command. Credentials are used for requests to the configured API base, and no unrelated collection or automatic account action was found.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs the build; no install hook is declared.
- The bin entry runs the CLI command parser, and auth/browser actions are reached through explicit commands.
- Browser process execution opens the OAuth URL during login; it does not run an embedded shell payload.
- API credentials are sent as Bearer authorization to the configured Imagifly API base, which defaults to https://imagifly.net/api/v1.
- The flagged auth file combines environment access, network calls, and child_process usage, but the inspected code ties them to the documented login/API flow.
- The package has network and filesystem access for its image/video API features and saving user-requested credentials or media.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/commands/auth.jsView on unpkg · L2A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/commands/auth.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @imagifly/cli@0.1.3.
See all versions of @imagifly/cli for other recorded verdicts.
- Review the evidence and your use of @imagifly/cli@0.1.3 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.