royalcms/stack

The package is licensed, has a stable version, and avoids install-time scripts, but its documentation is minimal and the project has no security policy or automated security scanning. The repository and registry show no activity since September 2019, making abandonment the main concern.

Latest v5.0.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has had only one release, published in September 2019, with no releases in the last 12 months. That long period without a new release is strong evidence of abandonment risk.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with the old last push, this indicates the project is no longer actively maintained.

Package scaffolding

The artifact includes a README, but it is only 16 characters and provides little guidance for consumers. The absence of tests and a changelog in the published artifact is normal packaging practice and is not a gap.

Repo package mention

The repository name does not match the package name and its README does not mention the package. That weakens confidence that the linked repository is the package's maintained home.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest security-process gap that reinforces the limited maintenance evidence.