deepsec

Read the source on GitHub Project homepage

What it does

An editorial selection.

Agent-powered vulnerability scanner you run on your own infrastructure for deep, on-demand review of whole codebases.

Why it is listed

Tuned for hard-to-find, long-lived bugs. Scans of large codebases can cost thousands of dollars in model usage, so budget for it.

GitHub describes it as: Deepsec is a security harness for finding vulnerabilities in your codebase powered by coding agents

Counts were observed on 27/10/2026, 23:15:40 UTC. Observations older than 36 hours are excluded from current movement rankings.

Repository at a glance

Stars: 8,271
Forks: 509
Open issues: 28
Merged PRs: 80
Commits, last 30 days: 1
Stars, 7 days: unavailable
Stars, 30 days: unavailable

Counts observed on 27/10/2026, 23:15:40 UTC. Growth uses complete dated windows; see Methodology.

History

History: 2 observations, 2026-10-27 to 2026-10-28. Dots are observations; lines connect consecutive daily observations only.

Project details

Language: TypeScript
Licence: Apache-2.0
Created: 30 Apr 2026
Last push: 29 Sept 2026
Latest release: none published
Category: Security
Topics: none listed
Observed: 2026-10-27 23:15:40 UTC

Explore and get started

Use the project's own documentation for supported platforms, dependencies and installation steps. The README and release notes are maintained by vercel-labs.

Read the README and setup instructionsFeatures, prerequisites, examples and documentation links.
Browse releases and changelogsPublished versions and the changes made between releases.
Check licence and usage termsApache-2.0 is the licence reported by GitHub; read the repository terms before use.
Read pull requestsProposed changes and development discussions.
Browse reported issuesKnown problems, feature requests and maintainer responses.

Development context

These are observations of work in the repository. They do not establish quality, security or support commitments.

Total commits on default branch: 105
Open pull requests: 50
Closed issues, lifetime: 12
Median time to close an issue: 0.3 days
Median time to merge a pull request: 0.0 days

Close and merge times use up to 20 most recently updated closed issues or merged pull requests. They omit unresolved work and are context, not a maintenance score. Sample limits.

Other projects in Security, ordered by shared topics and then name. These are discovery links, not equivalence claims.