Report suspected vulnerabilities privately through GitHub private vulnerability reporting. If that form is not available, contact ERPC support from the ERPC Web Dashboard and ask for a private channel. Do not open a public issue for a suspected vulnerability, an exposed credential or an exploitable detail.
Include enough to reproduce the issue safely: package and version (crates.io
solana-stream-sdk, npm @validators-dao/solana-stream-sdk,
@validators-dao/solana-shreds-client, @validators-dao/solana-entry-decoder, or a
sample client), runtime and operating system, the impact, and a minimal reproduction.
Redact API keys, X_TOKEN values, endpoint URLs that carry a key (?api-key=…),
wallet files and key material from the report. Never send a real secret as proof.
This policy covers the SDK packages, the sample clients in client/ and temp-release/
(the templates slv bot init installs), the repository tooling, and the dependencies as
this repository integrates them. Issues in ERPC endpoints or other services go to their
operators; describe the SDK side of the interaction.
Security fixes go to the latest published version of each package.
scripts/run-gitleaks.shscans the whole history for credentials andscripts/check-oss-hygiene.shchecks tracked files for non-public hosts, internal references and key material (CI, every pull request).cargo deny check(deny.toml) andpnpm auditcheck dependencies for advisories, licenses and sources (CI, every pull request).deny.tomllists each accepted advisory with its reason.- The SDK, the sample clients in
client/and the TypeScript templates intemp-release/keep credentials out of logs: endpoints and RPC errors are logged without the credentials, path or query of their URLs (solana_stream_sdk::redact,src/utils/redact.ts). The Rust templates intemp-release/get this when they move to SDK 4.0.