npmpackage.info

Gathering detailed insights and metrics for call-me-maybe

call-me-maybe

Let your JS API users either give you a callback or receive a promise

1.0.2

MIT

JavaScript

2,101,237,057 2.7

Installations

npm install call-me-maybe

Pull Requests

Open

1

Total

10

Closed

8

Merged

1

Issues

Open

2

Total

5

Closed

3

Releases

v1.0.2

Published on 31 Oct 2022

v1.0.2-beta.1

Published on 31 Oct 2022

View all 2 releases

Developer

limulus

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

18.12.0

NPM Version

8.19.2 Statistics

39 Stars

25 Commits

4 Forks

3 Watching

3 Branches

2 Contributors

Updated on 29 Apr 2024

Languages

JavaScript (98.4%)

Shell (1.6%)

Total Downloads

Cumulative downloads

Total Downloads

2,101,237,057

Last day

-22.9%

1,152,037

Compared to previous day

Last week

-6.1%

7,551,821

Compared to previous week

Last month

7.2%

32,965,318

Compared to previous month

Last year

-15.3%

355,655,129

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

@commitlint/config-conventional browserify commitlint husky is-ci karma karma-browserify karma-browserstack-launcher karma-mocha mocha promise semantic-release

Versions

call-me-maybe

Let your JS API users either give you a callback or receive a promise.

Usage

1var maybe = require("call-me-maybe")
2
3module.exports = function asyncFunc (cb) {
4  return maybe(cb, new Promise(function(resolve, reject) {
5    // ...
6  }))
7}

API

maybe(cb, promise)

If the callback cb is truthy, returns undefined and will call cb when promise is settled. The parameters passed to cb are standard error-first:

If promise is fulfilled, then it is called with the result of the promise: cb(null, result)
If promise is rejected, then it is called with the rejection error: cb(err)

If cb is falsey, then promise is returned.

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

License

Determines if the project has defined a license.

3

Pinned-Dependencies

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

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

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

0

Token-Permissions

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

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.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

2.7

/10

Last Scanned on 2024-11-25

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