stepzen@0.60.0
The StepZen CLI
AI Security Review
scanned 6h ago · by lpm-firewall-aiThe package performs runtime analytics by default and sends account and project identifiers, including endpoint and workspace names. The activity fits the CLI’s purpose and no credential or file exfiltration was found, but the collection is not clearly disclosed in the inspected source, so it warrants a warning.
Static reason
No blocking static signals were detected.
Trigger
When the CLI runs tracked actions such as deploy or init; analytics is enabled unless STEPZEN_DISABLE_ANALYTICS is set.
Impact
Exposes account and project identifiers and usage activity to analytics without clear source disclosure; no credential theft or file collection was identified.
Mechanism
Segment events include the StepZen account ID and project-selected values such as the deploy endpoint or workspace name.
AI rationale
The package performs runtime analytics by default and sends account and project identifiers, including endpoint and workspace names. The activity fits the CLI’s purpose and no credential or file exfiltration was found, but the collection is not clearly disclosed in the inspected source, so it warrants a warning.
Evidence
lib/shared/segment.jslib/commands/deploy.js
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- Runtime analytics initializes by default; users must set STEPZEN_DISABLE_ANALYTICS to disable it.
- Tracked events include the StepZen account ID and an objectType property.
- The deploy command passes the endpoint name into a tracked event.
- The init event includes the workspace name.
Evidence against
- The analytics report CLI activity and StepZen project identifiers, rather than credentials or file contents.
- The package is the StepZen CLI, and the tracked events concern its login, deploy, init and import commands.
- The SDK sends MCSP API keys to IBM MCSP token endpoints to obtain service tokens.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsTelemetryUrlStrings
Source & flagged code
4 flaggedbin/dev.cmdView file
•path = bin/dev.cmd
kind = build_helper
sizeBytes = 86
magicHex = [redacted]
Medium
lib/commands/import/curl.js#virtual:normalized:round1View file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 13
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
lib/commands/import/curl.js#virtual:normalized:round1View on unpkglib/shared/segment.jsView file
Findings
1 High6 Medium5 Low
HighSemantic Analysis Limitedlib/commands/import/curl.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperbin/dev.cmd
MediumStructural Risk Force Deep Review
MediumAi Review Evidencelib/shared/segment.js
MediumAi Review Evidencelib/shared/segment.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
Affected versions and remediation
This report applies to stepzen@0.60.0.
See all versions of stepzen for other recorded verdicts.
- Review the evidence and your use of stepzen@0.60.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.