zfr/zfr-stripe

MIT licensing, tests, release notes, and a small dependency set make the code easier to assess. There is no security policy or repository security scanning, increasing the maintenance concern.

Latest v3.5.2

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 73 releases since December 2013, but its latest release was in January 2016 and it had no releases in the last 12 months. This long publication gap is a major abandonment concern.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months, consistent with the package's long release hiatus. The repository is not archived, but there is no recent activity to offset the concern.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while 8 issues and 1 pull request remain open. This suggests the project is not actively being maintained.

Repo tooling

Composer is used for builds, but no security scanning tools are configured in the repository. The missing scanning is a maintenance and transparency gap, though not severe by itself.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap for a payment API client.