teamwork

v3.2.0

Wait for multiple callback For more information about how to use this package see README

Latest version published 6 years ago
License: BSD-3-Clause

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

50 / 100

Explore Similar Packages

Security

No known security issues
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
3.2.0 | 03/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.1.0 | 03/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.0.3 | 11/2018
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.1.0 | 09/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.1.2 | 12/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
BSD-3-Clause
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.

Get started free

Popularity

Recognized

Weekly Downloads (18,502)

Download trend
GitHub Stars
14
Forks
13
Contributors
6

Direct Usage Popularity

Uncommon

The npm package teamwork receives a total of 18,502 downloads a week. As such, we scored teamwork popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package teamwork, we found that it has been starred 14 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
Yes
Contributors
6
Funding
No

This project has seen only 10 or less contributors.


Embed Package Health Score Badge

package health: 50/100 package health 50/100

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
0
Open PR
0
Last Release
6 years ago
Last Commit
30 days ago

Further analysis of the maintenance status of teamwork 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 teamwork 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
9 years
Dependencies
0 Direct
Versions
20
Install Size
4.74 kB
Dist-tags
1
# of Files
6
Maintainers
5
TS Typings
Yes

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