Gathering detailed insights and metrics for http-assert-plus
Gathering detailed insights and metrics for http-assert-plus
npm install http-assert-plus
Typescript
Module System
Min. Node Version
Node Version
NPM Version
71.3
Supply Chain
99.3
Quality
75.4
Maintenance
100
Vulnerability
100
License
JavaScript (50.33%)
TypeScript (49.67%)
Love this project? Help keep it running — sponsor us today! 🚀
Total Downloads
10,927
Last Day
23
Last Week
46
Last Month
192
Last Year
4,923
48 Commits
2 Watching
1 Branches
1 Contributors
Minified
Minified + Gzipped
Latest Version
2.0.1
Package Id
http-assert-plus@2.0.1
Unpacked Size
20.84 kB
Size
5.32 kB
File Count
5
NPM Version
8.19.3
Node Version
16.19.1
Publised On
10 May 2023
Cumulative downloads
Total Downloads
Last day
109.1%
23
Compared to previous day
Last week
-2.1%
46
Compared to previous week
Last month
-21%
192
Compared to previous month
Last year
151.9%
4,923
Compared to previous year
More assertions with status codes.
1import assert from 'http-assert-plus'; 2// or 3const assert = require('http-assert-plus'); 4 5const username = 'jdrydn'; 6assert(username === 'not-jdrydn', 403, 'Authorization failed', { 7 code: 'NOT_AUTHORIZED', 8 username, 9}); 10 11// Error: Authorization failed 12// at http-assert-plus/README.md:22:1 { 13// code: 'NOT_AUTHORIZED', 14// statusCode: 403, 15// status: 403, 16// statusText: 'Forbidden', 17// username: 'jdrydn' 18// }
$ npm install --save http-assert-plus
This API matches the built-in assert
module, and builds upon the success of http-assert
, with a few differences:
Error
when the assertion fails.assert(value, [status], [message], [props])
Tests if value
is truthy, and throws an Error
if falsey.
assert.ok(value, [status], [message], [props])
Alias for above, tests if value
is truthy, and throws an Error
if falsey.
assert.fail([status], [message], [props])
Always throws an Error
with the provided status/message/props.
assert.equal(a, b, [status], [message], [props])
Tests shallow, coercive equality between a
& b
using ==
.
assert.notEqual(a, b, [status], [message], [props])
Tests shallow, coercive inequality between a
& b
using !=
.
assert.strictEqual(a, b, [status], [message], [props])
Tests strict equality between a
& b
using ===
.
assert.notStrictEqual(a, b, [status], [message], [props])
Tests strict inequality between a
& b
using !==
.
assert.includes(a, b, [status], [message], [props])
Tests whether a
includes b
- where a
has a method call includes
.
assert.notIncludes(a, b, [status], [message], [props])
Tests whether a
does not include b
- where a
has a method includes
.
If you're looking for deep equality checks, check out deep-equal
:
1import assert from 'http-assert-plus';
2import deepEqual from 'deep-equal';
3
4assert(deepEqual(a, b), 400, 'These two are not entirely equal');
5assert(deepEqual(a, b, { strict: true }), 400, 'These two are not entirely equal');
6// Error: Array does not strict-equal
7// at http-assert-plus/README.md:72:1 {
8// statusCode: 400,
9// status: 400,
10// statusText: 'Bad Request'
11// }
Yes! Not all browsers support Error.captureStackTrace
so this library checks if it is present in the current environment - if it isn't available the only behaviour you'll likely want to change is to pre-construct Error
arguments to preserve a proper stack trace, like so:
1const { origin } = window.location; 2 3// In browsers, do this: 4assert(origin.startsWith('https://'), new Error('Expected origin to start with https://'), { origin }); 5// Error: Expected origin to start with https:// 6// at http-assert-plus/README.md:99:39 { 7// origin: 'http://localhost:4000', 8// } 9 10// Not this 11assert(origin.startsWith('https://'), 'Expected origin to start with https://'); 12// Error: Expected origin to start with https:// 13// at node_modules/http-assert-plus/index.cjs:56:38 { 14// at http-assert-plus/README.md:107:1 { 15// origin: 'http://localhost:4000', 16// }
If you don't use a construct such as new Error
, when reading stacktraces just ignore the first line as it'll always be the assert
function :wink:
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 3
Details
Reason
7 existing vulnerabilities detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/28 approved changesets -- 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
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-01-27
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