osquery-node
osquery-node copied to clipboard
node.js client for osquery
Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project. #### Changes included in this PR - Changes to the following...
#### Description This PR fixes one or more vulnerable packages in the `npm` dependencies of this project. See the [Snyk test report](https://app.snyk.io/org/sidorares/test/github/29bd1f04-8249-49b1-a226-ccc588909d16/master..snyk-fix-899a0375423cd823f3f31d536a5c3462) for more details. #### Snyk Project: [sidorares/osquery-node:package.json](https://app.snyk.io/org/sidorares/project/29bd1f04-8249-49b1-a226-ccc588909d16) ####...
#### Description This PR fixes one or more vulnerable packages in the `npm` dependencies of this project. See the [Snyk test report](https://app.snyk.io/org/sidorares/test/github/29bd1f04-8249-49b1-a226-ccc588909d16/master..snyk-fix-98aq32) for more details. #### Snyk Project: [sidorares/osquery-node:package.json](https://app.snyk.io/org/sidorares/project/29bd1f04-8249-49b1-a226-ccc588909d16) ####...
This project has vulnerabilities that could not be fixed, or were patched when no upgrade was available. Good news, new upgrades or patches have now been published! This pull request...
Is it possible to run on windows?
This project has vulnerabilities that could not be fixed, or were patched when no upgrade was available. Good news, new upgrades or patches have now been published! This pull request...
Apparently this can lead to many "/var/osquery/osquery.em.*" files and attempts address in use errors. This may only happen if the script is terminated unexpectedly (not sure).
When sending a response, all value types must be a string or writeString will fail: (this is using { "foo": 2 } having changed the schema to be "INTEGER"): ```...