feat: integrate dependency health v2 provider and tree models#45
Closed
DevonL wants to merge 1 commit into
Closed
Conversation
10 tasks
Contributor
There was a problem hiding this comment.
Pull request overview
This PR integrates dependency health v2 provider and tree models by adding comprehensive support for parsing lockfiles from 14 different package managers (npm, Python, Maven, Gradle, Go, Cargo, Ruby, Docker, NuGet, Dart, Composer, Helm, Swift, Hex) and analyzing upstream dependency availability through Cloudsmith repositories.
Changes:
- Added lockfile parsers for 14 package management ecosystems with proper dependency extraction and tree building
- Introduced upstream gap analysis to identify missing dependencies in upstream proxies
- Created registry endpoint builders for direct package verification across multiple registries
- Refactored duplicate code in upstreamChecker.js into shared module-level functions
- Updated manifestParser.js to use new shared utility functions for consistent path validation
Reviewed changes
Copilot reviewed 65 out of 78 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| util/upstreamGapAnalyzer.js | New analyzer for upstream dependency availability with progress tracking and concurrency control |
| util/upstreamChecker.js | Refactored to extract helper functions (isCacheObjectRecord, getUpstreamRequestOptions, isWarningWorthyUpstreamFormatError) into module-level shared functions |
| util/registryEndpoints.js | New comprehensive registry endpoint builder supporting 15+ package formats with custom URL strategies |
| util/lockfileResolver.js | New orchestrator for lockfile detection and parsing across multiple ecosystems |
| util/lockfileParsers/shared.js | New shared utilities (pathExists, readUtf8, readJson, buildTree, etc.) for parser implementations |
| util/lockfileParsers/*.js | 14 new parsers (npmParser, pythonParser, mavenParser, gradleParser, goParser, cargoParser, rubyParser, dockerParser, nugetParser, dartParser, composerParser, helmParser, swiftParser, hexParser) for ecosystem-specific lockfile parsing |
| util/manifestParser.js | Updated to use shared utility functions for file reading and path validation |
Files not reviewed (2)
- test/fixtures/npm/package-lock.json: Language not supported
- test/fixtures/npm/pnpm-lock.yaml: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
cecf115 to
000c05a
Compare
000c05a to
52bb976
Compare
Collaborator
Author
|
Retargeting base branch to PR #42. Reopening as new PR. |
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📄 Summary
Resolution of transient dependencies
🔍 Related Issues
Link to any related GitHub issues (e.g.,
Fixes #12,Closes #34):🧪 Type of Change
Please check the relevant type tag for this PR title:
[FIX]Bug fix[NEW]New thing[REFACTOR]Internal changes such as code restructuring or optimization that does not alter functionality[DOC]Documentation-only changes[CHORE]Maintenance, cleanup, or CI configuration🧪 How Has This Been Tested?
Describe how you tested your changes. Include CI runs, local tests, manual verification, or screenshots if applicable.
📸 Screenshots (if applicable)
If UI or logs are affected, include before/after screenshots or output.
✅ Checklist