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

docs: update SECURITY.md with audit commit + fix small typos #263

Merged
merged 2 commits into from
Jan 28, 2025
Merged
Changes from all commits
Commits
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
12 changes: 6 additions & 6 deletions SECURITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,14 +6,14 @@ Please see [Releases](https://github.com/Layr-Labs/eigenda-proxy/releases)

## Audit reports

Audit reports are published in the `docs/audits` folder: https://github.com/Layr-Labs/eigenda-proxy/main/docs/audits
Audit reports are published in the [docs/audits](https://github.com/Layr-Labs/eigenda-proxy/tree/main/docs/audits) folder.

| Date | Report Link |
| ------- | ----------- |
| 202501 | [pdf](https://github.com/Layr-Labs/eigenda-proxy/blob/main/docs/audits/Sigma_Prime_EigenDA_Proxy_Security_Assessment_Report.pdf) |
| Date | Release (Commit) Audited | Report Link | Findings Addressed in Release |
| ------ | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- |
| 202501 | v1.6.1 (9e1b746) | [pdf](https://github.com/Layr-Labs/eigenda-proxy/blob/main/docs/audits/Sigma_Prime_EigenDA_Proxy_Security_Assessment_Report.pdf) | v1.6.2 |

## Reporting a Vulnerability

**Please do not file a public ticket** mentioning the vulnerability.
**Please do not file a public ticket** mentioning a vulnerability.

Please report security vulnerabilities to [email protected] with the all the relavent details included in the email.
Please report security vulnerabilities to [email protected] with all the relavent details included in the email.
Loading