Risky to adopt: the latest release and repository activity are from February 2016, with no commits or active maintainers in the last three months. It has a clear MIT license, a useful README, and organization backing, but the long abandonment gap makes compatibility and support a liability.
38%
Total Score
50
100
69
50
The package has seven releases, but its latest release was about 10 years ago and it has had no releases in the last 12 months. That long release gap is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers during the last three months, reinforcing the release-history evidence that development has effectively stopped.
The package runs pre-install and post-create-project Composer scripts, so installation performs additional actions beyond dependency extraction. This is expected for a project template but still warrants review before automated installation.
Three registry publishing accounts are listed, but registry access does not demonstrate current maintenance activity. The organization-backed repository provides some ownership context, yet the activity signals show no recent work.
Composer build tooling is present, showing a defined packaging workflow. No security scanning tools are configured, which is a transparency and maintenance gap for a package with install-time scripts.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
sebastian/diff Version 1.4.* | — | — |
sebastian/version Version 1.0.* | — | — |
sebastian/exporter Version 1.2.* | — | — |
sebastian/comparator Version ^1.2 | — | — |
sebastian/environment Version 1.3.* | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.