Release History

Changelog

What's new in DeepSweep agent authorization

122 releases

77 security patterns

Latest: v2.0.31

Fixed

Apply from the findings list works on files you don't have open. Choosing Apply on a finding in another file now opens that file and fixes the line you chose. Before, it asked you to review the file even though nothing had changed. If the file did change since the review, DeepSweep still asks you to look again.

Fixed

Automatic fixes only where they work. "Auto-fix available" and Apply now appear only on findings DeepSweep can change itself, and Apply changes the line you chose. If the file changed since the review, DeepSweep asks you to look again instead of editing another line.
Debug settings are switched off correctly. Python files get False, and one-line JavaScript and TypeScript config objects are fixed in place. A setting DeepSweep cannot change safely is left as it is, with a prompt you can copy.
Fix all says when nothing can be fixed automatically, instead of offering an upgrade for it.

Added

Certificate checks turned back on for Node. When a line sets NODE_TLS_REJECT_UNAUTHORIZED to "0" on its own, DeepSweep can set it back to "1".

Changed

Fewer suggestions at once. On some installs, DeepSweep now shows at most one suggestion a day (the upgrade offer, the README badge, the short survey or the EU AI Act readiness note) instead of several after a review. The others wait for a later day, and none of them is used up while it waits. Your own commands, review results and anything about your code are never held back.

Fixed

The optional usage report keeps when you started. The date you first used DeepSweep and the version you started on are now recorded. Before, they were usually lost before the report was sent.