registry / @teambit/cli / 0.0.1429
@teambit/cli@0.0.1429
⚠ Under reviewAI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest has no install scripts, and inspected files show ordinary CLI exports and runtime imports. Because source for selected runtime dependencies is unavailable, the package cannot be cleared; the unavailable source alone does not establish malicious behavior.
Static reason
No blocking static signals were detected.
Trigger
Loading or invoking the exported CLI runtime.
Impact
The behavior of those dependencies cannot be established from the available source.
Mechanism
The CLI runtime imports dependencies in the @teambit scope whose source was unavailable for inspection.
AI rationale
The manifest has no install scripts, and inspected files show ordinary CLI exports and runtime imports. Because source for selected runtime dependencies is unavailable, the package cannot be cleared; the unavailable source alone does not establish malicious behavior.
Evidence
package.jsondist/cli.main.runtime.jsdist/cli-parser.js
Decision evidence
public snapshotAI called this Manual Review at 93.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest declares several runtime dependencies in the @teambit scope.
- The exported CLI runtime imports dependencies whose source was unavailable in this snapshot.
Evidence against
- The manifest has no install lifecycle scripts, and the entrypoint exports CLI functionality.
- The inspected lodash manifest identifies it as a utility library; its entrypoint loads lodash.js.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggedpackage.jsonView file
17.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.constants": "0.0.50",
"@teambit/bit-error": "0.0.404",
"@teambit/lega
Low
Suspicious Dependency Evidence
The manifest declares several runtime dependencies in the @teambit scope.
package.jsonView on unpkg · L171{
"name": "@teambit/cli",
"version": "0.0.1429",
"homepage": "https://bit.cloud/teambit/harmony/cli",
"main": "dist/index.js",
"componentId": {
"scope": "teambit.harmony",
"name": "cli",
"version": "0.0.1429"
},
"dependencies": {
"chalk": "4.1.2",
Low
Suspicious Dependency Evidence
The manifest declares several runtime dependencies in the @teambit scope.
package.jsonView on unpkg · L1dist/cli.main.runtime.jsView file
Findings
1 Medium10 Low
MediumEnvironment Vars
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Dependency Evidencepackage.json
LowSuspicious Dependency Evidencedist/cli.main.runtime.js
LowSuspicious Dependency Evidencedist/cli-parser.js
LowSuspicious Dependency Evidencepackage.json
LowSuspicious Dependency Evidencedist/index.js
LowSuspicious Dependency Evidence.lpm-dependency-evidence-8a87c2bd-6f07-4ebc-a2ab-29f51a116f53/2/npm-linux/package.json
LowSuspicious Dependency Evidence.lpm-dependency-evidence-8a87c2bd-6f07-4ebc-a2ab-29f51a116f53/2/npm-linux/index.js
Affected versions and remediation
This report applies to @teambit/cli@0.0.1429.
See all versions of @teambit/cli for other recorded verdicts.
- Review the evidence and your use of @teambit/cli@0.0.1429 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.