search

dint-dev / cryptography

Cryptography for Flutter developers: encryption, digital signatures, key agreement, etc.
https://pub.dev/packages/cryptography
Apache License 2.0
161 stars 85 forks source link

Is this repo/package dead? #189

Open savejeff opened 1 week ago

savejeff commented 1 week ago

Currently, it seems it does not work/compile on Android needing pretty simple fixes to the build.gradle. No commit were made for over a year.

Before using this package in my project, I would like to be sure it gets basic fixes

petrleocompel commented 5 days ago

Please @terrier989 add some maintainers so we can continue working on these packages...

As mentioned in many issues like #180 and more you can find... Fix exist and it is kinda easy but .. Even pull request not been merged for long time. And those are the basic fixes.

Link in "README" does not work - Maintained by [gohilla.com](https://gohilla.com/). The site is gone. Link in the "group/organization" https://github.com/dint-dev - https://www.dint.dev/ works but no contact.

@terrier989 is the only public member in https://github.com/dint-dev group.

I've been waiting for fix for over a half year - even just "merging" the code would be enough.

savejeff commented 5 days ago

@petrleocompel thx for putting together the informations 👌 I have a bad feeling that the owner is not active anymore, but let's hope

petrleocompel commented 5 days ago

@savejeff If I will not get a response I will have to do stuff on my own... I took a look on forks... but

Screenshot 2024-10-15 at 9 05 15

The real "maintaining" is not really there. Some people just for fix one thing and does not care anymore. And then it is abandoned again.

So even I will go by route of fork .. but with automated release and try some "extra people" to invite and request like 2/3 people to validate a merge on their own.

petrleocompel commented 5 days ago

@savejeff I sent an email to @terrier989.

Hopefully at least that will reach him.

Still to get it of their back a little there is some stuff to do... Currently it seems releases were done manually (no CI/CD setup to publish packages to pub.dev). So to publish the package under same name it will still take some time to "setup" that from the original maintainer.