Back to Docs
Release History
Changelog
What's new in DeepSweep agent authorization
55 releases
77 security patterns
Latest: v1.33.0
Fixed
- A review that returns no result no longer reports a perfect score. When a review came back with nothing to report, the usage data we collect recorded it as a flawless result on a clean project. It is now recorded as what it was: no result.
- The CI workflow we hand you points at the right Action. "Copy GitHub Action" produced a workflow referencing an action that does not exist, so pasting it into your repository made your next push fail its checks. It now references the published DeepSweep action and runs.
- A grade now requires a review that read something. Opening your editor with no folder open produced "A+ — 100/100, perfectly secure" for a workspace DeepSweep had never read, and that grade was then stored, shown in the status bar and offered as a badge. A review that reads no files now says so and offers to open a folder instead.
- The dependency check reported "All packages verified" after examining zero packages. Since 1.9.5 the extension sent your package list in a shape the service could not read, so no package was ever checked — and that empty result was reported back to you as a clean one. Your dependencies are now genuinely checked, and a review that cannot check them says so rather than passing them.
- Fix prompts carry the file and the line. "Copy fix prompt" put a generic one-line description of the rule on your clipboard, with nothing an agent could act on. It now carries the severity, the file and line, the offending line with any secret masked out, the fix guidance, and an acceptance check the agent can verify itself.
- The weekly digest no longer repeats a grade from a review that never happened. Devices carrying that fabricated A+ were told "Last grade A+ (100/100). Run a review to confirm you're still clean" about a project nothing had read. A stored grade now carries proof that files were read; without it the digest stays quiet until your next real review.
- Your grade counts distinct problems, not repeated lines. The same issue on twenty lines of one file was charged twenty times over, which graded real projects F on a handful of problems. It now counts once, at its worst severity, and every finding is still listed and still navigable. Grades from earlier versions are not comparable with this one.
- "After three successful reviews" now means three successful reviews. Reviews that read nothing counted toward the totals behind the share prompt and the sign-in hint, so three editor launches with no folder open were enough to fire both on your first real review.
- The status badge could never resolve a grade. The grade was stored under one key while the badge URL asked for another, so every badge rendered the grey "not validated" placeholder; both now come from a single value. That value is a hash rather than your folder name, so a badge in a public README no longer discloses the directory name of a private project, and DeepSweep refuses to produce a badge at all for a workspace it has not reviewed.
Added
- The verdict names what it did not check. A project declaring dependencies in an ecosystem the check does not cover — Go, Cargo, Maven, Gradle, Composer or RubyGems — now gets one line in the health card saying those were not verified, instead of a partial review presented as a complete one.
Changed
- The offer shown after a review points at something you can get today. The review-complete panel linked the waitlist for an unreleased product; it now links the human security audit, and names the editor you are working in.
Added
- DeepSweep is on the VS Code Marketplace. VS Code users can install DeepSweep straight from the Marketplace and receive updates automatically through the editor. Installing from Open VSX — the registry serving Cursor, Windsurf, Antigravity and Trae — is unchanged.
Changed
- The compatibility list names only tools you can still get. Roo Code, Continue and Supermaven were shut down by their vendors, so they no longer appear in the "works alongside" list or the extension description. Reviews are unchanged: configuration those tools left behind in a workspace is still detected and reviewed.