Something went wrong. Try again.
Identities for entities did.bot
agent llm did
Something went wrong. Try again.
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647# cargo-about configuration. Run with `scripts/gen-notices.sh`, which writes# THIRD-PARTY-NOTICES.txt and the Dockerfile copies that into the image.## deny.toml decides which licence terms this dependency graph may carry.# This file answers the obligation those terms carry back: a permissive# licence asks that its notice travel with a binary redistribution, so the# notices have to be produced from the same graph the binary links.
# The graph is `didbot-serve` with `route53`, which is what the Dockerfile# builds -- see its `--features route53` comment for why that feature is# repeated on every build in it. One target, because the image is glibc# x86_64 Linux; `didbot-site-anim`'s wasm is served as a file from the site# and is not part of this binary.targets = ["x86_64-unknown-linux-gnu"]
# A test dependency compiles into test binaries, which this image never# carries. Build dependencies stay in: a proc macro's expansion becomes part# of the shipped object code, so its notice belongs beside the rest.ignore-dev-dependencies = trueignore-build-dependencies = false
# A crate whose licence cargo-about cannot determine is an error rather than# a silent omission -- the whole point of the file is that nothing linked# goes unnamed.accepted = [ "MIT", "Apache-2.0", "Apache-2.0 WITH LLVM-exception", "BSD-2-Clause", "BSD-3-Clause", "ISC", "Unicode-3.0", "Unlicense", "Zlib", "0BSD", "MIT-0", "BSL-1.0", "CDLA-Permissive-2.0", "MPL-2.0",]
# `ring`'s licence field is not SPDX-expressible; deny.toml clarifies it the# same way, against the same LICENSE file. cargo-about reads that file whole,# so the notice carries the grant verbatim.[ring]accepted = ["ISC", "MIT", "OpenSSL"]