Skip to main content
Report suspected vulnerabilities, exposed credentials, package compromise or unsafe documentation through the official BRIK64 contact path published on BRIK64.com. Do not include secrets in public issues.

Useful Security Reports

  • Affected package, command or page.
  • Reproduction steps.
  • Observed output.
  • Expected behavior.
  • Whether source, generated artifacts or update manifests are involved.
  • Whether the issue affects installation, updates, SDK examples, MCP/API behavior or agent instructions.

Documentation Security

Docs issues can be security-relevant when they:
  • publish unsafe installation instructions;
  • expose private infrastructure;
  • suggest uploading source where local artifacts should be used;
  • overstate release artifact hardening;
  • instruct agents to write outside managed sections.

Sensitive Reports

If a report contains credentials, tokens, private paths or sensitive account details, stop and move it to the approved private reporting path.