-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature] Update deps.dev collector to take advantage of the new API #1768
Comments
@rakshitgondwal would you be interested in working on this? |
@rakshitgondwal have you started any work on this? If not, @nathannaveen would like to take it over. |
Hi @pxp928, nope I didn't get the time to do so, and sure someone else can take this over. |
Hey @pxp928, could I work on this? |
Recently I have been working on this issue, and realize that since the deps.dev For example, when doing a purl batch lookup https://docs.deps.dev/api/v3alpha/#purllookupbatch, if any of the repos passed to the batch request aren't contained in the deps.dev database, it returns So the only way to check whether a purl is contained in the deps.dev database is to manually do a This issues will probably disappear when the Additionally, we directly use the Line 27 in dad65eb
The issue with this, is that Note that I didn't realize we directly use the So I think the best way to go about this is to wait for the version to become stable and then implement it. If you want to run some tests, this is the batch request that will return nil: main...nathannaveen:guac:nathan/depsdevNewAPI#diff-82819d87163ba23dd5d158849f788068d5eadd6e1818517c879ec08b0745131cR455 |
Is your feature request related to a problem? Please describe.
With the new release of the API for deps.dev -> https://blog.deps.dev/api-v3/
purl
when querying for information (no need to decompose the purl as we are currently doing)guac/pkg/handler/collector/deps_dev/deps_dev.go
Lines 401 to 419 in e283206
Describe the solution you'd like
upgrade the current deps.dev collector to use the latest API features
The text was updated successfully, but these errors were encountered: