W-18839348 chore: missing required files for ospo compliance #6404
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
mshanemc
approved these changes
Jul 8, 2025
mshanemc
changed the title
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.
What does this PR do?This pull request includes updates to licensing, documentation, and security policies to improve clarity, compliance, and governance. Key changes include updating the license file, enhancing documentation in
README.md, introducing a detailed security policy, and adding a guide on licensing practices.Licensing Updates:
LICENSE.txtto reflect the current year (2025) and revised the copyright holder name to "Salesforce, Inc." instead of "Salesforce.com, inc.".how_to_license.mdfile detailing the BSD 3-Clause License, license header requirements, and guidelines for third-party dependencies.Documentation Enhancements:
README.mdby fixing grammatical inconsistencies (e.g., replacing "don’t" with "don't") and adding a new "Project Governance & Support" section with links to key governance documents likeLICENSE.txt,CODE_OF_CONDUCT.md, andSECURITY.md. [1] [2]Security Policy:
SECURITY.mdfile with a comprehensive guide on reporting vulnerabilities, preferred communication languages, and Salesforce's responsible disclosure policy.What issues does this PR fix or reference?
@W-18839348@