Get in touch

Contact & report an issue

Public technical questions are best answered in public so the next person with the same question can find the answer. For anything else, the contact form on sparkgoldentech.com/contact routes directly into our message inbox — we see every submission. Pick the channel that fits your situation:

Bug or feature request

Open a public issue on GitHub. Searchable, version-tracked, and the next person with the same problem will find the answer. Include a minimal reproduction, your traceless-style version, and the framework you're using.

Open a GitHub issue

Security vulnerability

Don't open a public issue. Open a private GitHub Security Advisory, or email us with Security advisory in the subject. Initial response within 72 hours; full process in the Security Policy.

Open a security advisory

Everything else

Press, partnerships, conduct reports, "we'd like to use this at our company", or "I just wanted to say thanks". The contact form on sparkgoldentech.com is the recommended path — submissions land in our database and we reply from there. Email is also fine.

Open the contact form

Direct email also works: team@sparkgoldentech.com. The contact form just gives us a structured place to track every incoming request alongside our other communications.

What to include in a bug report

Issues that get triaged and fixed fastest tend to share a few ingredients. None are mandatory; all of them help.

  • A minimal reproduction. Smallest possible input that triggers the bug. Trim away unrelated styling, unrelated tokens, unrelated framework code. A small public repository or sandbox link works best.
  • What you expected vs what happened. One line each is fine.
  • Versions. traceless-style version, framework version (Next, Vite, etc.), Node version, @swc/core version if you're using the SWC parser.
  • The actual error. Full text, including the diagnostic code (e.g., TLS0301) if it came from the validator.

Response expectations

  • GitHub issues: typically triaged within a week. The issue tracker shows current activity.
  • Security email: initial response within 72 hours, usually faster. Full SLA in the Security Policy.
  • General email: a couple of business days. If you don't hear back within a week, it almost certainly went to spam — resend with a different subject line.

Looking for documentation?

Most "how do I do X" questions are answered in the docs. Quick anchors:

Mailing address

For physical correspondence (we'd be surprised, but it happens):

Spark Golden Tech
Tevragh Zeina, District R, No. 0457
Nouakchott, Mauritania