Skip to content

docs(license): correct the apexcharts MIT boundary and record the OEM gap - #3240

Merged
rubenvdlinde merged 1 commit into
developmentfrom
fix/apexcharts-license-note-oem
Aug 31, 2026
Merged

docs(license): correct the apexcharts MIT boundary and record the OEM gap#3240
rubenvdlinde merged 1 commit into
developmentfrom
fix/apexcharts-license-note-oem

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Two corrections to the note added earlier today, one of them material.

1. The MIT boundary is 5.1.0, not 6.0.0

Measured per version:

version licence
4.7.0 MIT
5.0.0 MIT ← last MIT release
5.1.0 SEE LICENSE IN LICENSE
5.2.0 ApexCharts License
6.0.0, 7.0.0 SEE LICENSE IN LICENSE

The earlier note said 6.0.0 and understated how far back the proprietary line starts. Anything above 5.0.0 is licensed.

2. The revenue threshold is not the nearest trigger

The licence separately requires a paid OEM / Redistribution licence for:

embedding ApexCharts into a product or platform used by other people

waived only if:

your app simply renders static charts and users cannot configure or interact with them

Both chart views set the charts to be interactive:

// src/views/register/RegisterDetail.vue:401  and  src/views/schema/SchemaDetails.vue:306
toolbar: { show: true },
zoom:    { enabled: true },

and this app is distributed to third parties through the Nextcloud App Store. So the exemption does not apply on its face.

The Community tier also lists "sublicensing under different terms" as not allowed, which is worth a look given this app ships under EUPL-1.2.

What this does and does not settle

Conduction being below USD 2M settles the Community tier for its own use. It does not settle redistribution. The override text now says that explicitly, so it reads as a recorded open question rather than as a clearance.

Not changing the dependency here — that is a licence decision (stay on 7 with an OEM licence, or drop to 5.0.0, the last MIT release). Raising it for the maintainers.

… gap

Two corrections to the note added earlier today.

1. The MIT boundary is 5.1.0, not 6.0.0. Measured per version:
   4.7.0 MIT, 5.0.0 MIT, 5.1.0 'SEE LICENSE IN LICENSE',
   5.2.0 'ApexCharts License', 6.0.0 and 7.0.0 likewise. So the last MIT
   release is 5.0.0, and the earlier note understated how far back the
   proprietary line starts.

2. The revenue threshold is not the nearest trigger. The licence also
   requires a paid OEM/Redistribution licence for 'embedding ApexCharts into
   a product or platform used by other people', waived only if the app
   'simply renders static charts and users cannot configure or interact with
   them'. RegisterDetail.vue and SchemaDetails.vue both set
   toolbar: { show: true } and zoom: { enabled: true }, and this app is
   distributed to third parties through the Nextcloud App Store, so the
   exemption does not apply on its face.

Conduction being below USD 2M settles the Community tier for its OWN use. It
does not settle redistribution. The note now says so rather than reading as a
clearance.
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/openregister @ c16d705

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-specs
test-l10n
test-l10n-parity
format
check-schema-l10n
check-l10n-js
composer ✅ 174/174
npm ✅ 543/543
app:check-code ⏭️
info.xml
REUSE
PHPUnit ⏭️ not run for this diff — no file in this diff matches the code globs, and none carries a source extension — the heavy tier has nothing to decide about it.
Newman
Playwright ⏭️ deferred — runs on the promotion into beta/main, not on a pull request into development
Hydra gates

Quality workflow — 2026-08-31 17:38 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde
rubenvdlinde merged commit 5c5a734 into development Aug 31, 2026
47 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant