The README is clear and the dependency set is small, but the project has no tests or security policy. Its private-beta warning and nearly eight years without maintenance make adoption a liability.
38%
Total Score
25
100
79
75
Only two releases exist, with none in the last 12 months; the latest was published nearly eight years ago. This is strong evidence of abandonment despite the package not being registry-deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the nearly eight-year gap since its last push.
The registry lists one maintainer, which creates a thin publishing base. The linked repository is user-owned rather than organization-backed, so there is little provided evidence of broader maintenance capacity.
Composer is used for the build, but no security-scanning tools are present. The missing scanning reduces maintenance assurance but does not by itself indicate the package is unsafe.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency and maintenance weakness, though it is less significant than the lack of recent development.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
envms/fluentpdo Version ^1.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.