Zcash CocoaPods to SPM integration (iOS) [draft]

[j0ntz]

Draft: iOS Zcash SDK SPM integration validation

Stacked on the RN 0.83 + reanimated 4.5.0 base (PR #6047). Adds the ZcashLightClientKit Swift Package to edge.xcodeproj and patches the react-native-zcash podspec to stop vendoring the SDK (pairs with EdgeApp/react-native-zcash#68).

Purpose of this draft PR: validate the iOS SPM build on CI. The local headless xcodebuild deadlocks in waitForRemoteSourcePackagesToFinishLoading, so CI is the build driver.

Known remaining issue: static-link gRPC collision (piratechain pod gRPC-Swift 1.8 vs SPM grpc-swift 1.27.5). Fix in progress: migrate PirateLightClientKit to SPM so the resolver unifies the gRPC/NIO/SwiftProtobuf/SQLite graph.

https://claude.ai/code/session_019nYrjJ47fMBDnp9XdXT33g

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​react-test-renderer@​19.1.0
	@​react-native/​metro-config@​0.79.2 ⏵ 0.83.2	+1		+1	+1
	@​babel/​preset-typescript@​7.27.1 ⏵ 7.29.7				+1
	@​react-native/​typescript-config@​0.79.2 ⏵ 0.83.2			+10	+1
	@​react-native-community/​cli@​18.0.0 ⏵ 20.0.0	+1	+75	+1
	expo@​53.0.20 ⏵ 55.0.0-preview.9
	@​types/​react@​19.1.9 ⏵ 19.2.17
	react-native-gesture-handler@​2.28.0 ⏵ 2.32.0			+1
	react-test-renderer@​19.0.0 ⏵ 19.2.0	+1		+1
	@​react-native/​babel-preset@​0.79.5 ⏵ 0.83.2	+1		+1
	react-native-bootsplash@​6.3.8 ⏵ 7.3.2	-15			+1
	react@​19.0.0 ⏵ 19.2.0
	react-native-worklets@​0.6.1 ⏵ 0.10.0	+1		+3
	react-native@​0.79.2 ⏵ 0.83.2
	react-native-reanimated@​3.19.5 ⏵ 4.5.0	+1		+1	+1
	@​react-native-community/​cli-platform-android@​18.0.0 ⏵ 20.0.0				+1
	@​react-native-community/​cli-platform-ios@​18.0.0 ⏵ 20.0.0				+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @emnapi/runtime is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/react-native-bootsplash@7.3.2 → npm/jest@30.0.0 → npm/@emnapi/runtime@1.11.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/runtime@1.11.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @expo/cli is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/expo@55.0.0-preview.9 → npm/@expo/cli@55.0.6 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@expo/cli@55.0.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @expo/cli is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/expo@55.0.0-preview.9 → npm/@expo/cli@55.0.6 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@expo/cli@55.0.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Publisher changed: npm @expo/log-box is now published by brentvatne Author: brentvatne From: package-lock.json → npm/expo@55.0.0-preview.9 → npm/@expo/log-box@55.0.5 ℹ Read more on: This package | This alert | What is unstable ownership? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@expo/log-box@55.0.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm fast-xml-parser is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/@react-native-community/cli-platform-android@20.0.0 → npm/@react-native-community/cli-platform-ios@20.0.0 → npm/@react-native-community/cli@20.0.0 → npm/fast-xml-parser@4.5.6 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/fast-xml-parser@4.5.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm node-forge is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/expo@55.0.0-preview.9 → npm/@walletconnect/web3wallet@1.10.1 → npm/node-forge@1.4.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/node-forge@1.4.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm react-native-bootsplash is 62.0% likely obfuscated Confidence: 0.62 Location: Package overview From: package-lock.json → npm/react-native-bootsplash@7.3.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/react-native-bootsplash@7.3.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm react-native-bootsplash is 60.0% likely obfuscated Confidence: 0.60 Location: Package overview From: package-lock.json → npm/react-native-bootsplash@7.3.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/react-native-bootsplash@7.3.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm react-native is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/react-native@0.83.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/react-native@0.83.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Low adoption: npm @expo/log-box Location: Package overview From: package-lock.json → npm/expo@55.0.0-preview.9 → npm/@expo/log-box@55.0.5 ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@expo/log-box@55.0.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Low adoption: npm expo-modules-core Location: Package overview From: package-lock.json → npm/expo@55.0.0-preview.9 → npm/expo-modules-core@55.0.7 ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/expo-modules-core@55.0.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Low adoption: npm fetch-nodeshim Location: Package overview From: package-lock.json → npm/expo@55.0.0-preview.9 → npm/fetch-nodeshim@0.4.10 ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/fetch-nodeshim@0.4.10. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report