Skip to content

Security: ChainForgee/ChainForge

Security

SECURITY.md

Security Policy

Supported Versions

The following versions of ChainForge are currently receiving security updates:

Version Supported
latest
< 1.0

Reporting a Vulnerability

ChainForge handles sensitive humanitarian aid data and recipient PII. We take security seriously.

Please do NOT report security vulnerabilities through public GitHub Issues.

How to Report

  1. Email: Send a detailed report to the maintainers via the contact information in the README.
  2. GitHub Private Disclosure: Use GitHub's private vulnerability reporting feature.

What to Include

  • A description of the vulnerability and its potential impact
  • Steps to reproduce the issue
  • Any proof-of-concept code (if applicable)
  • Suggested fix (if you have one)

Response Timeline

  • Acknowledgement: Within 48 hours
  • Initial assessment: Within 5 business days
  • Patch or mitigation: Within 30 days for critical issues

Scope

Areas of particular concern given ChainForge's use case:

  • Smart contract vulnerabilities on Stellar/Soroban
  • PII data exposure or leakage
  • Authentication and authorization bypasses
  • SQL/NoSQL injection
  • Insecure data transmission

Thank you for helping keep ChainForge and its users safe.

There aren't any published security advisories