@salesforce/b2c-cli@2.10.0
⚠ Under reviewA Salesforce B2C Commerce CLI
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe inspected launcher and package entrypoint show normal CLI setup, with no confirmed attack behavior. Because the primary runtime SDK source was unavailable, the unresolved dependency prevents a clean verdict.
Decision evidence
public snapshot- The manifest names a command-line entrypoint and declares the matching Salesforce tooling SDK as a runtime dependency.
- The launcher imports configuration support from that SDK, and the package re-exports its command and configuration APIs.
- The SDK source was unavailable in the inspected package snapshot, so its runtime behavior could not be verified.
- No preinstall or postinstall hook was found in the manifest, and the inspected launcher starts the CLI after loading environment configuration.
Source & flagged code
5 flaggedPackage contains a possible secret pattern.
dist/commands/_test/index.jsView on unpkg · L30Findings
Affected versions and remediation
This report applies to @salesforce/b2c-cli@2.10.0.
See all versions of @salesforce/b2c-cli for other recorded verdicts.
- Review the evidence and your use of @salesforce/b2c-cli@2.10.0 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.