Skip to content

Add internal-use and bug bounty exclusion note to README #446

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
anupsdf merged 1 commit into from
Oct 16, 2026
Merged

Add internal-use and bug bounty exclusion note to README #446

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
14 changes: 14 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
Loading