For me, it does appear, but as search result 79:

(Nobody clicks to page 8, though, so this is effectively the same as not showing up at all.)

Just observing the results it looks like it's fuzzy-matching "packages" to "package" and then matching ~every package that exists due to the word "package" appearing in the package description:

Package log implements a simple logging package.

Package fmt implements formatted I/O with functions analogous to C's printf and scanf.

Ideally the fact that the exact search string "packages" matches the package name exactly as well as the last segment of the import path would cause the go/packages result to rank much more highly; ideally as the first result.

seems to be worse now, we get a random selection of standard library packages.

Duplicate of #41369