Skip to content

chore: add CLAUDE.md with Hacken bug bounty PR guidelines #404

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.

Sign up for GitHub

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

Merged
rootulp merged 1 commit into from
Apr 7, 2026
Merged

chore: add CLAUDE.md with Hacken bug bounty PR guidelines #404

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# CLAUDE.md

Comment on lines +1 to +2
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

CLAUDE.md is intended to provide context for the Claude Code tool, specifically build and test commands. Including these commands (as found in the README) will allow the tool to operate more effectively within this repository.

Suggested change
# CLAUDE.md
# CLAUDE.md
## Build and Test
- Build: make build
- Test: make test
- Lint: make lint
- Benchmarks: make bench

## Security PRs

- For PRs that resolve Hacken bug bounty reports, do not include details about the bug in the PR description. Instead, link to a Linear issue that contains more details on the bug and the link to the Hacken bug bounty report.
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

security-medium medium

The guideline should also explicitly mention PR titles, as they are often public and can inadvertently disclose vulnerability details. Additionally, consider generalizing this rule to all security-related PRs, not just Hacken reports, to ensure a consistent security posture for all sensitive fixes.

Suggested change
- For PRs that resolve Hacken bug bounty reports, do not include details about the bug in the PR description. Instead, link to a Linear issue that contains more details on the bug and the link to the Hacken bug bounty report.
- For PRs that resolve security vulnerabilities (including Hacken bug bounty reports), do not include details about the bug in the PR title or description. Instead, link to a Linear issue that contains the vulnerability details and a link to the original report.

Loading