Package Health/groupdocscloud/groupdocs-editor-cloud

groupdocscloud/groupdocs-editor-cloud

The MIT license, tests, and clear package README support adoption. Security policy and automated scanning are absent, leaving less transparency around ongoing maintenance.

Latest 25.7

Packagist

60%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has six releases over about 6 years and none in the last 12 months, with a median interval of about 363 days. This indicates slow maintenance and lowers confidence in timely fixes.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. Combined with no registry releases in the last 12 months, this is meaningful evidence of slowed maintenance.

Repo issue activity

There were no new or closed issues in the last month and two open pull requests remain, suggesting limited recent project activity. This is a supporting maintenance concern rather than evidence of abandonment on its own.

Repo tooling

The repository uses Composer but reports no security scanning tools. The missing automated scanning reduces supply-chain transparency, though it does not by itself indicate an unsafe release.

Security policy

The repository has no security policy. That leaves vulnerability reporting and response expectations unclear for a cloud SDK, which modestly lowers project transparency.