Does AI plagiarize and take credit for work of others ?

Here's a function, done with an AI that revealed zero sources throughout.
I used AI to help me write this function last night. And, obviously, I guided it throughout the process to ensure I wasn't copying anyone else, so as not to violate other people's licenses.

It's my work. With the benefits of AI. I'd be very curious if any human being can conclude it is not original work, provided they can give at least some evidence that it may have been copied from other people's work (I'll settle for just fair plausibility, I'm not looking for extreme "beyond reasonable doubt" level of evidence). It shouldn't be too hard, there are several MAX7219 libraries on GitHub that AI might have copied from (or that humans could have directly copied from pre-AI).

void Max7219::setRamPixel(uint16_t x, uint16_t y, uint8_t pixelvalue) {
    uint16_t idx;
    uint8_t bitIdx;
    uint16_t linx, liny;
    // x position is 0..(8*mHorizQty - 1), y position is 0..(8*mVertQty - 1)
    if (mDisplayData == nullptr) return; // Ensure display data is initialized
    if (x >= 8 * mHorizQty || y >= 8 * mVertQty) return; // Validate x and y positions
    // each byte in mDisplayData represents a row of 8 pixels
    // transformation:
    // linx and liny represent the positions if the modules were all in a sigle line
    linx = (((mVertQty-1)-(y/8))*mHorizQty*8) + x;
    liny = (y % 8);
    // now do the calculations using the transformed linx and liny, i.e.
    // as if all modules were on a single 8x8 line
    idx = (linx/8) + (liny * mQty); // Calculate RAM byte index in the display data
    bitIdx = (uint8_t)(7 - (linx % 8)); //Calculate bit index within the byte, where most significant bit is at position 0
    if (pixelvalue) {
        mDisplayData[idx] |= (1 << bitIdx); // Set the pixel
    } else {
        mDisplayData[idx] &= ~(1 << bitIdx); // Clear the pixel
    }
}

And, incidentally, I can give fair evidence that it is my work (just so that the challenge is balanced, I'm not asking for anything unreasonable!).

This mostly happens when using Gemini Code Assist in VS Code. It highlights potential issues re licensing.

In my opinion, the best way around some of this minefield, is to place an acknowledgement in the header stating that the code was AI generated etc.

I'm using JetBrains IDEs, and just noticed they have a Gemini plug-in, I'll have to give it a try too.

Occasionally AI has been quite helpful with arrays such as the ones you show; I tend to 'force' my desired encoding for the first few values, and then it figures out the pattern from there, and continues it (not always successfully, but enough to help save time overall).

I'm also finding I'm commenting my code a lot better than pre-AI, since that acts as a guide too.

I'm using JetBrains IDEs, and just noticed they have a Gemini plug-in, I'll have to give it a try too.

Occasionally AI has been quite helpful with arrays such as the ones you show; I tend to 'force' my desired encoding for the first few values, and then it figures out the pattern from there, and continues it (not always successfully, but enough to help save time overall).

I'm also finding I'm commenting my code a lot better than pre-AI, since that acts as a guide too.