Package Health/dev-lnk/laravel-code-builder

dev-lnk/laravel-code-builder

Its README, tests, release notes, and clear MIT licensing make the package reasonably transparent to consumers. The lack of recent development, security scanning, and pinned workflow images leaves meaningful maintenance and build-integrity concerns.

Latest v1.2

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was about two years ago, and there were no releases in the last 12 months. The earlier 17-release history shows initial activity but does not offset the current pause.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with a project that has stopped receiving recent maintenance.

Repo tooling

Composer build tooling is present, but the repository reports no security scanning tools, leaving a meaningful security-process gap for a package that generates application code.

Security policy

The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.

Workflow audit

All four workflows were analyzed and had no untrusted checkouts or script injection, but all nine action references are unpinned and two high-confidence findings identify floating container images, including latest. This weakens build reproducibility and supply-chain hygiene.