• Prescan reported 11 files scanned and no unnamed holder; every holder it matched (Yuki Kishimoto, Rust Nostr Developers, Nostr Dev Kit Developers) is named in debian/copyright, so there was no file from that list to account for.
• LICENSE is MIT and identical to the License: MIT paragraph in debian/copyright; src/constant.rs:1-3, src/lib.rs:1-3 and src/prelude.rs:1-3 carry Copyright (c) 2022-2023 Yuki Kishimoto, Copyright (c) 2023-2025 Rust Nostr Developers, Distributed under the MIT software license, matching their stanza exactly.
• src/store.rs has no copyright header (which is why debcargo's hint has no stanza for it); it is covered by Files: * with the LICENSE's holder and licence, and it is the only remaining file class that needed checking.
• Complete tree walked (excluding .pc/ and debian/cargo-checksum.json): no LICENSE/COPYING/NOTICE/AUTHORS in any subdirectory, no vendored code, no generated, minified or binary file; the remaining upstream files are Cargo.toml, Cargo.toml.orig, Cargo.lock, .cargo_vcs_info.json, CHANGELOG.md and README.md, all crate metadata or text under the Files: * stanza.
• Copyright-format 6.9 checked: Files: * first with the more specific src stanza after it, and debian/* last, so the override order is correct and every path is matched; multi-line Files lists are valid.
• Patch 0001-relax-dependencies.patch changes only lru version = "0.18" to ">=0.16", and has full DEP-3 headers (Description, Forwarded: not-needed, Author, Last-Update); Debian ships lru 0.16.4, so the relaxation is needed and not a version-change fault.
• Build dependencies are satisfiable: librust-indexmap-2+default-dev is provided by librust-indexmap-dev 2.14.2-1 (>= 2.14), librust-lru-dev is 0.16.4-2 (>= 0.16), librust-tokio+sync-dev is provided by librust-tokio-dev 1.53.2-1 (>= 1.37); cargo:native, rustc:native and libstd-rust-dev come with dh-sequence-cargo -> dh-cargo -> cargo -> rustc.
• <!nocheck> on every Build-Depends-Arch entry is not a FTBFS-nocheck: for a dh-cargo library package the compile happens in the test step (sub test in Buildsystem/cargo.pm defaults to cargo build), which dh skips at compat 13 under nocheck (debhelper tool), and cargo prepare-debian --link-from-system only symlinks whatever is in /usr/share/cargo/registry, so dh_auto_configure succeeds without those crates.
• dh_auto_test -- test --all || true in debian/rules is the documented test_is_broken handling, not an accident: Cargo.toml.orig has nostr-gossip-test-suite.workspace = true, the published Cargo.toml has an empty [dev-dependencies], and src/store.rs:445-447 imports nostr_gossip_test_suite, so cargo test cannot build; the maintainers replace it with debian/tests/smoke-test (565 lines, builds a downstream crate offline against /usr/share/cargo/registry and checks NIP-65/NIP-17/hints/most-received/All/filtering/fetch-status/LRU eviction).
• debian/tests/control declares the smoke test's extra needs (librust-nostr-0.45+rand-dev, +os-rng-dev, tokio macros/rt, rustc >= 1.85.0, dh-cargo for cargo) which the script really uses, and Architecture: !riscv64 on the plain-package stanza; the flaky/allow-stderr restrictions come from test_is_broken and only make the test non-blocking, they do not stop it running.
• Standards-Version 4.7.4 has the same first two components as Policy 4.7.4.1, so it is current; source format is 3.0 (quilt); changelog version 0.45.1-1, distribution unstable, dated Sat, 14 Nov 2026 (a correct date); Vcs-Git/Vcs-Browser use the debcargo-conf subdirectory form; X-Cargo-Crate/-Version match the crate.
• uscan found the packaged version as the newest upstream release (upstream 0.45.1, packaged 0.45.1).

• librust-nostr-0.45+std-dev and librust-nostr-gossip-0.45-dev, needed both to build and to depend on, are neither in the archive lists nor in the NEW queue snapshot of 2026-11-14; they are presumably part of the same batch of nostr uploads, but their existence could not be confirmed.
• The autopkgtest was not run (the package cannot be built or tested here); whether the smoke test's fixtures still match the stored relay-list and status semantics is taken as passing.

None.