Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update security information #157

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

achilleas-kal
Copy link
Contributor

@achilleas-kal achilleas-kal commented Oct 8, 2024

Summary by CodeRabbit

  • Documentation
    • Updated contact information for reporting security vulnerabilities.
    • Clarified reporting instructions for issues with Cosmos SDK or CometBFT.
    • Improved readability with minor wording adjustments.

Copy link

coderabbitai bot commented Oct 8, 2024

Walkthrough

The changes in the SECURITY.md file include updates to contact information, specifically changing the email address for reporting security vulnerabilities and rephrasing references to the team name. Additionally, the instructions for reporting issues related to the Cosmos SDK have been revised to direct users to HackerOne instead of a previous security page. Minor wording adjustments have been made for clarity, while the overall structure of the document remains unchanged.

Changes

File Change Summary
SECURITY.md - Updated email address from [email protected] to [email protected].
- Changed "Injective Labs team" to "Injective Foundation team."
- Revised reporting instructions to direct users to HackerOne instead of Tendermint's security page.
- Minor wording adjustments for clarity.

Poem

In the garden of code, a change we embrace,
With new paths for reporting, we quicken the pace.
From labs to foundations, we hop with delight,
Security's stronger, our future is bright!
So gather your bunnies, let’s celebrate cheer,
For clarity blossoms, and safety is near! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8c5558d and 1dccee6.

📒 Files selected for processing (1)
  • SECURITY.md (2 hunks)
🧰 Additional context used
🪛 LanguageTool
SECURITY.md

[style] ~26-~26: Consider using the synonym “brief” (= concise, using a few words, not lasting long) to strengthen your wording.
Context: ...email should include the issue ID and a short description of why it should be handled...

(QUICK_BRIEF)


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • 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. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai 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

Documentation and Community

  • 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.

@achilleas-kal achilleas-kal requested a review from Ri-go October 8, 2024 14:03
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