Security

Security should be easy to verify

Teams should be able to verify publisher identity, expected behavior, and support paths before adopting any tool. This page summarizes how Betascribe handles that baseline.

User verification checklist

  • Confirm publisher identity and linked repository.
  • Review recent release notes and issue response quality.
  • Read extension behavior and permissions before install.
  • Report suspicious extensions directly in the Marketplace when needed.

Betascribe commitments

  • No obfuscated logic in released extension packages.
  • Clear documentation for what each extension does.
  • Public support and security contact channels.
  • Plain-language disclosure when AI features are introduced.
  • Human approval remains explicit for critical workflow actions.

Responsible disclosure

Email security@betascribe.com with reproduction steps, impact summary, and logs. We triage quickly and communicate status until resolution.

Open support options