Skip to content

Security: seifip/yugaku

Security

SECURITY.md

Security Policy

Supported versions

Security fixes are applied to the latest revision of the default branch. No released version currently has a long-term support commitment.

Reporting a vulnerability

Do not open a public issue for vulnerabilities involving code execution, credential or personal-data exposure, browser automation boundaries, or permission bypasses. Use GitHub's private vulnerability reporting for this repository. If private reporting is unavailable, contact the maintainer through the email listed on the seifip GitHub profile without including exploit details in the first message.

Include affected versions, impact, reproduction steps, and any proposed remediation. Please allow a reasonable remediation window before public disclosure.

Security boundaries

  • Yugaku reads only the screen region a user selects and performs OCR locally through Apple Vision.
  • Migaku authentication remains inside the user's dedicated Chrome profile.
  • Yugaku must not read Chrome credentials, cookies, tokens, or extension storage.
  • Card and known-status mutations require an explicit user action.
  • Chrome DevTools exposes a powerful local control surface. Do not bind its debugging port to a public interface or reuse a sensitive daily-browsing profile.

There aren't any published security advisories