cohensive/asset

Release historydanger

The package has five releases, but its latest release was over six years ago and it has had no releases in the last 12 months. That strongly raises abandonment risk for a framework integration package.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the stale registry release history, this is a meaningful maintenance concern.

Repo package mentioncaution

The repository name does not match the package name, although its README does mention the package. The README reference is reassuring, but the naming mismatch still leaves some uncertainty about repository ownership and publication provenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.

Security policycaution

The linked repository has no security policy. That weakens the project's disclosure and maintenance transparency, although it is less serious than the lack of recent releases and commits.