unassertify

v2.1.1

Browserify transform for unassert: Encourages programming with assertions by providing tools to compile them away

MIT
Latest version published 4 years ago
    npm install unassertify
  

Package Health Score

48 / 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
2.1.1 | 04/2018
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.5 | 10/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.2 | 05/2015
  • 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 unassertify
Get started free

Popularity

Small

Weekly Downloads (9,600)

Download trend
Dependents
96
GitHub Stars
76
Forks
5
Contributors
2

Direct Usage Popularity

Uncommon

The npm package unassertify receives a total of 9,600 downloads a week. As such, we scored unassertify popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package unassertify, we found that it has been starred 76 times, and that 96 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

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
2
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 48/100 package health 48/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
1
Open PR
0
Last Release
4 years ago
Last Commit
4 years ago

Further analysis of the maintenance status of unassertify 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 unassertify 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
7 years
Dependencies
6 Direct
Versions
12
Install Size
14.1 kB
Dist-tags
1
# of Files
5
Maintainers
1
TS Typings
No

unassertify 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.