juniwalk/orm

This release appears generally suitable to depend on: it is a mature MIT-licensed package with 118 releases over roughly 3.8 years, 12 releases in the last 12 months, a stable major version, tests, a complete source tree, and no registry deprecation or install-time lifecycle scripts. The main reservations are that repository commit activity reports no commits or active maintainers in the last 3 months, the repository has no security scanning or security policy, and publishing access is held by one maintainer. Those concerns are partly offset by the very recent repository push and release, frequent release history, and a repository that clearly matches and documents the package, but the lack of recent observed commit activity warrants continued maintenance scrutiny.

Latest v3.2.7

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, creating concentration risk, although registry access records publishing authority rather than actual maintenance activity.

Project backing

The repository is owned by a user account rather than an organization, so there is no organizational backing signal to offset the thin maintainer base.

Repo commit activity

The repository reports zero commits and zero active maintainers in the last 3 months, a concrete concern about recent development activity. The very recent push and frequent release history provide partial counterevidence but do not fully remove the maintenance uncertainty.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month; this is neutral to mildly cautionary because it may reflect either stability or limited community engagement.

Repo popularity

The repository has zero stars and forks and one watcher. Low popularity is supporting evidence of limited external adoption, but it is not by itself evidence that a small package is unhealthy.