Consider feature to allow a package to declare itself as a fork of another package
Link backs to the original isn't controversial, but links from original to forks could be used for spam.
I guess we can look at github. It has a way to view forks, but hidden quite away, so it doesn't feel very spammy
Thought: Could we somehow detect forkyness via the github api (for packages with a repository link)...
I wouldn't rely on github api for forkyness, as you could just create a new repository with a full copy, and github wouldn't really link to the original content in any way.
However, I'm not sure if this should be a structured feature of pub.dev. Forks on github server an integrity purpose for interacting between different repositories, using pull requests. Forks on pub.dev are merely an indication that the package used the code base of another package at one point, but may have diverged from it a lot. This information is important while the divergence is small, but has very little importance later. I think putting it into the README.md in a free form may be good enough for most practical use cases.