First: An "internal package" is created when two versions of a package must be installed at the same time due to library dependencies. This happens from time to time when upgrading packages with `pkg_add -u` after upgrading the OS; either from -release to -release or from -current snapshot to snapshot. Here's an example:
I have libreoffice installed, which has a library dependency on poppler. I have two versions of the poppler package installed. The internal package, which is just the library portion of poppler-24.01.0, and the full package of poppler-24.02.0:
Code:
.libs1-poppler-24.01.0 Stub libraries for .libs-poppler-24.01.0
poppler-24.02.0 PDF rendering library
The package of libreoffice I have installed was built from ports when poppler was still at version 24.01.0, and those matching library components in /usr/local/lib/libpoppler.so.76.0 must remain available for libreoffice to use. The newer version of poppler, including the newer libpoppler.so.77.0 library, is needed by other installed applications, such as gimp.
These internal packages can be deleted, along with other unneeded automatically installed dependencies, when no longer needed, by using `pkg_delete -a`.
Second: Built-in applications are part of a cohesive OpenBSD release. While individual applications brought in from third party sources may have displayable version numbers, there is no specific tool to list them all.