Review Results

Comment

The change only adds a new runtime dependency entry in .SRCINFO: `ntsync-autoload`. By itself this metadata update does not introduce executable code, network access, privilege escalation, or packaging behavior changes in the reviewed diff. I did not see any evidence in the provided hunk of malicious installation logic or integrity issues. Security impact is low and limited to dependency metadata; any risk would depend on the separately maintained package, not this .SRCINFO edit.

@@ -15,6 +15,7 @@ pkgbase = proton-ge-custom-bin
 	license = MPL
 	license = custom
 	depends = python
+	depends = ntsync-autoload
 	optdepends = vulkan-icd-loader: dxvk dependency
 	optdepends = lib32-vulkan-icd-loader: dxvk dependency for 32bit prefixes
 	optdepends = kdialog: KDE splash dialog support

Comment

The change only updates a sha512 checksum entry in .SRCINFO for an existing source file; no URLs, build logic, install scripts, or package metadata are altered. On its face this is a low-risk integrity metadata refresh, with no evidence of added code execution, persistence, or supply-chain red flags in the provided hunk.

@@ -40,7 +41,7 @@ pkgbase = proton-ge-custom-bin
 	source = pam_limits.conf
 	sha512sums = 5d1a841d3f8f65f9e62742f84eeccfb198a0292a97ba9109f377a550a4de0e2913d1e17b3d90ecd37ac09411dc67e54662dc1be301554ce05fd128d842252deb
 	sha512sums = 78ede6d50f9c43407da511c8b37dcf60aae2ddbd461c0081f0d0ce3de08ace3a84dee86e9253acbac829b47c5818ef4e1a354ccb05feaa9853ce279dc3f903fd
-	sha512sums = ac2bd634838ffe6b90f2637e229013f0993fc1013271dbeefd216dc262a8bb79e4a5ce15a75cbfcb0c3b521d32f4ebe1ed25a6b066b99cc327b60bd6d7212e6f
+	sha512sums = d56baad80c2752fd1a2fdd75eafd07165b09cbc257d8a2641c186970117e93417355cbbc7b0f1bfae908a896aed3773fcfefc920c8c6c3135908586f444e3fa5
 	sha512sums = 60bcb1ad899d108fca9c6267321d11871feae96b696e44607ef533becc6decb493e93cbe699382e8163ad83f35cfa003a059499c37278f31afeba4700be6e356
 	source_x86_64 = GE-Proton11-5_1-x86_64.tar.gz::https://github.com/GloriousEggroll/proton-ge-custom/releases/download/GE-Proton11-5/GE-Proton11-5-x86_64.tar.gz
 	sha512sums_x86_64 = 8fb1f3ae65a8dc22efd8099ff489075f0eebddf01c445b423244589f6f0a1e19c01de5d1e722b97fc1ebaf6390c813052ed55290058f8d21f1353a36146f4a2c

Comment

The only change is adding `ntsync-autoload` to depends(). This is a packaging dependency change, not executable code. I checked the surrounding PKGBUILD context: the package already installs a modules-load.d file and other config under /usr/lib/modules-load.d, so depending on an ntsync autoload helper is plausibly related to enabling the ntsync kernel module for Proton/Wine compatibility. The change does not introduce network fetches, privilege escalation, post-install scripts, or other persistence mechanisms. No security issue is evident from this diff alone.

@@ -20,6 +20,7 @@ conflicts=('proton-ge-custom' 'proton-ge-bin')
 ## dependencies
 depends=(
   'python'
+  'ntsync-autoload'
 )
 
 optdepends=(

Comment

The only substantive change is replacing the SHA-512 checksum for one archived source file and adding a new runtime dependency on `ntsync-autoload`. I do not see any evidence of malicious code execution, network fetches outside `source=()`, privilege escalation, or packaging writes outside `$pkgdir` in the reviewed hunk. The checksum update is consistent with a source artifact change and does not by itself indicate tampering. The new dependency is notable because it affects runtime behavior, but from this diff alone it appears to be a normal kernel-module autoload helper rather than a persistence or privilege mechanism. Overall this looks low risk.

@@ -75,7 +76,7 @@ source_aarch64=(
 sha512sums=(
   '5d1a841d3f8f65f9e62742f84eeccfb198a0292a97ba9109f377a550a4de0e2913d1e17b3d90ecd37ac09411dc67e54662dc1be301554ce05fd128d842252deb'
   '78ede6d50f9c43407da511c8b37dcf60aae2ddbd461c0081f0d0ce3de08ace3a84dee86e9253acbac829b47c5818ef4e1a354ccb05feaa9853ce279dc3f903fd'
-  'ac2bd634838ffe6b90f2637e229013f0993fc1013271dbeefd216dc262a8bb79e4a5ce15a75cbfcb0c3b521d32f4ebe1ed25a6b066b99cc327b60bd6d7212e6f'
+  'd56baad80c2752fd1a2fdd75eafd07165b09cbc257d8a2641c186970117e93417355cbbc7b0f1bfae908a896aed3773fcfefc920c8c6c3135908586f444e3fa5'
   '60bcb1ad899d108fca9c6267321d11871feae96b696e44607ef533becc6decb493e93cbe699382e8163ad83f35cfa003a059499c37278f31afeba4700be6e356'
 )
 

Comment

The only change in this hunk is removal of the trailing newline from proton-ge-custom-bin.conf while keeping the same content ('ntsync'). This is a non-functional formatting change with no impact on build behavior, packaging, execution, or security posture. No suspicious sources, scripts, permissions, or persistence mechanisms are introduced.

@@ -1 +1 @@
-ntsync
+ntsync
\ No newline at end of file