majuto/laravel-jasper

The release is clearly licensed and includes a useful README, while the repository matches the package and has no install-time scripts. Its small dependency footprint is a modest positive, but the project lacks security-policy and automated security-scanning evidence.

Latest v0.1.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, both from April 2019, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency consumers may need to keep compatible.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.

Repo tooling

Composer is used for the build, but no security-scanning tools are present. That is a transparency and maintenance-hygiene gap, not a standalone reason to reject the package.

Security policy

The repository has no security policy. For a package handling configured service credentials, this weakens the project's disclosure and maintenance transparency.

Version stability

Version v0.1.1 is not a stable major release, which signals an immature API and adds compatibility risk even though it is not marked as a prerelease.