An application built with m0 (`m0 build --release`)

This directory was written beside the application's binary by `m0 build
--release`, and an `m0 image` copies it into the image with the rest of
`dist/`. The application is its author's, under its author's terms. This
notice describes the parts of the artifact that are not, and why their
licence texts travel with it: an artifact redistributed without them breaks
the terms below.

--------------------------------------------------------------------------------

mojo-http and lightbug_http — compiled into the binary

The binary was compiled from the mojo-http framework's source, which the m0
wheel carries, and that source includes a hard fork of lightbug_http.

    mojo-http      Copyright (c) 2025-2026 Wm Talcott
                   MIT License; see LICENSE.mojo-http.txt
    lightbug_http  Copyright (c) 2023 Valentin Erokhin
                   MIT License; see LICENSE.lightbug_http.txt

The MIT License requires its notice to travel with copies "or substantial
portions" of the software, and a compiled binary is such a copy.

--------------------------------------------------------------------------------

Mojo runtime libraries — the shared libraries beside the binary
Copyright Modular Inc

The binary loads the Mojo runtime from its own directory. `m0 build
--release` copied in every library the binary links from the toolchain it
was built with. On macOS these are always

    libKGENCompilerRTShared.dylib
    libMSupportGlobals.dylib
    libAsyncRTRuntimeGlobals.dylib

and on Linux the same three as .so files. Their sources are licensed under
the Apache License 2.0 with LLVM Exceptions in modular/modular; see
LICENSE.mojo-runtime.txt. The wheel Modular distributes the built files in
(mojo-compiler) carries no licence file, and its metadata names Modular's
MAX License instead. Read that way, the MAX License of 2026-10-21 permits
redistributing them as part of an application with material functionality
of its own (its section 1.2), provided a human-readable copy of its terms
goes with them; LICENSE.max.txt is that copy. Its section 1.5 keeps the
Apache terms in control of any component they cover.

A binary that uses MAX (`max.algorithm`'s `parallelize`, a GPU's
`DeviceContext`) also links libAsyncRTMojoBindings, and on a GPU path
loads libMGPRT. Neither has open source: they are MAX's, under the MAX
License alone (LICENSE.max.txt).

MODIFICATION NOTICE (Apache License 2.0, section 4(b)): each runtime
library here has been changed. On macOS its Mach-O install name and rpath
were rewritten so the set resolves beside itself rather than in the
directory it was built in, and it was re-signed ad hoc, because arm64 macOS
invalidates a code signature on any Mach-O edit. On Linux its DT_RUNPATH
was rewritten to $ORIGIN for the same reason. No source was changed and no
code was recompiled; the executable code is byte for byte as Modular built
it.

--------------------------------------------------------------------------------

What is not here

No Python is in the artifact, and m0 adds no other code to it. A library the
application opens at run time, such as libsqlite3 or libpq for the storage
packages, is the system's, installed beside the artifact rather than
shipped in it.
