alarm

v2.0.0

Set an alarm that will call the given function at the specified time.

MIT
Latest version published 4 years ago
    npm install alarm
  

Package Health Score

49 / 100

Popularity

Limited

Weekly Downloads (11)

Download trend
Dependents
0
GitHub Stars
10
Forks
0
Contributors
1

Direct Usage Popularity


The npm package alarm receives a total of 11 downloads a week. As such, we scored alarm popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package alarm, we found that it has been starred 10 times, and that 0 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

12/2015
05/2017

Direct Vulnerabilities

1.0.2
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
2.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

1.0.2
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
2.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

1.0.2
  • 0
    H
  • 0
    M
  • 0
    L
Popular
2.0.0
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like alarm 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 alarm
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
0
Last Release
4 years ago
Last Commit
4 years ago

Further analysis of the maintenance status of alarm 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 alarm 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
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
1
Funding
Yes

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 49/100 package health 49/100

Package

Node.js Compatibility
>=0.10.0

Age
6 years
Dependencies
0 Direct
Versions
5
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

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