Potential fix for code scanning alert no. 8: Clear-text logging of sensitive information

[thegreatalxx]

Potential fix for https://github.com/thealxlabs/conductor/security/code-scanning/8

In general, to fix clear-text logging of sensitive information, you should avoid passing potentially sensitive values into logging functions or, if necessary, sanitize/mask them before logging. For test frameworks that log "detail" or "result" values, ensure that test callbacks return only non-sensitive summaries, not raw secrets or configuration values.

For this specific case, the tainted data reaches the sink because the test case OAuth redirect URI defaults to localhost returns creds.redirectUri, and test() passes that as detail into pass(), which logs it when --verbose is used. We can fix this without affecting test semantics by changing that test to return a non-sensitive string like 'ok' instead of creds.redirectUri. The assertion if (!creds.redirectUri.includes('localhost')) throw ... already checks correctness, so the return value is only for logging. This breaks the taint flow while leaving behavior (pass/fail conditions) unchanged.

Concretely:

• In test-all.mjs, inside async function testConfig(), modify the OAuth redirect URI defaults to localhost test so that:
  • It no longer returns creds.redirectUri.
  • It returns a generic string (e.g., 'ok') after cleaning up environment variables.
    No changes are needed to pass() or getOAuthCredentials; we only adjust the test's return value so that sensitive data is not logged.

---

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

[coderabbitai]

Warning

Rate limit exceeded

@thealxlabs has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 16 minutes and 6 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch alert-autofix-8

---

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 and usage tips.}