Package Health/kodansha/wack-cloudfront-invalidation

kodansha/wack-cloudfront-invalidation

Usable with caveats: it has clear ownership, licensing, tests, release notes, and a steady release history. However, the repository has had no commits or active maintainers in the last three months, and the project lacks a security policy and explicit workflow token permissions.

Latest v0.2.2

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers in the last three months. Although the release history is healthy, this recent inactivity lowers confidence in ongoing maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected, leaving a security-hygiene gap without making the package unfit to use.

Security policy

The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.

Token permissions

The single workflow has no top-level token permissions declaration. No write permissions were detected, but explicitly limiting permissions would provide stronger workflow hygiene.

Version stability

Version v0.2.2 is not a prerelease, but the package remains below major version 1, so compatibility expectations are less mature.