build: REUSE compliance (§4.3) + reuse lint CI gate#41
Merged
Conversation
Vault wasn't REUSE-compliant (no LICENSES/, no REUSE.toml; single SPDX tag only), yet CLAUDE.md §4.3/§5.2 make `reuse lint` passing non-negotiable. - LICENSES/GPL-3.0-or-later.txt — the only license Vault's files assert (deps are covered by cargo-deny, not REUSE). Copied from the compliant `construct/` sibling. - REUSE.toml — a single `path="**"` annotation supplying SPDX-FileCopyrightText + GPL-3.0-or-later in bulk (precedence=override, mirroring construct/), so no per-file copyright headers are needed and example SPDX in docs/prose isn't mis-parsed. Vault vendors no third-party files in-tree (rbw/cruxpass are gitignored), so one annotation covers everything. - CI: a `REUSE lint` job (pip install reuse → reuse lint), mirroring the Projects repo's job; `just reuse` + folded into `just ci`. `reuse lint` now passes: 77/77 files have copyright + license info, GPL-3.0-or-later only, 0 errors. Satisfies the §5.2 LICENSES/ posture requirement. No Rust changed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Brings Vault into REUSE compliance (https://reuse.software, Standard §4.3/§5.2) and enforces it in CI. Vault's own CLAUDE.md makes
reuse lintpassing non-negotiable, but the repo had noLICENSES/dir, noREUSE.toml, and no reuse CI job — files carried only a singleSPDX-License-Identifier(noSPDX-FileCopyrightText), soreuse lintwould fail.How (mirrors the compliant
construct/sibling + the Projects repo's CI)LICENSES/GPL-3.0-or-later.txt— the only license Vault's files assert (deps are handled bycargo deny, not REUSE).REUSE.toml— onepath="**"annotation supplyingSPDX-FileCopyrightText+GPL-3.0-or-laterin bulk (precedence=override, so example SPDX tags in docs/prose aren't mis-parsed and no per-file copyright headers are needed). Vault vendors no third-party files in-tree (rbw/cruxpass are gitignored), so one annotation covers the whole repo.REUSE lintjob (pip install reuse→reuse lint), mirroring the Projects repo's working job. Also addedjust reuseand folded it intojust ci.Verification
reuse lintpasses locally (uvx reuse lint): 77/77 files have copyright + license info,GPL-3.0-or-lateronly, 0 errors — "compliant with version 3.3 of the REUSE Specification". No Rust changed, so the existing gates are unaffected (fmt/buildconfirmed clean). The new CI job mirrors a known-working one and runs on this PR.Satisfies the §5.2
LICENSES/posture requirement (a pre-v0.1compliance item).🤖 Generated with Claude Code