Skip to main content

License audit: 2026-10-08

The original Go/npm policy gate passes with three metadata exceptions, but license clearance for the whole distributed product is not established. A commercial product or permissive open core appears feasible, subject to closing the issues below. This is a technical source-tree audit; contributor rights and the actual distribution require review.

Update after owner decisions​

The owner selected Apache-2.0 core, copyright 2026 Dmitry Lakhvich, and support-only sales initially, deferring proprietary module boundaries. The current project-authored code now has the root LICENSE grant; own npm/Python metadata and SDK license files are aligned. Third-party terms remain unchanged. Earlier restrictions on commercial use of the core were superseded by the final Apache choice. Future enterprise needs explicit paths and terms; no automatic two-year opening is promised.

This resolves the own-license selection/metadata finding, not release clearance for Python environments, images, model weights, assets, ownership or shipped notices. The table below preserves observations from the original pre-license snapshot.

Original findings​

SurfaceObservationRequired action
Own codeNo root LICENSE; root package.json says ISC; Node SDK/dashboard/site lack license; Python SDK lacks project.licenseApprove MIT/Apache/proprietary scope and align LICENSE/metadata
EnterpriseOn-prem/PKI/license implementation is in the shared source tree; no explicit legal carve-outDefine paid files, separate terms and independent core build
Go/npmOriginal scanner: 117 module entries + 5 npm summaries; 3 missing-metadata findings with live exceptionsExtended scanner discovers modules, tests, replacements and individual npm versions
PythonSDK uses openai/httpx plus hatchling/test extras; classifier Dockerfile installs torch/transformers/uvicorn/fastapi/sentencepiece/numpy/accelerate without pinsExact transitive inventory and licenses for release environments
Redis serverCompose/Helm use redis:7-alpineSelect image digest and review actual version/license
GrafanaCompose uses grafana/grafana:11.0.0Separate AGPL component: review source/notices and modifications for SaaS/redistribution
ModelsLlama-3-70B, Mistral-7B-Instruct, BAAI/bge, Xenova/bge, intfloat/e5 in configsPin weight revisions, retain licenses/AUP and define on-prem bundle contents
PricingNOTICE-litellm.txt is preserved; upstream has an enterprise carve-outRetain MIT notice for the imported catalog; do not copy upstream enterprise code
Containers/OSAlpine, distroless, PostgreSQL/pgvector, TEI, vLLM and other servicesSBOM and notice/source obligations for shipped images
Assets/ownershipSVG/docs/data are outside Go/npm metadata checksEstablish provenance and contributor/relicensing rights

Redis: 7.2 and earlier are BSD; 7.4–7.8 use RSALv2/SSPLv1; 8+ also offers AGPLv3: official licensing table. Grafana OSS uses AGPL: version 11 license. This does not automatically require opening the entire gateway: review component separation, modifications, network use and actual distribution.

The configured Llama 3 (not Llama 3.1) has separate Community License terms: Meta Llama 3 LICENSE. Model API terms and output/dataset rights are also not established by the client SDK license.

Changes implemented​

The existing scripts/quality/license_check.py scanner now uses Git discovery for modules/lockfiles, includes Go test deps and actual replacement directories, fails closed for npm v1 missing metadata and invalid SPDX syntax, records full JSON findings/errors/exceptions, hashes binary assets and provides a separate blocking release mode. Generic as-is/PUBLIC DOMAIN markers and license-text truncation were removed. Text inventory is no longer called a notice bundle.

Policy and procedure in standards/license-compliance.md are referenced from AGENTS.md, the Go security skill and quality classifier. Both MIT and Apache-2.0 core models are supported as candidates with separately licensed proprietary enterprise components. Own license grants and dependency versions were not changed; human approval was not fabricated.

Limits are recorded in every JSON. Generate fresh machine evidence using make licenses-report; --release blocks until the owner's licensing decision and scoped human evidence exist. Quality manifests and execution results are provided in the handoff; a green dependency policy gate is not release clearance.

Python environment sample​

A fresh SDK/test environment resolved certifi==2026.7.22 with MPL-2.0 metadata. The new optional --python-inventory accepts pip inspect JSON and flags this under the conservative permissive-only policy. This is a snapshot of the audit environment, not a lock for every deployment or the classifier container.

MPL allows combining covered files with proprietary code; shipping those covered files still carries its notice/source obligations. It does not automatically require opening the whole SDK or enterprise product: certifi license, Mozilla MPL FAQ. Do not remove TLS verification or blindly replace trust roots to silence the gate. Review distribution obligations or an approved packaging choice separately.

Verification fixes​

The documentation uses repository paths as code references for files outside the Docusaurus docs plugin. Two pre-existing Starlark tests used the production watchdog while checking shared-program concurrency and caller cancellation. Their test-only watchdog budget is now explicitly longer so it cannot mask the intended invariant under race instrumentation/whole-suite contention. Assertions and dedicated watchdog enforcement tests remain in place; runtime defaults are unchanged.

The shadow-comparison integration fixture now sets created_at explicitly inside the host-clock report window. This avoids a Docker VM/database clock skew excluding newly inserted rows before org-isolation/cost assertions run. Production queries and assertions remain unchanged.