Manifest mashup opportunity with Socket Registry

[jdalton]

👋 Socket.dev dev here. Also, the Lodash guy (please replace it with whatever promotes builtin stuff and simplicity). At Socket we've released the Socket Registry as a place to catalog our growing collection of overrides. We also have a @socketsecurity/registry package that exposes our manifest.json. I really like the idea of sharing and where possible consolidating. So figured you might be consume our manifest.json or give pointers to what kind of data you'd like tracked to make it more useful for others to consume.

[43081j]

Interesting work you are doing for sure

So if I understood correctly, you do very similar to this repo but we use codemods while you use overrides

The actual detection and manifests are very similar I think

There should be some way we can work together, otherwise it is a lot of duplicated work. I'll have a think but it may also be worth us having a catch up call around this one day

[jdalton]

@43081j

Interesting work you are doing for sure

So if I understood correctly, you do very similar to this repo but we use codemods while you use overrides

Yes. Codemods are where I'd like to go eventually. While evaluating solutions a few months back the wiring to replace the code wasn't in place (in this or another project that consumes this). The overrides route was a more ready-to-go approach as package managers support it out of the box.

There should be some way we can work together, otherwise it is a lot of duplicated work. I'll have a think but it may also be worth us having a catch up call around this one day

Great! In the meantime I'm taking inspiration from some of your field names (like "moduleName") and schema stuff (may help folks consume it) to align more closely.