Add organization-wide SECURITY.md - #13
Merged
Merged
Conversation
Grantim
approved these changes
Sep 8, 2026
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
2 participants
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.
Adds an organization-wide security policy. A
SECURITY.mdin this repository is shown on the Security tab of every MeshInspector repository that has none of its own, so this covers MeshLib and the OpenCTM fork at once.Prompted by the S9S Security Research report of 2026-09-07 (OpenCTM heap overflows, fixed in MeshInspector/OpenCTM#2 and #3, shipped via MeshLib#6800), whose authors noted that there was no
SECURITY.mdand no private reporting channel and had to fall back to the org profile email.The policy names two private channels, GitHub private vulnerability reporting and support@meshinspector.com, sets a three-business-day acknowledgement target, states that fixes ship with the next MeshLib release and are public on merge unless a disclosure date is agreed, and promises credit by default.
Before merging, enable private vulnerability reporting on the repositories the policy points to, otherwise the first channel does not exist: