Search Criteria
Package Details: mollysocket 1.7.1-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/mollysocket.git (read-only, click to copy) |
|---|---|
| Package Base: | mollysocket |
| Description: | MollySocket allows getting Signal notifications via UnifiedPush. |
| Upstream URL: | https://github.com/mollyim/mollysocket |
| Licenses: | AGPL-3.0 |
| Submitter: | jwh |
| Maintainer: | jwh |
| Last Packager: | jwh |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2026-01-08 23:13 (UTC) |
| Last Updated: | 2026-06-14 16:49 (UTC) |
Dependencies (3)
- cargo (rust-beta-binAUR, rustup-gitAUR, rust-gitAUR, rust, rustup) (make)
- clang (llvm-gitAUR, clang-minimal-gitAUR, clang17-binAUR, clang-static-gitAUR) (make)
- toml-cliAUR (make)
Latest Comments
jwh commented on 2026-06-15 00:02 (UTC)
A few packages have definitely been rolled back, that is, the history no longer shows the malicious commits but the dates no longer match it seems.
re vapid, I can't remember actually - I only did enough to get it working and haven't touched it since
taba commented on 2026-06-14 23:47 (UTC)
What was wrong with the vapid service?
taba commented on 2026-06-14 23:47 (UTC)
Pretty sure you can't roll back commits here. Also the recent attacks are irrelevant, I review all scripts.
jwh commented on 2026-06-14 21:04 (UTC) (edited on 2026-06-14 21:07 (UTC) by jwh)
The recent "attacks" aside, one should always review and use a chroot to build anyway and not use abandoned/orphaned packages. The real problem now is, due to the rolling back of commits etc, it's not entirely clear in some cases if its the original as dates have changed.
taba commented on 2026-06-14 20:59 (UTC)
Was a dependence on another AUR package necessary? Reviewing PKGBUILDs is not fun.