npmpackage.info

Gathering detailed insights and metrics for network-error-logging

Other packages similar to network-error-logging

micro-ftch

0.4.0

Wrappers for built-in fetch() enabling killswitch, logging, concurrency limit and other features

reporting-api

1.0.3

Roll your own Reporting API collector. Supports CSP, COEP, COOP, Document-Policy, Crash reports, Deprecation reports, Intervention reports and Network Error Logging

loglevel

1.9.2

Minimal lightweight logging for JavaScript, adding reliable log level methods to any available console.log methods

winston

3.17.0

A logger for just about everything.

Gathering detailed insights and metrics for network-error-logging

network-error-logging

Middleware for setting the NEL HTTP response header

1.2.1

MIT

JavaScript

629.00 B

76,794 3.8

Installations

npm install network-error-logging

Score

68.2

Supply Chain

74.1

Quality

75.7

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

3

Total

229

Closed

83

Merged

143

Issues

Open

0

Total

5

Closed

5

Releases

Unable to fetch releases

Developer

Cherry

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

>=12

Typescript Support

Yes

Node Version

12.18.2

NPM Version

6.14.8 Statistics

5 Stars

344 Commits

4 Forks

3 Watching

4 Branches

3 Contributors

Updated on 29 Sept 2024

Bundle Size

1.95 kB

Minified

629.00 B

Minified + Gzipped

Bundlephobia

Languages

JavaScript (57.46%)

TypeScript (42.54%)

Total Downloads

Cumulative downloads

Total Downloads

76,794

Last day

60.9%

Compared to previous day

Last week

3.1%

233

Compared to previous week

Last month

-1.9%

872

Compared to previous month

Last year

-28.5%

10,121

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

@types/express @types/mocha @types/supertest assert connect coveralls eslint eslint-config-nodecraft eslint-plugin-json eslint-plugin-node mocha nyc supertest ts-mocha typescript

Versions

Network Error Logging

This is Express middleware to set the NEL HTTP response header. You can read more about it here.

To use:

1const NEL = require('network-error-logging')
2
3// ...
4
5app.use(NEL({
6  report_to: 'endpoint-1', // REQUIRED to register. OPTIONAL if intention is to remove a previous registration. defined in the Report-To header
7  max_age: 31_536_000, // REQUIRED. seconds
8  include_subdomains: true, // OPTIONAL
9  success_fraction: 0.5, // OPTIONAL. sampling rate
10  failure_fraction: 0.5, // OPTIONAL. sampling rate
11  request_headers: ["If-None-Match"], // OPTIONAL. request headers whose names and values are included in the network error reports
12  response_headers: ["ETag"] // OPTIONAL. response headers whose names and values are included in the network error reports
13}))

For further documentation on each field, see https://w3c.github.io/network-error-logging/#nel-response-header.

This header is best set with a previously defined Report-To group. This module is a great way to do that.

https://report-uri.com/ is a great reporting platform for monitoring CSP, NEL, etc. error logs.

License

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

8

SAST

Determines if the project uses static code analysis.

7

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

1

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Security-Policy

Determines if the project has published a security policy.

Score

3.8

/10

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