Upstream source information
I'll have to double check what the files look like from an API perspective, but in terms of having importmod be able to better handle pages containing multiple mods on NexusMod (e.g. openmw-mods#115 (closed), where we get a false positive due to a "misc mods" collection), perhaps the thing to do would be to have, in metadata.yaml, a field which you can use to specify the files which correspond to the mod in question.
upstream: source: type: nexusmods id: morrowind/47068 files: Container Ownership*
Where files is an fnmatch-style pattern.
Currently the type and id are implicitly derived in importmod from the HOMEPAGE or NEXUS_URL fields in the pybuild, but I'd rather not mix implicit and explicit information, so we can have them explicitly specified here too.
Side note: Could also include types such as modding-openmw so we can track changes to mod lists, though it's worth noting that portmod itself isn't actually going to use this, this is just to facilitate importmod, so we don't need to care about the value of type beyond the fact that it's a string.
upstream: source: type: modding-openmw id: list/expanded-vanilla