READ FIRST: status update

[ChALkeR]

Some status updates:

1. The latest dataset is uploaded to https://gzemnid.nodejs.org/datasets/out.2019-06-04/
2. npm, Inc removed both byField view from the replicate host and shut down skimdb host completely, so gzemnid fetch is broken atm.
3. that will be fixed with proper replication (Replace 'fetch' with an npm registry follower. #26), but I observed some inconsistencies there, still investigating.
4. gzemnid sync now mirrors the whole replicate changes stream to ./pool/replicate, in lz4-packed chunks, and now uses all_docs instead of main_only. That would likely replace broken gzemnid fetch soon. Expected cache size for replicate stream is about 3-5 GiB.

[DanielRuf]

So gzemnid is not usable for now? Might be good because so far npmjs still provides 0 information like IoCs and so on when they remive a malicious package and you have no information what you have to look for.