current-year

v1.1.12

Get the current year.

MIT
Latest version published 12 months ago
    npm install current-year
  

Package Health Score

56 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Limited

Weekly Downloads (21)

Download trend
Dependents
2
GitHub Stars
1
Forks
0
Contributors
1

Direct Usage Popularity

Uncommon

The npm package current-year receives a total of 21 downloads a week. As such, we scored current-year popularity level to be Limited.

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

04/2016
08/2020

Direct Vulnerabilities

1.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.1.12
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

1.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.1.12
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

1.0.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.1.12
  • 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 current-year 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 current-year
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
0
Open PR
0
Last Release
12 months ago
Last Commit
12 months ago

Further analysis of the maintenance status of current-year 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 current-year 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
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 56/100 package health 56/100

Package

Node.js Compatibility
not defined

Age
5 years
Dependencies
0 Direct
Versions
15
Install Size
6.79 kB
Dist-tags
1
# of Files
4
Maintainers
1
TS Typings
No

current-year 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.