Installations

npm install wConsequence

Developer 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

Pull Requests

Open

0

Total

126

Closed

1

Merged

125

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Contributors

6

Unable to fetch Contributors

View all 6 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

Dependencies

5

wTools wProto wprocedure wCopyable wdeasync

Dev Dependencies

2

wTesting eslint

Optional Dependencies

1

wdeasync

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.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

SAST

Determines if the project uses static code analysis.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

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