chore: missing required files for ospo compliance (#68)

* chore: missing required files for ospo compliance

* Update how_to_license.md

* Update SECURITY.md

* Update CODEOWNERS

* Update CODEOWNERS

* Update LICENSE.txt

Author: CristiCanizales

CODEOWNERS

@@ -0,0 +1,15 @@
+# These owners will be the default owners for everything in
+
+# the repo. Unless a later match takes precedence,
+
+# @forcedotcom/ide-experience will be requested for
+
+# review when someone opens a pull request.
+
+# Order is important; the last matching pattern takes precedence
+
+# over the first matching pattern.
+
+#ECCN:Open Source
+#GUSINFO: Platform Dev Tools Scrum Team, IDE Experience Team
+*       @forcedotcom/ide-experience

SECURITY.md

@@ -0,0 +1,33 @@
+# Security
+
+## Reporting a Vulnerability
+
+We take the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations.
+
+If you believe you have found a security vulnerability, please report it to us as described below.
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Instead, please report them via email to [security@salesforce.com](mailto:security@salesforce.com).
+
+You should receive a response within 48 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
+
+Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
+
+- Type of issue (buffer overflow, SQL injection, cross-site scripting, etc.)
+- Full paths of source file(s) related to the vulnerability
+- The location of the affected source code (tag/branch/commit or direct URL)
+- Any special configuration required to reproduce the issue
+- Step-by-step instructions to reproduce the issue
+- Proof-of-concept or exploit code (if possible)
+- Impact of the issue, including how an attacker might exploit it
+
+This information will help us triage your report more quickly.
+
+## Preferred Languages
+
+We prefer all communications to be in English.
+
+## Policy
+
+Salesforce follows the principle of [Responsible Disclosure](https://en.wikipedia.org/wiki/Responsible_disclosure).

how_to_license.md

@@ -0,0 +1,66 @@
+# How to License
+
+This project is licensed under the BSD 3-Clause License - see the [LICENSE](LICENSE) file for details.
+
+## License Headers
+
+All source files should include the appropriate license header. For this project, use the BSD 3-Clause License header:
+
+```javascript
+/*
+ * Copyright (c) 2025, Salesforce Platform
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions are met:
+ *
+ * 1. Redistributions of source code must retain the above copyright notice, this
+ *    list of conditions and the following disclaimer.
+ *
+ * 2. Redistributions in binary form must reproduce the above copyright notice,
+ *    this list of conditions and the following disclaimer in the documentation
+ *    and/or other materials provided with the distribution.
+ *
+ * 3. Neither the name of the copyright holder nor the names of its
+ *    contributors may be used to endorse or promote products derived from
+ *    this software without specific prior written permission.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+ * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+ * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+ * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+ * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+ * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+ * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ */
+```
+
+## Adding License Headers to Files
+
+When adding new source files to this project, please include the appropriate license header at the top of the file.
+
+## Third-Party Dependencies
+
+When adding third-party dependencies to this project, ensure they are compatible with the BSD 3-Clause License. Common compatible licenses include:
+
+- MIT License
+- Apache License 2.0
+- BSD 2-Clause License
+- BSD 3-Clause License
+- ISC License
+
+If you need to add a dependency with a different license, please consult with the project maintainers to ensure compatibility.
+
+## License Compliance
+
+All contributors to this project must ensure that their contributions comply with the project's license terms. This includes:
+
+1. Ensuring all code is original or properly licensed
+2. Including appropriate license headers in source files
+3. Documenting any third-party dependencies and their licenses
+4. Following the terms of the BSD 3-Clause License for all contributions
+
+For questions about licensing, please contact the project maintainers or refer to the [LICENSE](LICENSE) file.