Gathering detailed insights and metrics for seq-logging
Gathering detailed insights and metrics for seq-logging
Gathering detailed insights and metrics for seq-logging
Gathering detailed insights and metrics for seq-logging
npm install seq-logging
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
26 Stars
219 Commits
15 Forks
8 Watching
2 Branches
14 Contributors
Updated on 28 Oct 2024
JavaScript (99.56%)
HTML (0.44%)
Cumulative downloads
Total Downloads
Last day
-6.6%
7,603
Compared to previous day
Last week
4.9%
49,941
Compared to previous week
Last month
2.5%
232,592
Compared to previous month
Last year
12.6%
2,101,515
Compared to previous year
2
4
This library makes it easy to support Seq from Node.js logging libraries, including Winston via winston-seq, Pino via
pino-seq
, Bunyan viabunyan-seq
, and Ts.ED logger via @tsed/logger-seq. It is not expected that applications will interact directly with this package.
1const seq = require('seq-logging');
Using seq-logging
in a browser context is the same, except the module to import is seq-logging/browser
.
1const seq = require('seq-logging/browser');
A Logger
is configured with serverUrl
, and optionally apiKey
as well as event and batch size limits.
requestTimeout
can be used to adjust timeout for stalled connections, default: 30s.
1const process = require('process'); 2const seq = require('seq-logging'); 3 4const logger = new seq.Logger({ serverUrl: 'http://localhost:5341' }); 5 6logger.emit({ 7 timestamp: new Date(), 8 level: 'Information', 9 messageTemplate: 'Hello for the {n}th time, {user}!', 10 properties: { 11 user: process.env.USERNAME, 12 n: 20 13 } 14}); 15 16logger.close();
Events are sent using the emit()
method, that internally performs asynchronous batching based on payload size.
When the application exits, close()
ensures all buffered events are written. This can be done at any time otherwise using the flush()
method. Both of these methods return promises indicating completion.
No vulnerabilities found.
Reason
all changesets reviewed
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
0 existing vulnerabilities detected
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More