Package Health

azartpay/azart-rpc-php

It includes a README, tests, an MIT license, and only two runtime dependencies. Those strengths improve transparency and adoption, but they do not offset the lack of recent maintenance for a library dependency.

Latest 2.0.3PackagistPackagist

38%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

0

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

63

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

75

Health Score Breakdown

Release historydanger

The package has had no release in about eight years, despite 15 total releases concentrated on June 5, 2018. Its stable 2.0.3 version is a modest positive, but the prolonged release gap signals abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the roughly eight-year pause in releases. No provided maintenance signal compensates for this lack of current activity.

Repo toolingcaution

Composer is used for the build, but no security-scanning tooling is present. That leaves a modest hygiene gap for a package that handles RPC connections.

Security policycaution

The repository has no security policy, which reduces transparency for reporting and handling vulnerabilities. This is a secondary concern compared with the maintenance gap.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Denis Paavilainen

Direct Dependencies

DependencyLast ReleaseScore
guzzlehttp/guzzle
Version ^6.2
—
—

Weekly Downloads

Info

Last Published
8 years ago
Created
9 years ago

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform