The MIT license, README, and package-to-repository match make the project transparent to inspect. No release or repository activity for more than seven years, plus no security scanning or policy, makes ongoing support uncertain.
42%
Total Score
50
80
50
The latest release was published more than seven years ago, with no releases in the last 12 months. The package has a substantial 24-release history, but the long current gap indicates likely abandonment.
The repository recorded no commits and no active maintainers in the last three months, consistent with the package's long release gap. This materially lowers confidence in ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. That is a maintenance and transparency gap for a package that remains available for dependency use.
The linked repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a modest transparency concern rather than evidence of a vulnerability.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
dibi/dibi Version >=3.0 | — | — |
nette/nette Version >=2.4 | — | — |
geniv/nette-locale Version >=2.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.