Potential fix for code scanning alert no. 9: Clear-text storage of sensitive information

[priyanshujain]

Potential fix for https://github.com/priyanshujain/infragpt/security/code-scanning/9

The best way to fix this clear-text storage of sensitive info is to adopt a "deny by default, allow by exception" approach: always allow-list explicitly the fields that are safe for storage, for every interaction type. This avoids risk from future data changes or insufficient sanitization. The function log_interaction should enforce that only whitelisted, non-sensitive fields are persisted for all interaction types. If a new interaction type is introduced, developers must consciously choose which fields to store, avoiding inadvertent logging of secrets like api_key or password.

Steps:

• Define a global dictionary of interaction types mapping to lists of allowed safe fields to store for each type: e.g. "agent_conversation_v2": [ ... ].
• In log_interaction, always use this allow-list to filter the sanitized data before logging, regardless of interaction type.
• Optionally, preserve/strengthen the existing sanitization function as defense-in-depth for types with no allow-list, by having it filter all keys except those known safe fields. For types not covered, log only the minimal ID/timestamp/type, and warn developers.
• No change of existing data structures or logged fields should occur, except that any future sensitive fields not in the allow-list will be omitted from logs.

---

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

[coderabbitai]

Warning

Rate limit exceeded

@priyanshujain has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 12 minutes and 19 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.

📥 Commits

Reviewing files that changed from the base of the PR and between bc83938 and da00392.

📒 Files selected for processing (1)

• cli/src/infragpt/history.py (2 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

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

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

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

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.