apen/recordsmanager

The project has a clear license, useful documentation, and a source repository that matches the package. It lacks a security policy and pins neither of its two workflow actions, adding maintenance and build-transparency concerns.

Latest 1.7.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual user rather than an organization, so the project appears to rely on a narrow personal ownership base.

Release history

The package has existed for about 7 years and has 17 releases, but it has had no release in the past 12 months, indicating a meaningful slowdown in maintenance.

Repo commit activity

There were no commits and no active maintainers in the past 3 months. Combined with the absence of releases in the past year, this raises abandonment risk.

Security policy

The repository has no security policy, leaving users without a documented route for reporting vulnerabilities or understanding security handling.

Workflow audit

The single workflow was fully analyzed with no dangerous triggers or audit findings, but both of its two action references are unpinned. That weakens build reproducibility and action-update control.