should

v13.2.3

test framework agnostic BDD-style assertions

MIT
Latest version published about 2 years ago
    npm install should
  

Package Health Score

64 / 100
  • Popularity
    Popular
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Sustainable

Popularity

Popular
Weekly Downloads (509,288)
Dependents
28.84K
GitHub Stars
1.9K
Forks
134
Contributors
68

The npm package should receives a total of 509,288 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,897 times, and that 28,845 other projects on 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.

Security

No known security issues

Security and license risk for recent versions


Direct Vulnerabilities

13.1.3
13.2.0
13.2.1
13.2.2
13.2.3
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

13.1.3
13.2.0
13.2.1
13.2.2
13.2.3
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

13.1.3
13.2.0
13.2.1
13.2.2
13.2.3
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Security Policy
No
All security vulnerabilities belong to production dependencies of direct and indirect packages.

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

We found a way for you to contribute to the project! Looks like should is missing a security policy.

    # Install the Snyk CLI and test your project
npm i snyk && snyk test should
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
8
Merged PR
31
Open PR
3
Last Commit
2 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.

Community

Sustainable
Readme.md
No
Contributing.md
No
Code of Conduct
No
Contributors
68
Funding
No
License
MIT

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.

Package

Node.js Compatibility
not defined

Age
10 years
Dependencies
5 Direct / 5 Total
Versions
5
Install Size
408 kB
Dist-tags
1
# of Files
10
Maintainers
3
TS Typings
No

We detected a total of 5 direct & transitive dependencies for should. See the full dependency tree of should

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.