Remove redundant line from SECURITY.txt #9048
Merged
Conversation
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
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 0944b61:
|
dcousens
changed the title
dcousens
force-pushed
the
no-recommendations
branch
from
e3fbe8d to
0944b61
Compare
Merged
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.
The Keystone team isn't making any attestations about Keystone 6's suitability for any particular purpose or industry, and to be honest, that will always need be evaluated by the developers and teams writing their own software.
This line in our SECURITY.txt is unhelpful in that respect, as even if we knew everything about a particular project, and even if we had multiple publicly-disclosed penetration tests, it would still be the downstream development teams who need to make any and all assessments, in line with our MIT license text.