registry / @devvit/cli / 0.15.1
@devvit/cli@0.15.1
⚠ Under reviewReddit's Dev Platform CLI Tool
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe static hints do not establish malicious behavior: the manifest has no install lifecycle hook, and initialization invokes npm as part of an explicit project setup flow. Source for selected runtime dependencies remains unavailable, so this inspection cannot support a clean verdict.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the CLI activates its command framework and command-specific runtime dependencies.
Impact
An attack cannot be confirmed or excluded across these unresolved dependency boundaries.
Mechanism
The manifest selects dependencies whose source could not be inspected; the available package source does not resolve their behavior.
AI rationale
The static hints do not establish malicious behavior: the manifest has no install lifecycle hook, and initialization invokes npm as part of an explicit project setup flow. Source for selected runtime dependencies remains unavailable, so this inspection cannot support a clean verdict.
Evidence
package.jsonbin/devvit.jsdist/commands/init.jsdist/commands/publish.js
Decision evidence
public snapshotAI called this Manual Review at 78.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest exposes a command-line entry point and declares selected runtime dependencies whose source is unavailable in this snapshot.
- Project dependency installation is performed by the explicit init flow; the inspected code runs npm in the newly initialized project directory.
- Publishing runs the project’s configured build script before authentication and upload; this is a runtime boundary whose imported dependency source remains unresolved.
Evidence against
- The manifest contains no preinstall, install, or postinstall lifecycle hook. The detected npm install invocation is inside project initialization, not an install-time package hook.
- The CLI entry point starts the command framework, and the inspected source does not establish covert collection or an unrelated recipient.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
Source & flagged code
7 flaggeddist/util/kill-process-tree.jsView file
1import { spawnSync } from 'node:child_process';
L2: import { execaCommand } from 'execa';
High
Child Process
Package source references child process execution.
dist/util/kill-process-tree.jsView on unpkg · L1dist/commands/upload.jsView file
22import chalk from 'chalk';
L23: import { execaCommand } from 'execa';
L24: import { REDDIT_DESKTOP } from '../lib/config.js';
High
dist/lib/hooks/init/check-node-version.jsView file
8
Findings
1 Critical4 High5 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/commands/publish.js
HighChild Processdist/util/kill-process-tree.js
HighShelldist/commands/upload.js
HighRuntime Package Installdist/commands/init.js
HighSemantic Analysis Limiteddist/commands/init.js#virtual:normalized:round1
MediumDynamic Requiredist/lib/hooks/init/check-node-version.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperbin/devvit.cmd
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Low
Affected versions and remediation
This report applies to @devvit/cli@0.15.1.
See all versions of @devvit/cli for other recorded verdicts.
- Review the evidence and your use of @devvit/cli@0.15.1 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.