#1113886 ITP: sql-tool -- Secure SQL tool for AI agents to interact with databases

Package:
wnpp
Source:
wnpp
Submitter:
Harsh Dadiya
Date:
2025-11-29 16:58:53 UTC
Severity:
normal
#1113886#5
Date:
2025-09-03 18:44:40 UTC
From:
To:
* Package name    : sql-tool
  Version         : 0.1.9
  Upstream Contact: Harsh Dadiya <harshdadiya@gmail.com>
* URL             : https://github.com/Dadiya-Harsh/sql-tool
* License         : MIT
  Programming Lang: Python
  Description     : Secure SQL tool for AI agents to interact with databases

SQL-Agent-Tool (sql-tool) is a secure and database-independent framework for enabling
AI agents to safely interact with relational databases. It supports multiple LLM providers
(Groq, OpenAI, DeepSeek, Gemini) and integrates with PostgreSQL, MySQL, SQLite, and OracleDB.
Features include schema reflection, natural language to SQL generation, parameter extraction,
and safe query execution.

This package is relevant for developers working on AI/ML systems where natural language
queries need to be translated into safe SQL commands. Unlike existing libraries, sql-tool
is designed with database-independence and security in mind, helping developers integrate
AI agents with databases reliably.

I plan to maintain this package myself. If needed, I may seek co-maintainers or sponsorship
through the Debian Python Team, as this package is Python-based.
#1113886#10
Date:
2025-09-03 19:21:18 UTC
From:
To:
Hi Harsh,

I think "sql-tool" is a bit too generic. Could you please change that?

Thanks! Bye :)
#1113886#15
Date:
2025-09-05 12:29:19 UTC
From:
To:
Hi Harsh,

It's for sure better than before! Still, as a first Debian contribution,
I'd focus on trying to fix an existing package, or package a software
which has lots of users, and you didn't write yourself.

Trying to get something into Debian where you are the upstream, is
sometimes seen as an attempt to advertise your project, without really
an intent of making Debian better. Not necessarily! But it often does.

If you need any help packaging something else, let me know :)

Bye!
#1113886#20
Date:
2025-09-05 12:41:49 UTC
From:
To:
Moreover, looking at the project's README, I notice this:

    ## 📜 License

    This project is licensed under a **dual license** model:

    - **Apache License 2.0** – For open source usage. See the
      [`LICENSE`](./LICENSE) file for full terms.
    - **Commercial License** – For proprietary or commercial use, please
      [contact the author](mailto:harshdadiya@gmail.com) to obtain
      a commercial license.

Restricting commercial usage is against the point six of the Debian Free
Software Guidelines (DFSG), see
<https://www.debian.org/social_contract.en.html#guidelines>.

If you want to get this into Debian, you have to reconsider your
licensing terms. If you want to keep restricting usage in proprietary
software (but still allowing commercial usage), you may want to
relicense your software under something like the GPL or AGPL, and keep
the "commercial" license as the second option. Some projects like Qt do
this.
#1113886#25
Date:
2025-09-05 15:40:14 UTC
From:
To:
Hi,

Sure! I explained myself poorly. I mean that you should focus on
packaging software written by others, instead of trying to get your own
projects into Debian.

Of course, if there's demand, packaging your own projects is fine as
well.

Packaging your own project, when it has a really low amount of users,
and when it is the first thing you package in Debian, can be seen as
a way of advertising your own stuff.

Hope it's clear now! Bye.

P.S. please try to keep the bug number email address in Cc, as otherwise
these discussions won't be included in the issue tracker.