Skip to content

Conversation

@AswinAsok
Copy link
Contributor

@AswinAsok AswinAsok commented Jan 7, 2026

No description provided.

@AswinAsok AswinAsok marked this pull request as draft January 7, 2026 06:19
@socket-security
Copy link

socket-security bot commented Jan 7, 2026

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 High
Obfuscated code: npm libheif-js is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: ?npm/[email protected]npm/[email protected]

ℹ 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 [email protected].

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/[email protected]. 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 High
Obfuscated code: npm zxcvbn is 98.0% likely obfuscated

Confidence: 0.98

Location: Package overview

From: web/packages/accounts/package.jsonnpm/[email protected]

ℹ 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 [email protected].

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/[email protected]. 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

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ad53435a89

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@socket-security
Copy link

socket-security bot commented Jan 7, 2026

@AswinAsok AswinAsok marked this pull request as ready for review January 8, 2026 08:38
@anandbaburajan
Copy link
Member

  • Lint is failing
  • Current naming is: Himalayas On Cycle - 1K KM to Leh (17 files)-4. Let's do Himalayas On Cycle - 1K KM to Leh (Part 4 - 17 files) and the first one should have "Part 1" as well
  • I tried download two albums, and in both of them, a few files failed. I clicked the retry button in both of them and the failed files in both of them successfully downloaded. Which makes me curious, why were the files failing at all? I briefly checked those few files, and didn't find anything weird about them. Note that the two albums were large (200+ photos)
  • I tried one of those albums again and didn't get any failed files :D
  • When clicking download on an album, the notification/toast says "Downloading ... 34/232 files" but since nothing is being downloaded until the zip is ready, it might be confusing. We could say "Processing" maybe? Not sure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants