phplrt/runtime
Its MIT licensing and focused dependency set make adoption straightforward. Organization backing helps, but the lack of tests, README, and security policy leaves maintenance evidence thin.
68%
Total Score
75
100
88
67
Health Score Breakdown
Only one registry account has publish access, which is a narrow publishing base; the organization-owned repository provides some compensating project backing.
Both the package artifact and linked repository expose only composer.json, leaving very little visible source or documentation and weakening transparency.
The missing tests and changelog are normal for a published artifact, but the absence of a README is a minor documentation gap for a runtime library.
All four recent commits came from one contributor, creating a meaningful continuity risk. Organization ownership partly compensates because maintenance can potentially be handed off.
Composer is used for builds, but no security scanning tools were detected, leaving security-maintenance practices less visible.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Kirill Nesmeyanov |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 phplrt/lexer Version ^4.1 | — | — |
phplrt/parser Version ^4.1 | — | — |
phplrt/source Version ^4.1 | — | — |
Weekly Downloads
Info
- Last Published
- 12 days ago
- Created
- 6 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.