digicademy/cobj_xslt

The package is clearly documented and licensed, with a matching organization-owned repository and release notes for this version. Its long publication gap, inactive commits, and lack of security policy or scanning reduce confidence in long-term support.

Latest 1.10.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published more than four years ago, with no releases in the last 12 months. This is meaningful abandonment risk for a dependency, despite the four-release history showing the project was previously maintained.

Repo commit activity

The repository had no commits and no active maintainers in the last three months. Combined with the old latest release, this materially lowers confidence in ongoing maintenance.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. This is a transparency and maintenance weakness, not evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The clear README and release history provide some transparency but do not replace that process.

Workflow audit

No GitHub Actions workflows were present, so there were no workflow triggers, unpinned actions, or dangerous audit findings to weigh. This leaves CI and release automation coverage unknown rather than indicating a clean build process.