ernestobaezf/laravel-apm

Release historydanger

Only two releases were published, both in September 2019, with no releases in the last 12 months. The long period without a release is strong evidence of abandonment risk.

Package scaffoldingcaution

A 2,505-character README is present, but its configuration and use-case sections still say “Coming,” and the repository reports no tests or changelog. Missing tests and changelog are normal for published artifacts, while the unfinished consumer documentation is a real integration gap.

Repo issue activitycaution

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is consistent with a dormant project, although it is weaker evidence than the stale release history.

Repo popularitycaution

The repository has zero stars and zero forks, with one watcher. Popularity is only supporting evidence, but these values provide no meaningful sign of community adoption or external maintenance.

Repo toolingcaution

Composer is used for builds, but no security-scanning tool is present. The missing scan is a hygiene gap rather than proof of unsafe code, but it reduces transparency for a package that has been inactive for years.