cuyz/magic-constant

The small dependency footprint, MIT licensing, tests in the repository, and release notes make the package easy to assess. Recent commit and issue activity are quiet, while all four workflow actions are unpinned and no security policy or scanning is present.

Latest 2.3.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The source repository is owned by an individual account rather than an organization. This does not establish a problem, but it provides less visible institutional backing for long-term maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. With a release in the broader recent history, this indicates a slowdown rather than proven abandonment, but it lowers confidence in prompt maintenance.

Repo issue activity

There is one open issue and one open pull request, but no new or closed issues or merged pull requests in the last month. This suggests limited current project interaction and modestly raises maintenance risk.

Repo tooling

The repository uses Make and Composer, but no security scanning tools are present. The missing scanning is a hygiene weakness, not evidence that the package is unsafe by itself.

Security policy

The repository has no security policy. That leaves vulnerability-reporting expectations unclear and is a transparency gap for a dependency intended for application code.