Package Health/dangermark/laravel-getresponse

dangermark/laravel-getresponse

The matching repository, MIT license, and small dependency surface support straightforward use. Documentation is present, but there is no security policy or test suite, leaving limited evidence for ongoing maintenance.

Latest 0.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published about 7 years ago, with none in the last 12 months. That is strong evidence of stagnation for a dependency intended to track a changing API.

Repo commit activity

The repository recorded no commits and no active maintainers in the last 3 months, while its last push was about 6 years ago. The non-archived status does not compensate for this prolonged inactivity.

Repo popularity

The repository has only 6 stars and 9 forks, indicating a small user base. Popularity is supporting evidence only and does not independently establish that the package is unsafe.

Repo tooling

Composer is used for builds, but no security scanning tooling is configured. The missing scanning is a modest transparency gap rather than evidence of an unsafe release.

Security policy

The repository has no security policy, so there is no stated process for reporting or handling vulnerabilities. This matters for a package that integrates with an external API.