fisharebest/ext-calendar

Recent repository activity is sparse, and all three GitHub Actions references are unpinned. Clear licensing, documented usage, repository tests, and a small dependency footprint reduce the concern.

Latest 2.6.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 19 releases since 2014, but none in the last 12 months and the latest registry release was in May 2022. This indicates stopped release maintenance, although the long history and short typical release interval show prior maturity.

Repo commit activity

The repository had zero commits and zero active maintainers in the last three months. Combined with no registry releases in the last 12 months, this points to limited current maintenance capacity.

Repo tooling

Composer is used as the build tool, but no security-scanning tool was detected. The missing scanning is a hygiene gap rather than evidence that the release is unsafe.

Security policy

The repository has no security policy. This weakens vulnerability-reporting transparency, though it is not by itself evidence of abandonment or a severe dependency risk.

Workflow audit

The single workflow was fully analyzed with no untrusted checkout, injection, or audit findings, and it avoids top-level write permissions. However, all three action references are unpinned, leaving a dependency-integrity hygiene gap.