registry / @teambit/cli / 0.0.1424
@teambit/cli@0.0.1424
⚠ Under reviewAI Security Review
scanned 9d ago · by lpm-firewall-aiThe inspected package source shows ordinary CLI setup and no install hook or concrete attack behavior. Several selected runtime dependencies remain unresolved in this snapshot, so source inspection cannot establish a clean verdict.
Static reason
No blocking static signals were detected.
Trigger
Using the CLI may load its declared runtime dependencies.
Impact
The unavailable dependency code prevents resolving whether the full runtime behavior is benign.
Mechanism
The CLI parser imports dependencies whose implementation source is unavailable for review.
AI rationale
The inspected package source shows ordinary CLI setup and no install hook or concrete attack behavior. Several selected runtime dependencies remain unresolved in this snapshot, so source inspection cannot establish a clean verdict.
Evidence
package.jsondist/cli-parser.js
Decision evidence
public snapshotAI called this Manual Review at 82.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest has no lifecycle scripts and exposes a CLI entrypoint.
- The runtime invokes command start callbacks for the current command, consistent with CLI behavior.
- The CLI parser imports several declared runtime dependencies, but source for some imported dependencies is unavailable in the inspected snapshot.
Evidence against
- No concrete attack behavior was identified in the inspected package source.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
4 flaggedpackage.jsonView file
51./dist/index.js",
"import": "./dist/esm.mjs"
},
"default": "./dist/index.js"
},
"./dist/*": "./dist/*",
"./artifacts/*": "./artifacts/*"
},
"private": false,
"engines": {
"node": ">=16.0.0"
},
"repository": {
"type": "git",
"url": "https://github.com/teambit/bit"
},
"keywords": [
"bit",
"bit-aspect",
"bit-core-aspect",
"components",
"collaboration",
"web"
]
}
Low
Suspicious Lifecycle Evidence
The manifest has no lifecycle scripts and exposes a CLI entrypoint.
package.jsonView on unpkg · L5111"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.70",
Low
Suspicious Dependency Evidence
The CLI parser imports several declared runtime dependencies, but source for some imported dependencies is unavailable in the inspected snapshot.
package.jsonView on unpkg · L11dist/cli.main.runtime.jsView file
Findings
1 Medium7 Low
MediumEnvironment Vars
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/cli.main.runtime.js
LowSuspicious Dependency Evidencepackage.json
LowSuspicious Dependency Evidencedist/cli-parser.js
Affected versions and remediation
This report applies to @teambit/cli@0.0.1424.
See all versions of @teambit/cli for other recorded verdicts.
- Review the evidence and your use of @teambit/cli@0.0.1424 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.