strongbond/pdf-filler-laravel

Release historydanger

Only two releases were published, both around four years ago, with no release in the past 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. No provided signal shows current maintenance capacity.

Repo package mentioncaution

The repository name does not match the package and its README does not mention the package, so the linked source may not clearly belong to this release. That weakens transparency even though a name mismatch can occur with subpackages.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The lack of scanning modestly reduces maintenance transparency.

Security policycaution

The repository has no security policy, reducing the project's documented process for receiving and handling vulnerability reports. This is a secondary hygiene concern rather than evidence that the package is unsafe.