AOSP and Google list are split it misleading ways #1123
Description
[note] not sure if you consider this a bug, but I wasn't quite sure which category to pick
some com.google.android.* packages are actually part of AOSP (and in fact open source, at least upstream), and the reason they are in a com.google package is (to my understanding) that this signifies that Google "owns" them, and an OEM is not supposed to change them in any way (unlike most AOSP code, where changes are generally allowed as long as the CTS still passes). These packages should therefore be in the AOSP list, or possibly in a separate list, but it's very much misleading for them to be in the Google list along actual spyware.
I don't have a list of which are which, but it should be reasonably trivial to check for each package in the Google list if the sources for it are available in AOSP (since such sources are going to contain the package ID at minimum inside the manifest)