Clear licensing and a usable README help adoption, while the open issue backlog and absent security policy add maintenance uncertainty. Treat this as legacy code and plan to own fixes if you adopt it.
38%
Total Score
33
100
75
83
The package has had no releases in the last 12 months, and its latest release was about 12 years ago. This is strong evidence of abandonment despite five historical releases.
There were no commits and no active maintainers in the last three months, consistent with the repository having received no push for about eight years.
The package and repository are owned by the same individual account, showing consistent ownership but no organizational backing to compensate for the inactive maintenance record.
There are 19 open issues and one open pull request, with no new or closed issues or pull requests in the last month. This suggests unresolved maintenance demand.
Composer is used as a build tool, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nette/nette 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.