Gathering detailed insights and metrics for wConsequence
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 for mutually exclusive access to a resource.
Installations
npm install wConsequenceDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Node Version
16.13.1
NPM Version
8.1.2
Score
27.1
Supply Chain
23.6
Quality
70.7
Maintenance
100
Vulnerability
97
License
Releases
Unable to fetch releases
Contributors
6
Unable to fetch Contributors
Languages
1
JavaScript
JavaScript (100%)
Developer
Wandalen
Download Statistics
Total Downloads
3,489,554
Last Day
12
Last Week
391
Last Month
3,034
Last Year
48,573
GitHub Statistics
2 Stars
2,131 Commits
5 Forks
3 Watching
2 Branches
6 Contributors
Maintainers
1
Package Meta Information
Latest Version
0.4.520
Package Id
wConsequence@0.4.520
Unpacked Size
220.50 kB
Size
34.88 kB
File Count
8
NPM Version
8.1.2
Node Version
16.13.1
Total Downloads
Cumulative downloads
Total Downloads
3,489,554
Last day
-89.1%
12
Compared to previous day
Last week
-64.9%
391
Compared to previous week
Last month
17.1%
3,034
Compared to previous month
Last year
-92.8%
48,573
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Versions
module::Consequence 
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 for mutually exclusive access to a resource.
Algorithmically speaking Consequence is 2 queues ( FIFO ) and a customizable arbitrating algorithm. The first queue contains available resources, the second queue includes competitors for this resources. At any specific moment, one or another queue may be empty or full. Arbitrating algorithm makes resource available for a competitor as soon as possible. There are 2 kinds of resource: regular and erroneous. Unlike Promise, Consequence is much more customizable and can solve engineering problem which Promise cant. But have in mind with great power great responsibility comes. Consequence can coexist and interact with a Promise, getting fulfillment/rejection of a Promise or fulfilling it. Use Consequence to get more flexibility and improve readability of asynchronous aspect of your application.
Try out from the repository
git clone https://github.com/Wandalen/wConsequence
cd wConsequence
will .npm.install
node sample/trivial/Sample.s
Make sure you have utility willbe installed. To install willbe: npm i -g willbe@stable. Willbe is required to build of the module.
To add to your project
npm add 'wConsequence@stable'
Willbe is not required to use the module in your project as submodule.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
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
Found 0/30 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/StandardPublish.yml:1
- Warn: no topLevel permission defined: .github/workflows/StandardPullRequest.yml:1
- Warn: no topLevel permission defined: .github/workflows/StandardPush.yml:1
- Info: no jobLevel write permissions found
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/StandardPush.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/Wandalen/wConsequence/StandardPush.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/StandardPush.yml:35: update your workflow using https://app.stepsecurity.io/secureworkflow/Wandalen/wConsequence/StandardPush.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/StandardPush.yml:53: update your workflow using https://app.stepsecurity.io/secureworkflow/Wandalen/wConsequence/StandardPush.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/StandardPush.yml:59: update your workflow using https://app.stepsecurity.io/secureworkflow/Wandalen/wConsequence/StandardPush.yml/master?enable=pin
- Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 3 third-party GitHubAction dependencies pinned
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
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'
Score
3.4
/10
Last Scanned on 2025-01-27
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