alchemy/ghostscript

Usable with caveats: the package is licensed, tested, documented, and backed by an organization, but its latest release was over eight years ago and recent repository activity is absent. Treat it as a mature, largely dormant dependency and verify compatibility before adopting it.

Latest 4.1.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has five releases since 2012, but its latest registry release was over eight years ago and it had no releases in the last 12 months. This is a meaningful maintenance concern despite its established history.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old latest release, this indicates a dormant project and raises the risk of slow fixes or compatibility updates.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while three issues and two pull requests remain open. This suggests limited current project responsiveness.

Repo tooling

Composer is used for builds, but no security-scanning tool is configured. The missing scanner is a modest transparency gap, not by itself evidence that the package is unsafe.

Security policy

The repository has no security policy. That weakens the project's documented vulnerability-reporting process, although it is less significant for this small, dormant library than the lack of recent maintenance.