Skip to content

Check trusted location before from_webstore in chromiumSideloaded - #50770

Merged
juan-fdz-hawa merged 1 commit into
mainfrom
50706-ai_tools-chromiumsideloaded-misclassifies-legitimate-browser-components
Aug 7, 2026
Merged

Check trusted location before from_webstore in chromiumSideloaded#50770
juan-fdz-hawa merged 1 commit into
mainfrom
50706-ai_tools-chromiumsideloaded-misclassifies-legitimate-browser-components

Conversation

@juan-fdz-hawa

@juan-fdz-hawa juan-fdz-hawa commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Resolves #50706

Screenshot 2026-08-07 at 12 18 44 PM

chromiumSideloaded returned true as soon as from_webstore was 0, never reaching the trusted-location check. First-party browser components are installed by the browser itself and so always report from_webstore:false, which made the location exemption unreachable and flagged components like Edge Copilot Bridge as sideloaded_unverified.

Check location for Internal/Component first. The existing collector fixture asserted the buggy behaviour and is updated to a genuinely sideloaded location, with a first-party component case added.

Checklist for submitter

If some of the following don't apply, delete the relevant line.

Testing

  • Added/updated automated tests
  • QA'd all new/changed functionality manually

For unreleased bug fixes in a release candidate, one of:

  • Confirmed that the fix is not expected to adversely impact load test results

Summary by CodeRabbit

Bug Fixes

  • Improved Chromium extension risk detection across Web Store and installation locations.
  • Trusted internal and component extensions are no longer incorrectly flagged as sideloaded.
  • Unknown, unpacked, and external extensions continue to be identified appropriately.
  • Improved handling of first-party components with broad host permissions, while preserving relevant risk indicators.

@juan-fdz-hawa

Copy link
Copy Markdown
Contributor Author

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor
✅ Action performed

Full review finished.

@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 2e5225ec-b553-4e53-990e-6047d30b40dd

📥 Commits

Reviewing files that changed from the base of the PR and between d2352ed and e287ab9.

📒 Files selected for processing (2)
  • orbit/pkg/table/ai_tools/internal/browserext/browserext_test.go
  • orbit/pkg/table/ai_tools/internal/browserext/risk.go
🚧 Files skipped from review as they are similar to previous changes (2)
  • orbit/pkg/table/ai_tools/internal/browserext/risk.go
  • orbit/pkg/table/ai_tools/internal/browserext/browserext_test.go

Walkthrough

The change updates Chromium extension classification so trusted internal and component locations are not marked as sideloaded, regardless of from_webstore. Tests add trusted and nontrusted location cases, extend the Chromium profile fixture with a first-party component, and verify that the component is recovered without the sideloaded_unverified risk flag.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the primary code change: checking trusted Chromium locations before from_webstore.
Description check ✅ Passed The description identifies the issue, explains the fix, references the linked issue, and documents automated testing, QA, and load-test impact.
Linked Issues check ✅ Passed The changes satisfy issue #50706 by prioritizing trusted locations, preserving untrusted-location detection, and adding regression tests.
Out of Scope Changes check ✅ Passed The changes are limited to chromiumSideloaded logic and related regression tests required by issue #50706.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 50706-ai_tools-chromiumsideloaded-misclassifies-legitimate-browser-components

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codecov

codecov Bot commented Aug 7, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.41%. Comparing base (12754cc) to head (e287ab9).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #50770   +/-   ##
=======================================
  Coverage   68.40%   68.41%           
=======================================
  Files        3963     3963           
  Lines      255174   255174           
  Branches    13616    13616           
=======================================
+ Hits       174555   174568   +13     
+ Misses      65020    65011    -9     
+ Partials    15599    15595    -4     
Flag Coverage Δ
backend 69.61% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Resolves #50706

chromiumSideloaded returned true as soon as from_webstore was 0, never
reaching the trusted-location check. First-party browser components are
installed by the browser itself and so always report from_webstore:false,
which made the location exemption unreachable and flagged components like
Edge Copilot Bridge as sideloaded_unverified.

Check location for Internal/Component first. The existing collector
fixture asserted the buggy behaviour and is updated to a genuinely
sideloaded location, with a first-party component case added.
@juan-fdz-hawa
juan-fdz-hawa force-pushed the 50706-ai_tools-chromiumsideloaded-misclassifies-legitimate-browser-components branch from d2352ed to e287ab9 Compare August 7, 2026 16:15
@juan-fdz-hawa
juan-fdz-hawa marked this pull request as ready for review August 7, 2026 16:19
@juan-fdz-hawa
juan-fdz-hawa requested a review from a team as a code owner August 7, 2026 16:19
@juan-fdz-hawa
juan-fdz-hawa merged commit 9cb3a5e into main Aug 7, 2026
56 checks passed
@juan-fdz-hawa
juan-fdz-hawa deleted the 50706-ai_tools-chromiumsideloaded-misclassifies-legitimate-browser-components branch August 7, 2026 19:39
juan-fdz-hawa added a commit that referenced this pull request Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ai_tools: chromiumSideloaded() misclassifies legitimate browser components as sideloaded_unverified

2 participants