fix: handling buffer with node or browser

[jaredwray]

Please check if the PR fulfills these requirements

• Followed the Contributing guidelines and Code of Conduct
• Tests for the changes have been added (for bug fixes/features) with 100% code coverage.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
fix: handling buffer with node or browser

[gemini-code-assist]

Code Review

This pull request removes the global Node.js type dependency by refactoring the getOrgIdFromPublicKey method to use globalThis.atob when available, falling back to a dynamically resolved Buffer. A review comment suggests a more robust implementation for the Buffer fallback to prevent runtime errors in environments where Buffer might be present but missing the from method.

[gemini-code-assist]

The current implementation for detecting and using Buffer is quite verbose and potentially unsafe. If globalThis.Buffer exists but does not have a from method (e.g., in certain polyfilled environments or very old Node.js versions), nodeBuffer?.from(...) will attempt to call undefined as a function, leading to a runtime error. A more robust and concise approach would be to use optional chaining on the method call itself and check the type of atob more strictly.

const decoded = typeof globalThis.atob === "function"
				? globalThis.atob(keyWithoutPrefix)
				: (globalThis as any).Buffer?.from?.(keyWithoutPrefix, "base64")?.toString() ?? "";