Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

brave / brave-core Public

Notifications You must be signed in to change notification settings
Fork 904
Star 2.6k

Code
Pull requests 238
Actions
Security
Insights

Additional navigation options

Code
Pull requests
Actions
Security
Insights

Enabling CRLSets; Capping the maximum component updates per request to go-updater to 1#1581

Merged

jumde merged 5 commits intomasterbrave/brave-core:masterfrom crlsetsbrave/brave-core:crlsetsCopy head branch name to clipboard

Mar 18, 2019

+759-192

Conversation Commits5 (5)Checks Files changed

Commits

Commits on Mar 15, 2019

Issue 518: Enabling CRLSets
jumde
committed
Lint fixes
jumde
committed
Issue 3615: Updating component updater to send one extension update per request.
jumde
committed
1. We should match only against CRLSet URLs instead of CRLSet hosts
jumde
committed
Reverting go-updater dev endpoint
jumde
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.