stanbic/laravel-monitoring

Release historydanger

The package has only four releases, all concentrated in about 9 days, with no releases in the last 12 months and the latest release about 22 months ago. That long silence is a meaningful abandonment risk despite the stable version number.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap. This provides no evidence of ongoing maintenance capacity.

Licensecaution

No declared license or license file was found in the package or repository. That creates a real adoption and legal-transparency concern for an open-source dependency.

Package scaffoldingcaution

The published artifact has no README, so consumers receive no package-level usage guidance; the absence of tests and changelog in the artifact is normal packaging practice. A GitHub release exists for this version, which partly offsets the documentation gap but has no release notes excerpt.

Repo package mentioncaution

The linked repository is named "laravel-Package" rather than matching this package, and its README reference could not be confirmed. A name mismatch can be normal for a sub-package, but there is no provided evidence establishing that relationship here.