The MIT license, matching repository, and usable README make its contents easy to inspect and integrate. A single maintainer, no security policy, and no security scanning reduce confidence in future fixes.
43%
Total Score
25
75
75
The package has had no release in more than eight years, with zero releases in the last 12 months. Its seven historical releases show it was once active, but do not compensate for the prolonged gap.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating little current capacity for fixes.
Only one registry maintainer is listed, which creates a thin publishing base for a project with no recent activity. The repository is user-owned rather than organization-backed, so there is no visible operational redundancy.
Composer is used as the build tool, but no security-scanning tooling is present. That reduces ongoing assurance for dependency and release hygiene.
The repository has no security policy, leaving no documented route or process for reporting vulnerabilities. This is a transparency gap, though it is less serious than the absence of recent maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
dibi/dibi Version >=3.0.0 | — | — |
nette/nette Version >=2.4.0 | — | — |
geniv/nette-locale Version >=1.0.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.