Open Source Licenses
Last Updated: August 29, 2026
1. What this page covers
The ArkCloud Health platform is built on open source software. This page acknowledges that software and records the licences it is used under.
It is about software we consume. For how our own software is licensed to you, and for the rules on using our name and marks, see Licensing.
2. Licence breakdown
Counted from the installed dependency tree on the date above. The platform declares 80 direct dependencies, which resolve together with their own dependencies to roughly 1,150 installed packages. Every direct dependency is under a permissive licence:
MIT
62 direct dependencies
Permissive. Requires that the copyright notice and licence text travel with the software.
Includes: React, Next.js, Radix UI, TanStack Query, Prisma tooling clients, Stripe, Twilio, Zod, Tailwind CSS
Apache-2.0
14 direct dependencies
Permissive, with an express patent grant and a requirement to state significant changes.
Includes: AWS SDK, OpenTelemetry, Prisma Client, TypeScript, SheetJS
ISC
3 direct dependencies
Permissive; functionally equivalent to MIT with simplified wording.
Includes: Auth.js (next-auth), Lucide icons
BSD-3-Clause
1 direct dependency
Permissive, and additionally forbids using the author's name to endorse derived work.
Includes: bcryptjs
No copyleft in the shipped product
No direct dependency is under the GPL, the LGPL, the AGPL or any other reciprocal licence, and none is under a source-available licence that restricts commercial or hosted use. That is a deliberate constraint on what we take on, not an accident of the current dependency set - it is what allows the platform to be offered as a hosted service without your organisation inheriting a source-disclosure obligation.
3. The full attribution notice
The complete notice - every package, its version, its copyright holders and the verbatim text of its licence - is generated from the dependency tree of each release rather than maintained by hand, so that it is correct for the build you are actually running.
Request a copy for a specific release by writing to [email protected] with the version. Customers under a signed agreement can also obtain it through their account contact as part of a security or procurement review.
4. Our obligations, and yours
We retain all copyright notices, licence text and attribution required by each licence, we do not represent open source components as our own work, and we do not use a project’s name or marks to imply that it endorses this product.
Access to the platform gives you a licence to use the service under the Terms of Service. It does not grant you any right in the underlying open source components beyond what their own licences give you directly, and it does not grant you a licence to our proprietary code.
5. Reporting an attribution problem
If you maintain a project you believe is used here without correct attribution, or you find an error in a licence statement on this page, write to [email protected]. We treat attribution defects as defects: tell us what is wrong and we will correct it and say when the correction shipped.
- The project name and repository URL.
- Where you believe it is used in our platform.
- What the notice says today and what it should say.
The counts on this page are a snapshot taken on the Last Updated date and will drift as dependencies change between releases. The generated attribution notice for a given release, not this summary, is the authoritative record for that release.