vladshut/ecurring-api

Release historydanger

The last release was published in December 2019, and there have been no releases in the past 12 months. Eight releases show some initial development, but the long period of inactivity is a substantial abandonment concern.

Repo commit activitydanger

There were zero commits and zero active maintainers in the past three months, consistent with a project that has not been maintained since 2019. This materially increases the risk of unaddressed compatibility and maintenance problems.

Project backingcaution

The repository is owned by an individual account rather than an organization, so there is no organizational backing signal to compensate for the thin maintenance history.

Repo toolingcaution

The repository uses Composer and Make, but no security-scanning tools were detected. That is a modest transparency and maintenance gap, partly offset by the otherwise complete source and test layout.

Security policycaution

No security policy was found in the repository. For a client handling API credentials and payment-related data, the absence of a documented reporting path is a meaningful transparency gap.