this post was submitted on 15 Jul 2024
45 points (100.0% liked)

Jerboa

10300 readers
2 users here now

Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.

Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.

Built With

Features

Installation / Releases

Support / Donate

Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.

Crypto

Contact

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 4 months ago (1 children)
[–] [email protected] -1 points 4 months ago (1 children)

Check the code for suspicious lines and then check the compiled app for network traffic etc

[–] [email protected] 2 points 4 months ago* (last edited 4 months ago) (1 children)

There were dozens of dependency upgrades in this release, I have no idea why you think this specific one has security issues. Either way we don't have time to read through every line of code of every dep update, but here's the source code: https://android.googlesource.com/platform/tools/base

If you find something, you might want to submit a PR as it would affect not just ours, but a lot of android projects.

[–] [email protected] -2 points 4 months ago (1 children)

Reading through the code of the dependency is not required. What is required is reading through the merge request to see if the dependency isn't used for malicious or wasteful purposes. Checking on the authenticity of the dependency is a good idea too.

[–] [email protected] 2 points 4 months ago (1 children)

Open up an issue for your concerns on the google issue tracker, here it is linked for you: https://android.googlesource.com/platform/tools/base

[–] [email protected] -2 points 4 months ago

It's not the dependency itself that concerns me. It's the usage of it in the app. As we already know, it's easy to insert trojan code in testing procedures.