BUILD NOTE
Browser games often include more than one kind of material: original code, generated or hand-made art, open-source libraries, fonts, sounds, and build tooling. Even when a project is small, credits and notices should be easy to find. Clear attribution protects the project and helps visitors understand what is original to the lab.
Practical note
There are two useful places for credits. The first is inside the game, where a menu or license area can travel with the playable build. The second is the project page, where a short credits section can explain that the public copy, screenshots, and maintenance notes are original to Diligesker’s Lab while included libraries remain governed by their own licenses.
Credits should not be a dumping ground for every development detail. They should focus on what a visitor or reviewer needs to know: where the playable build is hosted, whether third-party libraries are used, and where license information can be checked. If the game changes, the credit note should be reviewed too.
This approach is practical for WordPress-hosted games. The page stays readable, the game retains its own license area, and the site avoids the impression that project descriptions are copied from a marketplace or another source.