Skip to content

Security: TheHypertextStudio/release-engineering

SECURITY.md

Security policy

This policy applies to every Hypertext Studio repository that does not have its own SECURITY.md.

Report a vulnerability

Report vulnerabilities privately through GitHub:

  1. Open the repository's Security tab.
  2. Select Report a vulnerability.
  3. Describe the problem, the affected version or commit, the steps that reproduce it, and the impact you expect.

Only you and the Studio can read the report. GitHub keeps the conversation, any fix and the published advisory together in one place.

Do not open a public issue, pull request or discussion about a vulnerability, and do not send details by email or social media. If Report a vulnerability is missing from a repository, report it privately through the organization's community repository instead and name the affected repository in the report.

What to expect

  • An acknowledgement within 3 business days.
  • An assessment within 10 business days: whether the report is confirmed, how severe it is, and the planned fix.
  • Updates in the report as the fix progresses, and a request for your review before an advisory is published.
  • Credit in the published advisory, unless you ask to stay anonymous.

Supported versions

Fixes go into the latest release of each product and into its main branch. A repository that supports older releases says so in its own security policy.

Scope

In scope: code in a public Studio repository and the builds and services published from it.

Out of scope: findings that need physical access to an unlocked device, social engineering of the Studio, denial-of-service testing, and reports produced only by automated scanners with no demonstrated impact.

Testing rules

Test only against accounts and data you own. Stop and report as soon as you can reach data that is not yours, and do not keep, change or share it. Good-faith research that follows this policy will not be pursued as a violation.

There aren't any published security advisories