Composer.json: add link to security policy #131
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
This is a new feature available since Composer 2.6.0, which was released a little while ago. When this key is added, it will also show a link to the security policy on Packagist. The security policy itself has been added to the organisation `.github` repository and can be accessed via the `security/policy` link on each repo. Refs: * https://github.com/composer/composer/releases/tag/2.6.0 * composer/composer#11271 * composer/packagist#1353
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 is a new feature available since Composer 2.6.0, which was released a little while ago.
When this key is added, it will also show a link to the security policy on Packagist.
The security policy itself has been added to the organisation
.githubrepository and can be accessed via thesecurity/policylink on each repo.Refs:
Re-creation of #129, but now against the correct branch.