47 issues in loggly/node-loggly-bulk
Hi! The direct dependency package request has been deprecated in Feb 2020 (https://www.npmjs.com/package/request). All versions of request including the latest one are affected by prototype pollution ...
The following will yield TypeError: createClient is not a function with Yarn 2: import { createClient } from 'node-loggly-bulk'; I was able to circumvent this by using a direct import: import ...
It would be great to add flushLogs() method in case of graceful-shutdown (isBuk: true).
If you create multiple instances with bulk enabled and using two different accounts some logs will not make it to loggly. Looking through the code, it looks like there are singletons that are created ...
Issue I've been trying to get node-loggly-bulk running on AWS lambda and have been running into timeout issues. One inconsistency I ran into was passing in the isBulk property and expecting it to ...
Versions of request before 2.83.0 are susceptible to a ReDoS attack via it's dependency tough-cookie. Version 2.83.0 of request upgrades the version of touch-cookie to one that is no longer susceptible ...
In this PR, I have handled the undefined tag issue https://github.com/loggly/winston-loggly-bulk/issues/33 which crashes the whole app. I've covered the below points in this bug fix- (a) Calculate ...
As per the current scenario, the library writes the networks errors on console which sometimes pollute the other important logs when the numbers are so high. In this PR, I have made the error writing ...
Issue Snyk has flagged stringstream v0.0.5 as a security vulnerability. > Affected versions of this package are vulnerable to Uninitialized Memory Exposure. An attacker could extract sensitive data ...