pro_grammertoLinux@lemmy.ml·6 months agocross-posted to: opensource@lemmy.mlNeofetch development discontinued, repository archived(github.com)external-linkarrow-up1405arrow-down12message-square72file-textfedilink
arrow-up1403arrow-down1external-linkNeofetch development discontinued, repository archived(github.com)pro_grammertoLinux@lemmy.ml·6 months agocross-posted to: opensource@lemmy.mlmessage-square72file-textfedilink
cross-posted from: https://programming.dev/post/13437386 The author’s profile says this: “Have taken up farming.”
minus-squareOtterEnglisharrow-up38arrow-down1·6 months agoedit-26 months agolinkfedilinkIt would need to keep up with future changes and any security updates
minus-squaremoreeniarrow-up30arrow-down2·6 months agolinkfedilinkWell, it does its job for now. As for the security updates… Isn’t neofetch just a little fancy tool to display data from your system that is already exposed to any process on your distribution? What attack surface does it introduce?
minus-squareOtterEnglisharrow-up26arrow-down0·6 months agolinkfedilinkGoing by the releases, it didn’t need updates that often, but it still needed updates to fix and ensure compatibility as things changed Security wise, I think you’re right
It would need to keep up with future changes and any security updates
Well, it does its job for now. As for the security updates… Isn’t neofetch just a little fancy tool to display data from your system that is already exposed to any process on your distribution? What attack surface does it introduce?
Going by the releases, it didn’t need updates that often, but it still needed updates to fix and ensure compatibility as things changed
Security wise, I think you’re right