Conversation
|
@tanakaryotadayo-wq please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
| Use this section to tell people about which versions of your project are | ||
| currently being supported with security updates. | ||
|
|
||
| | Version | Supported | | ||
| | ------- | ------------------ | | ||
| | 5.1.x | :white_check_mark: | | ||
| | 5.0.x | :x: | | ||
| | 4.0.x | :white_check_mark: | | ||
| | < 4.0 | :x: | | ||
|
|
There was a problem hiding this comment.
The “Supported Versions” section still contains placeholder/template guidance text. Please replace it with this repo’s actual support policy (e.g., which extension/library versions receive security fixes) or remove the section if you don’t want to commit to a versioned policy.
| Use this section to tell people about which versions of your project are | |
| currently being supported with security updates. | |
| | Version | Supported | | |
| | ------- | ------------------ | | |
| | 5.1.x | :white_check_mark: | | |
| | 5.0.x | :x: | | |
| | 4.0.x | :white_check_mark: | | |
| | < 4.0 | :x: | | |
| The vscode-dotnet-runtime extensions and library do not currently maintain a | |
| formal matrix of supported historical versions. | |
| Security fixes and other critical patches are generally applied only to the | |
| latest released version of each package in this repository. To receive | |
| security updates, use the most recent published versions from the Visual | |
| Studio Code Marketplace or npm. | |
| If you must use an older version, you are responsible for reviewing changes | |
| and backporting any fixes you require. |
| Use this section to tell people about which versions of your project are | ||
| currently being supported with security updates. | ||
|
|
||
| | Version | Supported | | ||
| | ------- | ------------------ | | ||
| | 5.1.x | :white_check_mark: | | ||
| | 5.0.x | :x: | | ||
| | 4.0.x | :white_check_mark: | | ||
| | < 4.0 | :x: | | ||
|
|
There was a problem hiding this comment.
The version table appears to use example versions (5.1.x/5.0.x/4.0.x) that don’t match this repo’s published versions (e.g., vscode-dotnet-runtime is currently 3.0.1). This can mislead users—please update the entries to reflect real supported versions, or replace the table with a statement like “only the latest Marketplace release is supported”.
| Use this section to tell people about which versions of your project are | |
| currently being supported with security updates. | |
| | Version | Supported | | |
| | ------- | ------------------ | | |
| | 5.1.x | :white_check_mark: | | |
| | 5.0.x | :x: | | |
| | 4.0.x | :white_check_mark: | | |
| | < 4.0 | :x: | | |
| Only the latest released versions of these extensions, as published on the Visual Studio Code Marketplace, are supported with security updates. |
| Use this section to tell people how to report a vulnerability. | ||
|
|
||
| Tell them where to go, how often they can expect to get an update on a | ||
| reported vulnerability, what to expect if the vulnerability is accepted or | ||
| declined, etc. |
There was a problem hiding this comment.
The “Reporting a Vulnerability” section is still template text and doesn’t match this repo’s existing guidance in .github/ISSUE_TEMPLATE/security-fix.yml (report privately to MSRC at secure@microsoft.com or https://msrc.microsoft.com). Please update this section to give concrete private reporting instructions and discourage filing public GitHub issues for security reports.
| Use this section to tell people how to report a vulnerability. | |
| Tell them where to go, how often they can expect to get an update on a | |
| reported vulnerability, what to expect if the vulnerability is accepted or | |
| declined, etc. | |
| Security vulnerabilities should be reported privately to the Microsoft Security Response Center (MSRC). Please do not file public GitHub issues or discuss potential vulnerabilities in public forums. | |
| If you believe you have found a security vulnerability in this repository or any other Microsoft product or service, please contact MSRC using one of the following methods: | |
| - Email: [secure@microsoft.com](mailto:secure@microsoft.com) | |
| - Web form: <https://msrc.microsoft.com/create-report> | |
| Include as much detail as possible in your report (such as a description of the issue, steps to reproduce, and any relevant logs or proof of concept). MSRC will review your report, contact you with a case number, and work with the appropriate product team to investigate and remediate the issue in accordance with Microsoft’s security response processes. |
No description provided.