Legal
Terms of Use
Last updated: May 2, 2026
Two things, one site
These terms cover two related but distinct things:
- The traceless-style library — the npm package, source code on GitHub, and the published extensions for VS Code and browser DevTools. Governed by the MIT license. You can use the library commercially, fork it, embed it in proprietary products, modify it — the MIT terms are the full story for the code itself.
- The documentation website at
traceless-style.dev— the static pages, prose, screenshots, and search index. Free to read, link to, and quote with attribution. The following sections cover acceptable use of the website.
Acceptable use of the website
Read it, link to it, share it, copy snippets to teach others, embed examples in your own posts. We want the docs to be useful.
Don't scrape it aggressively, run automated load against it, attempt to circumvent Cloudflare's rate limiting, or try to deface the deployed site. If you want a local copy of the docs to ship with your offline tool, clone the repository; that's what it's for.
Content we link to
The docs reference external services (npm, GitHub, the VS Code Marketplace, Open VSX, etc.) and quote third-party libraries by name (Tailwind, StyleX, Vanilla Extract, ...). We don't endorse those services or libraries beyond what's stated; mentions are editorial. If you find a quote of someone else's work that you think is misrepresented, email us and we'll correct it.
The library, again
The traceless-style npm package and every artifact under the @sparkgoldentech organization is licensed under MIT. The full license text is in every release tarball and in the repository's LICENSE file. The MIT license includes its own warranty disclaimer; the disclaimer below restates it for the website but doesn't modify the library's license.
No warranty, no liability
The website and the library are provided as is and as available. To the maximum extent allowed by applicable law, Spark Golden Tech and the maintainers disclaim all warranties — express, implied, or statutory — including merchantability, fitness for a particular purpose, accuracy, and non-infringement.
We won't be liable for any indirect, incidental, special, consequential, or punitive damages arising out of your use of the website or the library, including lost profits, lost data, or business interruption, even if we knew such damages were possible. The total liability cap, if a court ever finds us liable for something, is the amount you paid us — which, for a free open-source project, is zero.
You're responsible for what you build
The library generates atomic CSS at build time from your input. It includes a strict-by-default WCAG 2.1 AA contrast validator and value-injection guards, but ultimate responsibility for the accessibility, security, performance, and correctness of the applications you ship using it rests with you. Run your own QA; do your own pen testing; verify accessibility with real users.
Bug reports and pull requests
Contributions to the library are welcome under the same MIT terms; by submitting a pull request you agree your contribution is licensed under the project's MIT license. The project's CONTRIBUTING.md covers the workflow.
If you find a security vulnerability, please do not open a public issue. See the Security Policy for the responsible-disclosure process.
Account-free
There are no user accounts on this site. Nothing to sign up for, nothing to log into, no plan tiers, no payment. If you ever land on a "Sign in" or "Upgrade" page on traceless-style.dev, it's not us — the URL has been intercepted somehow and you should treat it as suspicious.
Governing law
Spark Golden Tech operates from the Islamic Republic of Mauritania. These terms are governed by the laws of Mauritania, without regard to its conflict-of-laws provisions. Any dispute arising from these terms or use of the website that can't be resolved by direct discussion will be brought before the competent courts in Nouakchott.
If these terms change
We'll update this page and the "Last updated" date at the top. Material changes will also appear in the project's git history on the website repository, which is the public source of truth for every revision. Continued use after a change constitutes acceptance.
Contact
Questions about these terms go to [email protected]. Or see all the ways to reach us.