should

v13.2.3

test framework agnostic BDD-style assertions

MIT
Latest version published 4 years ago
    npm install should
  
We couldn't find any similar packages Browse all packages

Package Health Score

58 / 100

Security

No known security issues
Powered by Snyk
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
13.2.3 | 07/2018
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
13.1.3 | 10/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
12.0.0 | 08/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
11.2.1 | 03/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
11.1.2 | 12/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test should
Get started free

Popularity

Popular

Weekly Downloads (853,104)

Download trend
Dependents
29.03K
GitHub Stars
1.91K
Forks
132
Contributors
70

Direct Usage Popularity

TOP 5%

The npm package should receives a total of 853,104 downloads a week. As such, we scored should popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package should, we found that it has been starred 1,912 times, and that 29,034 other projects in the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
70
Funding
No

With more than 10 contributors for the should repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like should is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 58/100 package health 58/100

Maintenance

Inactive
archived

Commit Frequency

No Recent Commits
Open Issues
8
Open PR
3
Last Release
4 years ago
Last Commit
3 years ago

Further analysis of the maintenance status of should based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for should is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
not defined

Age
11 years
Dependencies
5 Direct
Versions
115
Install Size
408 kB
Dist-tags
1
# of Files
10
Maintainers
3
TS Typings
Yes

should has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.