You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking through the source code of this mod, when I noticed a .jar file that I could only view as raw. Pardon me if this is a silly issue, I am not very familiar with the Java language, but it seems like you are statically linking to this dependency. It would be better for build reproducibility if this was addressed. I propose adding it as a git submodule, so the entire source tree could be explored, but ydy.
As of right now, I cannot verify that this mod is not malicious. It would do me (any many others in the anarchy community) a great service if you could change how this is done. Pardon my paranoia -- I just remember the XZ and Fracturiser situations, and I don't want history to repeat itself, especially as members of my group have used this mod and it could have potentially exposed base coordinates, passwords, etc. We just don't know without being able to check it.
Thank you for your time, rfresh.
The text was updated successfully, but these errors were encountered:
The .jar file is not malicious i can confirm that I have checked it and as @rfresh2 stated "this mod is a compile-only dependency. it's not included in Xaeroplus's output jar, nor can it change anything about Xaeroplus' output jar.
Good morning.
I was looking through the source code of this mod, when I noticed a .jar file that I could only view as raw. Pardon me if this is a silly issue, I am not very familiar with the Java language, but it seems like you are statically linking to this dependency. It would be better for build reproducibility if this was addressed. I propose adding it as a git submodule, so the entire source tree could be explored, but ydy.
As of right now, I cannot verify that this mod is not malicious. It would do me (any many others in the anarchy community) a great service if you could change how this is done. Pardon my paranoia -- I just remember the XZ and Fracturiser situations, and I don't want history to repeat itself, especially as members of my group have used this mod and it could have potentially exposed base coordinates, passwords, etc. We just don't know without being able to check it.
Thank you for your time, rfresh.
The text was updated successfully, but these errors were encountered: