Gathering detailed insights and metrics for @ava/babel-plugin-throws-helper
Gathering detailed insights and metrics for @ava/babel-plugin-throws-helper
Babel plugin for protecting against improper use of `t.throws()` in AVA
Installations
npm install @ava/babel-plugin-throws-helperDeveloper Guide
BETA
Typescript
No
Module System
N/A
Min. Node Version
>=8.9.4 <9 || >=10.0.0 <11 || >=12.0.0
Node Version
12.8.0
NPM Version
6.10.3
Score
99.7
Supply Chain
69.4
Quality
77.8
Maintenance
100
Vulnerability
100
License
Releases
Unable to fetch releases
Languages
1
JavaScript
JavaScript (100%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
3 Stars
76 Commits
3 Forks
6 Watchers
1 Branches
6 Contributors
Updated on Jan 28, 2023
Bundle Size
1.24 kB
Minified
661.00 B
Minified + Gzipped
Maintainers
3
Package Meta Information
Latest Version
4.0.0
Package Id
@ava/babel-plugin-throws-helper@4.0.0
Size
2.50 kB
NPM Version
6.10.3
Node Version
12.8.0
Published on
Aug 11, 2019
Total Downloads
Cumulative downloads
Total Downloads
NaN
Dev Dependencies
5
babel-plugin-throws-helper 
Babel plugin for protecting against improper use of
t.throws()in AVA
Probably not useful except as an internal plugin for the AVA test runner.
Issue
I've seen a lot of incorrect use of the throws assertion in other test runner and even done the mistake myself sometimes. Now I'm beginning to see it with AVA too, so would be nice to be preemptive about it.
People don't realize they need to wrap their call in a function, so many end up doing
t.throws(foo())instead oft.throws(() => foo());. It's an easy mistake to make.
The difficulty is that t.throws(foo()) is allowed if foo() returns a promise or a function. There is no good way to differentiate between the two at runtime. So providing a good error message is going to take some AST transform magic.
Solution
See test.js.md for the transformation this plugin performs.
License
MIT © James Talmage
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: license:0
- Info: FSF or OSI recognized license: MIT License: license:0
Reason
security policy file detected
Details
- Info: security policy file detected: github.com/avajs/.github/SECURITY.md:1
- Info: Found linked content: github.com/avajs/.github/SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: github.com/avajs/.github/SECURITY.md:1
- Info: Found text in security policy: github.com/avajs/.github/SECURITY.md:1
Reason
Found 2/20 approved changesets -- score normalized to 1
Reason
project is archived
Details
- Warn: Repository is archived.
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 18 are checked with a SAST tool
Score
4
/10
Last Scanned on 2025-06-23
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