There is no security policy or automated security scanning, which weakens transparency for long-term maintenance. MIT licensing, a README, and repository tests make the code easier to evaluate, but do not offset the maintenance concern.
38%
Total Score
50
100
67
75
The package has had no release in more than 11 years; all nine releases occurred on the same day in 2015, indicating severe abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no work since 2015.
Composer build tooling is present, but no security scanning tools were detected, leaving a maintenance and transparency gap.
The repository is not archived, which preserves a path for future maintenance, but its last push was in 2015 and does not offset the inactivity evidence.
The repository has no security policy, leaving no documented process for receiving or disclosing vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/lexer Version 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.