@timmalabs/fullcalendar

v4.3.1

Full-sized drag & drop event calendar

MIT
Latest version published 2 years ago
    npm install @timmalabs/fullcalendar
  

Package Health Score

66 / 100

Popularity

Small

Weekly Downloads (8)

Download trend
Dependents
0
GitHub Stars
14.21K
Forks
3.24K
Contributors
130

Direct Usage Popularity


The npm package @timmalabs/fullcalendar receives a total of 8 downloads a week. As such, we scored @timmalabs/fullcalendar popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @timmalabs/fullcalendar, we found that it has been starred 14,211 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

01/2020

Direct Vulnerabilities

Popular
4.3.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
4.3.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
4.3.1
  • 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 @timmalabs/fullcalendar 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 @timmalabs/fullcalendar
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
647
Open PR
16
Last Release
2 years ago
Last Commit
2 months ago

Further analysis of the maintenance status of @timmalabs/fullcalendar 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 @timmalabs/fullcalendar 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

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
130
Funding
No

A good and healthy external contribution signal for @timmalabs/fullcalendar project, which invites more than one hundred open source maintainers to collaborate on the repository.

We found a way for you to contribute to the project! Looks like @timmalabs/fullcalendar is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 66/100 package health 66/100

Package

Node.js Compatibility
not defined

Age
2 years
Dependencies
0 Direct
Versions
2
Install Size
2.46 MB
Dist-tags
1
# of Files
601
Maintainers
2
TS Typings
No

@timmalabs/fullcalendar 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.