Skip to content

Security: Acrossed-com/acrossed

Security

SECURITY.md

Security policy

We take the security of Acrossed and the applications it protects very seriously. Thank you for taking the time to disclose responsibly.

Reporting a vulnerability

Please do not open a public GitHub issue for security problems.

Instead, email security@acrossed.com with:

  1. A description of the issue and the impact you believe it has.
  2. Steps to reproduce, ideally with a minimal proof of concept.
  3. The affected component (engine, dashboard, sdk-node, sdk-python, sdk-go).
  4. Your name or handle if you'd like to be credited in the advisory.

We will acknowledge receipt within 2 business days and aim to provide a status update within 5 business days.

If the vulnerability is confirmed we will:

  • Issue a fix in a private branch.
  • Coordinate a release date with you.
  • Credit you in the published GitHub Security Advisory (unless you'd prefer to remain anonymous).

Supported versions

Version Supported
1.x
< 1.0 (preview)

Only the latest minor of the current major receives security fixes.

Hall of fame

Researchers who have responsibly disclosed issues to us will be listed here once advisories are published.

Our security commitments

  • Every release is signed.
  • All HTTP traffic between the SDKs and the engine is HMAC-SHA256 signed.
  • The engine is stateless and never persists request bodies.
  • Production secrets, infrastructure topology, and operational tooling for acrossed.com are intentionally not part of this repository.

There aren’t any published security advisories