From 6638f92a95c4db5bec2e5178515d1dfc904e9bcb Mon Sep 17 00:00:00 2001 From: Jay Geng Date: Fri, 16 Oct 2026 11:59:38 -0400 Subject: [PATCH] Add internal-use and bug bounty exclusion note to README --- README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/README.md b/README.md index d7fa0fde..e02cfd7c 100644 --- a/README.md +++ b/README.md @@ -7,6 +7,20 @@ feeding them traffic (and/or invoking their internal load-generation testing subsystem). It is a second-generation tool, replacing the functionality of an older and now-retired package called Stellar Core commander (SCC). +> [!IMPORTANT] +> ## ⚠️ Internal testing tool—for use on Stellar's test infrastructure only +> +> This repository is maintained by the Stellar Development Foundation as an +> integration testing tool for stellar-core. It is intended to run inside +> SDF's internal test infrastructure, against short-lived test networks. It is +> not intended to be served, deployed as a service, or exposed to external +> networks or users, and is not supported for any other use. +> +> **Security researchers:** this repository is excluded from the +> [Stellar bug bounty program](https://hackerone.com/stellar). Vulnerabilities +> in Supercluster itself are out of scope. Vulnerabilities in stellar-core +> should be reported against stellar-core. + ## Why a new tool SSC Has the following differences from SCC: