aspose/slides-sdk-php

A clear README, tests, MIT licensing, and an organization-backed repository improve adoption confidence. The main concern is no repository commits or active maintainers in the last three months, while no security scanning or policy leaves transparency weaker.

Latest 26.6

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months. Despite recent registry releases, this lack of observed source activity raises maintenance and abandonment concern.

Repo popularity

The repository has 2 stars, 3 forks, and 1 watcher. This is limited community evidence, but popularity is only supporting evidence and the organization backing and release history partly compensate.

Repo tooling

The repository uses Composer for builds, but no security-scanning tools were detected. The missing scanning coverage weakens development transparency without proving that the package is unsafe.

Security policy

The repository has no security policy. For a cloud API SDK, this leaves vulnerability reporting and response expectations undocumented, creating a modest transparency gap.

Workflow audit

No GitHub Actions workflows were analyzed, with 0 workflows total and no failed files. This provides no workflow risk evidence, but it also offers no evidence of automated build or release controls.