r4nkt/laravel-dto-action

Release historydanger

Although the package has five releases over roughly six years, it has had no release in the last four years; the latest release was June 2022. That is a substantial maintenance and abandonment concern.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the four-year release gap and increasing abandonment risk.

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 repository has no security policy, leaving vulnerability reporting and disclosure guidance undocumented. This matters for a dependency but is not severe on its own.

Workflow auditcaution

Both workflows were analyzed successfully and have no untrusted triggers or script-injection findings, but all five action references are unpinned and the audit found a high-confidence unpinned container image. This is avoidable build-integrity hygiene risk.