laraveljutsu/bazooka

The package is small and understandable, with a clear README, tests, an MIT declaration, and a minimal runtime dependency. Its lack of a security policy adds a modest transparency concern alongside the inactive project.

Latest v1.0.15

Packagist

56%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual account rather than an organization, so there is no provided organizational backing to offset the thin maintenance evidence.

Release history

The package shipped 16 releases in a brief burst, then had no releases in the following 19 months. That long silence is a meaningful maintenance concern despite the initially active cadence.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, following a last push about 19 months ago. This indicates sustained inactivity and raises abandonment risk.

Repo tooling

Composer build tooling is present, but no security-scanning tooling was detected. The missing scanning is a modest process gap rather than evidence of unsafe code.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This reduces transparency for a package intended to run inside applications.