signals

v1.0.0

Custom Event/Messaging System

Unknown
Latest version published 9 years ago
    npm install signals
  

Package Health Score

50 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Recognized
Download trend

Weekly Downloads (23,556)

Dependents
182
GitHub Stars
1.88K
Forks
191
Contributors
4

The npm package signals receives a total of 23,556 downloads a week. As such, we scored signals popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package signals, we found that it has been starred 1,883 times, and that 182 other projects in the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

07/2011
02/2012
07/2012
10/2012
11/2012

Direct Vulnerabilities

0.6.3
  • 0
    H
  • 0
    M
  • 0
    L
0.7.4
  • 0
    H
  • 0
    M
  • 0
    L
0.8.1
  • 0
    H
  • 0
    M
  • 0
    L
0.9.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.0.0
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.6.3
  • 0
    H
  • 0
    M
  • 0
    L
0.7.4
  • 0
    H
  • 0
    M
  • 0
    L
0.8.1
  • 0
    H
  • 0
    M
  • 0
    L
0.9.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.0.0
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

0.6.3
  • 0
    H
  • 0
    M
  • 0
    L
0.7.4
  • 0
    H
  • 0
    M
  • 0
    L
0.8.1
  • 0
    H
  • 0
    M
  • 0
    L
0.9.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.0.0
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
Unknown
Alert

Unable to detect license

We couldn’t find an appropriate license for this project. It is highly advised to make sure the project license is compatible with your business needs before including it as a dependency, to keep yourself protected from infringement suits or loss of your own code.


Security Policy
No

We found a way for you to contribute to the project! Looks like signals is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test signals
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
10
Open PR
6
Last Release
9 years ago
Last Commit
8 years ago

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

Community

Limited
Readme.md
No
Contributing.md
No
Code of Conduct
No
Contributors
4
Funding
No

This project has seen only 10 or less contributors.

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

How about a good first contribution to this project? It seems that signals is missing a LICENSE file.

How about a good first contribution to this project? It seems that signals is missing a README file.


Embed Package Health Score Badge

package health: 50/100 package health 50/100

Package

Node.js Compatibility
not defined

Age
10 years
Dependencies
0 Direct
Versions
12
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
Yes

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