DEPRECATED -- DevSkim plugin for Sublime Text 3.
Перейти к файлу
Michael Scovetta ef3d7cd97c Fixed broken link to keymap. 2017-03-14 23:54:25 -07:00
DevSkim-Common Bumped rules to Microsoft/DevSkim@97946ef394 2017-03-14 23:44:02 -07:00
css Initial import from internal repository. 2016-10-17 12:37:59 -07:00
doc Update broken links to DevSkim-Rules (fixes #1). 2017-02-02 14:16:22 -08:00
messages Bump version to 0.2.1. 2017-01-18 15:17:48 -08:00
.gitignore Fix gitignore to exclude DevSkim-Common directory. 2017-02-03 11:10:25 -08:00
CONTRIBUTING.md Update broken links to DevSkim-Rules (fixes #1). 2017-02-02 14:16:22 -08:00
Default (Linux).sublime-keymap Updated key mapping to avoid overwriting default mapping. 2017-01-04 16:46:29 -08:00
Default (OSX).sublime-keymap Updated key mapping to avoid overwriting default mapping. 2017-01-04 16:46:29 -08:00
Default (Windows).sublime-keymap Updated key mapping to avoid overwriting default mapping. 2017-01-04 16:46:29 -08:00
DevSkim.py Add filename to execute() call, minor README fixes. 2017-03-14 23:39:17 -07:00
DevSkim.sublime-commands Initial import from internal repository. 2016-10-17 12:37:59 -07:00
DevSkim.sublime-project Initial import from internal repository. 2016-10-17 12:37:59 -07:00
DevSkim.sublime-settings Improved stylesheet loading and testing code. Minor updates to messages. 2016-12-15 10:45:44 -08:00
LICENSE.txt Initial import from internal repository. 2016-10-17 12:37:59 -07:00
Main.sublime-menu Fixed broken link to keymap. 2017-03-14 23:54:25 -07:00
README.md Add filename to execute() call, minor README fixes. 2017-03-14 23:39:17 -07:00
messages.json Bump version to 0.2.1. 2017-01-18 15:17:48 -08:00

README.md

DevSkim Plugin for Sublime Text

The plugin implements a security linter within the Sublime Text editor, leveraging the rules from the DevSkim repository. It helps software engineers to write secure code by flagging potentially dangerous calls, and gives in-context advice for remediation.

PUBLIC PREVIEW

DevSkim is currently in public preview. We're looking forward to working with the community to improve both the scanning engines and rules over the next few months, and welcome your feedback and contributions!

DevSkim Demo

Requirements

The plugin requires Sublime Text 3 (build >= 3114), and will function on Windows, Linux, and MacOS.

Installation

Install this plugin using Package Control from Sublime Text. The package name is DevSkim.

Alternatively, you can clone this repository into your Sublime Text "Packages" folder. For example, under Windows:

cd "%APPDATA%\"Sublime Text 3\Packages"
git clone https://github.com/Microsoft/DevSkim-Sublime-Plugin.git DevSkim

MacOS:

cd ~/"Library/Application Support/Sublime Text 3/Packages"
git clone https://github.com/Microsoft/DevSkim-Sublime-Plugin.git DevSkim

Linux:

cd ~/.config/sublime-text-3/Packages
git clone https://github.com/Microsoft/DevSkim-Sublime-Plugin.git DevSkim

Note if you are using the portable version of Sublime Text, the location will be different. See the Sublime Text documentation for more information.

IMPORTANT If you already have a package called DevSkim installed, either remove this first, or clone this repo to a different folder.

Using DevSkim

By default, DevSkim will run as you type, highlighting code that fails a rule. If you click on a highlighted bit of code, you will see the rule in the status bar.

You can run a full scan by pressing Ctrl-Shift-g, which will result in a popup showing all findings for the file. You can also choose DevSkim: Analyze File from the Command Palette.

Platform support

Operating System:

The plugin has identical behavior across Windows, MacOS, and Linux.

Sublime Text Version:

The plugin requires Sublime Text 3 builds >= 3114.

Settings

You can customize how DevSkim works through the Settings -- User menu item. If you change any settings, you should reload the DevSkim configuration, either by restarting Sublime Text or by running the command DevSkim: Reload Configuration.

Rules System

The plugin supports both built-in and custom rules:

Built-In Rules

Built-in rules come from the DevSkim repository, and should be stored in the DevSkim-Common/rules directory within the DevSkim package directory.

Rules are organized by subdirectory and file, but are flattened internally when loaded.

Each rule contains a set of patterns (strings and regular expressions) to match, a list of file types to apply the rule to, and, optionally, a list of possible code fixes.

Information how writing rules can be found at Writing-Rules

Reporting Issues

Please see CONTRIBUTING for information on reporting issues and contributing code.

Tips and Known Issues

See tips and known issues in the wiki page.