Outdated VS Code extension release

Open
#751 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp, vscode
Domain
devtools, security

Research direction

Start by locating the VS Code extension project and its current DevSkim release and .NET version references. Compare them with DevSkim v1.0.70 and the latest CLI release; done means the extension uses the latest DevSkim build and supports .NET 10, with the extension still usable instead of requiring the CLI.

Written by the indexing model from the issue text.

Description

enhancement

Is your feature request related to a problem? Please describe.
The current VS Code extension is outdated (6 months behind) and has not been updated to use v1.0.70.
A new VS Code extension with the latest DevSkim release is way overdue.

Describe the solution you'd like
The VS Code plugin to be updated to support .Net 10 and latest DevSkim build.

Describe alternatives you've considered
Using the CLI is not practical.

Additional context
Unless the VS Code extension is being abandoned, like with the VS extension, it should be updated to match the latest DevSkim CLI releases.

Dominant language
C#
Stars
1k
Forks
132
Avg merge
1m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/DevSkim

All issues in microsoft/DevSkim

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.