program: add solana-security-txt#360
Merged
2501babe merged 1 commit intosolana-program:mainfrom Apr 13, 2026
Merged
Conversation
This was referenced Apr 13, 2026
joncinque
approved these changes
Apr 13, 2026
| // Optional Fields | ||
| preferred_languages: "en", | ||
| source_code: "https://github.com/solana-program/stake/tree/main/program", | ||
| source_release: concat!("program@v", env!("CARGO_PKG_VERSION")), |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
i remember someone last month on discord confused about how to figure out what bpf stake they were supposed to verify against so i thought itd be nice to add this. doesnt help us for v5 but will next time!
in the spl repos we never filled out
source_releasebecause it doesnt really work with the github actions release flow, but i think this is a nice solution. no new commit needed, automatically the correct thing for releases we actually do. it will be wrong for ad hoc builds obviously. but i think this is fine since the whole point is for people to godeployed build -> github tag -> self-verificationand we only deploy tagged releasesthe project url is less than ideal but seems like the least bad thing, solana.com has a few pages on staking and stake accounts but nothing that actually mentions the stake program