zao-web/qbo-connect

The package has a clear license, a usable README, and organization backing, but it lacks tests and security scanning. Its small project footprint does not offset the prolonged inactivity, so pinning this release carries substantial maintenance risk.

Latest v0.1.3

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in November 2017, with no releases in the last 12 months and only three releases overall. Nearly nine years without a release is strong evidence of abandonment for a library dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. This materially raises the risk that compatibility and defects will not be addressed.

Package scaffolding

The artifact includes a README, which helps consumers, while the absence of tests and a changelog is normal for a published package and is not itself a gap under the packaging rules. Repository-level tests and changelog are also absent, leaving little visible maintenance evidence beyond the README.

Repo tooling

Composer is used for builds, but no security scanning tools are present in the repository. That is a maintenance and transparency gap, though it is less significant than the prolonged inactivity.

Security policy

The repository has no security policy, so users have no documented channel or process for reporting vulnerabilities. This adds a transparency concern for a package handling OAuth connections.