signals

v1.0.0

Custom Event/Messaging System

Unknown
Latest version published 10 years ago
    npm install signals
  
We couldn't find any similar packages Browse all packages

Package Health Score

50 / 100

Security

No known security issues
Powered by Snyk
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
1.0.0 | 11/2012
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.9.0 | 10/2012
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.8.1 | 07/2012
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.7.4 | 02/2012
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.6.3 | 07/2011
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
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

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test signals
Get started free

Popularity

Recognized

Weekly Downloads (30,759)

Download trend
Dependents
182
GitHub Stars
1.91K
Forks
190
Contributors
4

Direct Usage Popularity

TOP 30%

The npm package signals receives a total of 30,759 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,913 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.

Community

Limited
Readme.md
Yes
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.


Embed Package Health Score Badge

package health: 50/100 package health 50/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
10
Open PR
7
Last Release
10 years ago
Last Commit
9 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.

Package

Node.js Compatibility
not defined

Age
11 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.