The package has a matching repository, MIT licensing, tests, and release notes for this version. A single publishing maintainer, no security scanning, and no recent commits reduce confidence that issues will be handled promptly.
68%
Total Score
67
100
79
75
Only one account has registry publishing access, which creates a thin publishing base. Repository ownership by an organization provides some backing, but does not demonstrate active maintenance by itself.
The package has six releases, but its latest registry release was about 18 months ago and there were no releases in the last 12 months. This indicates slowing maintenance, although the project is not abandoned based on the repository push activity.
There were no commits and no active maintainers in the last 3 months. The recent repository push is reassuring, but the current short-term activity is still absent.
The repository uses Composer build tooling, but no security-scanning tools were detected. That is a maintenance and transparency gap rather than evidence of unsafe code.
The repository has no security policy. This makes vulnerability reporting and coordinated fixes less clear for a package that modifies vendor runtime behavior.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nikic/php-parser Version ^5.0 | — | — |
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.