Repository navigation
Add REUSE compliance and SBoM - #110
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <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
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.
This PR makes the repository compliant with the REUSE specification. Each file now has an SPDX header or a
.licensesidecar. Copyright lines come from the Git history and follow renames. Each contributor appears with the year of their first change to the file. Lockfiles and.tool-versionsgetNONEand CC0-1.0. The logo licensing is the same as in oidcc.CI now checks REUSE compliance on PRs and on
main. On tags, CI also generates an SPDX SBoM, attests it and attaches it to the GitHub release, the same as in oidcc. The README now has a REUSE status badge. The badge needs the repository to be registered at api.reuse.software.