Skip to content

Update SECURITY.md #29

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
jeffyanta merged 1 commit into from
Dec 12, 2025
Merged

Update SECURITY.md #29

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
8 changes: 4 additions & 4 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Security and Issue Disclosures

In the interest of protecting the security of our users and their funds, we ask
that if you discover any security vulnerabilities in the Code SDK, the clients,
that if you discover any security vulnerabilities in the Flipcash SDK, the clients,
the packages, the on-chain smart contracts, or the mobile app, you report them
using the following proceedure. Our security team will review your report. Your
cooperation in maintaining the security of our products is appreciated.
Expand All @@ -15,7 +15,7 @@ cooperation in maintaining the security of our products is appreciated.
1. [Incident Response Process](#process)

<a name="reporting"></a>
## Reporting security problems in the Code Program Library
## Reporting security problems in the OCP Server

Please use this [Report a Vulnerability](https://github.com/code-payments/ocp-server/security/advisories/new) link.
Provide a helpful title and detailed description of the problem.
Expand All @@ -35,9 +35,9 @@ fix the issue isn't required.
## Process

If you do not receive a response in the advisory, send an email to
security@getcode.com with the full URL of the advisory you have created. DO NOT
security@flipcash.com with the full URL of the advisory you have created. DO NOT
include attachments or provide detail sufficient for exploitation regarding the
security issue in this email. **Only provide such details in the advisory**.

If you do not receive a response from security@getcode.com please followup with
If you do not receive a response from security@flipcash.com please followup with
the team directly.