We are, and we're talking to them. In an ideal world we would have loved to have merged the databases.

I expect the two databases will move in sync. The GitHub advisory database is licensed as CC BY 4.0 (i.e., attribution only), so we actively encourage others, including the Go Vulnerability Database, to pull from it.

I was also wondering about this — I feel like it was just a couple of weeks ago that I read about the Go team's new unified vulnerability schema/Open Source Vulnerabilities (OSV) database

Definitely a step in the right direction on both ends, though!

https://osv.dev/list

https://security.googleblog.com/2021/06/announcing-unified-v...

https://opensource.googleblog.com/2021/02/launching-osv-bett...