BabyElon - Audit 1

In the contract `BabyElon` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and the following: - function `setNoFeeWallet`: to make an `address` included or excluded from fees. - function `changeLpPair`: to add a `newPair` address as Lp pair addresses. - function `toggleCanSwapFees`: to set the `canSwapFees` to `true` or `false`. - function `changeWallets`: to set the new `marketingAddress` to receive all the fees in the contract which have been converted to BNBs in the `internalSwap()`. - function `setPresaleAddress`: to set an address out of or in the presale addresses list and include or exclude from the fees. - function `enableTrading`: to enable the trading process. - function `zeroLimits`: to set avoidMaxTxLimits to true and set maxWallet to totalSupply - function `changeMaxWallet`: to set `maxWallet`  In the contract `Ownable` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and: - function `transferOwnership`: to change the `owner` to another address. - function `renounceOwnership`: to set the `owner` address to zero. 

According to the following code in the constructor: ```solidity _approve(msg.sender, address(swapRouter), type(uint256).max); ``` The contract approves the max value from the `msg.sender` to `address(swapRouter)` which seems to serve no purpose but have potential risks, we would like to confirm with the client the design of the code and whether it is redundant.