registry / @nocobase/cli-v1 / 2.2.26

@nocobase/cli-v1@2.2.26

AI Security Review

scanned 3d ago · by lpm-firewall-ai

The manifest has no install lifecycle hook, and the flagged operations are tied to explicit CLI workflows. Package credentials are used for authentication to the package registry, with no concrete attack behavior established by the inspected source.

Static reason

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Trigger

A user invokes the package download, development, or E2E CLI command.

Impact

These operations support the requested CLI workflows; the inspected source does not establish covert credential disclosure or other concrete attack behavior.

Mechanism

The package command authenticates to the NocoBase package registry; development and E2E commands launch configured local tools and processes.

AI rationale

Evidence

package.jsonsrc/commands/pkg.jssrc/commands/e2e.jssrc/util.jssrc/commands/dev.js

Network endpoints2

pkg.nocobase.com/esm.sh

Decision evidence

public snapshot

AI called this Clean at 91.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json declares CLI entrypoints and has no lifecycle scripts.
The package download command uses the NocoBase package host by default and runs only as an explicit CLI command.
Saved license access keys are read from the local license file for package authentication.
The login request sends credentials to the configured package registry endpoint, and the command returns without credentials when none are available.
The E2E install and process launches occur inside the explicitly invoked E2E workflow.
Shell execution is exposed through a CLI utility; the inspected dynamic code generation parses npm version output.

Evidence against

Behavioral surface

Source

ChildProcessDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

Source & flagged code

6 flagged

src/commands/e2e.jsView file

Lines 1-31javascript

1/**

2 * This file is part of the NocoBase (R) project.

4 * Authors: NocoBase Team.

5 *

6 * This project is dual-licensed under AGPL-3.0 and NocoBase Commercial License.

7 * For more information, please refer to: https://www.nocobase.com/agreement.

8 */

10const { Command } = require('commander');

11const { run, isPortReachable, checkDBDialect, storagePathJoin } = require('../util');

12const { execSync } = require('node:child_process');

13const axios = require('axios');

High

Child Process

Package source references child process execution.

src/commands/e2e.jsView on unpkg · L11

14const { pTest } = require('./p-test');

15const os = require('os');

16const treeKill = require('tree-kill');

17const chalk = require('chalk');

19/**

20 * 检查服务是否启动成功

21 */

22const checkServer = async (duration = 1000, max = 60 * 10) => {

23 return new Promise((resolve, reject) => {

24 let count = 0;

25 const timer = setInterval(async () => {

26 if (count++ > max) {

27 clearInterval(timer);

28 return reject(new Error('Server start timeout.'));

29 }

31 // if (!(await checkPort(PORT))) {

Lines 103-143javascript

103 run('nocobase-v1', [process.env.APP_ENV === 'production' ? 'start' : 'dev'], options);

104}

105

106process.on('SIGINT', async () =>

src/util.jsView file

Lines 1-31javascript

1/**

2 * This file is part of the NocoBase (R) project.

4 * Authors: NocoBase Team.

5 *

6 * This project is dual-licensed under AGPL-3.0 and NocoBase Commercial License.

7 * For more information, please refer to: https://www.nocobase.com/agreement.

8 */

10const net =

bin/index.jsView file

Lines 1-22javascript

1#!/usr/bin/env node

3const chalk = require('chalk');

4const { initEnv, genTsConfigPaths } = require('../src/util');

Medium

src/commands/dev.jsView file

•matchType = previous_version_dangerous_delta matchedPackage = @nocobase/cli-v1@2.1.17 matchedIdentity = npm:QG5vY29iYXNlL2NsaS12MQ:2.1.17 similarity = 0.889 summary = stored previous version shares package body but lacks this dangerous source file

Critical

Previous Version Dangerous Delta

This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.

src/commands/dev.jsView on unpkg

Source & flagged code

6 flagged · loading source

src/commands/e2e.jsView file

11const { run, isPortReachable, checkDBDialect, storagePathJoin } = require('../util'); L12: const { execSync } = require('node:child_process'); L13: const axios = require('axios');

High

Child Process

Package source references child process execution.

src/commands/e2e.jsView on unpkg · L11

123try { L124: execSync( L125: `npx playwright codegen --load-storage=${authFile} ${process.env.APP_BASE_URL} --save-storage=${authFile}`, L126: commonConfig,

High

Runtime Package Install

Package source invokes a package manager install command at runtime.

src/commands/e2e.jsView on unpkg · L123

src/util.jsView file

11const chalk = require('chalk'); L12: const execa = require('execa'); L13: const fg = require('fast-glob');

High

Shell

Package source references shell execution.

src/util.jsView on unpkg · L11

Findings

1 Critical3 High4 Medium4 Low

CriticalPrevious Version Dangerous Deltasrc/commands/dev.js

HighChild Processsrc/commands/e2e.js

HighShellsrc/util.js

HighRuntime Package Installsrc/commands/e2e.js

MediumDynamic Requirebin/index.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowEvalsrc/util.js

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to @nocobase/cli-v1@2.2.26.

See all versions of @nocobase/cli-v1 for other recorded verdicts.

Review the evidence and your use of @nocobase/cli-v1@2.2.26 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: 2026-10-20 08:56:56.815Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.