[cashflaretech-glitch]

Summary

Enforce Testnet-only deployment boundaries and redact secret-bearing child process output before exposing it to users.

Changes

• Guard the deploy command so and similar values are rejected before any subprocesses launch.
• Validate the deployment identity alias while preserving the existing MVP safety model.
• Redact secret-like values such as from terminal output.
• Add regression coverage for the deployment boundary and output sanitation.

Verification

@diginodes/stellarforge-cli@0.1.0 test
vitest run

RUN v5.0.1 /workspaces/stellarforge-cli

Deploying smart contract to Stellar Testnet.
Running 1 project test workflow.

Test Files 32 passed (32)
Tests 162 passed | 1 skipped (163)
Start at 22:19:21
Duration 11.40s (tests 88%, import 6%, transform 5%, worker 2%)

Isolate  32 workers spawned · ~97ms startup each (spawn + environment, per file)
         at least ~3.01s faster with isolate: false — reuses workers across files instead of one per file

@diginodes/stellarforge-cli@0.1.0 typecheck
tsc -p tsconfig.json --noEmit

@diginodes/stellarforge-cli@0.1.0 lint
eslint .

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 49467aa0-8416-42c4-ae54-a9e48d2071e1

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[dDevAhmed]

@cashflaretech-glitch where is the issue reference?