[iscekic]

Adds encryptExport and decryptExport: the Rust core seals a payload with an age passphrase recipient (scrypt, ASCII armor) and opens it again. The payload format is the app's concern. A wrong passphrase reports WrongPassphrase; a damaged, truncated or foreign file reports the new InvalidExport category. Encryption requires a passphrase of at least 8 characters and caps the payload at 16 MiB. Both calls run off the JavaScript thread.

The scrypt work factor is fixed at 18, the age CLI default, so files move between this library and the age CLI in both directions.

Verified: Rust tests (round trip, wrong passphrase, tampering, truncation, foreign input, limits, and interop with the age 1.1.1 CLI both ways), the Android build, and the TypeScript checks. The macOS CI job verifies the iOS build.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​age@​0.11.5
	cargo/​sha2@​0.10.9

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.

Priority	Alert  (click "▶" to expand/collapse)	Action
	License policy violation: cargo self_cell License: LicenseRef-GPL-2.0-only-vsftpd-OpenSSL - The applicable license policy does not permit this license (5) (self_cell-1.3.0/LICENSE-GPLv2) From: rust/Cargo.lock → cargo/age@0.11.5 → cargo/self_cell@1.3.0 ℹ Read more on: This package | This alert | What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/self_cell@1.3.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
	Potential security risk (AI signal): cargo age is 96.0% likely risky Notes: The artifact is not executable source code and does not itself demonstrate malware. However, it exposes an AGE private key and a plaintext file key (YELLOW SUBMARINE), creating a serious confidentiality and credential-compromise risk. Revoke or rotate the AGE identity and file key, remove them from package contents and version history, and inspect the decrypted payload separately before use. Confidence: 0.96 Severity: 0.78 From: rust/Cargo.lock → cargo/age@0.11.5 ℹ Read more on: This package | This alert | What are AI-detected potential security risks? 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: An AI system identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/age@0.11.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
	Potential security risk (AI signal): cargo block-buffer is 96.0% likely risky Notes: No malicious behavior or supply-chain attack indicators are present. The code contains potentially serious unsafe-code defects: a lazy-path integer underflow for nonempty inputs shorter than one block, and insufficiently demonstrated alignment/layout validity when reinterpreting bytes as Block<N>. These issues should be fixed or proven with stronger invariants before use with untrusted input. Confidence: 0.96 Severity: 0.72 From: rust/Cargo.lock → cargo/age@0.11.5 → cargo/sha2@0.10.9 → cargo/block-buffer@0.10.4 ℹ Read more on: This package | This alert | What are AI-detected potential security risks? 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: An AI system identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/block-buffer@0.10.4. 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

View full report