Skip to content

What you can do

The MIT License lets you do all of this, without asking permission and without paying anything:

  • Use Core in personal, commercial and client projects.
  • Copy it, modify it and merge it with other code.
  • Publish and redistribute it, with or without changes, and sublicense it.
  • Sell copies.

The one thing it asks

One condition: the copyright notice and the license text must be included in all copies of Core, or in any substantial portion of it that you copy. The license sets no other conditions.

In practice:

  • With the npm package @taishods/core ships the LICENSE and NOTICE files. The package's CSS and JavaScript files also begin with a comment carrying the notice: TaishoDS — Copyright (c) 2026 Pablo Di Filippo. Licencia MIT (ver LICENSE).
  • With the CDN The files served from the CDN carry the same comment, so the notice travels with them.
  • If a tool strips comments When your own code is bundled or minified together with Core, some tools remove comments. The notice then no longer comes with that copy, so it is a good idea to include it some other way, for example through your project's own LICENSE file or a legal notices page.

No warranty

Core is provided “as is”, without warranty of any kind, express or implied. The license spells this out and names, without limiting itself to them, the warranties of merchantability, fitness for a particular purpose and noninfringement.

Put plainly: if something breaks, or using Core causes you harm, the authors and copyright holders are not liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise. You use Core at your own risk.

The brand is separate

The code is MIT; the name and the logo are not. A copyright license governs code, not a name or a visual identity. The trademark policy covers the names “Taisho” and “TaishoDS”, the logo, the graphic mark and the visual identity of the system and its documentation. Its rule in one line: you may say that a product uses Taisho; you may not say that it is Taisho.

Always allowed

  • Use Taisho in personal, commercial or client projects.
  • Fork it, modify it and publish your own version.
  • Say what a product is built with: “made with Taisho”, “based on Taisho” or “compatible with Taisho”.
  • Write tutorials, courses, articles and talks that use the name to refer to the system.
  • Use the name in honest comparisons with other design systems.

None of this requires asking permission.

Not allowed

  • Call your fork or derivative “Taisho”, or give it a name that could be confused with it, such as “Taisho UI” or “TaishoDS Pro”.
  • Use the name or the logo in a way that suggests a product is official, is endorsed by Taisho or came from this project.
  • Use the logo as the logo of your own product or service.
  • Register “Taisho”, or anything close enough to it, as a trademark, domain name, social media account or package, in any jurisdiction.

The full document, with the details and how to ask about a doubtful case, is the trademark policy (TRADEMARK.md), written in Spanish.

What comes from third parties

The package's NOTICE file names TaishoDS Core, its MIT license, the trademark exception and what the package includes from third parties, with the text of their license. You can read it inside the package published on npm.

  • The package ships no font files.
  • Core's JavaScript and the markup examples in the package include the paths of a few Lucide icons, distributed under that project's license (ISC; some derive from Feather, under the MIT license). The NOTICE carries that text in full.
  • The rest of the Lucide icons do not come with Core: they come from the lucide-static package, which is installed separately under that same license.
  • The taisho command uses two dependencies that npm installs along with the package, jiti and esbuild, both MIT-licensed according to their own packages.

Each of these is governed by its own license, not by TaishoDS's.

Contributions

By contributing, you agree that your contribution is published under the project's MIT License. The Taisho name and visual identity stay outside that license. This is set out in the contributing guide (CONTRIBUTING.md), written in Spanish.

Full license text

This is the content of the LICENSE file in the public repository, unchanged. It is the legal text, and it is in English.

LICENSE
MIT License

Copyright (c) 2026 Pablo Di Filippo

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

This page is a summary

This page is meant to help you get your bearings. It does not replace the license text or the trademark policy, which are the documents that count, and it is not legal advice. For a specific question about a use, it is wise to consult a professional.