registry / @devvit/cli / 0.14.2
@devvit/cli@0.14.2
Reddit's Dev Platform CLI Tool
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no registry install lifecycle hook or self-dependency chain. Its risky primitives are tied to explicit CLI workflows and project-local configuration, with no concrete malicious behavior found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user explicitly runs devvit init or devvit playtest.
Impact
The commands can modify or run the user's selected project, but no covert persistence, credential harvesting, or unconsented exfiltration was found.
Mechanism
Project initialization, project dependency installation, and execution of the project's configured development script.
AI rationale
The package has no registry install lifecycle hook or self-dependency chain. Its risky primitives are tied to explicit CLI workflows and project-local configuration, with no concrete malicious behavior found.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no preinstall, install, or postinstall hook.
- The runtime npm install is an exported helper used by the explicit init command.
- The shell execution in playtest runs only the current project's configured scripts.dev command.
- The process utility only terminates the child process tree started for development.
- The dynamic require reads this package's package.json to check the Node.js version.
Evidence against
- Explicit init can rewrite a newly created project's package.json and install its dependencies.
- Explicit playtest can run a project's scripts.dev with a shell.
- User-invoked app publishing can upload a supplied source bundle to a server-provided URL.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
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 · L11import { spawnSync } from 'node:child_process';
L2: import { execaCommand } from 'execa';
L3: /**
High
dist/lib/hooks/init/check-node-version.jsView file
8// Verify that the user is using a supported version of Node.js, based on the engines property in package.json
L9: const require = createRequire(import.meta.url);
L10: const { engines } = require('../../../../package.json');
Medium
Findings
1 Critical4 High5 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/commands/playtest.js
HighChild Processdist/util/kill-process-tree.js
HighShelldist/util/kill-process-tree.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.14.2.
See all versions of @devvit/cli for other recorded verdicts.
- Review the evidence and your use of @devvit/cli@0.14.2 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.