The REUSE.toml file at the repository root carries an override annotation that reassigns the copyright holder of a wide set of files to a single individual under a stale year, while every Ruby source file, every shell script, and every workflow in the same tree carries Copyright (c) 2024-2026 Zerocracy.
The relevant block is REUSE.toml:1-32. Lines 5-30 declare one annotation block whose path glob covers **.md, **.json, **.txt, Gemfile.lock, README.md, renovate.json, and a long list of binary patterns. Lines 30-32 then set precedence = "override" with SPDX-FileCopyrightText = "Copyright (c) 2025 Yegor Bugayenko" and SPDX-License-Identifier = "MIT". By contrast, every file with an inline SPDX header in the same tree credits Zerocracy: entry.sh:2, Rakefile:3, lib/say.rb:3, judges/say-hello/say-hello.rb:3, judges/say-hello/hello-said.yml:1, test/test__helper.rb:3, test/test_say.rb:3, test/test_entry.rb:3, every .github/workflows/*.yml, .rubocop.yml:1, .rultor.yml:1, and LICENSE.txt. The REUSE.toml itself was tagged as Copyright (c) 2025 Yegor Bugayenko on lines 1-2 of the file.
Two problems follow. First, precedence = "override" instructs the REUSE tooling to ignore any inline SPDX header on a matching file, so the build's REUSE compliance report attributes README.md, Gemfile.lock, renovate.json, and every .md/.json/.txt artifact to a different copyright holder than the source files alongside them. Second, the year is frozen at 2025 while the rest of the repository has already been bumped to 2024-2026, so the attribution is not just inconsistent in holder but also stale in span.
Fix: change the SPDX-FileCopyrightText on REUSE.toml:31 to Copyright (c) 2024-2026 Zerocracy, and update the file header on REUSE.toml:1 to match. If the intent was genuinely to keep README.md/Gemfile.lock under a different holder than the source tree, the path list should be narrowed to only those files and the discrepancy should be documented.
The
REUSE.tomlfile at the repository root carries an override annotation that reassigns the copyright holder of a wide set of files to a single individual under a stale year, while every Ruby source file, every shell script, and every workflow in the same tree carriesCopyright (c) 2024-2026 Zerocracy.The relevant block is
REUSE.toml:1-32. Lines 5-30 declare one annotation block whosepathglob covers**.md,**.json,**.txt,Gemfile.lock,README.md,renovate.json, and a long list of binary patterns. Lines 30-32 then setprecedence = "override"withSPDX-FileCopyrightText = "Copyright (c) 2025 Yegor Bugayenko"andSPDX-License-Identifier = "MIT". By contrast, every file with an inline SPDX header in the same tree creditsZerocracy:entry.sh:2,Rakefile:3,lib/say.rb:3,judges/say-hello/say-hello.rb:3,judges/say-hello/hello-said.yml:1,test/test__helper.rb:3,test/test_say.rb:3,test/test_entry.rb:3, every.github/workflows/*.yml,.rubocop.yml:1,.rultor.yml:1, andLICENSE.txt. TheREUSE.tomlitself was tagged asCopyright (c) 2025 Yegor Bugayenkoon lines 1-2 of the file.Two problems follow. First,
precedence = "override"instructs the REUSE tooling to ignore any inline SPDX header on a matching file, so the build's REUSE compliance report attributesREADME.md,Gemfile.lock,renovate.json, and every.md/.json/.txtartifact to a different copyright holder than the source files alongside them. Second, the year is frozen at 2025 while the rest of the repository has already been bumped to2024-2026, so the attribution is not just inconsistent in holder but also stale in span.Fix: change the
SPDX-FileCopyrightTextonREUSE.toml:31toCopyright (c) 2024-2026 Zerocracy, and update the file header onREUSE.toml:1to match. If the intent was genuinely to keepREADME.md/Gemfile.lockunder a different holder than the source tree, thepathlist should be narrowed to only those files and the discrepancy should be documented.