There are at least 2 distributions that are in core and that define 'cuckoo packages': packages that don't have their own .pm, but are defined in another. For example Test-Simple contains Test::Builder::Tester::Tie which is defined in Test::Builder::Tester, and Pod-Parser defines 9 such packages. See: https://metacpan.org/release/Test-Simple https://metacpan.org/release/Pod-Parser For these dists, the regular modules are listed recognised as being core in Module::CoreList, but the cuckoo packages aren't. This causes a problem if you do something like the following: Build a list of all packages associated with a dist, by parsing 02packages.details.txt Lookup all packages in Module::CoreList to decide if the dist is core, and if so, look at upstream to see whether upstream is 'cpan'. Obviously there are additional hoops I could jump through, to identify these cases, but I think that Module::CoreList should include the cuckoo packages as well, so that things 'match up'. Before I put the time in, if I identified all such dists and modules, and patched Module::CoreList, I want to check whether such a patch would in principle be accepted? Cheers, NeilThread Next