visualpay/sdk

This is a well-scaffolded, licensed PHP SDK with tests, a changelog, a security policy, minimal runtime dependencies, no install-time lifecycle scripts, and a linked repository that is not archived. However, version 1.0.0 was released only recently, with just one release and no demonstrated maintenance history; the repository also has no observed popularity or issue activity. The single maintainer account, absent security-scanning tooling, and workflow without top-level token permissions add moderate transparency and operational concerns, but there is no evidence here of deprecation, dangerous workflow patterns, or repository/package disconnect. It is usable for adoption with normal dependency and release monitoring, but its long-term maintenance maturity is not yet established.

Latest 1.0.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

There is one registry publishing account. This is a modest resilience concern for an individually owned project, particularly because no broader organizational backing is shown.

Project backing

The repository is owned by a user account rather than an organization, and no registry namespace is provided. This supports a small-project interpretation and offers limited evidence of institutional backing.

Release history

The package is brand new: it has one release, was first published recently, and has no historical release cadence. This limits evidence of maintenance reliability and maturity.

Repo issue activity

There are no open issues or pull requests and no activity recorded in the last month. With a newly created project this may simply reflect limited exposure, but it provides no evidence of an active user or contributor community.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the absence of any adoption signal modestly reduces confidence in project maturity.