registry / @teambit/cli / 0.0.1431
@teambit/cli@0.0.1431
⚠ Under reviewAI Security Review
scanned 7d ago · by lpm-firewall-aiThe inspected source shows no confirmed attack, and the process launch is associated with configured CLI paging. Runtime dependencies required by the CLI have unresolved source, so their behavior cannot be cleared from this snapshot.
Static reason
No blocking static signals were detected.
Trigger
Import or use of the CLI runtime and parser.
Impact
No malicious effect is confirmed, but the incomplete dependency review prevents a clean determination.
Mechanism
The CLI modules require Harmony and legacy dependencies whose implementations were unavailable in the package snapshot.
AI rationale
The inspected source shows no confirmed attack, and the process launch is associated with configured CLI paging. Runtime dependencies required by the CLI have unresolved source, so their behavior cannot be cleared from this snapshot.
Evidence
package.jsondist/index.jsdist/cli.aspect.jsdist/cli-parser.js
Decision evidence
public snapshotAI called this Manual Review at 86.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest points to the CLI entrypoint and declares runtime dependencies, including Harmony and legacy modules.
- The exported CLI paths require Harmony and legacy modules whose implementations were not available for this review, leaving runtime behavior unresolved.
- The pager reads BIT_PAGER or PAGER, defaults to less, and spawns the selected pager.
Evidence against
- No concrete attack was identified in the inspected package source; the observed child process launch is tied to pager configuration.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedpackage.jsonView file
1{
"name": "@teambit/cli",
"version": "0.0.1431",
"homepage": "https://bit.cloud/teambit/harmony/cli",
"main": "dist/index.js",
"componentId": {
"scope": "teambit.harmony",
"name": "cli",
"version": "0.0.1431"
},
"dependencies": {
"chalk": "4.1.2",
"didyoumean": "1.2.1",
"lodash": "4.18.1",
"yargs": "17.0.1",
"p-map-series": "2.1.0",
"fs-extra": "10.0.0",
"pad-right": "0.2.2",
"@teambit/legacy.loader": "0.0.34",
"@teambit/legacy.logger": "0.0.71",
"@teambit/harmony.modules.runtimes": "0.0.4",
"@teambit/har
Low
Suspicious Dependency Evidence
The manifest points to the CLI entrypoint and declares runtime dependencies, including Harmony and legacy modules.
package.jsonView on unpkg · L1dist/index.jsView file
204const data = require("./cli.aspect");
_cli = function () {
return data;
};
return data;
}
function _globalFlags() {
const data = _interopRequireDefault(require("./globa
Low
Ai Review Evidence
The exported CLI paths require Harmony and legacy modules whose implementations were not available for this review, leaving runtime behavior unresolved.
dist/index.jsView on unpkg · L204Findings
1 Medium9 Low
MediumEnvironment Vars
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Dependency Evidencepackage.json
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/cli.aspect.js
LowAi Review Evidencedist/cli-parser.js
LowAi Review Evidencedist/pager.js
LowAi Review Evidencedist/pager.js
Affected versions and remediation
This report applies to @teambit/cli@0.0.1431.
See all versions of @teambit/cli for other recorded verdicts.
- Review the evidence and your use of @teambit/cli@0.0.1431 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.