LEGAL · LICENSES
Licenses and third-party notices, mapped to the software you use.
Review approved license records, open-source notices, attribution requirements, and applicable source or redistribution information for ZoikoSuite software and distributed components.
LICENSE SCOPE & DEFINITIONS
Preventing the most common licensing confusion before you enter the registry
Open-source software
Distributed under a license that qualifies as open source under its terms; OSI approval shown only when verified.
Source-available
Source may be viewable, but the license may impose restrictions inconsistent with open-source definitions — never grouped under Open Source.
Public domain / dedication
Rights status depends on the specific instrument and jurisdictional treatment.
Proprietary / commercial
Third-party component governed by negotiated or vendor terms — public record may disclose category without exposing the contract.
Fonts / icons / media
Non-code assets can carry separate attribution, redistribution, or embedding terms.
Data / documentation
Datasets, schemas, examples, or reference text may use separate terms.
Model / AI asset
Model weights, artifacts, or evaluation data may carry model-specific terms — no assumption of open-source status.
Zoiko-authored SDK/sample code
Code published by Zoiko may use a specific developer license separate from the platform Terms of Service.
PUBLIC LICENSE REGISTRY
The primary product-proof surface — real governed registry, approved public records only
Search Rule
Specification
Exact identifiers
Searching MIT, Apache-2.0, MPL-2.0, or another identifier matches the stored approved identifier/expression — never a guessed family.
Custom licenses
Searchable by approved title and internal/public identifier — never assigned a fake SPDX ID.
Deprecated identifiers
Historical records display the release-era record plus current mapping if approved — historical legal evidence is never silently rewritten.
LICENSE DETAIL VIEW — STRUCTURAL EXAMPLE
Summary never replaces the operative text
COMPONENT IDENTITY
[ Public component name, version, supplier/publisher, package ecosystem ]
LICENSE IDENTITY
[ Full license name; SPDX identifier/expression where applicable; OSI status only when verified ]
OPERATIVE TEXT
[ Link or embedded verified license text; text hash/version where maintained ]
COPYRIGHT / ATTRIBUTION
[ Required copyright notices and attribution wording ]
NOTICE REQUIREMENTS
[ Whether NOTICE/attribution file content must accompany distribution ]
SOURCE / COPYLEFT
[ Whether a source offer or reciprocal obligation is triggered for this distribution ]
APPLICABILITY
[ Product; release; module; platform; distribution form; deployment mode ]
EVIDENCE & REVIEW
[ Last reviewed date; evidence source class; Legal approval state; public record version ]
OPEN-SOURCE NOTICES & ATTRIBUTION
Reproducible from the registry — never a hand-edited page
Notice Block
Requirement
Bundle identity
Product/release/distribution, generated-at timestamp, notice version, scope statement.
Ordering
Stable deterministic order (e.g. component A-Z) to support diffing and audit.
Downloads
HTML and plain text required; PDF optional; machine-readable export where approved.
No-sales gate
Notices and legally required source/attribution information never require a demo request or marketing consent.
THIRD-PARTY COMMERCIAL & RESTRICTED COMPONENTS
Not every dependency can or should publish contractual terms
Scenario
Public Behavior
Internal Behavior
Commercial SDK with attribution requirement
Component identity, attribution, applicable distribution, and "commercial terms on file."
Contract owner, renewal, usage restrictions, evidence, expiry, release gate.
Restricted license terms
"License details restricted" only if accurate, plus an enterprise licensing contact.
Access-controlled contract record and approval history.
Expired/terminated right
Never published as active or shipped in new artifacts unless approved transition rights apply.
Release blocker, replacement plan, renewal/termination evidence.
SOURCE CODE, COPYLEFT & WRITTEN-OFFER FULFILLMENT
Only for records where verified obligations require it — never implies all ZoikoSuite source is open source
Element
Required Behavior
Eligibility
Captures product/release/distribution and component/license context — never requires proof of purchase unless the license legally permits and Legal approves.
Request CTA
Request corresponding source/licensing materials — no sales CTA in the primary path.
Fulfillment states
Received → validation → awaiting details → materials prepared → fulfilled → rejected with legal basis → duplicate → closed.
Written-offer expiry
If a legally relevant period applies, fulfillment stays available for the full required period.
FONTS, ICONS, MEDIA, DOCUMENTATION, DATA & MODEL LICENSES
Disclosed separately from code licensing
Fonts
Family/version, license, embedding/distribution conditions, required attribution, product surfaces.
Icons / illustrations / media
Asset library, creator/provider, license, permitted use, attribution, modifications.
Data / datasets
Dataset/provider, license or terms, permitted use, redistribution, attribution, update/version.
AI models / model assets
Provider/model version, model license/terms, weights/source status, usage boundaries — never a generic "open model" label.
SDKS, APIS, SAMPLE CODE & DEVELOPER DISTRIBUTION
SDK rights are never assumed to include third-party redistribution
Item
Required Treatment
SDK package
Exact package/repository, version, developer license, redistribution rights, dependencies/notices.
Sample code
Separates code license from documentation copyright; includes a copyable license header if required.
Container image
Notices tied to image digest/tag and base-image/component obligations.
Partner redistribution
SDK rights are never assumed to allow redistribution of bundled third-party materials — routed to partner/license review where needed.
DISTRIBUTION & DEPLOYMENT NOTICE MATRIX
Notices mapped to how the software actually ships
| Distribution | License/Notice Expectation | Design Note |
|---|---|---|
| Hosted SaaS | Public notices where attribution or network-use obligations apply; internal inventory remains complete. | Not all internal server dependencies require public attribution. |
| Web client | Client-delivered JS/WASM/assets mapped to the web release notice. | Avoid exposing source-map or internal path data. |
| Desktop/mobile app | Legal notices shipped in-app and/or with the package where required. | Offline access expected. |
| Agent / connector / CLI | Notice file shipped with installer/binary/archive; linked to public registry by version. | Exact artifact/version required. |
| Single-tenant / on-prem | Customer package includes applicable notice bundle and source-offer instructions. | Customer-specific add-ons handled separately. |
MACHINE-READABLE NOTICES & SBOM BRIDGE
A controlled bridge — not a claim that a public SBOM exists
| Surface | Specification |
|---|---|
| Public machine-readable notice | Optional SPDX JSON/tag-value export generated from the public subset of verified records. |
| Restricted SBOM request | Enterprise customers/security reviewers request richer SBOM/provenance evidence through the Trust/Security procurement flow. |
| Security separation | No vulnerability/CVE status, private repository path, dependency path, infrastructure mapping, or signing secret appears on this page. |
LICENSE COMPATIBILITY, EXCEPTIONS & RELEASE GATES
Unknown or conflicting licenses fail closed — public omission never equals approval
| Internal State | Required Handling | Public Behavior |
|---|---|---|
| Approved | Legal/engineering determination complete; obligations mapped; evidence current. | Record may publish if marked public. |
| Review required | Scanner or engineer identifies new/changed license or use context. | Not published as approved; shipment gated if unresolved. |
| Unknown license | No reliable license metadata/text. | Fail closed — "Unknown - blocked." Public omission does not equal approval. |
| License conflict | Incompatible terms or obligations with intended distribution. | Release blocker until replaced, isolated, relicensed, or resolved. |
HISTORICAL NOTICES, SUPERCEDED RELEASES & CHANGES
Every release notice has a stable, immutable identifier
Element
Requirement
Release archive
Browse supported and historical notice bundles by product, version, distribution, and release date.
Superseded state
Old records remain available where useful but clearly marked superseded.
Change log
New component; removed component; version changed; license changed; attribution changed; source-offer changed; correction.
LICENSING QUESTIONS, SOURCE REQUESTS & CORRECTIONS
No sales routing by default
ENTERPRISE PROCUREMENT & ASSURANCE HANDOFF
Routine diligence answered here — higher-sensitivity evidence goes through Trust/Security
Current open-source notices
Downloadable release notice bundle.
No handoff required.
Machine-readable licensing inventory
Approved public SPDX-aligned export.
Restricted export if more detail is needed.
Full SBOM
Availability/status explained without promising it.
Trust/Security evidence workflow under appropriate controls.
Commercial third-party terms
Publicly states that restricted third-party rights are governed separately.
Legal/procurement response — vendor contract is never exposed.
FREQUENTLY ASKED