@fullcalendar/common vulnerabilities

internal package
Licenses: MIT

Package Health Score

61/100
  • securityNo known security issues
  • popularityInfluential project
  • maintenanceInactive
  • communitySustainable

Maintenance

INACTIVE

Commit Frequency

Loading chart...

Open Issues
1028
Open PR
50
New PRS
1
Last Release
2 years ago
Last Commit
3 months ago
Maintainers
1

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

Popularity

INFLUENTIAL PROJECT
Weekly downloads (198.6k)
GitHub Stars
20.1k
Forks
3.7k
Contributors
0

The npm package @fullcalendar/common receives a total of 198,620 downloads a week. As such, we scored @fullcalendar/common popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package @fullcalendar/common, we found that it has been starred 20,098 times.

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
Yes
Code of Conduct
No
Contributors
0
Funding
No
LICENSE
MIT

This project has seen only 10 or less contributors.

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

License

MIT>=0;

Direct Vulnerabilities

No direct vulnerabilities have been found for this package in Snyk’s vulnerability database. This does not include vulnerabilities belonging to this package’s dependencies.

Does your project rely on vulnerable package dependencies?

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities (in both your packages & their dependencies) and provides automated fixes for free.

Scan for indirect vulnerabilities

Security

NO KNOWN SECURITY ISSUES
Show only direct vulnerabilities in latest version

No vulnerabilities found in the latest version

No vulnerabilities found

Package versions

25 VERSIONS IN TOTAL See all versions
versionpublisheddirect vulnerabilities
6.0.0-beta.13 Aug, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
5.11.58 May, 2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
5.11.424 Jan, 2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
5.11.323 Aug, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
5.11.227 Jul, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
5.11.08 Apr, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
5.10.13 Nov, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
5.10.013 Oct, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
5.9.028 Jul, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
5.8.016 Jun, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

@fullcalendar/common dependencies

1 IN TOTAL

@fullcalendar/common development dependencies

1 IN TOTAL