The artifact is licensed, documented, and includes tests. However, the linked project has had no commits for over a year, while its 613 releases were published within seconds and none appeared in the last 12 months; pinning this fork is risky.
38%
Total Score
25
78
83
The package is 603 days old, yet all 613 releases appear concentrated within seconds and there were no releases in the last 12 months. This unusual history and current release silence materially weaken confidence in ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, indicating no observed recent development. The repository is not archived, but that does not compensate for the complete lack of recent activity.
The package is published under a user namespace and the linked repository is owned by a user account, with no organization backing shown. That leaves a thin ownership structure for a core testing dependency.
The linked repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no independent sign of an established or actively adopted project.
Composer and Phing provide build tooling, but no security-scanning tools were detected. This is a modest transparency gap, partially offset by the repository's tests and security policy.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
sebastian/diff Version ^6.0.2 | — | — |
sebastian/type Version ^5.1.0 | — | — |
phar-io/version Version ^3.2.1 | — | — |
phar-io/manifest Version ^2.0.4 | — | — |
myclabs/deep-copy Version ^1.12.1 | — | — |
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.