Skip to content

Security: boredpolymath/Branchlock

SECURITY.md

Security Policy

System and Scope

Branchlock is a static, browser-based prototype for reviewing GitHub Actions security findings. This policy covers the files in this repository, especially the deployable application in workflow-guardian-prototype/dist/.

The deployed v1 service may read public GitHub workflow files through GitHub's public API. It does not accept credentials, cookies, OAuth tokens, or GitHub App installations; it does not modify repositories or persist reports server-side.

Threat Model and Trust Boundaries

Repository names and browser-local preferences are treated as untrusted input. Findings displayed by the prototype are bundled sample data. Browser storage is a local convenience feature, not a secure data store.

Security Invariants

  • Never request, store, expose, or transmit access tokens, credentials, cookies, or secrets.
  • Reject supplied authorization headers and private repositories rather than attempting authenticated access.
  • Do not log repository identifiers, request bodies, workflow contents, report contents, or IP addresses.
  • Never write to a user’s repository or execute repository content.
  • Keep report history and preferences local to the browser.
  • Escape user-controlled values before rendering them into the page.

Reportable Findings

Please report vulnerabilities that could cause credential exposure, cross-site scripting, unsafe handling of user input, unauthorized network transmission, unintended repository mutation, or compromise of the offline application shell.

Out of Scope

Sample finding data and simulated scan behavior are product-demo content, not claims of live GitHub analysis. Vulnerabilities in third-party browsers, extensions, or static-hosting infrastructure are outside this repository’s scope.

Reporting a Vulnerability

Please do not open a public issue for a suspected vulnerability. Report it privately to the repository owner through GitHub’s security advisory reporting flow, with reproduction steps and impact. We will acknowledge the report and coordinate a fix before public disclosure.

There aren't any published security advisories