-
Notifications
You must be signed in to change notification settings - Fork 6
Fix/Bitbucket Integration Issues. #27
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
Merged
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
60846db
Add GitLab-com Provider Type and Gitea Guide Link
Amazing-Stardom 02fff3f
Merge branch 'loc-pricing' into fix/github-connector
Amazing-Stardom be3889c
Refine LLM Error Handling and Gitea Patch URL Generation
Amazing-Stardom 0ebdf2d
Implement Bitbucket Comment Posting
Amazing-Stardom 12a730f
Merge branch 'loc-pricing' into fix/github-connector
Amazing-Stardom 2fdfd15
Refactor Bitbucket API Interactions
Amazing-Stardom 7bb843d
Fix Diff Line Identification and Implement Bitbucket Comment Fallback
Amazing-Stardom ef1d5ee
Refine Diff Line Processing and Bitbucket Comment Threading
Amazing-Stardom 85a4af9
Refactor Bitbucket API Interactions
Amazing-Stardom 4cf51b4
Merge branch 'loc-pricing' into fix/github-connector
Amazing-Stardom 3138489
Refactor Bitbucket Artifact Context Propagation
Amazing-Stardom c153351
Refactor Diff Hunk Line Parsing
Amazing-Stardom cbc34ca
Standardize Bitbucket API Interactions
Amazing-Stardom fbdcfc7
Merge branch 'master' into fix/github-connector
Amazing-Stardom 796ed7b
Update PostCSS Ecosystem Dependencies
Amazing-Stardom 70ac543
Refactor Line Parsing for Delimiter Robustness
Amazing-Stardom File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,76 @@ | ||
| # How to fix OSV scanner vulnerabilities | ||
|
|
||
| This document describes how to run the same security scan locally and how to fix the vulnerabilities. | ||
|
|
||
|
|
||
| ## How to run OSV scanner Localy | ||
|
|
||
| Generate a security report by running the following command: | ||
|
|
||
| ```bash | ||
| make security-osv | ||
| ``` | ||
|
|
||
| The `make security-osv` Makefile target runs `osv-scanner` recursively across the repository and writes a dated JSON report to `security_issues/`. | ||
|
|
||
| The output of the scan is: | ||
|
|
||
| ``` | ||
| Scanning dir . | ||
| Warning: plugin transitivedependency/pomxml can be risky when run on untrusted artifacts. Please ensure you trust the source code and artifacts before proceeding. | ||
| Starting filesystem walk for root: / | ||
| Scanned /home/gk/hex/LiveReview/go.mod file and found 148 packages | ||
| Scanned /home/gk/hex/LiveReview/internal/prompts/vendor/cmd file and found 0 packages | ||
| Scanned /home/gk/hex/LiveReview/extension/livereview/package-lock.json file and found 378 packages | ||
| Scanned /home/gk/hex/LiveReview/ui/package-lock.json file and found 1287 packages | ||
| End status: 407 dirs visited, 1971 inodes visited, 4 Extract calls, 602.472549ms elapsed, 602.472606ms wall time | ||
| Wrote security_issues/osv-scanner-05-04-2026.json | ||
| Updated security_issues/osv-scanner-latest.json | ||
| ``` | ||
|
|
||
| So, osv-scan report will be generaed. | ||
|
|
||
| This report will have all the vulnerabilities found in the repository. | ||
|
|
||
| Ideally, the report should be empty. | ||
|
|
||
| ```json | ||
| { | ||
| "results": [], | ||
| "experimental_config": { | ||
| "licenses": { | ||
| "summary": false, | ||
| "allowlist": null | ||
| } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
|
|
||
| ## How to fix vulnerabilities | ||
|
|
||
| 1. Select the osv-scanner report. | ||
| 2. Add to AI prompt and ask to fix the vulnerabilities. | ||
| 3. AI will fix the vulnerabilities by updating the dependencies. | ||
| 4. Run `make security-osv` again to verify that the vulnerabilities are fixed. | ||
| 5. If vulnerabilities are still present, repeat the process by actually looking into each vulnerability and fix it manually. | ||
|
|
||
| ## Verify the fix | ||
|
|
||
| If all vulnerabilities are fixed, the `make security-osv` command will not find any vulnerabilities and the report will be empty. | ||
|
|
||
| ```json | ||
| { | ||
| "results": [], | ||
| "experimental_config": { | ||
| "licenses": { | ||
| "summary": false, | ||
| "allowlist": null | ||
| } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| Now Verify by running ui, server and extension. | ||
| This is for local verification wheather the change in package.json or go.mod is correct or not. | ||
|
|
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.