cc @Mo Zhu

I merged and deployed Zach’s patch to remove the service worker. We’ll see if it works!

Hi! Regarding running tests on windows, I've found that if you set an environment variable like

$Env:GTEST_FILTER='windows_eventlog.*'

you can run a single unit test. This feature is already documented, but only for Linux/macOs. I think it will be useful to include a a few lines explaining it on the windows section.

@seph did you perhaps miss checking in a couple of JSON files in https://github.com/osquery/osquery-site/pull/262/files? Or did the process change? Comparing with https://github.com/osquery/osquery-site/commit/e0ad36eb03172220859a72d2270a9ad83893a1e8 and expecting to see the schema and downloads JSON.

👀

@zwass ^^^ I did miss them in that PR.

Just deployed with ^^^^

#271 Bump json5 from 1.0.1 to 1.0.2 Pull request opened by dependabot[bot] Bumps json5 from 1.0.1 to 1.0.2. Release notes Sourced from json5's releases.

v1.0.2

• Fix: Properties with the name

__proto__

are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295). This has been backported to v1. (#298)

Changelog Sourced from json5's changelog.

Unreleased [code, diff]

v2.2.3 [code, diff]

• Fix: json5@2.2.3 is now the 'latest' release according to npm instead of v1.0.2. (#299)

v2.2.2 [code, diff]

• Fix: Properties with the name

__proto__

are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

v2.2.1 [code, diff]

• Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

v2.2.0 [code, diff]

• New: Accurate and documented TypeScript declarations are now included. There is no need to install

@types/json5

. (#236, #244)

v2.1.3 [code, diff]

• Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

v2.1.2 [code, diff]

... (truncated) Commits • `a62db1e` 1.0.2 • `e0c23fe` docs: update CHANGELOG for v1.0.2 • `62a6540` fix: add proto to objects and arrays • See full diff in compare view Dependabot compatibility score Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@dependabot rebase

. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: •

@dependabot rebase

will rebase this PR •

@dependabot recreate

will recreate this PR, overwriting any edits that have been made to it •

@dependabot merge

will merge this PR after your CI passes on it •

@dependabot squash and merge

will squash and merge this PR after your CI passes on it •

@dependabot cancel merge

will cancel a previously requested merge and block automerging •

@dependabot reopen

will reopen this PR if it is closed •

@dependabot close

will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually •

@dependabot ignore this major version

will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this minor version

will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this dependency

will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) •

@dependabot use these labels

will set the current labels as the default for future PRs for this repo and language •

@dependabot use these reviewers

will set the current reviewers as the default for future PRs for this repo and language •

@dependabot use these assignees

will set the current assignees as the default for future PRs for this repo and language •

@dependabot use this milestone

will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the Security Alerts page. osquery/osquery-site

#272 Update website for 5.7.0 release Pull request opened by zwass osquery/osquery-site

1 new commit pushed to

<https://github.com/osquery/osquery-site/tree/source|source>

by directionless

<https://github.com/osquery/osquery-site/commit/dfea284622ad14dd3bbc9cf2b2c043b7825a07c3|dfea2846>

- Update website for 5.7.0 release (#272) osquery/osquery-site

Deployment to github-pages by directionless osquery/osquery-site

I merged and deployed ^^^. Thank you Zach

1 new commit pushed to

<https://github.com/osquery/osquery-site/tree/source|source>

by directionless

<https://github.com/osquery/osquery-site/commit/3f59aca540dbaa5d231bb3aa8d1d19599d5b1df1|3f59aca5>

- Add CodeQL workflow for GitHub code scanning (#266) osquery/osquery-site

#266 Add CodeQL workflow for GitHub code scanning Pull request opened by lgtm-com[bot] Hi

osquery/osquery-site

! This is a one-off automatically generated pull request from LGTM.com 🤖. You might have heard that we’ve integrated LGTM’s underlying CodeQL analysis engine natively into GitHub. The result is *GitHub code scanning*! With LGTM fully integrated into code scanning, we are focused on improving CodeQL within the native GitHub code scanning experience. In order to take advantage of current and future improvements to our analysis capabilities, we suggest you enable code scanning on your repository. Please take a look at our blog post for more information. This pull request enables code scanning by adding an auto-generated `codeql.yml` workflow file for GitHub Actions to your repository — take a look! We tested it before opening this pull request, so all should be working ✔️. In fact, you might already have seen some alerts appear on this pull request! Where needed and if possible, we’ve adjusted the configuration to the needs of your particular repository. But of course, you should feel free to tweak it further! Check this page for detailed documentation. Questions? Check out the FAQ below! FAQ Click here to expand the FAQ section How often will the code scanning analysis run? By default, code scanning will trigger a scan with the CodeQL engine on the following events: • On every pull request — to flag up potential security problems for you to investigate before merging a PR. • On every push to your default branch and other protected branches — this keeps the analysis results on your repository’s Security tab up to date. • Once a week at a fixed time — to make sure you benefit from the latest updated security analysis even when no code was committed or PRs were opened. What will this cost? Nothing! The CodeQL engine will run inside GitHub Actions, making use of your unlimited free compute minutes for public repositories. What types of problems does CodeQL find? The CodeQL engine that powers GitHub code scanning is the exact same engine that powers LGTM.com. The exact set of rules has been tweaked slightly, but you should see almost exactly the same types of alerts as you were used to on LGTM.com: we’ve enabled the `security-and-quality` query suite for you. How do I upgrade my CodeQL engine? No need! New versions of the CodeQL analysis are constantly deployed on GitHub.com; your repository will automatically benefit from the most recently released version. The analysis doesn’t seem to be working If you get an error in GitHub Actions that indicates that CodeQL wasn’t able to analyze your code, please follow the instructions here to debug the analysis. *How do I disable LGTM.com?* If you have LGTM’s automatic pull request analysis enabled, then you can follow these steps to disable the LGTM pull request analysis. You don’t actually need to remove your repository from LGTM.com; it will automatically be removed in the next few months as part of the deprecation of LGTM.com (more info here). Which source code hosting platforms does code scanning support? GitHub code scanning is deeply integrated within GitHub itself. If you’d like to scan source code that is hosted elsewhere, we suggest that you create a mirror of that code on GitHub. How do I know this PR is legitimate? This PR is filed by the official LGTM.com GitHub App, in line with the deprecation timeline that was announced on the official GitHub Blog. The proposed GitHub Action workflow uses the official open source GitHub CodeQL Action. If you have any other questions or concerns, please join the discussion here in the official GitHub community! I have another question / how do I get in touch? Please join the discussion here to ask further questions and send us suggestions! osquery/osquery-site ✅ All checks have passed 1/1 successful checks

#273 Bump ua-parser-js from 0.7.28 to 0.7.33 Pull request opened by dependabot[bot] Bumps ua-parser-js from 0.7.28 to 0.7.33. Changelog Sourced from ua-parser-js's changelog.

Version 0.7.33 / 1.0.33

• Add new browser : Cobalt

• Identify Macintosh as an Apple device

• Fix ReDoS vulnerability

Version 0.8

Version 0.8 was created by accident. This version is now deprecated and no longer maintained, please update to version 0.7 / 1.0.

Commits • `f2d0db0` Bump version 0.7.33 • `a6140a1` Remove unsafe regex in trim() function • `a886604` Fix #605 - Identify Macintosh as Apple device • `b814bcd` Merge pull request #606 from rileyjshaw/patch-1 • `7f71024` Fix documentation • `c239ac5` Merge pull request #604 from obecerra3/master • `8d3c2d3` Add new browser: Cobalt • `d11fc47` Bump version 0.7.32 • `b490110` Merge branch 'develop' of github.com:faisalman/ua-parser-js • `cb5da5e` Merge pull request #600 from moekm/develop • Additional commits viewable in compare view Dependabot compatibility score Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@dependabot rebase

. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: •

@dependabot rebase

will rebase this PR •

@dependabot recreate

will recreate this PR, overwriting any edits that have been made to it •

@dependabot merge

will merge this PR after your CI passes on it •

@dependabot squash and merge

will squash and merge this PR after your CI passes on it •

@dependabot cancel merge

will cancel a previously requested merge and block automerging •

@dependabot reopen

will reopen this PR if it is closed •

@dependabot close

will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually •

@dependabot ignore this major version

will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this minor version

will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this dependency

will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) •

@dependabot use these labels

will set the current labels as the default for future PRs for this repo and language •

@dependabot use these reviewers

will set the current reviewers as the default for future PRs for this repo and language •

@dependabot use these assignees

will set the current assignees as the default for future PRs for this repo and language •

@dependabot use this milestone

will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the Security Alerts page. osquery/osquery-site ✅ All checks have passed 3/3 successful checks

#274 `apt-key` is deprecated on Debian-based systems Issue created by lengau The `apt-key` command is deprecated as of apt v2.4.0. (This currently affects Debian testing and unstable, Ubuntu 22.04+ and any dsitributions based on those.) The most straightforward way to change the documentation would be to have it request the following commands:

export OSQUERY_KEY=1484120AC4E9F8A1A577AEEE97A80C63C9D8B80B
sudo gpg --no-default-keyring --keyring /etc/apt/keyrings/osquery.gpg --keyserver <hkp://keyserver.ubuntu.com> $OSQUERY_KEY
sudo add-apt-repository 'deb [arch=amd64 signed-by=/etc/apt/keyrings/osquery.gpg] <https://pkg.osquery.io/deb> deb main'
sudo apt install osquery

Other changes to this block: 1. Removed

apt-get update

step, since

add-apt-repository

does this automatically 2. Changed

apt-get

to the newer

apt

command. osquery/osquery-site

#275 docs: Update instructions for apt-key deprecation Pull request opened by lengau Fixes #274 osquery/osquery-site

#276 Add 5.8.1 as a release Pull request opened by directionless osquery/osquery-site ✅ All checks have passed 3/3 successful checks

^^^ if anyone is around to thumb it

1 new commit pushed to

<https://github.com/osquery/osquery-site/tree/source|source>

by directionless

<https://github.com/osquery/osquery-site/commit/116eac48ad88ad6b831336dc668df57a33520bf5|116eac48>

- Add 5.8.1 as a release (#276) osquery/osquery-site

Deployment to github-pages by directionless osquery/osquery-site

#277 Release 5.8.2 and update runner version Pull request opened by directionless Push out the 5.8.2 release, and since it's now required, update the github actions runner to the current version osquery/osquery-site ✅ All checks have passed 3/3 successful checks

1 new commit pushed to

<https://github.com/osquery/osquery-site/tree/source|source>

by directionless

<https://github.com/osquery/osquery-site/commit/6477ae054a5885f8170f9a97217d80c449fe2dd5|6477ae05>

- docs: Update instructions for apt-key deprecation (#275) osquery/osquery-site

#275 docs: Update instructions for apt-key deprecation Pull request opened by lengau Fixes #274 osquery/osquery-site ✅ All checks have passed 3/3 successful checks

#274 `apt-key` is deprecated on Debian-based systems Issue created by lengau The `apt-key` command is deprecated as of apt v2.4.0. (This currently affects Debian testing and unstable, Ubuntu 22.04+ and any dsitributions based on those.) The most straightforward way to change the documentation would be to have it request the following commands:

export OSQUERY_KEY=1484120AC4E9F8A1A577AEEE97A80C63C9D8B80B
sudo gpg --no-default-keyring --keyring /etc/apt/keyrings/osquery.gpg --keyserver <hkp://keyserver.ubuntu.com> $OSQUERY_KEY
sudo add-apt-repository 'deb [arch=amd64 signed-by=/etc/apt/keyrings/osquery.gpg] <https://pkg.osquery.io/deb> deb main'
sudo apt install osquery

Other changes to this block: 1. Removed

apt-get update

step, since

add-apt-repository

does this automatically 2. Changed

apt-get

to the newer

apt

command. osquery/osquery-site

1 new commit pushed to

<https://github.com/osquery/osquery-site/tree/source|source>

by directionless

<https://github.com/osquery/osquery-site/commit/03fdfb96b566f0f3cd8d5c62b1bdb49b077ec172|03fdfb96>

- Release 5.8.2 and update runner version (#277) osquery/osquery-site

Deployment to github-pages by directionless osquery/osquery-site

#278 Fix schema page visual jumping #49 Pull request opened by hirohe toggle 'noscroll' style on body will cause #49 issue in some browsers this pr instead use

overscroll-behavior: none

to prevent over scrolling on side list that causing scrolling chain osquery/osquery-site ✅ All checks have passed 3/3 successful checks

1 new commit pushed to

<https://github.com/osquery/osquery-site/tree/source|source>

by directionless

<https://github.com/osquery/osquery-site/commit/b30a59634e91286a0738e8ec6d2533a6b4a39da6|b30a5963>

- Fix schema page visual jumping #49 (#278) osquery/osquery-site

Anyone around for https://github.com/osquery/osquery-site/pull/279 ?