These repos seem more different compared to the repositories that updatecontrib currently tracks, which are primarily golang.org/x repos with Go code. (The proposal repository is a notable exception in that it doesn't have much Go code at all.)

vscode-go is primarily written in TypeScript, does not reuse the same license as in the Go repository, and has its own contribution guide. Is it desirable for its contributors to be automatically added to the Go repository's CONTRIBUTORS file? CC @hyangah for input.

vulndb is currently described as "Neither the code, nor the data, nor the existence of this repository is to be considered stable until an approved proposal." so perhaps we need to wait for that to change before considering next steps, but CC @rolandshoemaker and @FiloSottile for early input.

Agree that vscode-go is distinct from other Go projects even though vscode-go follows the same contribution guide as the other Go projects

• uses a different language
• the project was transferred later in its lifetime
• uses a different license

So, it's unnecessary to share the CONTRIBUTORS file.
For vscode-go project, the git history will be the best source of truth, and we acknowledge the contributors in its CHANGELOG for every release.

Thanks for the input @hyangah.

We've reached the decision that neither of these repositories will be used to seed contributor data. Thank you for the feedback, this has been helpful in clarifying what should seed the data.