Gathering detailed insights and metrics for trace-and-clarify-if-possible
Gathering detailed insights and metrics for trace-and-clarify-if-possible
Gathering detailed insights and metrics for trace-and-clarify-if-possible
Gathering detailed insights and metrics for trace-and-clarify-if-possible
npm install trace-and-clarify-if-possible
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
2 Stars
22 Commits
2 Watching
4 Branches
1 Contributors
Updated on 25 Sept 2020
Minified
Minified + Gzipped
JavaScript (74.86%)
HTML (25.14%)
Cumulative downloads
Total Downloads
Last day
-2.1%
456
Compared to previous day
Last week
6.6%
2,604
Compared to previous week
Last month
28.3%
11,165
Compared to previous month
Last year
-28%
123,394
Compared to previous year
11
Use
trace
andclarify
if supported by the current node version
trace and clarify can help greatly to analyze stack-traces
trace
shows the part of the stack that would otherwise disappear due to asynchronous callbacksclarify
removes uninteresting parts of the stackSadly, trace
can is only compatible with NodeJS version >=4. It makes sense to include trace
in your tests all the time (not in production code though). However, when you run the test in Travis CI with multiple node versions <4, the tests will break.
This package include trace
and clarify
only for supported node versions.
npm install trace-and-clarify-if-possible
Put the following line a module that is loaded at the start of your program or testcase-spec (remember, do not use in production).
1require('trace-and-clarify-if-possible')
Or, you can put --require trace-and-clarify-if-possible into your
test/mocha.opts` to activate it for all tests
trace-and-clarify-if-possible
is published under the MIT-license.
See LICENSE.md for details.
For release notes, see CHANGELOG.md
See CONTRIBUTING.md.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/15 approved changesets -- 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
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
46 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-18
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