monoland/monokit

Release historydanger

The package has only two releases, both about five years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a framework-style application dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the five-year release gap. No provided maintenance signal compensates for this inactivity.

Lifecycle scriptscaution

The package defines post-autoload-dump, post-create-project-cmd, and post-root-package-install scripts. Install-time execution increases review and trust requirements, especially for a stale package.

Package scaffoldingcaution

A 3,810-character README and GitHub release are positive transparency signals, but the README is generic Laravel template material and does not document this package specifically. Missing tests and a changelog are normal for a published artifact and are not counted against it.

Repo package mentioncaution

The repository name matches the package, but its README does not mention the package. The matching name is reassuring, while the missing package reference leaves some provenance ambiguity.