ctwillie/laravel-usps

Release historydanger

Only two releases were published, both in November 2019, with no release in nearly seven years. This is strong evidence of abandonment risk despite the repository remaining available.

Repo commit activitydanger

There were no commits or active maintainers in the last three months, consistent with a repository that has been inactive for years. The absence of recent development materially raises abandonment risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tooling was detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This weakens project transparency for a package that makes API requests.

Version stabilitycaution

The latest release is still on the 0.1 line, indicating an immature API after years without further releases. That increases compatibility uncertainty for adopters.