Wrong license check blocks installation. One of the most popular and simple packages, rgbcolor, which is used in most packages out there as referenced, is blocked because it says it doesn’t have MIT license, but thats not true. It does!
Because of this almost no packages can be installed, for example like jspdf.
LOG:
Installation blocked because the following packages use disallowed licenses: - rgbcolor@1.0.1: MIT OR SEE LICENSE IN FEEL-FREE.md (trailing tokens in license expression) Retool only permits packages whose dependency tree uses these licenses: MIT, BSD-2-Clause, BSD-3-Clause, ISC, Apache-2.0, 0BSD, Unlicense, CC0-1.0, Zlib, X11.
On Retool Cloud, installing npm packages for a custom component library (e.g., jspdf) is blocked because a transitive dependency, rgbcolor@1.0.1, declares its license as 'MIT OR SEE LICENSE IN FEEL-FREE.md' — an SPDX expression with 'trailing tokens' that fails to parse against Retool's license allowlist, even though the package is effectively MIT-licensed. This is reported as a false-positive that prevents many popular packages from installing.
AI Response
Custom component libraries run a license check that only permits dependency trees using an allowlist of SPDX identifiers (MIT, BSD-2-Clause, BSD-3-Clause, ISC, Apache-2.0, 0BSD, Unlicense, CC0-1.0, Zlib, X11). The block here stems from the non-standard license string on rgbcolor@1.0.1, which the parser rejects because of the 'trailing tokens' after 'MIT'. As a practical workaround, consider pinning or overriding the offending transitive dependency to a version with a clean SPDX license field (e.g., via a package.json 'overrides'/'resolutions' entry pointing to a fork or patched version), or using an alternative package whose full dependency tree resolves to allowlisted licenses. No public forum topic or documentation page was found that directly corroborates this specific SPDX parsing behavior or offers an official fix, so a dedicated bug report on the Community forum with the exact log would help surface a targeted resolution.
Sources
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a , , or . Or by marking this post as the "Solution"! Let us know if you have any feedback here.
Thanks for reporting this here and submitting a breakage report.
We have identified the issue and are in the process of shipping a fix. We appreciate the report!
, 
, or 
. Or by marking this post as the "Solution"! Let us know if you have any feedback 