Skip to content

Opsec update #2

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
saleel merged 2 commits into from
Feb 5, 2026
Merged

Opsec update #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a23776e
update repo docs
randyquaye Feb 5, 2026
56932e5
update sec email
randyquaye Feb 5, 2026
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
7 changes: 7 additions & 0 deletions .github/CODEOWNERS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# CODEOWNERS for Aztec Staking Dashboard


# Default owners for everything not matched by a more specific rule
* @AztecProtocol/sdb-review


2 changes: 2 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,8 @@ If you find a bug, please open an issue with:
4. **Environment details** (browser, OS, Node version)
5. **Screenshots** if applicable

If your report relates to a **security vulnerability or security-sensitive issue**, please **do not** open a public issue and instead follow the private disclosure process described in `SECURITY.md`.

### Suggesting Features

For feature requests, open an issue with:
Expand Down
35 changes: 35 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
## Security Policy

We take the security of the Aztec Staking Dashboard seriously and strongly encourage researchers to report security vulnerabilities privately. Please use the guidelines below when reporting security issues.

## Reporting Security Vulnerabilities

- **Do not** open public GitHub issues or pull requests for suspected security vulnerabilities.

Instead, please use the [Private Vulnerability Reporting](https://github.com/AztecProtocol/staking-dashboard/security/advisories/new) process on GitHub.
Copy link

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

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

There is a trailing space at the end of this line after "GitHub." which should be removed for clean formatting.

Suggested change
Instead, please use the [Private Vulnerability Reporting](https://github.com/AztecProtocol/staking-dashboard/security/advisories/new) process on GitHub.
Instead, please use the [Private Vulnerability Reporting](https://github.com/AztecProtocol/staking-dashboard/security/advisories/new) process on GitHub.

Copilot uses AI. Check for mistakes.

- Navigate to the "Security" tab of this repository.
- Click "Report a vulnerability" on the left sidebar.
- Fill out the form with the details of your discovery:
1. Description of the vulnerability and potential impact
2. Steps to reproduce (including logs, requests, or PoCs as appropriate)
3. Environment details (browser, OS, network assumptions)

You can also email security@aztec.foundation
Copy link

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

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

This sentence is missing ending punctuation. Add a period at the end for consistency with standard sentence structure.

Suggested change
You can also email security@aztec.foundation
You can also email security@aztec.foundation.

Copilot uses AI. Check for mistakes.

We will:
- Acknowledge receipt of your report as soon as reasonably possible
- Investigate and validate the issue
- Work on a fix and coordinate disclosure timing with you when appropriate

If you believe a vulnerability is actively being exploited or has severe impact (e.g. loss of funds, key compromise, or broad user impact), please clearly mark the report as **CRITICAL** in the pvr/email subject.

## Reporting Non‑Security Bugs and Feature Requests
Copy link

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

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

The heading uses a non-breaking hyphen (U+2011) instead of a standard hyphen. This should be changed to use a regular hyphen for consistency and to avoid potential issues with text processing tools and search functionality.

Suggested change
## Reporting Non‑Security Bugs and Feature Requests
## Reporting Non-Security Bugs and Feature Requests

Copilot uses AI. Check for mistakes.

For issues that are **not** security-sensitive (UI glitches, performance problems, feature requests, etc.):

- **Use GitHub Issues** to report bugs, following the guidance in `CONTRIBUTING.md`
- **Use GitHub Issues or Discussions** to suggest new features or enhancements

Keeping normal bugs and feature requests public helps the community track progress and collaborate on fixes, while keeping security issues private helps protect users until a fix is available.

Loading