priskz/sorad-entity

Release historydanger

The package has only one release, 0.1.0, published about eight years ago, with no releases in the last 12 months. This is strong evidence of stagnation for a library dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old release history, this materially increases abandonment risk.

Dependency profilecaution

Five runtime dependencies, including several related packages, create meaningful transitive maintenance exposure for a small, old package. No development dependencies are declared, so the profile does not show a broader project toolchain.

Maintainerscaution

One registry maintainer is consistent with a small personal project, but it provides little redundancy if that maintainer stops responding.

Project backingcaution

The registry namespace and repository are owned by the same individual account. This confirms consistent ownership but does not provide organizational backing or maintainer redundancy.