Licensing

visx License and Safety: MIT Terms and Safe Installs

Before you ship charts in a client project or a paid product, two questions come up: are you allowed to use visx this way, and are the files you're installing safe? Here's a plain-English answer to both. It's general information, not legal advice. Read our disclaimer for the details.

visx uses the MIT license

visx is published by Airbnb under the MIT license, one of the most permissive open-source licenses. In practice it lets you:

  • Use visx in personal, commercial, internal and client projects.
  • Modify the code and ship your changes.
  • Bundle it into closed-source products.
  • Charge for the product you build with it.

What you have to do

The main condition is attribution: the copyright notice and license text must be included "in all copies or substantial portions" of the software. For most web apps, that's already handled, because the license file ships inside each package in node_modules. Many bundlers can also collect third-party licenses into one file for you. If you copy visx source code directly into your own repository, keep the original license header or file with it.

The license also says the software is provided "as is", without warranty. You're responsible for testing it in your product.

Names and trademarks

The MIT license covers the code, not brand names. You can say your product "uses visx", but don't imply that Airbnb endorses your product. visx.app is an independent site and is not affiliated with Airbnb. Our about page explains who we are.

The license for files you download here

The visx React starter kit and the individual chart components on visx.app are our own code, also released under the MIT license. Each ZIP includes a LICENSE file. They import visx from npm rather than copying its source.

Safe installation habits

Most supply-chain problems in the JavaScript ecosystem come from look-alike package names or compromised dependencies, not from well-known libraries. A few habits go a long way:

  1. Check the scope. Official packages are published under @visx/. Be wary of unscoped names that merely contain "visx".
  2. Install from the official registry. Use npm, Yarn or pnpm with their default registry rather than downloading tarballs from unknown sites.
  3. Commit your lockfile. package-lock.json, yarn.lock or pnpm-lock.yaml pins exact versions so builds can't change underneath you.
  4. Run an audit. npm audit flags known vulnerabilities in your dependency tree.
  5. Read before you run. Open any downloaded project's package.json and check its scripts before running npm install.

What's inside our downloads

  • Only readable source files: .tsx, .ts, .json, .csv, .md and one index.html.
  • No executables, installers, minified bundles or postinstall scripts.
  • Dependencies listed in package.json come straight from the official npm registry.

You can open every file in a text editor before installing anything. If something in a download looks wrong, tell us and we'll investigate quickly.