reyesoft/crypto-qr

The repository has had no commits in the last three months, and its releases are widely spaced. It remains clearly maintained enough to have current source, tests, licensing, and a recent stable release, but missing security policy and unpinned workflow actions reduce confidence.

Latest 2.1.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The project has existed for about 8 years and released once in the last 12 months, but its median release interval is about 18 months, indicating a slow maintenance cadence.

Repo commit activity

There were no commits and no active maintainers in the last three months. Although the latest release is relatively recent, the lack of recent development is a maintenance concern.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.

Workflow audit

The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all three action references are unpinned, which weakens build reproducibility.