hardimpactdev/craft-laravel

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no distinct replacement identified. Although the release history is active, package-level deprecation makes this release unsuitable for a new dependency.

Dangerous workflowscaution

One workflow uses pull_request_target and another uses workflow_run, both requiring careful trust-boundary handling. No untrusted checkout or script-injection patterns were detected, so the workflow risk is limited rather than severe.

Repo bus factorcaution

One contributor made all 16 commits in the last 3 months, leaving no demonstrated backup maintainer. This increases continuity risk for a user-owned project.

Repo package mentioncaution

The repository name does not match the package name, and its README does not mention the package. That raises a concrete concern that the published package may be associated with the wrong or repurposed repository.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, so this does not independently make the package unsafe, but it provides no additional evidence of community adoption.