Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This repository is no longer maintained #140

Closed
phatify opened this issue Dec 21, 2022 · 4 comments
Closed

This repository is no longer maintained #140

phatify opened this issue Dec 21, 2022 · 4 comments

Comments

@phatify
Copy link

phatify commented Dec 21, 2022

Who is maintaining it?
It has not been updated for a long time, should we trust it to use?

@ahkhanjani
Copy link

It has not been updated for a long time, should we trust it to use?

It's the best you don't use a library last published 7 years ago for security purposes.

@dcodeIO
Copy link
Owner

dcodeIO commented Aug 18, 2023

This is code, not a banana. I'm not aware of any time-induced breakage, hence closing.

@aggregate1166877
Copy link

It's the best you don't use a library last published 7 years ago for security purposes.

Actually, it's precisely the opposite when crypto is involved. You DO NOT want security-critical libraries constantly adding fluff for the sake of living on the edge. You want a battle-tested solution known to work correctly.

This is a cryptographic library, not an emoticon pack. It will need an update only when something is found to be insecure or broken.

@foxxyz
Copy link

foxxyz commented Jun 2, 2024

This is code, not a banana. I'm not aware of any time-induced breakage, hence closing.

While this is a fun response, the computing environment doesn't stand still. Language advances, deprecations, engine and operating system changes will require maintenance and occasional updates.

Right now I can't even install the dev dependencies to run the tests, which does warrant attention.

Actually, it's precisely the opposite when crypto is involved. You DO NOT want security-critical libraries constantly adding fluff for the sake of living on the edge. You want a battle-tested solution known to work correctly.

I don't think they were advocating for adding fluff. I agree that you want to be conservative with regards to making feature changes, but regular maintenance is critical to security.

@dcodeIO If you need support in maintaining this library, let me know and I'd be happy to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants