Package Health/withinboredom/common-records

withinboredom/common-records

The project includes tests, clear documentation, a matching source repository, and a recent release note. Its single maintainer, stalled release and commit activity, and unpinned workflow actions add ongoing maintenance and build-integrity concerns.

Latest v0.2.0

Packagist

64%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry maintainer is responsible for publishing the package. The matching user-owned repository supports clear ownership, but the narrow maintainer base increases continuity risk.

Release history

The package has had three releases, but none in the last 12 months and its latest release was about 15 months ago. This is a meaningful maintenance concern, though the repository was pushed more recently.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, which weakens evidence of ongoing maintenance. The recent repository push provides limited compensation but does not show sustained activity.

Security policy

The linked repository has no security policy. This is a transparency gap, although the package has no reported workflow audit findings and uses Dependabot for scanning.

Workflow audit

The workflow is fully analyzed, uses read-only permissions, and has no reported audit findings, but all three action references are unpinned. That leaves avoidable build-integrity exposure.