Contact

DriftCSS does not have a telephone number, postal office, or sales inbox. Support is public and asynchronous on GitHub, which is the same place the source lives.

Bugs, questions, and feature requests: open an issue at github.com/MarioCadenas/driftcss/issues. Include the plugin version (@driftcss/vite@alpha), Vite and React versions, a reduced CSS + className snippet, and whether strict or purge is on. Search existing issues first.

Security reports: prefer GitHub's private vulnerability reporting on that repository if it is enabled; otherwise open a private security advisory from the repo Security tab. Do not file a public issue that includes exploit details for a supply-chain or extractor bug until there is a fix.

Documentation on this site: if a page is wrong or an agent cannot parse a machine file (openapi.json, llms.txt, MCP card), file an issue and link the URL. The docs Worker is part of the same repository (apps/driftcss-landing).

X: @Drift_CSS for product updates. Bugs still belong on GitHub issues, not replies.

npm packages: @driftcss/vite, @driftcss/core, driftcss (CLI), eslint-plugin-driftcss. Package pages on npm link back to the GitHub repo; use GitHub, not npm reviews, for technical contact.

There is no chat widget and no SLA. Alpha software: replies happen when the maintainer can read the queue. See also About and Privacy.