registry / @blendsdk/lockstep / 1.2.0

@blendsdk/lockstep@1.2.0

A comprehensive monorepo package management tool that maintains synchronized versions across all packages (lockstep versioning) with flexible CI/CD integration.

AI Security Review

scanned 19h ago · by lpm-firewall-ai

Explicit `lockstep publish` can execute shell syntax embedded in `--tag`, `--access`, or the current Git branch name. This is a command-injection vulnerability, not evidence of intentional package malware.

Static reason

No blocking static signals were detected.

Trigger

Run `lockstep publish` with crafted option values or from a crafted branch.

Impact

Arbitrary commands may run with the invoking user's permissions.

Mechanism

unsanitized shell-command interpolation into execSync

Rationale

No install-time or covert malicious behavior was found, but the publish implementation contains a concrete command-injection path. Warn rather than block because exploitation requires the explicit publish workflow.

Evidence

package.jsondist/provenance.jsdist/lockstep.jsdist/changelog/llm-provider.jsdist/changelog/prompts.js

Decision evidence

public snapshot

AI called this Suspicious at 94.0% confidence as Critical Vulnerability with low false-positive risk.

Evidence for warning

dist/provenance.js builds a shell command from unsanitized access and tag values.
dist/lockstep.js passes that command to execSync during publish.

@blendsdk/lockstep@1.2.0

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code