-
-
Notifications
You must be signed in to change notification settings - Fork 309
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Adds a new v2 importer pipeline to ingest CloudVulnDB advisories from the project’s public RSS feed, along with fixtures/tests and a pytest configuration tweak to avoid collecting setup.py in Docker.
Changes:
- Introduce
CloudVulnDBImporterPipelineand RSS parsing helpers to produceAdvisoryDataV2. - Register the new importer in the central importer registry.
- Add unit tests + RSS/XML and expected JSON fixtures; update pytest
addoptsto ignoresetup.pyduring collection.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| vulnerabilities/pipelines/v2_importers/cloudvulndb_importer.py | New CloudVulnDB RSS-based v2 importer implementation. |
| vulnerabilities/importers/init.py | Registers the new v2 importer in the importers registry. |
| vulnerabilities/tests/test_cloudvulndb_importer.py | Adds unit tests for RSS parsing and advisory ID derivation. |
| vulnerabilities/tests/test_data/cloudvulndb/cloudvulndb_rss_mock.xml | Adds mocked RSS fixture for deterministic tests. |
| vulnerabilities/tests/test_data/cloudvulndb/expected_cloudvulndb_advisory_output1.json | Adds expected AdvisoryDataV2 JSON output fixture. |
| pyproject.toml | Updates pytest collection options to ignore setup.py. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
159276b to
d964334
Compare
- add CloudVulnDB v2 importer pipeline - register importer - add tests and fixtures - ignore setup.py in pytest collection Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: Tushar Goel <tushar.goel.dav@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: Tushar Goel <tushar.goel.dav@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: Tushar Goel <tushar.goel.dav@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: Tushar Goel <tushar.goel.dav@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
...lines Signed-off-by: ziad hany <ziadhany2016@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: ziad hany <ziadhany2016@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: ziad hany <ziadhany2016@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: ziad hany <ziadhany2016@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Resolves: aboutcode-org#2186 Signed-off-by: Keshav Priyadarshi <git@keshav.space> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: Keshav Priyadarshi <git@keshav.space> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Resolves: aboutcode-org#2187 Signed-off-by: Keshav Priyadarshi <git@keshav.space> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: Tushar Goel <tushar.goel.dav@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: Tushar Goel <tushar.goel.dav@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: Tushar Goel <tushar.goel.dav@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: Tushar Goel <tushar.goel.dav@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: Tushar Goel <tushar.goel.dav@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
Signed-off-by: Tushar Goel <tushar.goel.dav@gmail.com> Signed-off-by: Tedsig42 <teddams047@gmail.com>
2be778e to
ce44242
Compare
@ziadhany
ziadhany
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Tednoob17 please fix the DOC, and see the comments below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To keep things simple, let’s split each importer into its own PR, but we should first double-check the quality of the data source.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please avoid unrelated changes to the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We already have a PR for importing enisa:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need to change this file? Is this vide-code? Please don't submit AI-generated code.
Add a new v2 importer for CloudVulnDB from the public RSS feed.
Changes
Testing