chore: Add repository in package.json files #746
Merged
Conversation
This file contains 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
Add 'repository' field [1] to various package.json to create a link between release artifacts and corresponding code in the project's repository. This helps SBOM tools such as ORT [2] to create better SBOMs and reduces amount of code that needs to scanned and reviewed for license compliance. [1]: https://docs.npmjs.com/cli/v7/configuring-npm/package-json#repository [2]: https://github.com/oss-review-toolkit/ort Signed-off-by: Thomas Steenbergen <opensource@steenbe.nl>
The committers listed above are authorized under a signed CLA. |
✅ Deploy Preview for endearing-brigadeiros-63f9d0 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #746 +/- ##
=======================================
Coverage 57.34% 57.34%
=======================================
Files 46 46
Lines 1594 1594
=======================================
Hits 914 914
Misses 680 680 ☔ View full report in Codecov by Sentry. |
Psingle20
pushed a commit
to Psingle20/git-proxy
that referenced
this pull request
Nov 27, 2024
chore: Add repository in package.json files
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.
Add 'repository' field 1 to various package.json to create a link between release artifacts and corresponding code in the project's repository. This helps SBOM tools such as ORT 2 to create better SBOMs and reduces amount of code that needs to scanned and reviewed for license compliance.
Bit of context: I am working on generating high quality SBOM (e.g with licenses clarified till file level) for eventually all FINOS projects so they can be easier adopted and used in high compliance environments where SBOMs are or will be a "must-have". Don't want to burden maintainers with what's a FOSS consumer topic imo so when I see things causing SBOM issue you will see me shoot in PR to try to fix them.