Skip to content

Security: daniel-code/deeplake

Security

SECURITY.md

Security

Reporting a bug in Deep Lake

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them to security@activeloop.ai.

Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:

  • Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
  • Full paths of source file(s) related to the manifestation of the issue
  • The location of the affected source code (tag/branch/commit or direct URL)
  • Any special configuration required to reproduce the issue
  • Step-by-step instructions to reproduce the issue
  • Proof-of-concept or exploit code (if possible)
  • Impact of the issue, including how an attacker might exploit the issue

You should receive a response within 72 hours. If for some reason you do not, please follow up via email to ensure we received your original message.

After the initial reply to your report, the security team will endeavor to keep you informed of the progress being made towards a fix and full announcement, and may ask for additional information or guidance surrounding the reported issue.

Reporting a bug in a third party module

Security bugs in third party modules should be reported to their respective maintainers.

There aren’t any published security advisories