Skip to content

Latest commit

 

History

History
37 lines (23 loc) · 1.4 KB

Security.md

File metadata and controls

37 lines (23 loc) · 1.4 KB
Raw

Security

At stg-cli, we take security very seriously. We strive to ensure that our software is secure and that our users' data is protected.

Reporting Security Issues

If you discover a security vulnerability in stg-cli, please report it to us as soon as possible.

Please do not report security issues through the GitHub issue tracker or any other public forum.

Security Disclosure Policy

When reporting a security issue, please include as much detail as possible, including:

  • A description of the vulnerability.
  • Steps to reproduce the vulnerability.
  • Any potential impact of the vulnerability.
  • Any potential mitigations or workarounds for the vulnerability.

We will respond to your report as soon as possible and will work with you to resolve the issue.

Security Updates

We will release security updates for stg-cli as soon as possible after a vulnerability has been reported and confirmed. We will also notify users of the security update and provide instructions for updating their software.

Security Best Practices

Here are some security best practices to follow when using stg-cli:

  • Keep your software up to date.
  • Use strong and unique passwords.
  • Do not share your passwords with others.
  • Be cautious when clicking on links or downloading files.
  • Use a firewall and antivirus software.
  • Keep your operating system and other software up to date.

Thank you for helping us keep stg-cli secure.