Gathering detailed insights and metrics for assert-plus
Gathering detailed insights and metrics for assert-plus
Gathering detailed insights and metrics for assert-plus
Gathering detailed insights and metrics for assert-plus
npm install assert-plus
Typescript
Module System
Min. Node Version
Node Version
NPM Version
99.7
Supply Chain
99.5
Quality
82.3
Maintenance
100
Vulnerability
100
License
JavaScript (94.84%)
Makefile (5.16%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
121 Stars
38 Commits
25 Forks
34 Watchers
3 Branches
12 Contributors
Updated on Jun 11, 2025
Latest Version
1.0.0
Package Id
assert-plus@1.0.0
Size
3.85 kB
NPM Version
3.3.9
Node Version
0.10.40
Published on
Jan 27, 2016
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
This library is a super small wrapper over node's assert module that has two
things: (1) the ability to disable assertions with the environment variable
NODE_NDEBUG, and (2) some API wrappers for argument testing. Like
assert.string(myArg, 'myArg')
. As a simple example, most of my code looks
like this:
1 var assert = require('assert-plus'); 2 3 function fooAccount(options, callback) { 4 assert.object(options, 'options'); 5 assert.number(options.id, 'options.id'); 6 assert.bool(options.isManager, 'options.isManager'); 7 assert.string(options.name, 'options.name'); 8 assert.arrayOfString(options.email, 'options.email'); 9 assert.func(callback, 'callback'); 10 11 // Do stuff 12 callback(null, {}); 13 }
All methods that aren't part of node's core assert API are simply assumed to
take an argument, and then a string 'name' that's not a message; AssertionError
will be thrown if the assertion fails with a message like:
AssertionError: foo (string) is required
at test (/home/mark/work/foo/foo.js:3:9)
at Object.<anonymous> (/home/mark/work/foo/foo.js:15:1)
at Module._compile (module.js:446:26)
at Object..js (module.js:464:10)
at Module.load (module.js:353:31)
at Function._load (module.js:311:12)
at Array.0 (module.js:484:10)
at EventEmitter._tickCallback (node.js:190:38)
from:
1 function test(foo) { 2 assert.string(foo, 'foo'); 3 }
There you go. You can check that arrays are of a homogeneous type with Arrayof$Type
:
1 function test(foo) { 2 assert.arrayOfString(foo, 'foo'); 3 }
You can assert IFF an argument is not undefined
(i.e., an optional arg):
1 assert.optionalString(foo, 'foo');
Lastly, you can opt-out of assertion checking altogether by setting the
environment variable NODE_NDEBUG=1
. This is pseudo-useful if you have
lots of assertions, and don't want to pay typeof ()
taxes to v8 in
production. Be advised: The standard functions re-exported from assert
are
also disabled in assert-plus if NDEBUG is specified. Using them directly from
the assert
module avoids this behavior.
The complete list of APIs is:
npm install assert-plus
The MIT License (MIT) Copyright (c) 2012 Mark Cavage
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
0 existing vulnerabilities detected
Reason
Found 10/30 approved changesets -- score normalized to 3
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-07
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