Missing input validation in pixelToBits() leads to undefined behavior and invalid bitmap generation

The pixelToBits() function in PixelToBitmapAPELib lacks input validation to ensure the pixel parameter is within the valid range (0 to MAX_PIXEL_NUMBER = 98,279). While the function documentation states it accepts pixels "0 to MAX_PIXEL_NUMBER", there is no runtime check to enforce this constraint.

The function is declared public, making it accessible to any external caller, including future integrations, off-chain tools, and other contracts that may not implement proper input validation.

Add input validation to pixelToBits():

function pixelToBits(uint32 pixel) public pure returns (uint32 bitmap) {
    // Add input validation
    if (pixel > MAX_PIXEL_NUMBER) revert InvalidInputNumber();

    // ... rest of function
}

Golden Grid: Acknowledged.

Zealynx: Advised to implement it for extra caution.