pikaday-time

v1.6.1

Time support added to pikaday For more information about how to use this package see README

Latest version published 5 years ago
License: (0BSD OR MIT)

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

51 / 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.6.1 | 08/2017
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.5.1 | 12/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.4.1 | 06/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3.3 | 03/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
(0BSD OR MIT)
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

Small

Weekly Downloads (1,973)

Download trend
Dependents
0
GitHub Stars
152
Forks
76
Contributors
60

Direct Usage Popularity


The npm package pikaday-time receives a total of 1,973 downloads a week. As such, we scored pikaday-time popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package pikaday-time, we found that it has been starred 152 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.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
60
Funding
No

With more than 10 contributors for the pikaday-time repository, this is possibly a sign for a growing and inviting community.

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


Embed Package Health Score Badge

package health: 51/100 package health 51/100

Maintenance

Inactive

Commit Frequency

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

Further analysis of the maintenance status of pikaday-time 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 pikaday-time 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
8 years
Dependencies
1 Direct
Versions
7
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
Yes

pikaday-time 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.