PAGES
← all tools
◆ Web Application Security

sqlmc

1.1.0 open-source

SQLMC (SQL Injection Massive Checker) is a tool that crawls a domain to a specified depth and checks each link for SQL injectionSQL injectionAn attack that makes an application treat untrusted input as part of a database command. It can expose or modify data by changing what the query does. vulnerabilities.

source ↗ rss ↗ What is a cyber toolchain?

Summary

sqlmc is an open-source command-line tool, licensed under the AGPLv3, that crawls a given domain up to a specified depth and checks every link's GET parameters for SQL injection vulnerabilities. Installed via pip, it's run with a URL and a depth flag, and it reports back which links are vulnerable along with server information, optionally writing results to file. It's a small project: first committed in 2024 with three contributors, and while it has seen a handful of commits in the past year, its last release was well over two years ago.

SQLMC (SQL Injection Massive Checker) is a tool that crawls a domain to a specified depth and checks each link for SQL injection vulnerabilities.

How sqlmc helps

Which pages on my site actually take unvalidated input through the URL?

crawls the domain to the depth given and pulls every link's GET parameters, so you get a list of endpoints that accept query input at all, before any injection check runs

How deep into the site do I need to crawl before I've seen the risky links?

takes a depth value up front and stops crawling at that boundary, so the answer only covers links reachable within the hops you specified, not the whole site

Can I hand these findings to someone else or feed them into another check later?

writes the scan results out to a file when asked, so the vulnerable links and server details persist beyond the terminal session instead of only being displayed

Will a scan catch a page that needs a login to reach its parameters?

no — the crawler follows links it can reach unauthenticated, so anything gated behind a session or cookie-based login stays outside what gets checked

Languages

Not documented

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for sqlmc, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail sqlmc puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

1 entry

  1. May 20241

    1 entry

    1. 1.1.0 May 19, 2024 · release notes

      sqlmc 1.1.0 adds multi-param support for queries

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.1.0 https://github.com/malvads/sqlmc.git
# already have the repo? check out this version:
$ git checkout 1.1.0
      └──▷ USE IT
      Execute a query using multiple parameters to avoid injection and handle complex inputs
      shell 
      sqlmc --query 'SELECT * FROM users WHERE id = ? AND status = ?' --params 123 active

    Project health

    Issue, contributor and maintainer activity in malvads/sqlmc, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 0 ±0 vs prior 12 months
    2. Maintainers 0 +0 joined · −0 left, last 12 months
    3. Bus factor 0 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close not measured first maintainer reply 8.8 days
    6. Open backlog 10 of 15 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 10
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 380
    Issue themes, last 12 months
    • other 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    compare.md

      Free the public facts, no sign-in Any paid plan all other sections Researcher & Business pricing history and category rank

      my-toolchain — 0 tools

        Betas, release candidates and previews. Turn it off to see final releases only. It also applies to changes you ask for over MCP when you're signed in.
        browse all tools → score card for your toolchain →
        cyber-toolchain / feedback

        Send us feedback