dmk/mk30xlegacy

The source repository has tests, a clear README, and organizational ownership. Its only release was over three years ago, recent commit activity is absent, and all 10 workflow actions are unpinned, so future compatibility and build integrity need attention.

Latest 1.0.0

Packagist

62%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's only release, published over three years ago, with no releases in the last 12 months. That makes current compatibility and maintenance uncertain despite the repository remaining available.

Repo commit activity

There were no commits and no active maintainers in the last three months. This weakens evidence of ongoing development, although the repository's recent push shows it has not been abandoned outright.

Repo tooling

The project uses Composer, but no security-scanning tools were detected. For a small PHP extension this is a hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy, reducing transparency about vulnerability reporting and maintenance expectations. Organizational backing partly offsets this, but does not replace a documented process.

Workflow audit

The workflow audit completed successfully and found no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all 10 analyzed action references are unpinned, leaving the build exposed to upstream action changes.