License & Third-Party Attribution
This page exists so you can adopt TruePPM Community Edition with confidence. It tells you the license you are agreeing to, why no proprietary code is hiding in the open-source repository, and how the dependency licenses are mechanically verified on every build — not just promised.
The authoritative text is the LICENSE file at the repository root. If anything on this page ever disagrees with that file, the file wins.
Where the license text travels
Section titled “Where the license text travels”Apache 2.0 §4(a) requires anyone who receives a distribution to receive a copy of the License with it. The root LICENSE covers the repository, but it does not follow an artifact that leaves the repository on its own — so each separately-distributed package carries its own identical copy. The three PyPI packages also carry a copy of the root NOTICE (the project’s own copyright line) for the same reason — Apache 2.0 does not strictly require it, but a standalone package with no copyright statement anywhere in it is an attribution gap. trueppm-api and trueppm-mcp additionally carry a package-scoped NOTICES + licenses/*.txt (their own copyleft-dependency disclosures — see “certifi” and “psycopg” above), packaged the same way via each package’s license-files:
| Package | How it is distributed | Carries LICENSE | Carries NOTICE | Carries third-party NOTICES/licenses/ |
|---|---|---|---|---|
trueppm-scheduler | PyPI wheel / sdist | yes | yes | n/a (no copyleft dependency) |
trueppm-mcp | PyPI wheel / sdist | yes | yes | yes (certifi only) |
trueppm-api | PyPI wheel / sdist (in addition to the Docker image) | yes | yes | yes (psycopg + certifi) |
wasm-scheduler | publishable crate (the compiled .wasm is not bundled into the web app) | yes | — | — |
mobile | app binary installed on a device | yes | — | — |
helm | packaged chart tarball | yes | — | — |
web and website are not separately distributed — they ship inside the docs site, which carries the root LICENSE. The API Docker image also carries the root LICENSE and NOTICES (the API’s own Dockerfile copies both from the repository root, which is its build context), independently of the trueppm-api PyPI package above. The MCP Docker image’s build context is scoped to packages/mcp/ alone, so it cannot reach the repository root at all — it instead carries trueppm-mcp’s own NOTICES/licenses/ the same way it carries LICENSE/NOTICE: packaged into the installed wheel’s dist-info/licenses/ by license-files, which the Dockerfile’s COPY --from=builder /venv /venv brings into the final image.
A CI gate (lint:package-licenses) enforces this. It also fails if a new directory appears under packages/ without being classified as distributed or bundled, so the list cannot quietly go stale.
What “Community Edition” includes
Section titled “What “Community Edition” includes”Everything a project manager and their team need to run a program is in the Apache 2.0 Community Edition: the scheduling engine (CPM, Monte Carlo), the schedule view, Kanban boards and sprints, real-time collaboration, offline sync, 5-role RBAC, baseline comparison and in-app baseline capture, time tracking with a weekly timesheet, basic single sign-on (OIDC/OAuth login against your own identity provider), MS Project import/export, the REST and WebSocket API, a read-only MCP server, an operational audit log, notifications, read-only share links, the integrations (Jira import and a personal Jira source, GitLab/GitHub task links, Git-event automation, outbound webhooks), and the Helm chart. Every one of them is in the open core, not behind the enterprise boundary.
The enterprise boundary
Section titled “The enterprise boundary”TruePPM is open-core. Governance and portfolio features (org identity governance — SAML/SCIM/LDAP directory sync and enforced org-wide SSO — portfolio dashboards, cross-program resource leveling, approval workflows, the org-wide integration hub) are proprietary and live in a separate repository (trueppm-enterprise). Basic single sign-on (self-service OIDC/OAuth login against your own identity provider) belongs to the Apache 2.0 Community Edition, not the enterprise layer.
The dependency is strictly one-way — enterprise code depends on the core, never the reverse. The Community Edition never imports, links, or ships any proprietary code. Cloning and running the open-source repository pulls in zero enterprise code. This separation is an architectural rule, not a packaging convenience: it is enforced in the codebase and documented in the contributing guide.
Dependency licenses are enforced in CI, not just promised
Section titled “Dependency licenses are enforced in CI, not just promised”You do not have to take our word that the dependency tree is clean. Every merge request and every push to main runs automated license audits. A dependency carrying an incompatible license fails the pipeline and cannot merge.
-
Python dependencies (
license:check:py, viapip-licenses) — a strict allow-list applied to the whole dependency closure (scripts/ci/check-python-licenses.sh, also run for the MCP server). Only permissive licenses (MIT, BSD, Apache-2.0, ISC, PSF and similar) pass; any other license string, including GPL, AGPL, SSPL, BUSL and other copyleft or source-available licenses, fails the build until a maintainer reviews it. The few weak-copyleft packages below are named as per-package exceptions, so a new package carrying the same license still fails. LGPL is permitted under its library-linking (dynamic-linking) exemption: LGPL code is linked at runtime, not statically incorporated into TruePPM’s own source, so it does not affect the Apache 2.0 license of TruePPM’s code. MPL-2.0 is also permitted — it is file-level copyleft (it reaches modifications to the licensed files themselves, not software that merely depends on them) and is satisfied by a notice plus unmodified-source availability rather than a relinking obligation; seecertifibelow. -
JavaScript / npm dependencies (
license:check:web, vialicense-checker --production --onlyAllow) — a strict allowlist applied to the shipped dependency set. Only these licenses are permitted; anything else fails the build:MIT Apache-2.0 BSD-2-Clause BSD-3-Clause ISC 0BSDCC0-1.0 CC-BY-3.0 CC-BY-4.0 Python-2.0 Unlicense WTFPL BlueOak-1.0.0The audit runs against
--productiondependencies only, because license obligations attach to what is distributed, not to build- and test-time tooling that never reaches a user.³
The license boundary is therefore mechanically enforced on every change — a copyleft dependency cannot silently enter the codebase between reviews.
³ Because the npm audit is scoped to --production, a devDependency is deliberately outside the allowlist above — it is evaluated on whether it is distributed, and dev tooling distributes nothing. The accessibility test tooling @axe-core/playwright (and its axe-core engine) is a case worth flagging for reviewers: it is MPL-2.0, a file-level copyleft license that is not on the permitted list — but it runs only in CI’s end-to-end accessibility checks and is never bundled into the Community Edition web artifact, so it carries no obligation on the shipped product and is permitted. The rule of thumb: the allowlist governs what we ship; a devDependency is judged on distribution, and it distributes nothing.
Principal third-party dependencies
Section titled “Principal third-party dependencies”The tables below attribute the major direct dependencies by layer. They are not exhaustive; the complete, authoritative set is whatever the CI license jobs verify on each build. You can regenerate full transitive reports yourself with pip-licenses (Python) and npx license-checker (npm).
Backend (Python)
Section titled “Backend (Python)”| Library | Purpose | License |
|---|---|---|
| Django | Web framework | BSD-3-Clause |
| Django REST Framework | REST API | BSD-3-Clause |
| Django Channels / channels-redis | WebSockets | BSD-3-Clause |
| Celery | Task queue | BSD-3-Clause |
| django-allauth | Authentication | MIT |
| djangorestframework-simplejwt | JWT auth | MIT |
| django-simple-history | Audit history | BSD-3-Clause |
| drf-spectacular | OpenAPI schema | BSD-3-Clause |
| django-environ | Configuration | MIT |
| uvicorn | ASGI server | BSD-3-Clause |
| cryptography | Cryptographic primitives | Apache-2.0 OR BSD-3-Clause |
| defusedxml | Safe XML parsing | PSF (Python Software Foundation License) |
| psycopg (v3) | PostgreSQL driver | LGPL-3.0 ¹ |
| certifi | CA certificate bundle (transitive via requests/httpx) | MPL-2.0 ⁴ |
| redis-py | Valkey / Redis client | MIT |
| networkx | Graph algorithms (CPM engine) | BSD-3-Clause |
| numpy | Numerical computing (Monte Carlo) | BSD-3-Clause |
| trueppm-scheduler | TruePPM’s own scheduling engine ² | Apache-2.0 |
¹ psycopg is LGPL-3.0 — the one copyleft dependency, and it is permitted deliberately. It is dynamically linked, not statically incorporated, so under the LGPL’s library-linking exemption it does not affect the licensing of TruePPM’s own code. This is the honest detail behind “LGPL is permitted” above. Redistributing a frozen image (a self-hosted bundle that vendors the psycopg binary, rather than pip-installing it at build time) carries the LGPL’s standard relinking obligation (§4): you must let recipients replace the library. The stock TruePPM images install psycopg from PyPI as a normal, replaceable dependency, so this obligation is satisfied without any extra step — it only becomes your responsibility if you build a deliberately frozen/vendored derivative. The production API image installs the psycopg[c] build, which dynamically links the C extension against the system libpq so OS-level libpq/OpenSSL security upgrades flow through to the driver — a security-posture choice, not the relink lever: the §4 obligation above is over psycopg itself and is met identically by the precompiled psycopg[binary] wheel used for local development (both are replaceable site-packages wheels; libpq is permissively licensed). The full LGPL-3.0 (and the GPL-3.0 it incorporates) text and the relink statement travel with every distributed copy — they are in the repository’s NOTICES file and licenses/ directory, and are copied into the API Docker image, the primary redistribution vehicle.
² trueppm-scheduler is TruePPM’s own CPM/Monte Carlo engine, published as a standalone Apache 2.0 package on PyPI.
⁴ certifi is MPL-2.0. It is not a direct dependency of trueppm-api or trueppm-mcp — it arrives transitively via requests (the django-allauth[socialaccount] OpenID Connect provider, and the OpenTelemetry OTLP HTTP exporter) in the API, and via httpx in the MCP server. We redistribute it unmodified, and MPL-2.0’s obligations attach only to modifications of the licensed files themselves, so no source-disclosure step is triggered — only the notice-preservation requirement, which the repository’s NOTICES file and licenses/MPL-2.0.txt satisfy. It is deliberately left unpinned, since certifi ships a rolling CA bundle and a pin would eventually distribute stale root certificates. It travels with every distributed copy: the API and MCP Docker images (copied from the repository root into the API image; packaged into the MCP wheel’s dist-info/licenses/ for the MCP image), and the trueppm-api / trueppm-mcp PyPI sdists and wheels (via each package’s own NOTICES and licenses/MPL-2.0.txt, declared in license-files).
Frontend (TypeScript / React)
Section titled “Frontend (TypeScript / React)”| Library | Purpose | License |
|---|---|---|
| React / react-dom | UI framework | MIT |
| react-router | Routing | MIT |
| @tanstack/react-query | Server-state management | MIT |
| @tanstack/react-virtual | List virtualization | MIT |
| @dnd-kit (core, sortable, utilities) | Drag and drop | MIT |
| zustand | Client-state management | MIT |
| recharts | Charts | MIT |
| axios | HTTP client | MIT |
| jspdf | PDF export | MIT |
| html-to-image | Image export | MIT |
Infrastructure
Section titled “Infrastructure”| Component | Purpose | License |
|---|---|---|
| PostgreSQL | Database | PostgreSQL License (permissive, BSD-style) |
| Valkey | Cache & queue (Redis-compatible) | BSD-3-Clause |
A note on Visiban
Section titled “A note on Visiban”You may notice references to Visiban elsewhere in these docs. Visiban is a sibling project from the same maintainer — a Kanban platform, also Apache 2.0. TruePPM was built clean-room: it contains no Visiban code, imports, or dependencies (per ADR-0013). The relationship is shared authorship and shared values, not a code dependency.