You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@pombredanne, suppose we collected and indexing all the crates from Crates.io. Once we have all crates indexed, could you clarify the next steps? Should we focus on setting up querying functionality, integrating the index into PurlDB, or enriching the data in any particular way? Any guidance on priorities or additional requirements would be greatly appreciated!
suppose we collected and indexing all the crates from Crates.io. Once we have all crates indexed, could you clarify the next steps? Should we focus on setting up querying functionality, integrating the index into PurlDB, or enriching the data in any particular way? Any guidance on priorities or additional requirements would be greatly appreciated!
Getting the index is straightforward, this is just a git repo. With this the steps would be:
For batch operations:
Parse the index and populate the PurlDB with basic cargo packages
For one package from 1., further collect detailed metadata from the API
For one package from 2., further integrate the download and scan of the crate code
For the on-demand API endpoint:
For one package PURL as an input, do the 2. and 3. from above, on demand
This would establish the data in PurlDB to collect, index, match and have a comprehensive references for all the crates.
In terms of priority, the on-demand operations are likely higher priority to get some results fast to than the full batch operations that come afterwards. Unless Batch 1. is really easy, which it may be.
We need to collect all the crates and index them.
There is an API on crates.io and also a git repo with an index:
The text was updated successfully, but these errors were encountered: