Skip to content

🛡️ Sentinel: obfuscate sensitive tokens in CLI arguments - #35

Draft
piyyy314 wants to merge 2 commits into
mainfrom
sentinel/obfuscate-sensitive-tokens-1453252894358789402
Draft

🛡️ Sentinel: obfuscate sensitive tokens in CLI arguments#35
piyyy314 wants to merge 2 commits into
mainfrom
sentinel/obfuscate-sensitive-tokens-1453252894358789402

Conversation

@piyyy314

Copy link
Copy Markdown
Owner

Summary of Security Enhancement

  • Vulnerability / Security Concern: obfuscateArgs in src/lib/utils.ts only redacted username and password CLI flags. Other sensitive CLI options such as token and tfc-token were left unmasked in command args, posing a risk of credential leakage in analytics or telemetry event logging.
  • Fix: Updated obfuscateArgs to iterate over a list of sensitive keys (['username', 'password', 'token', 'tfc-token']) and obfuscate them to ${key}-set.
  • Verification: Added unit test cases in test/jest/unit/lib/util.spec.ts covering token and tfc-token obfuscation, and verified all unit tests pass with npx jest test/jest/unit/lib/util.spec.ts.

PR created automatically by Jules for task 1453252894358789402 started by @piyyy314

…logs

Redact sensitive token flags (`token` and `tfc-token`) alongside `username` and `password` in `obfuscateArgs` to prevent sensitive credentials from leaking into analytics and telemetry payloads.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@coderabbitai

coderabbitai Bot commented Aug 21, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7ae4aa3b-48be-4bd5-8ee3-7baa984a9833

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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

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

@piyyy314

piyyy314 commented Aug 21, 2026

Copy link
Copy Markdown
Owner Author

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

…logs

Redact sensitive token flags (`token` and `tfc-token`) alongside `username` and `password` in `obfuscateArgs` to prevent sensitive credentials from leaking into analytics and telemetry payloads.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant