Package Health

bushlanov-dev/max-bot-api-client-php

This is a generally healthy and actively maintained release: it has 33 releases over 411 days, 17 releases in the last 12 months, a stable non-prerelease version, a non-deprecated registry status, recent repository activity, four active contributors, a matching and package-referencing repository, and a substantial documented source tree. The main concerns are that the project is ultimately maintained by one registry publisher, commit activity is concentrated in one contributor, and the repository lacks a security policy and explicit GitHub Actions token permissions; these are meaningful hygiene and continuity gaps but are not severe enough to outweigh the strong release and maintenance evidence.

Latest 1.6.7PackagistPackagist

82%

Total Score

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

70

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

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

94

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

80

Health Score Breakdown

Maintainerscaution

Only one account has registry publish access, which creates some publishing continuity risk. However, registry access records do not establish actual maintenance capacity, and repository activity provides stronger evidence that the project is currently maintained.

Project backingcaution

The repository is owned by a user account rather than an organization, so there is no organizational backing to offset the concentrated contributor and single-publisher risks.

Repo bus factorcaution

Four contributors were active, but the leading contributor made 8 of 11 commits (about 73%), leaving a concentrated maintenance burden. The presence of three additional contributors reduces but does not eliminate this continuity concern.

Repo toolingcaution

The repository uses Composer build tooling, but no security scanning tools were detected. The absence of scanning is a security-process gap, though it does not by itself indicate poor package maintenance.

Security policycaution

No SECURITY.md or other repository security policy was found, limiting transparency about vulnerability reporting and response procedures.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Aleksandr Bushlanov

Direct Dependencies

DependencyLast ReleaseScore
psr/log
Version ^1.1||^2.0||^3.0
guzzlehttp/psr7
Version ^1.8||^2.0
psr/http-client
Version ^1.0
psr/http-factory
Version ^1.0
psr/http-message
Version ^1.0||^2.0

Weekly Downloads

Info

Last Published
11 days ago
Created
1 year 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