feat: wire dependency health commands, report ui, and docs#46
Closed
DevonL wants to merge 1 commit into
Closed
Conversation
10 tasks
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request adds comprehensive dependency health scanning, transitive dependency analysis, and compliance reporting features to the VS Code extension. The changes include lockfile parsing for 14+ package ecosystems, upstream proxy gap analysis, dependency enrichment (vulnerabilities, licenses, policies), and UI components for displaying compliance reports.
Changes:
- Refactored
upstreamChecker.jsto extract helper functions and addgetActiveRepositoryUpstreamsForFormatmethod - Added new utility modules:
packageNameNormalizer.js,lockfileResolver.js, andupstreamGapAnalyzer.jsfor unified dependency and upstream handling - Refactored
manifestParser.jsto use shared utilities and remove duplicate fs code - Added 14 new lockfile parser modules and shared parsing utilities in
lockfileParsers/directory - All new source files include proper copyright headers
Reviewed changes
Copilot reviewed 73 out of 86 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| util/upstreamChecker.js | Refactored private methods into module-level functions and added new method for getting active upstreams for a format |
| util/manifestParser.js | Migrated from direct fs usage to shared utilities and refactored pyproject parsing |
| util/packageNameNormalizer.js | New module for normalizing package names across ecosystems |
| util/lockfileResolver.js | New module providing unified interface for detecting and resolving lockfiles |
| util/upstreamGapAnalyzer.js | New module for analyzing which dependencies are reachable via upstream proxies |
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.
3f423f8 to
252bacf
Compare
252bacf to
0d3f8b9
Compare
Collaborator
Author
|
Retargeting base branch to PR #45. Reopening as new PR. |
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
Completion of reporting UI and doc updates
🔍 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