registry / @teambit/cli / 0.0.1428
@teambit/cli@0.0.1428
⚠ Under reviewAI Security Review
scanned 8d ago · by lpm-firewall-aiThe inspected local caller redacts token flags before passing command data to analytics, but does not establish the analytics dependency’s transfer behavior or recipient. That unresolved behavior prevents a clean verdict, while the inspected source does not establish an attack.
Static reason
No blocking static signals were detected.
Trigger
Running a CLI command that reaches the command runner’s initialization path.
Impact
The local source is insufficient to determine whether analytics sends data or to whom.
Mechanism
The runner supplies a command name, redacted flags, and arguments to the analytics dependency; the inspected source does not show what that dependency does with them.
AI rationale
The inspected local caller redacts token flags before passing command data to analytics, but does not establish the analytics dependency’s transfer behavior or recipient. That unresolved behavior prevents a clean verdict, while the inspected source does not establish an attack.
Evidence
package.jsondist/command-runner.js
Decision evidence
public snapshotAI called this Manual Review at 72.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest lists @teambit/legacy.analytics as a dependency, and the local command runner passes it the command name, redacted flags, and arguments; its implementation and any recipient are not established by the inspected package source.
- The runtime redacts token flags before initializing analytics.
- The entrypoint exposes CLI runtime modules through re-exports.
- The pager uses the configured BIT_PAGER or PAGER value and honors disabling paging.
Evidence against
- The inspected local analytics call redacts token flags before handing its payload to the analytics dependency.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
4 flaggedpackage.jsonView file
11"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/harmony": "0.4.12",
"@teambit/bit.get-bit-version": "0.0.31",
"@teambit/logger": "0.0.1502",
"@teambit/legacy.analytics": "0.0.117",
"@teambit/legacy.con
Low
Suspicious Dependency Evidence
The manifest lists @teambit/legacy.analytics as a dependency, and the local command runner passes it the command name, redacted flags, and arguments; its implementation and any recipient are not established by the inspected package source.
package.jsonView on unpkg · L11dist/command-runner.jsView file
119hing is logged or sent to analytics. The raw token
// is the user's bit.cloud credential; debug logs are persisted to disk and
// routinely shared in support tickets / issues.
const redactedFlags = this.getRedactedFlagsForReporting();
try {
_legacy4().Analytics.init(this.commandName, redactedFlags, this.args);
} catch (err) {
// ignoring the error, we don't want to fail the app if analytics failed.
_legacy().logger.error('failed to initialize analytics', err);
}
_legacy().logger.info(`[*] started a new comman
Findings
1 Medium7 Low
MediumEnvironment Vars
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Dependency Evidencepackage.json
LowAi Review Evidencedist/command-runner.js
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/pager.js
Affected versions and remediation
This report applies to @teambit/cli@0.0.1428.
See all versions of @teambit/cli for other recorded verdicts.
- Review the evidence and your use of @teambit/cli@0.0.1428 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.