Homepage

wConsequence vulnerabilities

Advanced synchronization mechanism. Asynchronous routines may use Consequence to wrap postponed result, what allows classify callback for such routines as output, not input, what improves analyzability of a program. Consequence may be used to make a queue
Licenses: MIT
Published: 9 years ago Last updated: 3 years ago Latest version: 0.4.520 Latest non-vulnerable version: 0.4.520
npm
GitHub

Package Health Score

36/100
  • securitySecurity review needed
  • popularityLimited
  • maintenanceInactive
  • communityLimited

Maintenance

INACTIVE

Commit Frequency

No commits over the last 6 months

Open Issues
0
Open PR
0
New PRS
0
Last Release
3 years ago
Last Commit
3 years ago
Maintainers
1

Further analysis of the maintenance status of wConsequence 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 wConsequence 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.

Popularity

LIMITED
Weekly downloads (608)
GitHub Stars
2
Forks
5
Contributors
0

The npm package wConsequence receives a total of 608 downloads a week. As such, we scored wConsequence popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package wConsequence, we found that it has been starred 2 times.

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
0
Funding
No
LICENSE
MIT

This project has seen only 10 or less contributors.

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

License

MIT>=0;
Report a new vulnerability Found a mistake?

Direct Vulnerabilities

No direct vulnerabilities have been found for this package in Snyk’s vulnerability database. This does not include vulnerabilities belonging to this package’s dependencies.

Does your project rely on vulnerable package dependencies?

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities (in both your packages & their dependencies) and provides automated fixes for free.

Scan for indirect vulnerabilities

Security

SECURITY REVIEW NEEDED
Show only direct vulnerabilities in latest version

No vulnerabilities found in the latest version

No vulnerabilities found

Package versions

580 VERSIONS IN TOTAL See all versions
versionpublisheddirect vulnerabilities
0.4.52025 Jul, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.4.51924 Jul, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.4.51818 Jun, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.4.51718 Jun, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.4.51615 Jun, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.4.51518 May, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.4.51413 May, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.4.51312 May, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.4.51210 May, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.4.5116 May, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

wConsequence dependencies

5 IN TOTAL
wToolswProtowprocedurewCopyablewdeasync

wConsequence development dependencies

2 IN TOTAL
wTestingeslint