Its license and readable package documentation are in place, but the single publisher and absent security policy provide little resilience. The repository also shows no meaningful community activity or ownership confirmation.
38%
Total Score
50
70
75
Only one registry account has publishing access. This is a thin publishing base and leaves the release dependent on a single individual, with no provided evidence of broader backing.
The package has had no releases in over four years, with only three releases ever and none in the last 12 months. This is strong evidence of abandonment risk for a dependency.
The linked repository is named `local`, does not match the package name, and does not mention the package in its README. That weakens confidence that the source repository actually represents this release.
The repository has zero stars and forks and only one watcher. Popularity is not required for a healthy package, but these values provide no supporting evidence of active community use or review.
The linked repository has no security policy. For a testing framework distributed as a dependency, this reduces transparency around vulnerability reporting and maintenance practices.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
sebastian/diff Version ^4.0.3 | — | — |
sebastian/type Version ^3.0 | — | — |
phar-io/version Version ^3.0.2 | — | — |
phar-io/manifest Version ^2.0.3 | — | — |
phpspec/prophecy 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.