loop-timer

v1.0.6

模拟 linux Crontab 的 js 定时任务,可以指定时间来执行任务,由于 JS 是单线程,所以如果指定的任务是个大计算量的任务,有可能会导致其他任务被延时执行,如果对时间准确性要求很高的,请慎用. 项目里面同时只会存在一个计时器, 如果有没有可以执行事件的时候,计时器将会被销毁,有新的可执行事件才会再次开启新的计时器. For more information about how to use this package see README

Latest version published 4 years ago
License: ISC

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

42 / 100

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
1.0.6 | 04/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
ISC
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

Limited

Weekly Downloads (0)

Download trend
GitHub Stars
1
Forks
0
Contributors
1

Direct Usage Popularity


The npm package loop-timer receives a total of 0 downloads a week. As such, we scored loop-timer popularity level to be Limited.

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

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 42/100 package health 42/100

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 loop-timer 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 loop-timer 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
4 years
Dependencies
0 Direct
Versions
7
Install Size
21 kB
Dist-tags
1
# of Files
8
Maintainers
1
TS Typings
No

loop-timer 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.