https://pkg.go.dev/license-policy has quite a bit of helpful wording, including:

If you use a package whose license is not detected, please inform the package author. If you are a package author who believes a license for one of your packages should have been detected and was not, please check for discrepancies between your license and the official text. If you still believe there is an error, please file an issue.

I would like to see a bit more information about what kinds of licenses are acceptable for pkgsite. For example, I can think of two cases where it is unlikely that pkgsite would add a particular license:

• If the license does not allow redistribution of the code, as this could cause problems with e.g. rendering examples
• If the license is entirely bespoke for one or few Go modules which aren't popular - I imagine that lawyers reviewing new licenses is expensive, and that doesn't scale if thousands of Go users write their own licenses from scratch

Moreover, it seems like a license being recognized by the Open Source Initiative is a significant factor, but this is not documented either.

It's also unclear to me if a license being recognized by OSI is a requirement or not. If it's not a requirement, do we still require licenses to include some OSS freedoms such as read/study/redistribute? If so, that should be documented as well.

cc @jba @hyangah