phaseo/sdk

Usable with caveats: the SDK is actively developed and well documented, but it is only 53 days old and all 77 recent commits come from one contributor. The repository also has no security scanning or security policy, so evaluate updates carefully before relying on it in a critical integration.

Latest v3.0.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 53 days old with two releases and a median release interval of about 53 days, so its maintenance track record is still limited. The latest release was published recently, which provides some evidence of ongoing activity.

Repo bus factor

One contributor made 100% of the 77 commits in the last three months, creating a significant single-person continuity risk. The organization-owned repository provides some backing, but no second active contributor is shown.

Repo commit activity

The repository recorded 77 commits in the last three months, showing strong recent activity. However, only one maintainer made those commits, so the activity does not demonstrate broad maintenance capacity.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured. The build setup is appropriate, while the missing security automation is a transparency and maintenance gap.

Security policy

The repository has no security policy, leaving vulnerability reporting and handling expectations undocumented. This is a real concern for an SDK that connects applications to a gateway.