fix(licence): pin apexcharts to its MIT range — 1.9.0+ is revenue-gated - #565
Open
rubenvdlinde wants to merge 1 commit into
Open
fix(licence): pin apexcharts to its MIT range — 1.9.0+ is revenue-gated#565rubenvdlinde wants to merge 1 commit into
rubenvdlinde wants to merge 1 commit into
Conversation
nc-vue is where this dependency is declared for the whole fleet, so this is the
root of the exposure.
ApexCharts changed licence. vue3-apexcharts <= 1.8.0 is MIT; >= 1.9.0 is a
DUAL, REVENUE-GATED licence — free only for individuals, non-profits, educators
and businesses under $2M USD annual revenue, commercial licence required above
that. The newer releases do not even carry a valid SPDX id ("see LICENSE in
LICENSE"), which is how CI noticed.
The `^1.7.0` range here resolves to 1.11.1, and every consumer inherits it.
openconnector's `quality / License (npm)` gate has been failing on exactly that
(openconnector#1108 pins it downstream; this fixes the source):
Disallowed license: vue3-apexcharts (1.11.1) uses
'Custom: https://apexcharts.com/media/vue-apexcharts.png'
Narrows the range to `>=1.7.0 <1.9.0` and adds overrides for the transitive
vue3 wrapper. openconnector's lock, regenerated with the same pin, resolves
vue3-apexcharts 1.8.0 and apexcharts 4.7.0 — both verified MIT against the npm
registry.
Consumers on `^1.7.0` today (openregister, larpingapp, petstore) still resolve
MIT versions, so they are not broken — but they can drift on any lock refresh.
Fixing it here is what stops that.
If the newer versions are wanted, that is a commercial-licence decision, not a
dependency bump.
This was referenced Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
nc-vue is where this dependency is declared for the whole fleet, so this is the root of the exposure.
ApexCharts changed licence.
vue3-apexcharts≤ 1.8.0 is MIT; ≥ 1.9.0 is a dual, revenue-gated licence — free only for individuals, non-profits, educators and businesses under $2M USD annual revenue; commercial licence required above that. The newer releases do not carry a valid SPDX id ("see LICENSE in LICENSE"), which is how CI noticed.The
^1.7.0range here resolves to 1.11.1, and every consumer inherits it. openconnector'squality / License (npm)gate has been failing on exactly that:openconnector#1108 pins it downstream; this fixes the source.
The change
Narrows the range to
>=1.7.0 <1.9.0and adds overrides for the transitive vue3 wrapper. Three lines, formatting preserved.openconnector's lock, regenerated with the same pin, resolves
vue3-apexcharts@1.8.0andapexcharts@4.7.0— both verified MIT against the npm registry, not assumed.Consumers
openregister,larpingapp,petstoresit on the same^1.7.0and currently still resolve MIT versions — so they are not broken, but they can drift on any lock refresh. Fixing it here is what stops that.Not a licence override
I deliberately did not add a
.license-overrides.jsonentry anywhere. That would have turned CI green while leaving the revenue-gated dependency in the shipped tree — the opposite of what the gate exists for.If the newer versions are actually wanted, that is a commercial-licence decision, not a dependency bump.
🤖 Generated with Claude Code