old unmaintained package with no license (seq-queue@0.0.5)

[andres645]

Hi,
I noticed that the MySQL2 project relies on the package seq-queue@0.0.5, which has not been maintained for over a decade and lacks a license. The absence of a license poses potential legal and compliance risks.

Given the importance of this issue, I would like to suggest either:

Replacing seq-queue with a maintained and licensed alternative, or
Working with the original maintainers of seq-queue (if possible) to update the package with a proper license.

This issue can potentially impact the ability to use this package in a compliant manner, so addressing it would be beneficial for the broader community.

Looking forward to your thoughts and any steps to resolve this.

Thank you for maintaining MySQL2!

[wellwelwel]

Hi, @andres645 🙋🏻‍♂️

This issue can potentially impact the ability to use this package in a compliant manner, so addressing it would be beneficial for the broader community.

12 years ago, MIT license was added and is present on npm, but it hasn't been added to package.json.

---

Working with the original maintainers of seq-queue (if possible) to update the package with a proper license.

Also, see:

• Add license to package.json changchang/seq-queue#3

---

This issue can potentially impact the ability to use this package in a compliant manner, so addressing it would be beneficial for the broader community.

This is the license published in the seq-queue npm package (and available in node_modules): https://cdn.jsdelivr.net/npm/seq-queue/LICENSE

[wellwelwel]

I think this issue can be closed as unplanned, but I'll keep it open for @sidorares 🙋🏻‍♂️

[andres645]

Thanks for the answer :)

[sidorares]

I'll close it as "If it ain't broke, don't fix it" :)
In theory we could migrate to a similar library, or copy the code ( it's just one small file and license allows that ) or rewrite part of the library that needs it to handle control manually, but as @wellwelwel pointed out there is no license conflict with myql2 MIT and no known bugs related to seq-queue, at least in a context of our usage.