withinboredom/records

The small codebase is clearly documented, tested, MIT-licensed, and has no runtime dependencies or install scripts. Its young, single-maintainer project has had no releases in 12 months and no commits in three months, while security documentation is absent.

Latest v0.1.3

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the absence of releases during the last year and indicating stalled maintenance.

Release history

The package is 474 days old with four releases, but it has had zero releases in the last 12 months; the short release history limits evidence of ongoing maintenance.

Repository archived

The linked repository is not archived, although its last push was over a year ago; the active repository status provides some compensating evidence against abandonment.

Security policy

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities; this is a transparency gap for a library consumers may embed.

Version stability

The latest release is v0.1.3 and the project has not reached a stable major version, so compatibility and long-term API expectations remain less established.