signals

v1.0.0

Custom Event/Messaging System

MIT
Latest version published almost 8 years ago
    npm install signals
  

Explore Similar Packages

Package Health Score

54 / 100
  • Popularity
    Recognized
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Sustainable

Popularity

Recognized
Weekly Downloads (15,634)
Dependents
182
GitHub Stars
1.87K
Forks
190
Contributors
4

The npm package signals receives a total of 15,634 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,866 times, and that 182 other projects on 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

Security and license risk for recent versions


Direct Vulnerabilities

0.7.4
0.8.0
0.8.1
0.9.0
1.0.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.7.4
0.8.0
0.8.1
0.9.0
1.0.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.7.4
0.8.0
0.8.1
0.9.0
1.0.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Security Policy
No
All security vulnerabilities belong to production dependencies of direct and indirect packages.

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

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

    # Install the Snyk CLI and test your project
npm i snyk && snyk test signals
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
10
Merged PR
4
Open PR
6
Last Commit
7 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.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
4
Funding
No
License
MIT

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.

Package

Node.js Compatibility
not defined

Age
9 years
Dependencies
0 Direct / 0 Total
Versions
5
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.