stefanfroemken/essen

Release historydanger

The package has only one release, published about eight years ago, with no releases in the last 12 months. This strongly suggests abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since its only release.

Maintainerscaution

Only one registry maintainer is listed, so there is limited visible publishing redundancy. The linked repository is user-owned rather than organization-backed, which does not compensate for that thin base.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are reported. That weakens ongoing assurance for a package with no recent maintenance activity.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, though it is less severe than the maintenance inactivity.