Add utility functions for various operations

[anto-deepsource]

No description provided.

[deepsource-development]

DeepSource Code Review

We reviewed changes in f21fc03...391ce4a on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Focus Area: Reliability

Security   Reliability   Complexity   Hygiene

Feedback

Control-flow and dead-code patterns

• Several issues are about code that can never run or always behaves one way: if (false), assignment in condition, statements after break, debugger halting execution.
• Worth scanning these utilities for “does this line ever execute / change anything?” to catch multiple problems in one pass.

Fundamental JS semantics in utility helpers

• Many findings are basic JS semantics: var scoping, Math as an object, undeclared variables, multiline expressions, hasOwnProperty usage.
• Since this is a utilities file that others will lean on, tightening these fundamentals now will pay off across anything that depends on them.

Code Review Summary

Analyzer	Status	Updated (UTC)	Details
JavaScript		Feb 12, 2026 11:54a.m.	Review ↗
Secrets		Feb 12, 2026 11:54a.m.	Review ↗

---

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

[deepsource-development]

`else` after `return` is redundant and verbose

The code snippet shows a console.log inside an else block that is redundant if the preceding if block returns or otherwise exits control flow. Such else blocks increase code nesting and reduce readability.
Remove the else block by placing its contents after the if block to simplify control flow and reduce nesting.

[deepsource-development]

Declared variable unused causes confusing code and minor slowdown

The parameter x in function isEven(x) is never referenced or used, indicating a likely incomplete implementation or refactoring oversight. This causes confusion and may degrade performance slightly due to unused memory allocation.
Remove or use the parameter x appropriately to clarify functionality and optimize code execution.

[deepsource-development]

Undeclared variable `x` causes runtime ReferenceError

The variable x used inside the console.log statement is not declared or defined anywhere visible, causing a ReferenceError at runtime which will stop JavaScript execution and break functionality.
Declare x before its usage using let, const, or var, or ensure it is properly imported or passed as a parameter to avoid runtime failures.

[deepsource-development]

Unnecessary `else` block after `return` causes clutter

When an if block contains a return statement, the subsequent else block is redundant because the flow will exit on the return. Keeping an else block causes unnecessary nesting and reduces code clarity. Remove the else block and place its contents after the if block instead to improve readability.

[deepsource-development]

Using undeclared `x` causes runtime ReferenceError

The variable x is used in a template literal expression for console output without being declared or defined anywhere, leading to runtime failure with ReferenceError if x is not in scope or global. This issues critical failures in JavaScript execution environment.

Declare x before usage, for example with let x = value; or ensure x is imported or passed as a parameter to avoid the ReferenceError and enable proper runtime behavior.

[deepsource-development]

Undeclared `iv` used in `createCipheriv` causes runtime errors

The code calls crypto.createCipheriv('aes-192-ecb', Buffer.from(ENCRYPTION_KEY), iv) where iv is not declared or initialized anywhere in the snippet. This will cause a ReferenceError when the code executes, breaking encryption functionality.

Declare and initialize the iv variable before using it, or remove it if the cipher mode does not require an initialization vector.

[deepsource-development]

Declared variable `str` is never used

The function isMatched declares the parameter str but does not use it anywhere in the function body, which indicates an unused variable issue. This can cause confusion for maintainers and might hint at incomplete implementation or refactoring.

Remove the unused parameter str from the function signature or implement its intended usage to resolve the issue.

[deepsource-development]

Accessing undeclared `process` causes ReferenceError

Using the undeclared variable process leads to a ReferenceError when that code executes because JavaScript cannot find a defined binding for it. This stops script execution and causes failures.

Declare or import process before usage or ensure it is globally defined in the environment to prevent runtime errors.

[deepsource-development]

Assignment `=` used instead of comparison `==` or `===`

The if condition uses a single equals sign (=), which is an assignment operator, not a comparison operator. The expression x = 2 assigns the value 2 to x and evaluates to 2, which is a truthy value. This means the condition will always be true, and the else branch will never be reached.

Replace the assignment operator = with a comparison operator, such as == for loose equality or === for strict equality, to correctly compare x with 2.

[deepsource-development]

`Math` is a static object, not a function or constructor

The code attempts to call Math as a function or constructor (Math()). However, Math is a built-in JavaScript object that provides static properties and methods, and it cannot be invoked. This will result in a TypeError at runtime, crashing the function.

Access properties and methods directly on the Math object. For example, to get the value of PI, use Math.PI instead of math.PI.