Is your feature request related to a problem? Please describe.
KerasTuner doesn't currently have a security policy defining how users or security researchers can privately disclose vulnerabilities they've found.
Describe the solution you'd like
KerasTuner should have a security policy. This would be best done in its own SECURITY.md file. These files are given special treatment by GitHub: the policy is displayed in the project's public security dashboard, and a new "issue type" is created that redirects users to the policy if they've found a vulnerability.
Is your feature request related to a problem? Please describe. KerasTuner doesn't currently have a security policy defining how users or security researchers can privately disclose vulnerabilities they've found.
Describe the solution you'd like KerasTuner should have a security policy. This would be best done in its own SECURITY.md file. These files are given special treatment by GitHub: the policy is displayed in the project's public security dashboard, and a new "issue type" is created that redirects users to the policy if they've found a vulnerability.
Additional context Other keras-team projects have adopted security policies (see https://github.com/keras-team/keras/pull/18762, https://github.com/keras-team/keras-cv/pull/2142, https://github.com/keras-team/tf-keras/pull/683).