Repository navigation
Security and conduct contacts at klv.ai, not klavi.ai - #1
Merged
Merged
Conversation
klavi.ai is another company's domain: reports sent to security@klavi.ai or conduct@klavi.ai would have gone to them. security@klv.ai is the contact security.txt already publishes. Docs only, no release.
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.
SECURITY.md and CODE_OF_CONDUCT.md sent reports to security@klavi.ai and conduct@klavi.ai. klavi.ai belongs to another company, so a private vulnerability report would have gone to them.
Both now say klv.ai. security@klv.ai is the address security.txt already publishes.
This is docs only, so there's no version bump. hatchling's sdist would carry the new text from the next release on.