Skip to content

Conversation

@cb1kenobi
Copy link
Contributor

@cb1kenobi cb1kenobi commented Nov 10, 2025

Status:

  • Android
    • Detect SDKs
    • Detect NDKs
    • AVD wrapper
    • Detect emulators and devices
    • Install apps on emulator/device
    • Emulator controls (start, stop, check booted, etc)
    • Track devices
  • Babel plugins
    • Global this
    • Titanium API
  • iOS
    • Detect certs
    • Detect devices (node-ios-device wrapper)
    • Detect keychains
    • Detect provisioning profiles
    • Detect simulators
    • Simulator controls (start, stop, etc)
    • Detect teams
    • Detect Xcode
    • Track devices
  • JDK
    • Detect JDKs
  • Titanium
    • Detect SDKs
    • Detect modules
    • Detect OS info
    • JS analyzer
    • tiapp.xml parser
  • Utils
    • Capitalize
    • Expand path
    • Is file/dir
    • Load Titanium SDK's manifest.json
    • plist library
    • png image info
    • Resize image
    • Suggest helper
    • Unzip helper
    • Version library
    • XML helper

@cb1kenobi cb1kenobi changed the title Refactor to ESM v7 - ESM refactor, consolidate node-appc, titaniumlib, etc Dec 4, 2025
@socket-security
Copy link

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 oxlint is 97.0% likely obfuscated

Confidence: 0.97

Location: Package overview

From: 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.

Warn High
Obfuscated code: npm vite is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: pnpm-lock.yamlnpm/[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.

View full report

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